Bug 172975 - blank screen and blinking curser when rebooted
blank screen and blinking curser when rebooted
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: grub (Show other bugs)
4.0
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Peter Jones
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-11 13:49 EST by marcel elias
Modified: 2011-07-27 14:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-07-27 14:03:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description marcel elias 2005-11-11 13:49:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921

Description of problem:
We have clients with approximately 300 servers.  They recently upgraded 10 of the nodes to RHEL AS4 u2 64bit.  The problem we are seeing is that when these servers are rebooted or there is a power failure, they will lose there mbr or get a corrupted grub.  The servers are dual Opteron, 4gb ram and 2 scsi hdd attached to an LSI 20320 scsi controller.  The drives are software raid0.  The partitions are as follows. swap is software raid0 1024, /boot is a physical raid0 volume comprised of software raid0, and / is software raid 0.  The current RHEL 3 machines are fine and can be rebooted all week long and do not exhibit this behavior and have been in production for quite a while with no issues.  The RHEL4 machines with the 2.6 kernel do however.  The machines must be network booted and the grub rescued.  The machine does not do this every reboot, but will do it eventially.  I currently have a unit from the farm in house and will be conducting some testing as well to see if this can be pinpointed.  Any help from anyone would be appreciated.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.install rhel4.
2.start rebooting machine
3.rescue grub
  

Actual Results:  Once I rescued grub everything works fine.  Problem is that the grid resides on the rhel4 nodes and can not for any reason be required to be rescued.

Additional info:
Comment 1 marcel elias 2005-11-11 17:15:06 EST
I have recieved word from the client that the /boot partition is 300mb software
raid1 and NOT a raid0 physical lvm volume.

Note You need to log in before you can comment on or make changes to this bug.