Hi!
After my NAS (QNAP TS109 with embedded Linux) behaved a bit strange, I
removed the hard disk (Seagate 500GB) and made a 1:1 image of the whole
drive with dd_rescue on my desktop. I worked on the image from here on
forward. The kernel version of the QNAP TS109 is at least 2.6.12.6-arm1
probably something newer.
The disk is partitioned into 3 drives:
----------------------------------------
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 66 530113+ 83 Linux
/dev/sdd2 67 132 530145 82 Linux swap / Solaris
/dev/sdd3 133 60791 487243417+ 83 Linux
/dev/sdd4 60792 60800 72292+ 83 Linux
-----------------------------------------
sdd1 and sdd4 can be mounted without a problem, the contain part of the
Firmware / OS as far as I can tell. But /dev/sdd3, which contains all
the data stored on the device, could not be mounted:
-----------------------------------------
root@grml ~ # mount /dev/sdd3 /mnt/floppy
mount: wrong fs type, bad option, bad superblock on /dev/sdd3,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
-----------------------------------------
dmesg gives me
-----------------------------------------
EXT3-fs: sdd3: couldn't mount because of unsupported optional features (40).
-----------------------------------------
I have tried to manually search for the superblocks with the program
"testdisk" and mke2fsk -n.
-----------------------------------------
root@grml ~ # mke2fs -n /dev/sdd3
mke2fs 1.40-WIP (14-Nov-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
60915712 inodes, 121810854 blocks
6090542 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
3718 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000
-----------------------------------------
and tried e2fsck with and without the -B option on all superblocks:
with -B option
-----------------------------------------
root@grml ~ # e2fsck -b 229376 -B 4096 /dev/sdd3
e2fsck 1.40-WIP (14-Nov-2006)
e2fsck: Filesystem has unsupported feature(s) while trying to open /dev/sdd3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
-----------------------------------------
without -B
-----------------------------------------
root@grml ~ # e2fsck -b 229376 /dev/sdd3
e2fsck 1.40-WIP (14-Nov-2006)
e2fsck: Bad magic number in super-block while trying to open /dev/sdd3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
-----------------------------------------
tune2fs gave me
-----------------------------------------
root@grml ~ # tune2fs -l /dev/sdd3
tune2fs 1.40.3 (05-Dec-2007)
tune2fs: Filesystem has unsupported feature(s) while trying to open
/dev/sdd3
Couldn't find valid filesystem superblock.
-----------------------------------------
To my surprise sdd3 was mountable with "mount -t ext4dev /dev/sdd3"
and dmesg wrote:
EXT4-fs warning: mounting fs with errors, running e2fsck is recommended
EXT4 FS on sdd3, internal journal
EXT4-fs: mounted filesystem with ordered data mode.
EXT4-fs: file extents enabled
But I could see all data. When I did a grep -r over the data about ~80%
showed an I/O error. dmesg gave
-----------------------------------------
grow_buffers: requested out-of-range block 142945162600120 for device sdd3
-----------------------------------------
with different block numbers.
Oh and debugfs on the ext4dev mounted partition gave:
-----------------------------------------
root@grml ~ # debugfs /mnt/floppy
debugfs 1.40.3 (05-Dec-2007)
/mnt/floppy: Attempt to read block from filesystem resulted in short
read while opening filesystem
debugfs: stats
stats: Filesystem not open
-----------------------------------------
Does anybody of you have an idea if there is a way to increase the
number of files that can be rescued? I really doubt that they use ext4
for the data partition, so what has happened here?
Thanks for any advice!
Gunter
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
