Topic: Can't mount Hard Drive

[laurie_lewis]

I have just reinstalled SME 6.01 and gone to remount a second hard drive and have got the following message.  I know that it was working a hour ago.  I had previously mounted it as ext3.  Now this

Code: [Select]

[root@kennel /]# mount -a
mount: wrong fs type, bad option, bad superblock on /dev/hdd1,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)
[root@kennel /]#


I have no idea of what to do to fix this problem and it was my backup drive with ALL my data on it?

HELP

thanks

Laurie

[jfarschman]

Laurie,

  It sounds like this disk was used before and has data one it.  If that's the case, maybe the drive is corrupt.  Is it being detected when you first boot up?     

dmesg |grep sectors
or
dmesg |grep hd

I think either of these should show you info about your drive if it was detected on bootup.  It will probably show you a similiar error message to the one you have already seen.  So maybe it's the superblock.

e2fsck -a /dev/hdd1

That may fix it.  I hope this helps.

[laurie_lewis]

Unfortunately this does not work.

I get an error message

Code: [Select]

The superblock could not be read or does not describe a correct ext2 filesyste.  If the device is valid and it really contains an ext2 fileysystem (and not wap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:  e2fsck -b 8193 <device>

Unfortunately this does not work either,

I have run a demo program called Quick Recover for Linux over the disk (runs on windows) and it brings up all the directories and files etc but I can not restore them (disabled in demo version) so I am unable to tell if they are still there in reality.  

This is my second backup disk to go like this - within the last week so I am a bit worried about what is causing it but more importantly I NEED to get the data back.

Any further ideas would be appreciated.

[jfarschman]

Sadly,

  I may not be much help today.  I've got a guy install a sattelite dish on the roof and I'm at home...  Also. the list time I did this was with xfs, in which case you would run

xfs_check /dev/mda4
xfs_repair -L /dev/mda4

But your on an entirely different file type.  Perhaps the e2fsck has an equivalent... but I need to run and work with the Dish man.  Sorry.

[laurie_lewis]

No problems,

I ran dmesg |grep hd and got the following response:

hdb1:  bad access: block=2, count =2
end request: I/O error, dev 03:41 (hdb), sector 2

It find the drive OK and describes it as it is also.

I also did dmesg |sectors and it came up with the drives but no error messages.

I also ran mke2fs -n /dev/hdb1 and it reported back that the "device size reported to be zero.  Invalid partition specified"

That makes me think that the repairs on the file system won't work becasue it doesn't even think anything is there to start with.  

Am I thinking straight?

Laurie

[jfarschman]

Laurie,

  Well... I have a few things you can try, but I don't know that they will work.  First try not using the /etc/fstab.  You -a command forces all the devices in fstab to be mounted and maybe it's misconfigured. So try:

mkdir /mnt/tmp
mount -t ext3 /dev/hdb1 /mnt/tmp

Also... since ext3 and ext2 share a lot in common, try:

mount -t ext2 /dev/hdb1 /mnt/tmp

and one more thing:

mount -t auto /dev/hdb1 /mnt/tmp

Finally... and it really helps if you know the location of your alternate superblocks, try what the error message suggested... sort of.  I think the default place to put the superblocks is 8191 and 16383

e2fsck -b 8191 /dev/hdb1
or
e2fsck -b 16383 /dev/hdb1

If none of this works, you have exhausted my bag of tricks.  If the data is important I'd use that other utility to get it.  I wish I knew more about salvaging data from a drive.

[MSmith]

Seems like I'm recommending Knoppix at least once a week, but have you tried booting from a Knoppix CD to see if it will see your drive & files?  If so ... ta da!

[kruhm]

I had the same problem. The answer is right there:

(could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?)

I'll do some searching for the exact command.

mount -t ext2 /dev/scd0 /dev/hdb1

check man mount

[yassa434]

I believe I had the same problem, I had installed a second HD on my SME svr and had all data stored on it for client users. After a power problem I had to rebuild my SME server and had exactly what you had described. I believe that you may have created the drive using ext2 and then converted to ext3, this seamed to be my problem. I could only reformat and restore the data!!!! All seams to be ok now.

hdd: attached ide-disk driver.
hdd: host protected area => 1
hdd: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=79408/16/63, UDMA(100)

my sys reports the above after dmesg |grep hd

it  may have someting to do with the protected area????

[laurie_lewis]

this is sad news for me.  I have tried and can not get it back no matter what.  I have found one program that will read it but can not part with the dollars being asked for it.  There is no guarantee it will raise the dead either.

thanks anyway