I'm with you on this one... last night I rebooted into win2k, and for some foolish reason typed "chkdsk" in the prompt window. My system instantly rebooted and /hdb1 was gone. (it's visible, but no, I don't want to format it).
What worries me, is that this has happened before. A power outage shutdown my system while I was in linux (SuSE at the time). I had a similar experience to yesterday, but I foolishly rewrote the paritition table and formatted the drive. Everything was gone, I did have backups for most things though. I did lose the data on my NTFS partition that time... but did recover my linux partition (the filenames were randomized). I suspect my secondary hard drive has issues that allow it to write bits unexpectedly when it loses power. (WD CAVIAR SE 200GB)
Now: there isn't much relevant information out there on this topic... most people think it's just a simple issue of some bit of code missing, or an incorrect syntax -- but it's a corrupted drive.
ahwkong is right.... "the /dev/hda5 is screwed up"
Code:
fdisk -l
/dev/hda1 * 1 1020 8193118+ 7 HPFS/NTFS
/dev/hda2 1021 14945 111852562+ f W95 Ext'd (LBA)
/dev/hda5 1021 2325 10482381 b W95 FAT32
/dev/hda6 2326 13798 92156841 83 Linux
/dev/hda7 13799 13927 1036161 82 Linux swap / Solaris
/dev/hda8 13928 14945 8177053+ 83 Linux
Disk /dev/hdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 24321 195358401 7 HPFS/NTFS
dev/hda1 and /dev/hda5 mount fine... so it isn't a software issue. /dev/hdb1 is visible, so it isn't a problem with the partition table.
Code:
dmesg | grep hdb1
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Mount option errors=recover not used.
Aborting without trying to recover.
NTFS-fs error (device hdb1): ntfs_fill_super(): Not an NTFS volume.
Code:
mount -t ntfs -o ro /dev/hdb1 /mnt/wing
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
or too many mounted file systems
So... it could be a boot sector issue... or a bad superblock... or something else... I'm reluctant to do anything at this point, as once again, i'm not certain of what i'm doing. Any ideas?
Cheers,
Cory.