On Thu, Jun 6, 2013 at 3:06 PM, Jesse Thompson <[email protected]> wrote: > Hello! > > I would like some help trying to boot from CD using Grub command line. > Trying to recover data from an ancient Compaq Proliant server which lacks a > way to set boot order in bios. > > Only apparent thing I know how to access is Grub command line. > > "ls" does not display the CD as a device, and I'm not sure if that means CD > drive itself is borked or inaccessable, or if I should insmod something to > make it visible.
For whatever reason, BIOSs only present the CDROM drive to bootloaders if the machine was booted from CD, so there is probably no way to access the CDROM drive through your BIOSs interfaces, but luckily grub does have its own native drivers as well. To load grub's native drivers you need to insmod the appropriate modules, which of course depends on what type of interface this drive uses. The modules available are "pata", "ahci" (SATA), "uhci" (one of the specifications for USB 1.0), "ohci" (the other), "ehci" (USB 2.0), and "usbms" (For mass storage devices connected via ohci,uhci, or ehci). Loading "ahci" or "pata" will disable grub's access to drives via BIOS interfaces (having two sets of software trying to access the hardware, grub and the BIOS, at the same time could be dangerous) and so you'll have to change grub's $prefix variable to point to the new device name so that grub can find its modules. There is a new command recently added (or soon to be added) to grub trunk which automates this (fixing $prefix when loading native drivers). And a final caveat, you cannot use chainloading when using grub's native drivers, you must load the kernel from the CDROM directly. -- Jordan Uggla (Jordan_U on irc.freenode.net) _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
