HDD isn't mounting (wrong fs type, bad option, bad superblock...)

MinasFilm · 11-28-2015, 06:43 PM

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...)

What else can I try to repair my HDD?

berndbausch · 11-29-2015, 07:01 PM

As most people's Ukrainian language skills are a bit lacking, please set LANG=C before you run your tests. This makes it easier to read your output.

Looks like your disk is close to retirement.

A few suggestions (just guesswork)

SMART
See if there are any messages about sdb1 in the system log
Does e2fsck claim that it actually repairs the main superblock?
Add the -v option to e2fsck for more info
Use the badblocks tool

MinasFilm · 01-09-2016, 01:55 PM

Quote:

Originally Posted by berndbausch

SMART

Code:

~$ sudo smartctl -a /dev/sdc

there is full result:
http://pastebin.com/QuXeM0nC

Quote:

Originally Posted by berndbausch

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

Code:

:~$ sudo e2fsck -f -b buckup_position -y  /dev/sdb1

(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?

Quote:

Originally Posted by berndbausch

Add the -v option to e2fsck for more info

Code:

~$ sudo e2fsck -f -b 32768  -y -v  /dev/sdc1 > data.txt

there is result (very big txt-file, in archive):
https://www.dropbox.com/s/4dovok4u3g...ta.txt.7z?dl=0

Quote:

Originally Posted by berndbausch

Use the badblocks tool

Code:

~$ sudo badblocks -sv /dev/sdc1
[sudo] password for sergey: 
Checking blocks 0 to 236007391
Checking for bad blocks (read-only test): done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

What to do next?

tredegar · 01-10-2016, 09:53 AM

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

Code:

sudo mount /dev/sdc1 /mnt

and see what happens.

MinasFilm · 01-16-2016, 04:57 AM

Quote:

Originally Posted by tredegar

So maybe try just

Code:

sudo mount /dev/sdc1 /mnt

and see what happens.

Code:

~$ LANG=C sudo mount /dev/sdc1 /mnt
mount: you must specify the filesystem type
~$ less /var/log/syslog | grep sdc1
Jan 16 12:36:57 blabla kernel: [57499.682738] EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
Jan 16 12:36:57 blabla kernel: [57499.683324] EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
Jan 16 12:36:57 blabla kernel: [57499.683824] EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
Jan 16 12:36:57 blabla kernel: [57499.684310] FAT-fs (sdc1): invalid media value (0x50)
Jan 16 12:36:57 blabla kernel: [57499.684312] FAT-fs (sdc1): Can't find a valid FAT filesystem

syg00 · 01-16-2016, 05:41 AM

Quote:

Originally Posted by berndbausch

Looks like your disk is close to retirement.

I'd say it is beyond that.

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)?

Code:

file -s /dev/sdc1

MinasFilm · 01-16-2016, 05:57 AM

Quote:

Originally Posted by syg00

What does this show (as root/sudo)?

Code:

file -s /dev/sdc1

Code:

sudo file -s /dev/sdc1
/dev/sdc1: data

MinasFilm · 01-22-2016, 09:20 AM

does anyone have any other ideas?

rknichols · 01-22-2016, 12:24 PM

My next step would be to run testdisk on /dev/sdc (or /dev/sdb, if that's the way it's being seen) and see what, if anything, it can find.

MinasFilm · 01-24-2016, 12:33 PM

Quote:

Originally Posted by rknichols

My next step would be to run testdisk on /dev/sdc (or /dev/sdb, if that's the way it's being seen) and see what, if anything, it can find.

I ran testdisk (in. 7.) - analyse
and received the following:

Code:

Disk /dev/sdc - 250 GB / 232 GiB - CHS 30401 255 63
Current partition structure:
     Partition                  Start        End    Size in sectors

No ext2, JFS, Reiser, cramfs or XFS marker
 1 * Linux                    0   1  1 29381 144 11  472014785
 1 * Linux                    0   1  1 29381 144 11  472014785
 2 E extended             29381 144 12 30401  75 10   16381952
 5 L Linux Swap           29381 176 44 30401  75 10   16379904

then the quick search with the result:

Code:

Disk /dev/sdc - 250 GB / 232 GiB - CHS 30401 255 63
     Partition               Start        End    Size in sectors
>* Linux Swap           29381 176 44 30401  75 10   16379904

Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
*=Primary bootable  P=Primary  L=Logical  E=Extended  D=Deleted
Keys A: add partition, L: load backup, T: change type,
     Enter: to continue
SWAP2 version 1, pagesize=4096, 8386 MB / 7998 MiB

But then I do not understand - what and how to use of the tools of testdisk?

rknichols · 01-24-2016, 03:12 PM

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.