mount: wrong fs type, bad option, bad superblock on /dev/hdc3
 

I get the above error when trying to access a HDD that used to house a SUSE install (i'm not sure how much is left of it, i resized it's partition...).

When i say
as the error goes on to reccomend, i get the answer:

Bend_request: I/O error, dev hdc, sector 176233066
ReiserFS: hdc3: warning: sh-2006: read_super_block: bread failed (dev hdc3, block 16, size 512)
end_request: I/O error, dev hdc, sector 176233178
ReiserFS: hdc3: warning: sh-2006: read_super_block: bread failed (dev hdc3, block 128, size 512)
ReiserFS: hdc3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on hdc3
end_request: I/O error, dev hdc, sector 176233066
ReiserFS: hdc3: warning: sh-2006: read_super_block: bread failed (dev hdc3, block 16, size 512)
end_request: I/O error, dev hdc, sector 176233178
ReiserFS: hdc3: warning: sh-2006: read_super_block: bread failed (dev hdc3, block 128, size 512)
ReiserFS: hdc3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on hdc3

My thinking is that this is basically saying "get a new hard drive" but i'd like to save a fair proportion of the data off this one, and ideally the functionality (even if not the data).
Any ideas? Currently trying to access it through a Knoppix live DVD, but i'm reliatively new to Linux so i don't know which rescue tool does what....
If the data's irretrievable, any ideas on how to make the hard drive useable post-format?

It's an IDE Maxtor DiamondMax 250GB. Been using as a storage drive for my Mandriva installation for a while, with no problems under Linux or Windows previously. BIOS has sketchy recognition of it - in CMOS setup it gives no info on cylinders or heads as on other drives.

Cheers!
Avi.

can you fdisk /dev/hdc -l to show what partitions are there?

fdisk /dev/hdc -l

gives

cannot open /dev/hdc

I *think* i managed to get qtparted to see it on the rescue disk earlier though. Will try that later. What results specifically would help?

Similar Problem
 

I am having a similar problem to what is listed above...

Here's a long story short - I reinstalled Windows 2K and it suddently started reading my hard drives (and partitions) as "parameter incorrect" and was asking me to format. Well, I decided I'd give the HDD a chance in linux to pull some data off.

I installed Mandriva 2005 and am attempting to mount a hard drive. When I attempt to mount hdc1 however I get:

"mount: wrong fs type, bad option, bad superblock on /dev/hdc1 or too many mounted file systems"

When I attempt to mount hdc2 I get:
I do not get an error as listed above, however if I attempt to ls I get "input/output error"

when I type "fdisk /dev/hdc -l"

"Device Boot Start End Blocks Id System
/dev/hdc1 1 12396 99570838+ 7 HPFS/NTFS
/dev/hdc2 12397 24792 99570870 7 HPFS/NTFS"

Is it possible to recover this data...? What confuses me is this happend to 2 new harddrives (6mo old). One is a 200gb and one is a 160gb.....

I'm in the same boat here, except i get a whole load more errors than already stated.

fdisk /dev/hdc -l gives:

knoppix@0[knoppix]$ fdisk /dev/hdc -l
Note: sector size is 2048 (not 512)

Disk /dev/hdc: 728 MB, 728190976 bytes
255 heads, 63 sectors/track, 22 cylinders
Units = cylinders of 16065 * 2048 = 32901120 bytes

Disk /dev/hdc doesn't contain a valid partition table

Now this doesnt seem quite right to me as its a 40gb hard drive (should be more like 38.... bytes)

Accepted I need a new hard drive, but i have maybe 1000 irreplaceable photos on there, which i would do anything to retrieve.

Is there much that can be done to DIY salvage or maybe get some pros in?

Hi guys,

Sounds like a few of you have corrupt partition tables.

try fsck /dev/deviceYouAreHavingProblemsWith

This will check all the things that cause problems in this area.

It will ask you lots of questions at the end of the process, In the main I would advise answering Yes to them all, unless it sounds grossly wrong.


Seb

Load up a livecd and reiserfsck

--check consistency checking (default)
--fix-fixable fix corruptions which can be fixed without
--rebuild-tree
--rebuild-sb super block checking and rebuilding if needed
(may require --rebuild-tree afterwards)
--rebuild-tree force fsck to rebuild filesystem from scratch
(takes a long time)

Should fix you up.:)

I had the same problem and fsck just fixed all my problems! :D

S.

fsck fixed the problem for me too thanks

Short read reading journal superblock
 

I just tried fsck and this is what I got:
[root@localhost todd]# fsck /dev/sda6
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
/dev/sda6: Attempt to read block from filesystem resulted in short read while reading block 529

/dev/sda6: Attempt to read block from filesystem resulted in short read reading journal superblock

fsck.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /dev/sda6
[root@localhost todd]#
________________________________________________________________________

Then I tried to run debugfs -w and when I try to view any of the files I get:
[root@localhost todd]# debugfs /dev/sda6 -w
debugfs 1.40.8 (13-Mar-2008)
debugfs: ls
2 (12) . 2 (12) .. 11 (20) lost+found 15679489 (12) todd
18104321 (16) share 11436033 (20) lisahedaria 4177921 (16) arlene
14123009 (20) candynally 5980161 (16) louis 2899969 (16) lpinson
2916353 (12) joe 4866049 (12) jeri 13189121 (16) xerox
3063809 (20) jeriwalter 3342337 (16) arlenem 2932737 (3860) joed
debugfs: cd todd
debugfs: ls

