https://bugzilla.novell.com/show_bug.cgi?id=774400
https://bugzilla.novell.com/show_bug.cgi?id=774400#c1
--- Comment #1 from Neil Rickert 2012-08-03 15:12:32 UTC ---
Here's a bit more detail.
The problem started on the first boot after install. The boot hung at:
"Creating device nodes with udev"
I waited for a while, with nothing happening and no disk activity. I then had
to force a power off.
On resume, I removed "splash=silent quiet" from the kernel line, as in the main
bug report. I wanted to see what was happening.
I was not prompted at all. No prompt for the key for either swap or "/home".
However, boot proceeded, and Yast started up to complete the install.
Part way through, Yast warned that "/home" was not mounted. I used CTL-ALT-F2
to get a command line, and I manually unlocked "/home". I tried to then mount
"/home", but an error message said that it was already mounted. So presumably
there was a background process running that was trying to mount, but could not.
CTL-ALT-F7 got me back to Yast, which completed the final install stages. I
then logged into KDE. Using an "xterm", I also unlock swap and did "swapon -a"
to add the swap.
I then ran "mkinitrd".
Everything now works, unless I try to repeat the problem of the initial bug
definition.
I have not tried to reproduce the boot hang, as I would probably have to do a
complete reinstall to get the appropriate conditions.
My guesses about that boot hang:
1) It could be an accidental glitch that will never happen again.
2) It could be because I also have an encrypted LVM on that disk, and the
installer insists on adding that to "/etc/crypttab" even though it is not
needed for the 12.2 RC1 running system.
3) The may have been a problem in the "initrd" generated during install.
My best guess is that it is (3), perhaps compounded by (2). I'll note that the
plymouth screen never started up during that initial boot, which probably
explains why I saw that "udev" message (it should have been hidden).
There does seem to be a problem with the initial creation of "initrd". It
apparently decides what to put in "initrd" based partly on what is currently
running. And when the first "initrd" is created, the install DVD is what is
running. So the crypto for swap/resume never made it into to the initial
"initrd", but did make it into the "initrd" that I regenerated after login.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.