https://bugzilla.novell.com/show_bug.cgi?id=827481 https://bugzilla.novell.com/show_bug.cgi?id=827481#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=827481 https://bugzilla.novell.com/show_bug.cgi?id=827481#c3 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |tobiaspotocek@gmail.com --- Comment #3 from Thomas Fehr 2013-07-09 12:20:13 UTC --- The log you attached contains only what was logged after first reboot of the newly installed system. The older logs are normally in /var/log/YaST2/y2log-*.gz. These would contain what was done and proposed during installation stage. Please attach full content of /var/log/YaST2 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=827481 https://bugzilla.novell.com/show_bug.cgi?id=827481#c5 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|tobiaspotocek@gmail.com | --- Comment #5 from Thomas Fehr 2013-07-11 15:20:09 UTC --- Thanks, that one was really tricky to debug. Source of problems is that /dev/md126 and /dev/md125 switch after install. The raid /dev/md126 during installation is accessible as /dev/md125 after install and vide versa. The happens sometimes and normal hint is to not rely in md numbers to be stable. This normally does not matter much since we use the id links in /etc/fstab by default (names for md partitions like e.g. /dev/disk/by-id/md-uuid-....-part..) which are not dependend on unstable raid numbering. For some reason yast2 decided to use /dev/md126p7 instead of /dev/disk/by-id/md-uuid-57da3bec:d363c92f:6ffa7028:4ae64adc-part7 in /etc/fstab and this was the cause of the problem. I did now numerous installations on raid setups like you had, but was unable to reproduce the problem until a had a quite close look at your y2log-3. You activated encryption for the swap partition (probably inadvertently) and deactivated it again afterward. Encryption is not compatible with using mount-by-id, so yast reverted to using the real device name in /etc/fstab. The bug was that it did not undo this setting after you switched encryption off again. So it still used real device name instead if by-id-name in /etc/fstab even after encryption for swap was switched off which lead, in combination with instable raid numbering, to problem setting up swap in your system. So best would be to simply use /dev/disk/by-id/md-uuid-57da3bec:d363c92f:6ffa7028:4ae64adc-part7 in /etc/fstab for you swap partition. The bug is of coruse fixed for upcoming 13.1. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=827481 https://bugzilla.novell.com/show_bug.cgi?id=827481#c7 --- Comment #7 from Tobiáš Potoček 2013-07-11 22:08:09 UTC --- Wow, I don't even remember doing something around swap and encryption. But it's good you managed to find the problem and fix it. -- 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.