Attempt to read block from filesystem resulted in short read
debugfs:
________________________________________________________________________

when I try to mount the partition I get:
[root@localhost todd]# mount /dev/sda6
mount: wrong fs type, bad option, bad superblock on /dev/sda6,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

[root@localhost todd]#

________________________________________________________________________
If I view the log file, this is what I get:

[root@localhost todd]# dmesg | tail
EXT3-fs: error loading journal.
ata1: EH complete
sd 0:0:0:0: [sda] 312500000 512-byte hardware sectors (160000 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 312500000 512-byte hardware sectors (160000 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[root@localhost todd]#
________________________________________________________________________
This is the first time that I've ever even really looked at the file system in 8 years of using Linux. I know I'm an idiot for not caring, but I do now. I've heard for years that ext3 is far better than NTFS and frankly that's always been good enough for me. So if anyone has a clue which direction to point me and can be of assistance it would be greatly appreciated. Yes this is the /home partition of a "win2k domain controler" where all of the user files are. It always bugs me when people start crying about how important the data is so I won't do it. Only that the data was important enough to me that my "win2k domain controler" is not win2k. I here by swear that I will help the next person with a problem that I know how to fix. I would have done that anyway but there it is. Thanks in advance.

Almost identical problem
 

Let's bump this thread a bit. This is my story:

I have 2 SATA HDDs and an old IDE HDD mounted on my computer. My /home folder and the / folder were two partitions on the IDE HDD (/dev/sdc6 and /dev/sdc7 respectively). Other files were on the other hard drives.

Today while chatting with work colleagues in Pidgin, there was a 2-second freeze, then everything started to go downhill. The keyboard stopped responding, and after a restart Grub could no longer find the partition table on sdc.

I tried a system restore using an OpenSuse 11.1 DVD (the distro currently installed), but it failed each time when running fsck on /dev/sdc6 or /dev/sdc7.

I reinstalled OpenSuse 11.1, keeping the troublesome HDD aside while resizing partitions on my other HDDs.

Here is what happens when I run fsck:
-----------------------------------------------------------------
>fsck -p /dev/sdc7
/dev/sdc7: Attempt to read block from filesystem resulted in short read while reading block 1545

/dev/sdc7: Attempt to read block from filesystem resulted in short read reading journal superblock

fsck.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /dev/sdc7
------------------------------------------------------------------

And fdisk -l:
------------------------------------------------------------------
>fdisk -l /dev/sdc7

Disk /dev/sdc7: 140.9 GB, 140940140544 bytes
255 heads, 63 sectors/track, 17134 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc7 doesn't contain a valid partition table

>fdisk -l /dev/sdc

Disk /dev/sdc: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x10541054

Device Boot Start End Blocks Id System
/dev/sdc1 1 19929 160079661 f W95 Ext'd (LBA)
/dev/sdc5 1 183 1469884+ 82 Linux swap / Solaris
/dev/sdc6 184 2794 20972826 83 Linux
/dev/sdc7 2795 19929 137636856 83 Linux

------------------------------------------------------------------

I used debugfs and managed to browse around without getting any errors:

------------------------------------------------------------------
>debugfs /dev/sdc7 -w
debugfs 1.41.1 (01-Sep-2008)
debugfs: ls
debugfs: cd nikozeta
debugfs: ls
------------------------------------------------------------------

After unsuccessfully trying to mount the troublesome partition using Yast, here is what I get when I run dmesg | tail:
------------------------------------------------------------------
>dmesg | tail
EXT3-fs: error loading journal.
ata6: EH complete
sd 5:0:0:0: [sdc] 320173056 512-byte hardware sectors: (163 GB/152 GiB)
sd 5:0:0:0: [sdc] Write Protect is off
sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:0:0:0: [sdc] 320173056 512-byte hardware sectors: (163 GB/152 GiB)
sd 5:0:0:0: [sdc] Write Protect is off
sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
------------------------------------------------------------------

The similarities with the previous post should be striking. If someone can point me to a solution, I will certainly post a detailed description of how I managed to get this important data (including all my passwords!!) :)

Recover some of your data
 

I should just mention that it is entirely possible to recover the non-corrupted parts of an unmountable device formatted with ext2 or ext3. Simply start the debugfs: (use -c instead of -w if the latter doesn't work)

>debugfs -w /dev/sdc6

Then you can navigate to the folder you want to save, and use dump or rdump (recursive dump) to get the non-corrupt files to your native (and working) file system. I just recovered all the files I needed like this.

I had similar problems with my hard drive after a power trip. The partition table corrupted. I tried everything mentioned here, nothing worked. Finally it was spinrite that saved me. It managed to fix everything back to normal.

bad magic number
 

at first fsck was not working.

then i tried "initialise /dev/sdb1 1900000" in debugfs for my pendrive and then did fsck command

fsck asked loads of question but fixed it.

I had same problem but fsck didnt fix it, i used this guide.
http://linuxexpresso.wordpress.com/2...ock-in-ubuntu/