Help! Help! I'm stuck inside of Windows with the Mandrake Blues Again!
Sad story
I run Mandrake 9.0 and Windows 98 SE on the same hard drive a Seagate 16 Gig. I spend most of my time in Mandrake. I decided to install a second hard drive, a 30 Gig Seagate. I got it used on eBay, okay! After I got it physically installed and then got the BIOS to recognize it as the "primary slave," I decided to use HardDrake to format and partition the new hard drive. That part didn't go very well, which I know is not a very good thing to say when you're logged in as su. But I thought in the end it formatted one huge ex2 partition. I wanted to partition about a third of the drive in Fat 32, but HardDrake didn't exactly show me the way to do Fat 32, so I decided to go into Windows and use Partition Magic to format for both file systems. I started from scratch in Windows, downloading Seagate's DiscWizard 2003, to format the new hard disc, then I used Partition Magic to create both a Fat 32 and a ex2 partitions. When I tried to reboot into Mandrake it just would not mount the hdb and gave me the error messages that I have copied below. So back in Windows I downloaded a hard drive utility from Seagate, Seatool, or similar; sure enough after writing over six bad sectors which succeeded, then another complete scan, the new hard disk failed the test. "DST - Errors - Status: 05". So I completely disconnected the hard drive, got BIOS to auto detect its new (original) configuration, then tried to boot into Mandrake but the error messages have continued. Is there a rescue?
Thanks in advance. Even though I've been in Mandrake for a little over a year, I'm still as green as green can be in the shell, so if there's anything to do I'll really need to have my hand held. Oh, mea culpa, already
{Error messages that occurs at "checking file systems" part of boot up, even though hdb is no longer attached:}
"fsck.ext3: No such file or directory while trying to open /dev/hdb5
fsck.ex3/dev/hdb5:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ex2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck.ext3: No such file or directory while trying to open /dev/hdb1
/dev/hdb6:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock
e2fsck -b 8193 ,device>
fsck.ext3: No such file or directory while trying to open /dev/hdb1
/dev/hdb6
The superblock could not be read or does not descrive a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), the the superblock
is corrupt, and you might try running e2fsck with an alternate superblock
e2fsck -b 8193 ,device>
fsck.ex3: No such file or directory while trying to open /dev/hdb6
Failed to check filesystem. Do you want to repair the errors? (Y/N)
(beware, you can loose data)
y
{More error messages as above. 3 ‘No such file or directory' and 2(?) ‘The superblock etc.' And then:}
[failed]
***An error occurred during the fsck
***Dropping you to a shell; the system will reboot
***When you leave the shell
(Repair filesystem) 1#"
That's where I usually exit.