[Bug 825172] New: Booting live USB for 13.1M2 fails on a UEFI box (Copy-on-write problem?)
https://bugzilla.novell.com/show_bug.cgi?id=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c0 Summary: Booting live USB for 13.1M2 fails on a UEFI box (Copy-on-write problem?) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Live Medium AssignedTo: coolo@suse.com ReportedBy: nrickert@ameritech.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I prepared a USB with the live Gnome image for 13.1M2, using ImageWriter (from opensuse 12.3). I booted as a UEFI boot. The GUI never came up. On a retry, the USB was unbootable. It appears that a CoW partition was created, and creating it destroyed the boot structure on the USB. Full details are given in a forum post: https://forums.opensuse.org/english/get-technical-help-here/pre-release-beta... See comments 21 and 22. Note that "fdisk" output is given there. The CoW partition seems to have been placed where it overwrites the boot structure, instead of it being placed in the unused 2G of space at the end of the USB. I retested using the live KDE, this time written to the USB with "dd_rescue". The results were similar. It did not boot to a GUI, and the USB was unbootable afterwards. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c1 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |ms@suse.com Severity|Major |Critical --- Comment #1 from Stephan Kulow <coolo@suse.com> 2013-06-17 03:29:08 CEST --- unbootable sounds critical to me. Marcus, this is hybridpersistance with overlayfs - I'm out :) -- 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=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c2 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Marcus Schaefer <ms@suse.com> 2013-06-17 03:58:26 UTC --- I can reproduce the bogus partition table, will try to fix this now btw, this is not related to the move from clicfs to overlayfs. I would say this case efi+persistent-writing was just not tested well enough -- 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=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c3 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #3 from Marcus Schaefer <ms@suse.com> 2013-06-17 08:48:10 UTC --- I fixed it: commit 796f274687db272f299429bf2290696d66a3adbd Author: Marcus Schäfer <ms@suse.de> Date: Mon Jun 17 16:46:00 2013 +0200 - fixed creation of iso persistent write partition (bnc #825172) * fixed detection of cylinder count for isohybrid tables * use isohybrid EFI bootable image by default, the partition table written in this case allows standard partition device (e.g /dev/sda1) for EFI and protective MBR thus works in both worlds correctly and allows the creation of additional partitions without problems * don't use a fixed partition number, use the next one free * always create a filesystem on the write partition with the 'hybrid' label, even if the used overlay technique does not urgently requires this. The label helps to identify the write device on reboot * use parted instead of fdisk. fdisk is not suitable when adding partitions to the GPT, use kiwi's createPartitionerInput method * fixed clicfs cow file check, check clicfs only if clicfs is used, with the move to overlayfs there is a choice now * search for persistent write partition by a blkid label search and don't actually mount/umount the partition by label * syslinux >= 4.04 is required to make all this work correctly -- 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=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c4 nilguy solz <mahindra11@yandex.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mahindra11@yandex.com --- Comment #4 from nilguy solz <mahindra11@yandex.com> 2013-06-21 06:02:04 UTC --- also facing similar issue live milestone gnome image 13.1 doesn't boot n didnt booted as uefi boot but facing similar issue it made my usb unbootable.......... -- 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=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c5 --- Comment #5 from Neil Rickert <nrickert@ameritech.net> 2013-06-21 09:41:56 UTC ---
but facing similar issue it made my usb unbootable
This problem was discovered too late for M2. You can wait for M3 and test whether the fix works. I'll be doing that. If you are looking for a workaround, then check Dale's post at the forum: https://forums.opensuse.org/english/get-technical-help-here/pre-release-beta... I have tested that, and it works. I made a live Gnome USB. I then used "fdisk" to create two additional partitions (partition 3 and partition 4). To do that you must be careful to tell fdisk to start the new partition after the current one. Don't accept the default of it being before partition 1. I made partition 3 minimal (2047 sectors), and partition 4 the rest of the USB. I formatted partition 4 as "ext4". The idea of the additional partitions is to fill the partition table, so that a desctructive partition cannot be created. I have booted this USB twice on a UEFI box and twice on a non-UEFI box, just to test that it does not self-destruct. -- 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