I just adore the install. Esp. of GRUB.
Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines?
I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right now, I'm installing on a replacement disk on a server that has no CD/DVD drive from a USB key. My options: on my home system, it was MRR on /dev/hda (which was being replaced, and was to become my backup drive), and here, in the MBR of the USB key; in both cases, *only* in the first sector of a partition on the new drive. I am NEVER OFFERED THE OPTION of the MBR of the drive I'm installing to.
*snarl*
mark "no grub, then linux rescue, then chcon, then grub install... I hope"
a cross post -- how tacky
On Fri, 4 Jun 2010, m.roth@5-cent.us wrote:
Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines?
certainly -- I had a data recovery a couple weeks ago where all I could reach on boot was the grub command prompt, a tight time deadline, no spare box to debug from, and a need to do exploration from that prompt
I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right
... snip
I am NEVER OFFERED THE OPTION of the MBR of the drive I'm installing to.
Yup -- Probably you did not get a clean initrd containing the needed driver module for the SATA drive controller in question. Happens a lot.
-- Russ herrold
On 6/4/10 11:10 AM, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
I just adore the install. Esp. of GRUB.
Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines?
I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right now, I'm installing on a replacement disk on a server that has no CD/DVD drive from a USB key. My options: on my home system, it was MRR on /dev/hda (which was being replaced, and was to become my backup drive), and here, in the MBR of the USB key; in both cases, *only* in the first sector of a partition on the new drive. I am NEVER OFFERED THE OPTION of the MBR of the drive I'm installing to.
*snarl*
mark "no grub, then linux rescue, then chcon, then grub install... I hope"
Not a GRUB bug, rather, Anaconda being overly "helpful".
On Fri, Jun 04, 2010 at 02:10:31PM -0400, m.roth@5-cent.us wrote:
I just adore the install. Esp. of GRUB.
Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines?
I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right now, I'm installing on a replacement disk on a server that has no CD/DVD drive from a USB key. My options: on my home system, it was MRR on /dev/hda (which was being replaced, and was to become my backup drive), and here, in the MBR of the USB key; in both cases, *only* in the first sector of a partition on the new drive. I am NEVER OFFERED THE OPTION of the MBR of the drive I'm installing to.
*snarl*
mark "no grub, then linux rescue, then chcon, then grub install... I hope"
Try `grub-install --root-directory=/path/to/your/new/system /dev/hda' (if there is on hda).
On Fri, Jun 04, 2010 at 02:10:31PM -0400, m.roth@5-cent.us wrote:
I just adore the install. Esp. of GRUB.
Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines?
I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right now, I'm installing on a replacement disk on a server that has no CD/DVD drive from a USB key. My options: on my home system, it was MRR on /dev/hda (which was being replaced, and was to become my backup drive), and here, in the MBR of the USB key; in both cases, *only* in the first sector of a partition on the new drive. I am NEVER OFFERED THE OPTION of the MBR of the drive I'm installing to.
*snarl*
mark "no grub, then linux rescue, then chcon, then grub install... I hope"
Try `grub-install --root-directory=/path/to/your/new/system /dev/hda' (if there is on hda).
I did the linux rescue, chroot (whoops, not chcon) to /mnt/sysimage, and did grub-install --no-floppy /dev/sda Now, when I reboot, it goes into the grub shell. Googling, and using the hostile find, I set root (hd0,0), and then setup (hd0). It claims everything is wonderful... but when I reboot, I go back to the grub shell.
From the grub shell, I've also tried telling it kernel
/vmlinuz-2.6.18-194.3.1.el5, and it claims it can't find that; neither can find.
This is *so* much more sophisticated than changing lilo.conf, and running lilo to update the MBR.... And no, I have no choice, this is work, so I have to use the mandated grub.
mark
Did you check the devices.map file? Last time I got to do the GRUB jig-o-despair was after adding disks to an array controller somehow turned /dev/sda into /dev/sdc...
m.roth@5-cent.us wrote:
I did the linux rescue, chroot (whoops, not chcon) to /mnt/sysimage, and did grub-install --no-floppy /dev/sda Now, when I reboot, it goes into the grub shell. Googling, and using the hostile find, I set root (hd0,0), and then setup (hd0). It claims everything is wonderful... but when I reboot, I go back to the grub shell.
From the grub shell, I've also tried telling it kernel
/vmlinuz-2.6.18-194.3.1.el5, and it claims it can't find that; neither can find.
This is *so* much more sophisticated than changing lilo.conf, and running lilo to update the MBR.... And no, I have no choice, this is work, so I have to use the mandated grub.
I just went through that last week. The problem is that grub is installed, but there is no config file. What I had to do was boot into rescue mode and create the /boot/grub/grub.conf by hand. I used one of my operational machines as a template.
On Fri, Jun 04, 2010 at 04:41:13PM -0400, m.roth@5-cent.us wrote:
On Fri, Jun 04, 2010 at 02:10:31PM -0400, m.roth@5-cent.us wrote:
I just adore the install. Esp. of GRUB.
<snip> > Try `grub-install --root-directory=/path/to/your/new/system /dev/hda' (if > there is on hda).
Now, is that root directory /, or /boot?
Root directory.
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
and it now boots. As I said, *so* much easier than editing /etc/lilo.conf, and rerunning lilo....
mark
On 6/4/10 2:59 PM, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
and it now boots. As I said, *so* much easier than editing /etc/lilo.conf, and rerunning lilo....
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mark, you might dislike Grub, but overall, it's saved me a lot of grief since lilo cannot start a "shell" so the poor sod can coerce the system to start another kernel if needed. (Yes, this has happened more than on one occasion with many the distro for me when dealing with rolling my own kernel.) That and lilo is completely useless on newer hardware (EFI and GPT labels anyone?) since it only understands BIOS addresses, whereas GRUB2 understands both. As stated in an earlier email in this thread, this is mostly caused by Anaconda and some of the GUI tools doing the wrong thing, not GRUB.
On Fri, Jun 04, 2010 at 03:06:30PM -0700, Gary Greene wrote:
On 6/4/10 2:59 PM, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
and it now boots. As I said, *so* much easier than editing /etc/lilo.conf, and rerunning lilo....
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mark, you might dislike Grub, but overall, it's saved me a lot of grief since lilo cannot start a "shell" so the poor sod can coerce the system to start another kernel if needed. (Yes, this has happened more than on one occasion with many the distro for me when dealing with rolling my own kernel.) That and lilo is completely useless on newer hardware (EFI and GPT labels anyone?) since it only understands BIOS addresses, whereas GRUB2 understands both. As stated in an earlier email in this thread, this is mostly caused by Anaconda and some of the GUI tools doing the wrong thing, not GRUB.
Lilo is good choice once you're running software raid. It can write MBR on all disks and kernel can boot only from one disk with no intervation. Grub's writing MBR only at the first disk.
On 6/4/10 3:10 PM, "Dominik Zyla" gavroche@gavroche.pl wrote:
On Fri, Jun 04, 2010 at 03:06:30PM -0700, Gary Greene wrote:
On 6/4/10 2:59 PM, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
and it now boots. As I said, *so* much easier than editing /etc/lilo.conf, and rerunning lilo....
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mark, you might dislike Grub, but overall, it's saved me a lot of grief since lilo cannot start a "shell" so the poor sod can coerce the system to start another kernel if needed. (Yes, this has happened more than on one occasion with many the distro for me when dealing with rolling my own kernel.) That and lilo is completely useless on newer hardware (EFI and GPT labels anyone?) since it only understands BIOS addresses, whereas GRUB2 understands both. As stated in an earlier email in this thread, this is mostly caused by Anaconda and some of the GUI tools doing the wrong thing, not GRUB.
Lilo is good choice once you're running software raid. It can write MBR on all disks and kernel can boot only from one disk with no intervation. Grub's writing MBR only at the first disk.
That's a misconception. Grub CAN write to ANY MBR, not just the disk at 0x80. This is trivial to do with grub shell. See the info pages for how.
m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
I did not create either of those links on my system and it booted just fine. I wonder what they are used for?
m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
I did not create either of those links on my system and it booted just fine. I wonder what they are used for?
No clue, but a "normal" install creates 'em.
mark
On Mon, Jun 7, 2010 at 8:16 AM, Bowie Bailey Bowie_Bailey@buc.com wrote:
m.roth@5-cent.us wrote:
Thanks, all, and with the help of the other admin, the system is up. What I had to do was linux rescue, the chroot /mnt/sysimage, grub-install /dev/sda
What I didn't get until later was it also needed /boot/grub/grub.conf, and then ln -s /boot/grub/grub.conf /boot/grub/menu.lst ln -s /boot/grub/grub.conf /etc/grub.conf
I did not create either of those links on my system and it booted just fine. I wonder what they are used for?
IIRC, /boot/grub/menu.lst is a legacy from earlier times when grub needed that one to boot. Sometime in the last three years or so, grub was changed to use a single uniform format file, so the menu.lst became a symlink to the actual grub.conf file.
I believe that /etc/grub.conf is just a convenience to match most other config files that live in /etc.
mhr
-
Bowie Bailey -
Dominik Zyla -
Gary Greene -
Jim Davis -
m.roth＠5-cent.us -
MHR -
R P Herrold