Hello guys.
Dude 6.45.8 with dude running on an Hex G3 with external 4Gb SD card from Kingston.
It worked perfectly for a lot of time but one day it failed.
Dude was unavaiable, I was unable to access the dude disk.
I removed the SD card and installed on an Intel NUC running Debian 9.
I tried to mount it, no avail.
Here are the operations I tried to recover it.
root@nvr:/home/elia# dmesg|tail
[ 3.598093] input: HDA Intel PCH Headphone Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 3.598220] input: HDA Intel PCH Front Headphone Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 3.598353] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 8.733796] r8169 0000:03:00.0 enp3s0: link up
[ 8.733810] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 20.716486] random: crng init done
[ 20.716490] random: 7 urandom warning(s) missed due to ratelimiting
[ 145.196356] mmc0: new ultra high speed SDR104 SDXC card at address aaaa
[ 145.208168] mmcblk0: mmc0:aaaa ACLCE 59.5 GiB
[ 145.213683] mmcblk0: p1
root@nvr:/home/elia# fdisk -l
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1dc467e9
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 226213887 226211840 107.9G 83 Linux
/dev/sda2 226215934 234440703 8224770 3.9G 5 Extended
/dev/sda5 226215936 234440703 8224768 3.9G 82 Linux swap / Solaris
Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 1 124735487 124735487 59.5G 83 Linux
root@nvr:/home/elia# ^C
root@nvr:/home/elia# /
bash: /: Is a directory
root@nvr:/home/elia# mkdir /mnt/mmcblk0p1
root@nvr:/home/elia# mount /dev/mmcblk0p1 /mnt/mmcblk0p1
mount: /dev/mmcblk0p1: can't read superblock
root@nvr:/home/elia# ls /mnt/mmcblk0p1
root@nvr:/home/elia# fdisk -l
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1dc467e9
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 226213887 226211840 107.9G 83 Linux
/dev/sda2 226215934 234440703 8224770 3.9G 5 Extended
/dev/sda5 226215936 234440703 8224768 3.9G 82 Linux swap / Solaris
Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 1 124735487 124735487 59.5G 83 Linux
root@nvr:/home/elia# fsck -y /dev/mmcblk0
mmcblk0 mmcblk0p1
root@nvr:/home/elia# fsck -y /dev/mmcblk0
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a dos partition table in /dev/mmcblk0
root@nvr:/home/elia# fsck -y /dev/mmcblk0
mmcblk0 mmcblk0p1
root@nvr:/home/elia# fsck -y /dev/mmcblk0
mmcblk0 mmcblk0p1
root@nvr:/home/elia# fsck -y /dev/mmcblk0
mmcblk0 mmcblk0p1
root@nvr:/home/elia# fsck -y /dev/mmcblk0p1
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
/dev/mmcblk0p1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext3: Unknown code ____ 251 while recovering journal of /dev/mmcblk0p1
fsck.ext3: unable to set superblock flags on /dev/mmcblk0p1
/dev/mmcblk0p1: ********** WARNING: Filesystem still has errors **********
root@nvr:/home/elia# mkdir /mnt/mmcblk0p1
mkdir: cannot create directory ‘/mnt/mmcblk0p1’: File exists
root@nvr:/home/elia# mount /dev/mmcblk0p1 /mnt/mmcblk0p1
mount: /dev/mmcblk0p1: can't read superblock
root@nvr:/home/elia# ls /mnt/mmcblk0p1
root@nvr:/home/elia# mount /dev/mmcblk0p1 /mnt/mmcblk0p1
mount: /dev/mmcblk0p1: can't read superblock
root@nvr:/home/elia# fsck -y /dev/mmcblk0p1
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
/dev/mmcblk0p1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext3: Unknown code ____ 251 while recovering journal of /dev/mmcblk0p1
fsck.ext3: unable to set superblock flags on /dev/mmcblk0p1
/dev/mmcblk0p1: ********** WARNING: Filesystem still has errors **********
--------------------------
Someone has hits?