[Bug 827481] New: Installer doesn't reflect changes done to the partition table and puts wrong swap entry into fstab (on RAID 0)
https://bugzilla.novell.com/show_bug.cgi?id=827481 https://bugzilla.novell.com/show_bug.cgi?id=827481#c0 Summary: Installer doesn't reflect changes done to the partition table and puts wrong swap entry into fstab (on RAID 0) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tobiaspotocek@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=546245) --> (http://bugzilla.novell.com/attachment.cgi?id=546245) Yast Installation Log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 During the installation, I canceled proposed partition setup and created my own. The problem was that the installer (probably) didn't notice those changes and put an old entry for swap partition into fstab. See attached Yast2 log, line 2582. There should be /dev/md125p7 instead of /dev/md126p7. My guess is also that this is related to the fact that I'm running OpenSuse on RAID 0 (which hasn't been created by OpenSuse). Reproducible: Always Steps to Reproduce: 1. Start OpenSuse 12.3 installer (on a machine with RAID 0) 2. Go to expert mode in partition setup 3. Delete all proposed partitions and create your own setup 4. Confirm and proceed rest of the installation as usual Actual Results: Wrong swap entry is put into fstab => swap doesn't work.. Another result is that OpenSuse hangs during the startup process trying to mount the missing swap partition until time limit is exceeded, i. e. the boot up process is very slow. That was the original symptom which lead to this discovery. Expected Results: Swap should be properly configured -- 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#c1 --- Comment #1 from Tobiáš Potoček <tobiaspotocek@gmail.com> 2013-06-29 11:57:58 UTC --- Additional result: the wrong entry is not only put to the fstab file, but also to the grub resume parameter. It has to be fixed as well to get hibernate working. -- 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#c FeiXiang Zhang <fxzhang@suse.com> 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#c2 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com AssignedTo|yast2-maintainers@suse.de |fehr@suse.com --- Comment #2 from Thomas Fehr <fehr@suse.com> 2013-07-09 12:11:36 UTC --- Reassigned to maintainer of yast2-storage -- 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 <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |tobiaspotocek@gmail.com --- Comment #3 from Thomas Fehr <fehr@suse.com> 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#c4 --- Comment #4 from Tobiáš Potoček <tobiaspotocek@gmail.com> 2013-07-10 20:43:55 UTC --- Created an attachment (id=547480) --> (http://bugzilla.novell.com/attachment.cgi?id=547480) Yast Installation Log (more) These are all y2log-* files I was able to find in /var/log/YaST2. If you need it I can pack the whole folder. -- 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 <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|tobiaspotocek@gmail.com | --- Comment #5 from Thomas Fehr <fehr@suse.com> 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#c6 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Thomas Fehr <fehr@suse.com> 2013-07-11 15:21:05 UTC --- Fixed in openSuSE:Factory -- 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 <tobiaspotocek@gmail.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com