Hi all.
sorry for an immediate question after subscribing, but I've managed to back myself into a frustrating corner. I've done some googling and come up dry, I figured I should try to post to the list while I dig through the archives.
I have an issue with grub on a centos reinstall. my system previously had 1x 120g ide drive, 3 1tb sata drives in raid 5 md, 2 300 g in a raid 1 md,the /boot partition was on the ide drive, os on the raid 1 in a volume group and everything seemed fine. I downloaded the x86_86 iso a few days back and decided to just to a complete reinstall rather than burn myself with some odd upgrade path trying to put newer, larger drives into a md with a much smaller drive.
I've since purchased some new drives and changed to 1 120 ide, 4 1 tb sata, 2 3tb sata. I've tried a few different combinations of install locations (e.g reused the ide as /boot, a 512 mb slice from a 1tb drive for /boot) but every layout I try seems to end up with a grub config that can not find the OS (if memory serves, the message comes back as error 15: file not found, hit return to reboot)
the thing that seems odd to me is when I do the reinstall, the hdds seem to start much higher than I'd expect. there's no /dev/sda, b, c, d, ... I think they start at i.
does anyone have some suggestions for what to try for this issue? Thanks.
zGreenfelder wrote:
Hi all.
sorry for an immediate question after subscribing, but I've managed to
Not a problem.
<snip> What's in /boot/grub/device.map?
Also, one thing you can try is, when the menu comes up, or it announces what it thinks it's going to boot, you can hit 'e' to get the menu, then 'e' again on that kernel, and you'll get the three lines - root, kernel and initrd, that you can edit in the grub shell. Now, that's pretty primitive, but it *does* have completion. Try editing the root= line, and remember that it calls *everything* <hdx), so try root (hd<tab) and see what it offers.
mark
On Fri, Jan 11, 2013 at 11:26 AM, m.roth@5-cent.us wrote:
zGreenfelder wrote:
Hi all.
sorry for an immediate question after subscribing, but I've managed to
Not a problem.
<snip> What's in /boot/grub/device.map?
Thanks for a quick response, I wait till I could be home and in front of the machine to be sure device map has (hd0) /dev/sdi
running find /grub/grub.conf from the grub shell when the machine tries to boot returns (hd0,0) and /dev/sdi1 is where /boot mounts.
Also, one thing you can try is, when the menu comes up, or it announces what it thinks it's going to boot, you can hit 'e' to get the menu, then 'e' again on that kernel, and you'll get the three lines - root, kernel and initrd, that you can edit in the grub shell. Now, that's pretty primitive, but it *does* have completion. Try editing the root= line, and remember that it calls *everything* <hdx), so try root (hd<tab) and see what it offers.
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
zGreenfelder wrote:
On Fri, Jan 11, 2013 at 11:26 AM, m.roth@5-cent.us wrote:
zGreenfelder wrote:
Hi all.
sorry for an immediate question after subscribing, but I've managed to
Not a problem.
<snip> What's in /boot/grub/device.map?
Thanks for a quick response, I wait till I could be home and in front of the machine to be sure device map has (hd0) /dev/sdi
running find /grub/grub.conf from the grub shell when the machine tries to boot returns (hd0,0) and /dev/sdi1 is where /boot mounts.
That's *very* odd. You don't have an HBA or something else - flash key? anything? What's on this system that it sees stuff that high?
Directly related: look at your BIOS, and see what drives it sees, and what's bootable, in what order. Perhaps you can move up the boot drive? <snip>
mark
-
m.roth＠5-cent.us -
zGreenfelder