HDD isn't mounting (wrong fs type, bad option, bad superblock...)
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
HDD isn't mounting (wrong fs type, bad option, bad superblock...)
I have the HDD WD scorpio 250GB (wd2500bevt).
HDD has two partition: main with xubuntu 12.04 (ext3) and swop-partition.
Since some time OS xubuntu has showed me errors of GRUB, and when I tried to mount HDD through the USB-adapter to the other PC, I have got this:
Code:
~$ sudo mount /dev/sdb1 /mnt -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
В некоторых случаях полезная информация может быть
найдена в syslog - попробуйте dmesg | tail или что-то
в этом роде
I checked the position of superblock-backups -
Code:
~$ sudo mke2fs -n /dev/sdb1
mke2fs 1.42.9 (4-Feb-2014)
Метка файловой системы=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
14753792 inodes, 59001848 blocks
2950092 blocks (5.00%) reserved for the super user
Первый блок данных=0
Maximum filesystem blocks=4294967296
1801 block groups
32768 blocks per group, 32768 fragments per group
8192 inod'ов в группе
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
and tried to repair superblock from his first backup:
Code:
:~$ sudo e2fsck -f -b 32768 -y /dev/sdb1
then I have tried to mount HDD again and got the same error message (wrong fs type, bad option, bad superblock...)
See if there are any messages about sdb1 in the system log
Code:
~$ LANG=C sudo mount /dev/sdc1 /mnt -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~$ less /var/log/syslog | grep sdc1
Jan 9 15:51:16 blabla kernel: [242525.119375] EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
Quote:
Originally Posted by berndbausch
Does e2fsck claim that it actually repairs the main superblock?
as I said, I tried to restore the superblock of ALL its copies with the command
(was found in all 14 copies, see above)
In the process of the utility have been fixed some bugs, and each run was successful.
How to determine whether the superblocks were corrected - I do not know?
Before you make any further changes to this drive, I strongly suggest you backup its disk image (using dd) to another device so you do not introduce further problems accidentally.
Are you sure the FS type is ext3 (this is how you are trying to mount it manually) because syslog says Can't find ext4 filesystem
On my system I don't need to specify the FS type, mount works it out for itself. So maybe try just
The OP seems to have done everything sensible. All ext[234] are handled by the same e2fsprogs code - sometimes the messages aren't consistent and appear misleading. What does this show (as root/sudo)?
I find it very strange that fsck claims to have repaired the filesystem (your results from "sudo e2fsck -f -b 32768 -y -v /dev/sdc1 > data.txt"), but testdisk still does not find a valid ext2/3/4 marker. Also, I've never had to tell e2fsck where to find a backup super block -- it has always found one automatically if the primary super block was not recognizable. Furthermore, I don't understand why the testdisk quick search is not showing partition 1 regardless of whether it found a valid filesystem there.
Normally, I would suggest selecting "[Advanced] Filesystem Utils" in testdisk and seeing what it suggested for backup super blocks, but it's probably going to find the same blocks you have already tried.
What version of testdisk are you using? I really don't know what is going on. Sorry.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.