[ale] rescue disk?

[Gary Maltzen]

If you can't find a BIOS upgrade for your system, you'll definitely want to
find a new mobo.

When I first installed a new 36GB drive in my Asus P5AB motherboard system,
the system refused to boot. I finally found a new (beta) flash BIOS that
cured the problem.

The other solution I found was to attach the drive to the second IDE
controller but NOT enable the second controller in BIOS. When Linux comes up
it uses it's own IDE controller routines and will be able to see the drive
in it's entirety. (This presumes you have a bootable drive on the first IDE
controller)

In the meantime, go visit Tom's site (www.toms.net) and get a copy of Tom's
Root/Boot; it is invaluable in emergency situations...

>
> this is a rather embarassing question...
>
>
> I need to build a rescue disk for a RedHat 6.1 (Cartman) computer.  I
> couldn't find a rescue.img in the 6.1 distribution so I downloaded
> rescue.img from a 5.2 distribution and put it on a floppy using rawrite,
> but the 5.2 install disk said it couldn't find a valid rescue.img on the
> floppy.
>
>
> You see, I got a new 60GB harddrive and my BIOS can't read it. I tried
> Maxtor's MaxBlast software to trick the computer into reading more than
> 32GB, but it blew away lilo, and I, um, neglected to create a custom
> rescue disk earlier. (i'll take my lashings now, thank you).  All I need
> to do is to boot Linux so that I can reinstall lilo.
>
> Of course, this won't help the bigger issue of getting Linux to see the
> full 60GB drive. My BIOS hangs when I boot the drive in a normal
> configuration and if I set the "limit cylinders" jumper it only sees a
> 32GB drive. any ideas? is my only choice to get a new motherboard that can
> handle large drives?


--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.