День Добрый!
Есть проблема с ext3. Вероятно что-то не так с диском, но хотелось бы восстановить данные.Итак собственно проблема:
root@Knoppix ~ $ mount -t ext3 /dev/hdd3 /mnt/test/
mount: wrong fs type, bad option, bad superblock on /dev/hdd3,
or too many mounted file systems
Пробую проверить диск:
root@Knoppix ~ $ fsck.ext3 /dev/hdd3
e2fsck 1.35 (28-Feb-2004)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/hdd3
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>
Пробую создать новый superblock:
root@Knoppix ~ $ mkfs.ext3 -S /dev/hdd3
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1311552 inodes, 2622611 blocks
131130 blocks (5.00%) reserved for the super user
First data block=0
81 block groups
32768 blocks per group, 32768 fragments per group
16192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Creating journal (8192 blocks): mkfs.ext3: File exists
while trying to create journal
Пробую указать резервный superblock:
root@Knoppix ~ $ fsck.ext3 -b 819200 /dev/hdd3
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: Bad magic number in super-block while trying to open /dev/hdd3
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>
Что еще можно было бы попробовать?
Спасибо за помощь!