Red Hat Bugzilla – Bug 112232
After install, system does not reboot
Last modified: 2007-11-30 17:06:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
Description of problem:
After the Red Hat 2.1 AS QU3 installation on a Bladecenter was
completed, the following text was displayed on the screen.
The blade never rebooted on its own after the install.
Apparently this occurs while any USB based filesystems are mounted;
an endless loop waiting for the filesystem to respond to the unmount
Unable to reproduce with RHL 9.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install AS 2.1 Update 3 on system using USB CDROM such as
Actual Results: Requires manual hardware reset.
Expected Results: System reboots.
At that point, everything looks unmounted -- /mnt/source should be the
last one that gets unmounted. Did this happen with U2? What are the
USB filesystems being mounted for?
Yes this was reproduced with U2. The USB CD-ROM is mounted for the
installation and does appear to be unmounted. However, the system
does not reboot.
Can you switch ttys at this point? If so, is there anything odd on
tty4? Can you get the output of Alt+SysRq+T?
Looks like it's not an anaconda bug since a similar hang can be
1. Mount USB CD-ROM
2. Attempt to reboot by executing init 6
3. Server will stop at "Unmounting filesystems" message.
Manual reset of the server is required.
ok not a regression "just" a normal bug
Has anyone at Red Hat been able to reproduce this on a blade?
I did find a possible workaround:
At the end of the installtion, at the "Finished" screen, I switched
to tty2 and ran "umount /mnt/source". I switched back to the GUI
screen, and clicked "Finished". System did not reboot and last
message seen was "Ejecting /tmp/cdrom"
I reinstalled and this time I ran these commands at the "Finished"
System did reboot, but CD was left in the CDROM.
fixed in u5 beta.