Description of problem:
Version-Release number of selected component (if applicable):
RHEL Server beta.
When executed on the physical machine, the installer always hangs in early stages of installation. The exact step where it happens varies: it can be as early as on "waiting devices to intialize" or more often when the first (with logo only) or second graphical screen comes out, in one case the installation proceeded as far as till next screen after device selection.
In one case I observed the bunch of error messages mentioning aacraid. The problem may be related to Adaptec 5405Z RAID controller that is used in this server. This controller works without any issues with RHEL 5 server edition.
I am not aware which component contributes to the crash, it may or may not be anaconda. The installer maybe should do something else than hanging silently.
The same DVD disk works well when installed into virtual machine on the same server.
Can you please attach the exact error messages you are seeing? These are in /tmp/syslog, which you can get to from tty2 when anaconda is running.
This bug goes away when I use a floppy with the Adaptec drive during installation.
(In reply to comment #3)
> This bug goes away when I use a floppy with the Adaptec drive during
A floppy? Can you be a bit more precise, you mean when you attach a floppy drive
to the system in question / insert a floppy into an already present / ... ?
Please don't leave us guessing things like this, but try to describe what you are doing, what you are seeing as a result and what you would have expected to see in as much detail as possible.
And we would still like that /tmp/syslog file.
I have attached the USB floppy containing aacraid driver while I know RHEL should have its own. I attached it before powering the server up so it was present during all booting and installation process. The floppy was active time to time (emitting sounds). With that floppy attached, the installation seems passing further but it hang immediately after message "partitioning changes will be written to the disk" and next time when checking the filesystems (the progress bar was running back and forward for some time when it stopped).
That do you mean as "tty2" ? Do you want me to connect null modem cable and try to talk using serial console?
Do you have any startup parameter - switch to force the installation in text and not in GUI mode? Maybe this could help?
Yesterday I tried more attempts with the USB floppy attached. The installer than passes the partitioning screen but reliably hangs when it starts scanning filesystems for consistency.
Please provide more details or web link on how to get "tty2" access during installation. I never did this before.
Yes we have an startup parameter called "text", note it is better to use "vnc" and then connect to the install with vnc, as text installs are very limited in functionality.
To get to tty2 press ctrl + alt + f2 all together.
When you say you've "attached the USB floppy containing aacraid driver", may I ask how you put the driver on the floppy and where you got this specific driver from ?
Adaptec 5405Z was sold together with the driver CD. After I booted from this CD into some kind of specific OS, one of the GUI options was "create a driver floppy". There is no floppy drive on the server (Supermicro 5016-MTFB, single quad core CPU, 24 Gb RAM, four 1 Tb hard drives attached to 5405Z, no other hard drives) so I attached external USB floppy drive and the tool wrote something in it. Deciding from the sound, the floppy driver is active during the installation.
Without floppy drive with this driver disk attached the installation usually hangs on the first screen with company logo only, at times even earlier. With drive it may proceed as far as till checking the filesystems but in some cases also hangs earlier.
I am not sure how probable is that just the installer is somehow unstable in a complex way that is influenced by the floppy present. Also it may be that we have the combination of the two bugs.
Can you please collect kernel messages from the system ? For example by having a serial console attached (and passing the console=.... argument for such when starting the installer) and logging the messages being send to the serial port.
Or by doing a vnc install and trying to get /tmp/syslog from tty2, but chances
are the hang is such that even tty2 will no longer function.
Created attachment 415500 [details]
Contents of /tmp and listing of /dev after Anaconda hang
Switching to console worked and I was able to copy contents of all /tmp folder plus the listing of /dev directory. Hope this will help.
Thanks for the logs, I'm afraid I see nothing special in the logs.
Can yuo try again, and when the installer hangs, switch to tty2 and do:
ps axf > ps.log
And attach ps.log here.
Also try running "top" from tty2 and see if there is some process using a lot
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
If you can provide the information requested in comment 11, please attach and reopen the bug.