Is my EMMC dead?

Omnia hardware Omnia HW problems
1

Hi,
my Omnia router is not booting, booting from usb rescue while serial is connected results in this:

Searching for medkit
[    9.831442] scsi 0:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[    9.839973] sd 0:0:0:0: [sda] 131072000 512-byte logical blocks: (67.1 GB/62.5 GiB)
[    9.847761] sd 0:0:0:0: [sda] Write Protect is off
[    9.852683] sd 0:0:0:0: [sda] No Caching mode page found
[    9.858008] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    9.915222]  sda: sda1
[    9.918235] sd 0:0:0:0: [sda] Attached SCSI removable disk
mount: mounting /dev/mmcblk1p1 on /mnt/src failed: No such device or address
mount: mounting /dev/sda on /mnt/src failed: Invalid argument
[   10.155746] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Trying device /dev/sda1
ls: medkit-omnia.tar.gz: No such file or directory
ls: medkit-omnia-*.tar.gz: No such file or directory
Found omnia-medkit-latest.tar.gz on device /dev/sda1
Nothing wrong with it
1
And its our newest one!
[   10.846381] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Repartitioning the drive...
Debug info:
fdisk: can't open '/dev/mmcblk0'
Partitioning drive failed

it seems as though the system doesn’t see the emmc device, is the emmc dead?

Regards

2

CC: @Stepan there is the same ticket in our support queue. Can you take a look?

3

Hello,
can you break the bootloader and send us the result of command mmc info and mmc part please?
Like this…

U-Boot 2021.10-rc3-00044-gbc930e94463f (Sep 08 2021 - 12:35:49 +0200)

SoC:   MV88F6820-A0 at 1600 MHz
DRAM:  1 GiB (800 MHz, 32-bit, 2T, ECC not enabled)
Disabling MCU watchdog... disabled
WDT:   Started with servicing (60s timeout)
MMC:   mv_sdh: 0
Loading Environment from SPIFlash... SF: Detected s25fl164k with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: Turris Omnia
Turris Omnia:
  RAM size: 1024 MiB
  Serial Number: 0000000ABCDEFEDC
Regdomain set to **
Net:   eth0: ethernet@70000, eth1: ethernet@30000, eth2: ethernet@34000
Hit any key to stop autoboot:  0 
=> mmc info
Device: mv_sdh
Manufacturer ID: 90
OEM: 14a
Name: H8G4a 
Bus Speed: 52000000
Mode: MMC High Speed (52MHz)
Rd Block Len: 512
MMC version 5.1
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 4 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
=> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     16              15269872        263fdf1c-01     83
=>
4 
U-Boot 2019.07 (Oct 08 2019 - 23:24:25 +0000), Build: jenkins-turris-os-packages-kittens-omnia-917

SoC:   MV88F6820-A0 at 1600 MHz
DRAM:  2 GiB (800 MHz, 32-bit, 2T, ECC not enabled)
Disabling MCU watchdog... disabled
WDT:   Started with servicing (60s timeout)
MMC:   mv_sdh: 0
Loading Environment from SPI Flash... SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: Turris Omnia
Turris Omnia:
  RAM size: 2048 MiB
  Serial Number: 0000000E00005421
Regdomain set to **
Net:   eth0: ethernet@70000, eth1: ethernet@30000, eth2: ethernet@34000
Hit any key to stop autoboot:  0 
=> 
=> 
=> mmc info
Device: mv_sdh
Manufacturer ID: 5a
OEM: 5a00
Name: Bus Speed: 97751
Mode: MMC legacy
Rd Block Len: 1
MMC version 1.2
High Capacity: No
Capacity: 4 Bytes
Bus Width: 1-bit
Erase Group Size: 512 Bytes
=> mmc part
## Unknown partition table type 0
1 Like
5

Any update on this problem ?

6

Really !!! no support in here or the support email?

7

As far as I know @moham96, our colleagues from Support were helping You via email.

8

Nope, i just received an email after my last replay to this topic

9

I see. My apologies. Our support had a lot of work due to the automatic migration from Turris OS 3.x that is happening simultaneously.