Re[4]: Unable to boot - Stuck at "GRUB" (SOLVED)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Doug,

Sunday, January 5, 2003, 4:49:10 PM, you wrote:

DB> I'm relatively new to linux and very new to grub.
DB> I've been reading the manual and searching google to learn about grub 
DB> before installing it.
DB> One thing the manual said...
DB>          Normally IDE drives number less than SCSI drives.
DB> That would seem to mean that (hd0,0) now points grub to the ide instead of 
DB> the scsi.

I found this out the hard way.  I'm still a bit confused that Grub
would modify an exiting device.map file when that could cause issues
(case in point).

DB> I expect the grub command line still works?

No, no it didn't.  However, that's where 'linux rescue' comes in
handy.

DB> I guessing it is now (hd1,0) instead of (hd0,0).

Yes, hd(0,0) was now the new IDE drive with sda becoming hd(1,0)

DB> If so, you can edit the grub.config or boot from the command line by entering:
DB> (assuming this is the kernel you want... otherwise change the kernel and 
DB> initrd version)

DB> root (hd1,0)
DB> kernel /boot/vmlinuz-2.4.19-ac4 ro root=LABEL=/ vga=791
DB> initrd /boot/initrd-2.4.19-ac4.img
DB> boot

I tried this, but did not have any luck(?).  Was still hanging up at
"GRUB" (no more beeps tho!).

Alternatives...

Since this did not work:
# grub-install --recheck /dev/sda
Probing devices to guess BIOS drives. This may take a long time.
/dev/md6 does not have any corresponding BIOS drive.

I had to run:
# grub --device-map=/boot/grub/device.map (*)
    grub> root (hd0,0)
     Filesystem type is ext2fs, partition type 0xfd
    grub> setup (hd0)
     Checking if "/boot/grub/stage1" exists... yes
     Checking if "/boot/grub/stage2" exists... yes
     Checking if "/boot/grub/e2fs_stage1_5" exists... yes
     Running "embed /boot/grub/e2fs_stage1_5 (hd0)"...  22 sectors are embedded.
    succeeded
     Running "install /boot/grub/stage1 (hd0) (hd0)1+22 p (hd0,0)/boot/grub/stage2
    /boot/grub/grub.conf"... succeeded
    Done.

    grub> exit

(*) device map has been edited to put IDE drive at the end

Rebooted and all was well once again.  Phew!

DB> Remember... I haven't used grub yet... this is guess based on my 
DB> understanding of the manual.

Wasn't a bad guess at all, and probably would work in other
configurations and/or situations.

Thanks for the assistance!

As a side note, what other OS could possibly cause you to start
pulling hairs, yet be so happy when you finally fix the problem with
the assistance of others?  What a trip! :)

-- 
Best regards,
 Brian Curtis



-- 
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux