RE: New install boot problem -
Do you know the bootloader you are using off the top of your head? Assuming GRUB, you just need to edit /boot/grub/grub.cfg to point it to the right location. If you run into problems with it, paste it in here and I'm sure we can get you sorted. :) Trenton Ray MIS Center for Life Resources 408 Mulberry Brownwood, TX 76801 http://cflr.us This message is intended for the use of the addressees only and may contain information that is privileged, confidential, and exempt from disclosure. Any review, disseminations, or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of this original message. Thank you! -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Bob Goodwin - Zuni, Virginia, USA Sent: Tuesday, January 29, 2013 12:50 PM To: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV Subject: New install boot problem - I've just replaced F-18 with SL-6.3 Live installed but I have to use the flash drive to boot from the hard drive. I believe my error is that it's looking on the wrong drive. How do I fix that? Bob -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux
Re: New install boot problem -
On 01/29/2013 01:54 PM, Trenton Ray wrote: Do you know the bootloader you are using off the top of your head? Assuming GRUB, you just need to edit /boot/grub/grub.cfg to point it to the right location. If you run into problems with it, paste it in here and I'm sure we can get you sorted. :) Trenton Ray MIS Center for Life Resources I looked at grub.conf but didn't see what pointed to boot? I'll look again as soon as it finishes yum update. Tnx, -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux
Re: New install boot problem -
On 01/29/2013 01:54 PM, Trenton Ray wrote: Do you know the bootloader you are using off the top of your head? Assuming GRUB, you just need to edit /boot/grub/grub.cfg to point it to the right location. If you run into problems with it, paste it in here and I'm sure we can get you sorted. :) Trenton Ray MIS Ok I tried changing it to /dev/sdb, it was /dev/sda, but that didn't do it so I guess I need some help. [root@box7 bobg]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd2,0) # kernel /vmlinuz-version ro root=/dev/sdc3 # initrd /initrd-[generic-]version.img #boot=/dev/sdb default=0 timeout=15 splashimage=(hd2,0)/grub/splash.xpm.gz hiddenmenu title Scientific Linux (2.6.32-279.19.1.el6.x86_64) root (hd2,0) kernel /vmlinuz-2.6.32-279.19.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.19.1.el6.x86_64.img title Scientific Linux (2.6.32-279.5.1.el6.x86_64) root (hd2,0) kernel /vmlinuz-2.6.32-279.5.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.5.1.el6.x86_64.img title Other rootnoverify (hd0,0) chainloader +1 Bob -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux
RE: New install boot problem -
GRUB has a strange methodology (well, strange to me given that I'm one of a handful of neo-luddites still using LILO) for determining disks. It's got root as hd2,0 which means (and I may be mistaken) the 2nd disk, first partition.. which makes sense in accordance with /dev/sdb but since GRUB sees 0 as a value and not a null, maybe change it to 1,0 ? I fear I'm just going to add to the confusing at this point and apologize for not being able to help offhand. -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Bob Goodwin - Zuni, Virginia, USA Sent: Tuesday, January 29, 2013 1:24 PM To: Trenton Ray Cc: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV Subject: Re: New install boot problem - On 01/29/2013 01:54 PM, Trenton Ray wrote: Do you know the bootloader you are using off the top of your head? Assuming GRUB, you just need to edit /boot/grub/grub.cfg to point it to the right location. If you run into problems with it, paste it in here and I'm sure we can get you sorted. :) Trenton Ray MIS Ok I tried changing it to /dev/sdb, it was /dev/sda, but that didn't do it so I guess I need some help. [root@box7 bobg]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd2,0) # kernel /vmlinuz-version ro root=/dev/sdc3 # initrd /initrd-[generic-]version.img #boot=/dev/sdb default=0 timeout=15 splashimage=(hd2,0)/grub/splash.xpm.gz hiddenmenu title Scientific Linux (2.6.32-279.19.1.el6.x86_64) root (hd2,0) kernel /vmlinuz-2.6.32-279.19.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.19.1.el6.x86_64.img title Scientific Linux (2.6.32-279.5.1.el6.x86_64) root (hd2,0) kernel /vmlinuz-2.6.32-279.5.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.5.1.el6.x86_64.img title Other rootnoverify (hd0,0) chainloader +1 Bob -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux
Re: New install boot problem -
GRUB has a strange methodology (well, strange to me given that I'm one of a handful of neo-luddites still using LILO) for determining disks. It's got root as hd2,0 which means (and I may be mistaken) the 2nd disk, first partition.. which makes sense in accordance with /dev/sdb but since GRUB sees 0 as a value and not a null, maybe change it to 1,0 ? I fear I'm just going to add to the confusing at this point and apologize for not being able to help offhand. grub numbers everything starting at 0, so your first hard drive (as seen by the BOIS) is 0, the second one is 1, third is 2, etc... Same numbering for partitions. - Bluejay Adametz Mind if I smoke? -- Why, are you on fire? -- NOTICE: This message, including any attachments, is only for the use of the intended recipient(s) and may contain confidential and privileged information, or information otherwise protected from disclosure by law. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination or distribution of this message or any of its attachments is strictly prohibited. If you received this message in error, please contact the sender immediately by reply email and destroy this message, including all attachments, and any copies thereof.
Re: New install boot problem -
On 29/01/13 20:40, Trenton Ray wrote: GRUB has a strange methodology (well, strange to me given that I'm one of a handful of neo-luddites still using LILO) for determining disks. It's got root as hd2,0 which means (and I may be mistaken) the 2nd disk, first partition.. which makes sense in accordance with /dev/sdb but since GRUB sees 0 as a value and not a null, maybe change it to 1,0 ? I fear I'm just going to add to the confusing at this point and apologize for not being able to help offhand. Most commonly you'll find that: /dev/sda - hd0 /dev/sdb - hd1 /dev/sdc - hd2 And then with partitions: /dev/sdX1 - hdX,0 /dev/sdX2 - hdX,1 /dev/sdX3 - hdX,2 ... and so forth ... [root@box7 bobg]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd2,0) # kernel /vmlinuz-version ro root=/dev/sdc3 # initrd /initrd-[generic-]version.img #boot=/dev/sdb This line ^^^ can set to /dev/sda if you want GRUB on your MBR of /dev/sda. But remove the leading # default=0 timeout=15 splashimage=(hd2,0)/grub/splash.xpm.gz This looks for the splashimage (background graphics) from /dev/sdb1 ... inside the grub/ directory on this partition. If you mount /dev/sdb1 on /boot ... that means /boot/grub on your file system. hiddenmenu title Scientific Linux (2.6.32-279.19.1.el6.x86_64) root (hd2,0) This expects kernels to be found on /dev/sdb1 kernel /vmlinuz-2.6.32-279.19.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.19.1.el6.x86_64.img title Scientific Linux (2.6.32-279.5.1.el6.x86_64) root (hd2,0) Same here as well. kernel /vmlinuz-2.6.32-279.5.1.el6.x86_64 ro root=UUID=088eabf7-7644-4acb-9017-bc510456357b rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-279.5.1.el6.x86_64.img title Other rootnoverify (hd0,0) chainloader +1 This would typically load Windows or so, installed on /dev/sda1 Hope this helps you understand the drive references a bit better. -- kind regards, David Sommerseth
Re: New install boot problem -
On 29 January 2013 18:49, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote: I've just replaced F-18 with SL-6.3 Live installed but I have to use the flash drive to boot from the hard drive. I believe my error is that it's looking on the wrong drive. How do I fix that? Hi Bob, Perhaps a page in the CentOS wiki [1] will help you. Regards, Alan. [1] http://wiki.centos.org/HowTos/GrubInstallation
Re: New install boot problem -
On 01/29/2013 04:12 PM, Alan Bartlett wrote: On 29 January 2013 18:49, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote: I've just replaced F-18 with SL-6.3 Live installed but I have to use the flash drive to boot from the hard drive. I believe my error is that it's looking on the wrong drive. How do I fix that? Hi Bob, Perhaps a page in the CentOS wiki [1] will help you. Regards, Alan. [1] http://wiki.centos.org/HowTos/GrubInstallation There was a drive /dev/sda that had windows and linux on it, it had been used for boot. After re-installing a couple of times I finally found the problem, simply disabled that drive in the BIOS. Last install leaves me with LVM but I guess I can live with that on this computer for now. Bob -- http://www.qrz.com/db/W2BOD box9 Fedora-18 Linux
