Hardware freezes on Dell Optiplex 320 while booting (https://bugzilla.redhat.com/show_bug.cgi?id=499204)
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot at GRUB (FAILS)
Boot centos 5.5 x86_64 install drop to shell and chroot (WORKS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches centos 5.5 grub (WORKS)
Compiled and installed grub package from fedora 13 on centos 5.5 x86_64 same problem. (FAILS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On Wed, Jul 28, 2010 at 12:45 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
If I understand the situation correctly, you can boot Fedora13 without any extra steps. Then, can you add a stanza for CentOS in the F13's grub.conf file and boot from there? Or use chainloader if CentOS has grub installed in its partition.
Akemi
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Wednesday, July 28, 2010 15:57 To: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 while booting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
On Wed, Jul 28, 2010 at 12:45 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk
layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
If I understand the situation correctly, you can boot Fedora13 without any extra steps. Then, can you add a stanza for CentOS in the F13's grub.conf file and boot from there? Or use chainloader if CentOS has grub installed in its partition.
Sounds like a plan. I will learn how to do that, and follow up within the week. Thanks.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
Jason Pyeron wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot at GRUB (FAILS) Boot centos 5.5 x86_64 install drop to shell and chroot (WORKS) Boot fedora 13 isolinux disc, choose boot hard disk, launches centos 5.5 grub (WORKS)
Compiled and installed grub package from fedora 13 on centos 5.5 x86_64 same problem. (FAILS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
Let me get this straight: you've installed CentOS 5.5? Have you checked /boot/grub/device.map, so that it looks something like ################# # this device map was generated by anaconda (hd0) /dev/sda ################# Do you have a /boot/grub/grub.conf?
mark
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of m.roth@5-cent.us Sent: Wednesday, July 28, 2010 16:11 To: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 while booting (https://bugzilla.redhat.com/show_bug.cgi?id=499204)
Jason Pyeron wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot
at GRUB (FAILS)
Boot centos 5.5 x86_64 install drop to shell and chroot (WORKS) Boot fedora 13 isolinux disc, choose boot hard disk,
launches centos 5.5
grub (WORKS)
Compiled and installed grub package from fedora 13 on
centos 5.5 x86_64
same problem. (FAILS)
Boot fedora 13 isolinux disc, choose boot hard disk,
launches newer grub
installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk
layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
Grub conf fine, take HD out and put in machine with different bios all is fine.
Let me get this straight: you've installed CentOS 5.5? Have you checked /boot/grub/device.map, so that it looks something like ################# # this device map was generated by anaconda (hd0) /dev/sda ################# Do you have a /boot/grub/grub.conf?
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
Jason Pyeron wrote:
[mailto:centos-bounces@centos.org] On Behalf Of m.roth@5-cent.us Jason Pyeron wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot
at GRUB (FAILS)
<snip>
Grub conf fine, take HD out and put in machine with different bios all is fine.
<snip> Hmmm... I can't remember if I mention this a day or two ago, but have you checked the BIOS for a funky setting - maybe under "advanced" or "integrated peripherals", to see if it's got a setting for... oh, was it SATA mode that I had the problem with? See if there's such a thing, and if so, change it to RAID instead of IDE.
mark
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of m.roth@5-cent.us Sent: Wednesday, July 28, 2010 17:20 To: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 while booting (https://bugzilla.redhat.com/show_bug.cgi?id=499204)
Jason Pyeron wrote:
[mailto:centos-bounces@centos.org] On Behalf Of m.roth@5-cent.us Jason Pyeron wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot
at GRUB (FAILS)
<snip> > Grub conf fine, take HD out and put in machine with different bios all > is fine. <snip> Hmmm... I can't remember if I mention this a day or two ago, but have you checked the BIOS for a funky setting - maybe under "advanced" or "integrated peripherals", to see if it's got a setting for... oh, was it SATA mode that I had the problem with? See if there's such a thing, and if so, change it to RAID instead of IDE.
The BIOS has almost no settings to change, and those that do exist have been toggled.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On Wed, Jul 28, 2010 at 3:45 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot at GRUB (FAILS)
Boot centos 5.5 x86_64 install drop to shell and chroot (WORKS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches centos 5.5 grub (WORKS)
Compiled and installed grub package from fedora 13 on centos 5.5 x86_64 same problem. (FAILS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
What does "FAILS" actually mean? I assume that you are only getting to the grub menu when booting from an F13 CD and chainloading to the CentOS grub.
If my assumption about the grub menu is correct, one of your grub stages must be broken. Have you tried re-installing grub with grub-install or at the grub cli?
What is the output of "fdisk -l", "cat /etc/fstab", and "cat /boot/grub/device.map"?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tom H Sent: Wednesday, July 28, 2010 16:55 To: centos@centos.org Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 while booting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
On Wed, Jul 28, 2010 at 3:45 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Steps tried:
Install from centos 5.5 x86_64 disc, locks up after reboot at GRUB (FAILS)
Boot centos 5.5 x86_64 install drop to shell and chroot (WORKS)
Boot fedora 13 isolinux disc, choose boot hard disk,
launches centos
5.5 grub (WORKS)
Compiled and installed grub package from fedora 13 on centos 5.5 x86_64 same problem. (FAILS)
Boot fedora 13 isolinux disc, choose boot hard disk, launches newer grub installed on centos (WORKS)
Installed fedora 13 x86_64 default settings for disk
layout. (WORKS)
https://bugzilla.redhat.com/show_bug.cgi?id=499204
Looking for advice on getting this hardware to boot unattended.
What does "FAILS" actually mean? I assume that you are only getting to the grub menu when booting from an F13 CD and chainloading to the CentOS grub.
Thanks for your debugging steps, this has already been confirmed as a BIOS / grub bug with this dell see the subject for your answer.
I am currently trying to make a workaround which is not invasive on the system or procedure.
If my assumption about the grub menu is correct, one of your grub stages must be broken. Have you tried re-installing grub with grub-install or at the grub cli?
What is the output of "fdisk -l", "cat /etc/fstab", and "cat /boot/grub/device.map"? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On Wed, Jul 28, 2010 at 5:08 PM, Jason Pyeron jpyeron@pdinc.us wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tom H Sent: Wednesday, July 28, 2010 16:55 To: centos@centos.org Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 while booting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
What does "FAILS" actually mean? I assume that you are only getting to the grub menu when booting from an F13 CD and chainloading to the CentOS grub.
If my assumption about the grub menu is correct, one of your grub stages must be broken. Have you tried re-installing grub with grub-install or at the grub cli?
What is the output of "fdisk -l", "cat /etc/fstab", and "cat /boot/grub/device.map"?
Thanks for your debugging steps, this has already been confirmed as a BIOS / grub bug with this dell see the subject for your answer.
I am currently trying to make a workaround which is not invasive on the system or procedure.
You're welcome. I am sorry. I didn't have the time to read the bug url yesterday. I now have - and have googled away... Amazing!
There seem to be two solutions, replace grub with lilo or grub2, neither of which conform to your "not invasive on the system or procedure" requirement.
Akemi Yagi suggested that you install F13 and chainload CentOS. It sounds nuts but it seems like the right solution to avoid messing with your default CentOS install - F13 as a bootloader (!). It reminds me of a colleague who has a Mac and keeps a minimal OSX install to boot F12 because he couldn't get F12 to work as a single-boot OS.
On Thu, Jul 29, 2010 at 1:27 PM, Tom H tomh0665@gmail.com wrote:
There seem to be two solutions, replace grub with lilo or grub2, neither of which conform to your "not invasive on the system or procedure" requirement.
Akemi Yagi suggested that you install F13 and chainload CentOS. It sounds nuts but it seems like the right solution to avoid messing with your default CentOS install - F13 as a bootloader (!). It reminds me of a colleague who has a Mac and keeps a minimal OSX install to boot F12 because he couldn't get F12 to work as a single-boot OS.
I myself have one desktop machine that refuses to cooperate with grub (or should I say grub refuses to cooperate with the hardware?). Long story short, I installed lilo and decided not to spend more time on the problem. The machine has been running fine for years... :)
Akemi
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Thursday, July 29, 2010 16:39 To: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320 whilebooting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
On Thu, Jul 29, 2010 at 1:27 PM, Tom H tomh0665@gmail.com wrote:
There seem to be two solutions, replace grub with lilo or grub2, neither of which conform to your "not invasive on the system or procedure" requirement.
Akemi Yagi suggested that you install F13 and chainload CentOS. It sounds nuts but it seems like the right solution to avoid
messing with
your default CentOS install - F13 as a bootloader (!). It
reminds me
of a colleague who has a Mac and keeps a minimal OSX install to boot F12 because he couldn't get F12 to work as a single-boot OS.
I myself have one desktop machine that refuses to cooperate with grub (or should I say grub refuses to cooperate with the hardware?). Long story short, I installed lilo and decided not to spend more time on the problem. The machine has been running fine for years... :)
Is there a yum way of installing lilo? Will it work with the devicemapper? (assumption is no)
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On Thu, Jul 29, 2010 at 2:31 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Is there a yum way of installing lilo? Will it work with the devicemapper? (assumption is no)
You can find some lilo-related information in this Forum thread:
https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_i...
I understand device-mapper support (partial?) was added to lilo some time ago but do not know the details.
Akemi
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Thursday, July 29, 2010 18:09 To: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320whilebooting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
On Thu, Jul 29, 2010 at 2:31 PM, Jason Pyeron jpyeron@pdinc.us wrote:
Is there a yum way of installing lilo? Will it work with
the devicemapper?
(assumption is no)
You can find some lilo-related information in this Forum thread:
https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_i... forum=37
Should I assume that updating lilo after kernel upgrades will be manual?
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On Jul 29, 2010, at 5:31 PM, "Jason Pyeron" jpyeron@pdinc.us wrote:
Is there a yum way of installing lilo? Will it work with the devicemapper? (assumption is no)
As long a LILO can boot the kernel off /boot and /boot is a Linux or MDRAID partition all the device-mapper related stuff will be done within the initrd.
As far as mirrored /boot is concerned, if LILO is set to look in that partition and it's file system is ext2/3 it can grab the kernel file. It's read-only during boot and the mdraid meta-data is kept at the end of the partition, so it should look and behave as a normal ext file system.
-Ross
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Ross Walker Sent: Thursday, July 29, 2010 18:22 To: CentOS mailing list Cc: CentOS mailing list Subject: Re: [CentOS] Hardware freezes on Dell Optiplex 320whilebooting(https://bugzilla.redhat.com/show_bug.cgi?id=499204)
On Jul 29, 2010, at 5:31 PM, "Jason Pyeron" jpyeron@pdinc.us wrote:
Is there a yum way of installing lilo? Will it work with
the devicemapper?
(assumption is no)
As long a LILO can boot the kernel off /boot and /boot is a Linux or MDRAID partition all the device-mapper related stuff will be done within the initrd.
As far as mirrored /boot is concerned, if LILO is set to look in that partition and it's file system is ext2/3 it can grab the kernel file. It's read-only during boot and the mdraid meta-data is kept at the end of the partition, so it should look and behave as a normal ext file system.
My /boot is just a plain jane ext3, first problem overted...
Thanks
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
At Thu, 29 Jul 2010 18:22:07 -0400 CentOS mailing list centos@centos.org wrote:
On Jul 29, 2010, at 5:31 PM, "Jason Pyeron" jpyeron@pdinc.us wrote:
Is there a yum way of installing lilo? Will it work with the devicemapper? (assumption is no)
As long a LILO can boot the kernel off /boot and /boot is a Linux or MDRAID partition all the device-mapper related stuff will be done within the initrd.
As far as mirrored /boot is concerned, if LILO is set to look in that partition and it's file system is ext2/3 it can grab the kernel file. It's read-only during boot and the mdraid meta-data is kept at the end of the partition, so it should look and behave as a normal ext file system.
The only 'tricky' bit is making sure that the LILO MBR stuff is 'mirrored' -- you just need to duplicate /etc/lilo.conf, changing disk to install lilo on (this is what I use -- I mirror /dev/sdaN with /dev/sdbN):
sed s/sda/sdb/g </etc/lilo.conf >/etc/lilo.conf-b /sbin/lilo -C /etc/lilo.conf /sbin/lilo -C /etc/lilo.conf-b
Actually, I don't think lilo cares what file system /boot is. Unlike grub, it does not even look at the 'file system' information at all. The lilo 'installer' (the program that runs on the running Linux system), just grabs the LBAs (used to convert to CHS) of the physical data blocks of the files (/boot/vmlinuz... and /boot/initrd...) and stores these addresses someplace, and stores the LBAs (used to convert to CHS) of where this infor is stored in the MBR. Lilo's boot loader just does low-level BIOS disk reads to read what it needs to read, using this raw LBAs (used to convert to CHS) info. Lilo is *simple* and *primitive* and is not bogged down trying to be clever.
MD's RAID works at the physical disk I/O level, so the all of the disks in a RAID1 mirror set have the same data at the same physical disk locations (same LBAs).
-Ross
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Akemi Yagi -
Jason Pyeron -
m.roth＠5-cent.us -
Robert Heller -
Ross Walker -
Tom H