http://bugzilla.opensuse.org/show_bug.cgi?id=916014 --- Comment #2 from Darren Freeman --- Notes from installing 12.3. Written as a journal so you can see my thoughts along the way. Assume there are other users going through this. First, there were three RAIDs detected by the installer, not two. The USB drive came up as its own array with a single spare disc. I used the command line to re-add it to the array it should have been added to, and it didn't need a resync. I figured at this point that it was safer to restart the installation and have it detect the correct number of arrays. Nope. Same thing, the USB drive is not part of the array, it's an extra array on its own. So try again this time unplugging it. Will have to re-add it after autodetection of the drives, pray for a fast resync. Third time, got all the way to ready to install, then from virtual console I added the USB drive back into the array, then ran the install. Minor wrinkle, still overall very smooth. One thing that I noticed is that when I was editing the mount-points of the logical volumes, the screen displayed which volume I was configuring. On the 13.x series I think this has been removed, so you have to remember which one you're editing. To whomever tries to replicate, see if 13.x displays the name of the LVM volume on the same screen as when you're entering the mount-point. However grub2 is not starting :/ This happened once on 13.1 and it's probably because I left it at "boot from MBR" instead of "custom partition" /dev/sda .. fix that from rescue.. Nope. We are simply not going to boot. Flashing cursor on top-left of screen is all I get. Suspect it's because the older grub2 can't deal with RAID1 on 1.x superblock. Try again.. zero /dev/sda1 and mount ext4 directly onto it as /boot. (This is how my working 12.2 install on the other server is set up.) Bootloader install into /dev/sda. I'm now pulling in some updates to 12.3. I note that you have just announced the end of maintenance for 12.3, which is not good news to anyone who can't get the 13.x series to boot. I also note that in text mode, the online update component of yast2 doesn't flag that some of the updates are to package management until after you've spent several minutes selecting the ones you want. At this point it's easier to say I'll install them all together rather than going back and manually figuring out which ones it wants you to install first. (This could be why yast2 died on my 13.1 install.) The Qt version instead filters them and shows you the ones you should do first, restarts, and then shows you the rest. Aaaand do we boot? Nope. Flashing cursor. What is going on now. Try again with boot from /boot partition. Still nothing. It occurs to me that /sda might not be what the BIOS is trying to boot from. Yeah, that had something to do with it. Turns out I can't enable booting from USB flash drive and not also have booting from the external USB drive, with unknown boot code on it. Unplug both. Grub works. System asks for unlock password. System boots. FINALLY! So apart from some BIOS confusion, 12.3 is basically working out of the box for LVM2 + crypto + RAID. I can't say whether the updates were needed, or all the extra mucking around with changing the /boot from RAID to raw partition, but I'd say not. My recollection is that this version *just* *works*. (Although I'm probably thinking of 12.2 since I think I skipped 12.3) Which is to say, 13.x are hideously broken for power users. There is a major regression waiting for people to find as they upgrade once-working systems. Now for some post-install clean up.. the remaining on-line updates, and I wish to have my /boot on a mirror in case the first drive should fail someday. I will post an update with what I find. I would be keen to update to 13.2 but first I need to hear some feedback about what went wrong. In three weeks I will be able to rebuild this machine again, but right now I need it working and I am way over my time budget. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916014 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |trenn@suse.com --- Comment #4 from Jiri Srain --- Please, don't mix multiple issues in a single bugreport - it makes it hard to handle then. I'm taking following as the most severe issue with 13.2: * 13.2 won't boot. It says it is waiting on a certain UUID to appear, which I guess is the logical volume for root. It will never appear. Some clever individual has decided that there should be no time-out, so it waits forever and you don't get a shell. Thomas, please, check whether it is a problem of dracud or something else, since it is what I see preventing the boot. Darren, feel free to create additional bugs for other issues you reported, thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916014 http://bugzilla.opensuse.org/show_bug.cgi?id=916014#c6 --- Comment #6 from Darren Freeman --- Well, my server is dead. Half way through the upgrade to Tumbleweed, I came into the room, saw the screen blanked, and hit enter. And it was at a prompt that said, "Abort, retry, ignore? [a/r/i] (a):" Well that sucks. It had stopped with the error, "Error: Subprocess failed. Error: RPM failed: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)" So now I'm getting errors that it can't cache the RPM database. zypper won't do anything. Lucky I have a backup of 13.1, the last time it would boot. 13.2 is truly terrible, as is Tumbleweed from the looks of it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916014 http://bugzilla.opensuse.org/show_bug.cgi?id=916014#c8 --- Comment #8 from Darren Freeman --- I tried to complete the upgrade, but in the end, I couldn't complete "zypper verify". It insisted on removing packages that were not installed, and it didn't offer to install packages that, according to rpm -Va, were missing. I had no idea how to get zypper's view of the system consistent with that of rpm. I restored my backup of 13.1. After a lot of effort with grub2 not working, I switched to grub 1, and it booted. Then I upgraded to 13.2 with OBS Kernel:stable. Then I switched to grub 2, which works perfectly. I still have the problem of not being asked for a password on boot. It sits there for a few minutes before dropping to an emergency shell. I don't need to boot failsafe, I can enter the two lines of magic to access /dev/system/root. Then when I exit, the system finishes booting. So I can boil all of this down to the following statement: On a completely up-to-date 13.2, upgraded from 13.1, with root on LVM on LUKS, Dracut will not prompt for a password. It was working on 13.1. This is a regression. I also have another machine with a fresh 13.2 install that is doing the same thing. I believe I have also had this happen on a third system. I think this is 100% reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916014 Björn Voigt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjoernv@arcor.de -- You are receiving this mail because: You are on the CC list for the bug.