[Bug 928540] New: YaSt internal error: Unknown device /dev/mapper_cr_swap from device_mapping.rb:65
http://bugzilla.opensuse.org/show_bug.cgi?id=928540 Bug ID: 928540 Summary: YaSt internal error: Unknown device /dev/mapper_cr_swap from device_mapping.rb:65 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 632312 --> http://bugzilla.opensuse.org/attachment.cgi?id=632312&action=edit YaST screen shot (German/English) (openSUSE 13.2 is the only Linux in the last 20 years that I was unable install and boot) When trying to install openSUSE 13.2 on a PC that has an old Windows/XP that I want to keep, my first attempt was to try BtrFS and in an encrypted logical volume. However it was not possible to boot the thing after Yast completed installation: Whatever I tried with GRUB2, it almost always ended with "cannot embed". Even with reading lots about it I could not get it to boot. Then I decided to start a-new, using LVM, encrypted swap, and mostly ext3. Again Yast failed to propose a boot configuration (See screenshot and logs). Not even your worst enemies deserve to get GRUB2: It's a terrible hack without proper documentation and diagnostic messages (try LILO if you don't believe), it's terribly slow and a nightmare to configure (vertried to remove or change a menu entry GRUB2 auto-created?). Sorry I had to say that... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928540 --- Comment #1 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 632313 --> http://bugzilla.opensuse.org/attachment.cgi?id=632313&action=edit YaST logs from the installation system -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928540 --- Comment #2 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- "vertried ..." in comment #0 actually means "Have you ever tried ..." (keyboard failure) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928540 --- Comment #4 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Josef Reidinger from comment #3)
1) windows do not let enough space after MBR section of disk ( nowadays it is usuall at least 1MB, but in old days it is often just few KB, so GRUB2 cannot embed stage 2 after MBR
Your message is clear and understandable. That emitted by the tools is not. Can parted fix the "too small gap after MBR", or won't obsolete Windows fail to boot after moving the NTFS partition? I could give that a try.
2) grub2 cannot install stage2 to btrfs due to its implementation that do not provide fixed easily addresable space that BIOS can load
So YaST should say that you cannot boot from BtrFS right now.
Possible sollutions is to use dedicated boot partition or use ext. Concerns about grub2 I cannot address as I work only on its configuration, on other hand if I compare it to LILO it is much more flexible and support more advanced setup ( for LILO we almost always need separated stupid boot with ext2, as for more complex fs it have problems )
I wonder which of these issues is directly related to the encrypted swap partition that caused an internal YaST error ("Unknown device").
So can you please try install latest Tumbleweed installation disk and if it is still problem, upload fresh logs?
I'll try to find the time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928540 --- Comment #5 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Ulrich Windl from comment #4)
(In reply to Josef Reidinger from comment #3)
Possible sollutions is to use dedicated boot partition or use ext. Concerns about grub2 I cannot address as I work only on its configuration, on other hand if I compare it to LILO it is much more flexible and support more advanced setup ( for LILO we almost always need separated stupid boot with ext2, as for more complex fs it have problems )
I wonder which of these issues is directly related to the encrypted swap partition that caused an internal YaST error ("Unknown device").
none, it is bug in yast2-bootloader, see bug#913540 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com