https://bugzilla.novell.com/show_bug.cgi?id=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c2 Jason Craig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |os-dev@jacraig.com --- Comment #2 from Jason Craig 2013-09-23 19:42:50 UTC --- I get same thing from both KDE and GNOME i686 live USB. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c4 Ricardo Varas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ricardoivaras@gmail.com --- Comment #4 from Ricardo Varas 2013-09-27 19:26:32 UTC --- I just downloaded KDE Beta 1 and I believe I'm facing the same bug. I used the dd command to copy the iso into my 1GB USB and after the first attempt to run the Live session or Install, it happens just like Neil R. is reporting. After that, the USB will never be recognized as bootable and will mount as "hybrid". -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c6 --- Comment #6 from Jason Craig 2013-10-07 17:24:27 UTC --- (In reply to comment #5)

I verified the downloaded image file (though "only" with the KTorrent data check, not sure if that's quite as reliable as md5 or sha).

I verified all my downloads against the supplied sha1 as well as the signature. Also if it helps, the x86_64 KDE did work for as normal, didn't try GNOME. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c8 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |ms@suse.com --- Comment #8 from Stephan Kulow 2013-10-08 06:03:42 CEST --- Marcus, I hope you can have a quick look to fix this ship stopper for 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c10 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@suse.com |snwint@suse.com --- Comment #10 from Marcus Schaefer 2013-10-08 10:13:30 UTC --- Well I would say the isohybrid tool on 13.1 is broken for 32bit See the following simple test: qemu-img create mydisk 2G 32bit image ===============> dd if=openSUSE-Factory-KDE-Live-Build0725-i686.iso of=mydisk conv=notrunc parted -m -s mydisk print Error: Invalid partition table - recursive partition on /root/mydisk. Sector size (logical/physical): 512B/512B BAD ! 64bit image ===============> dd if=openSUSE-Factory-KDE-Live-Build0725-x86_64.iso of=mydisk conv=notrunc parted -m -s mydisk print BYT; /root/mydisk:2147MB:file:512:512:msdos:; 1:2091kB:6285kB:4194kB:::type=ef; 2:6285kB:956MB:950MB:::boot, type=83; GOOD ! So it's not kiwi it's isohybrid. The broken partition table is the reason why the setup of the hybrid partition failed and why the numbering of partitions is invalid which caused many bad after effects up to the point that booting further is not possible anymore So far kiwi just trusts the result of isohybrid, maybe we should add a check if the written partition table can be read by parted so that we notice this hybrid iso is broken before use anyway I suggest to first fix isohybrid assigning to Steffen -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c12 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |snwint@suse.com --- Comment #12 from Marcus Schaefer 2013-10-08 19:27:20 UTC --- that's right, so I was able to reproduce the problem when building a 32bit iso without efi support. I have no idea why we build the 32bit iso without efi support ? anyway without efi isohybrid is called as follows: EXEC [/usr/bin/isohybrid --offset 0 --id 0x472ef954 --type 0x83 /tmp/mytest/iso-vmxFlavour/LimeJeOS-openSUSE-12.3.i686-1.12.3.iso 2>&1] The offset set to 0 caused the broken partition table. But I remember Robert had a good reason to set the offset to 0 in order to allow to boot the iso as iso on different bios implementations. When I set the offset to 64 I got a correct partition table output in parted next I tested the iso as disk with persistent writing as reported in this bug. I got one step further but I found that the iso header is only available on the entire disk device /dev/sda. Thus when /dev/sda is mounted to access the data from the iso all "partitions" are set as busy by the kernel. Because of this the mkfs tools refused to run on the persistent write partition because the kernel report it as busy. I know we workaround that by a losetup on /dev/sda but that's nasty and also not required if isohybrid is called in --uefi mode So I still think what isohybrid writes here is broken, I would expect that the iso header is available on the partition device if we would build the 32bit iso also with firmware="efi" we would solve the problem by another workaround Thoughts ? -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c14 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|snwint@suse.com | --- Comment #14 from Steffen Winterfeldt 2013-10-09 11:45:54 CEST --- For the 32-bit version there's no second set of iso meta data generated, so it can't use a nonzero offset. Maybe this part of the code is only triggered when an efi image is present? Marcus, when you create the new meta data for the partition, can you add a tag via tagmedia that points to the partition? Like 'tagmedia --add-tag "partition=<OFFSET>"'? This would make it more obvious that such a partition exists (and show where, in case you want to mount it). We don't use efi for 32-bit because it doesn't exist except on some Macs. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c16 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #16 from Neil Rickert 2013-10-11 21:09:35 UTC --- This problem is still there for RC1 (just tested). I have flagged this as reopened. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c18 --- Comment #18 from Neil Rickert 2013-10-13 14:17:20 UTC --- I am thinking aloud about this one. I am putting two and two together (and possibly coming up with 5). As a solution to an earlier problem -- bug 825172 -- there was a switch to using "parted" instead of "fdisk" for creating the hybrid partition. That earlier problem was related to the EFI structure of 64-bit isos. My experience is that "parted" does not like a non-efi "isohybrid" structured iso on a USB. When installing from one in the past, there has always been a message that partitions cannot be created on the USB. Together with comments above, I am thinking that "parted" cannot work with the current iso structure for 32-bit. Going back to "fdisk" might not be good either -- if the USB is being reused, it might have remnants of GPT partitioning which confuses "fdisk". If there isn't an easy fix, then my suggestion would be to completely skip the creation of a hybrid partition, at least on 32bit isos. It's probably too late for comprehensive changes for 13.1, so skipping the creation of hybrid will at least get out something that works on a USB. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c20 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|nrickert@ameritech.net | --- Comment #20 from Neil Rickert 2013-10-13 19:42:05 UTC ---

I need the /var/log/boot.kiwi file to say more about the problem

Where am I supposed to find those logs, given that the boot USB has been overwritten and a new ext4 file system created on top? -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c22 --- Comment #22 from Martin Schlander 2013-10-13 20:16:51 UTC --- Created an attachment (id=563221) --> (http://bugzilla.novell.com/attachment.cgi?id=563221) Photo of RC1 32-bit live-usb failing to boot on non-efi system -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c24 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|nrickert@ameritech.net | --- Comment #24 from Neil Rickert 2013-10-13 21:55:10 UTC --- Created an attachment (id=563227) --> (http://bugzilla.novell.com/attachment.cgi?id=563227) Boot.kiwi from failed boot I'll provide more info in an additional comment. -- 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=841392 https://bugzilla.novell.com/show_bug.cgi?id=841392#c26 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |coolo@suse.com --- Comment #26 from Marcus Schaefer 2013-10-14 09:10:11 UTC --- kiwi_revision='8214f9b604f2ab69692f0c86010ab390163c9141' ==> is still the old kiwi version (5.05.35) I had submitted the kiwi with the fix to Factory some time ago and it was accepted. So no idea why it is still build with the old version of course without the fix the partition table is still invalid here is the commit in the kiwi git which fixed this: commit 8a7cc82ce02ea83e15cc75d3e28f627ad4d98229 Author: Marcus Schäfer Date: Wed Oct 9 16:28:03 2013 +0200 - fixed iso hybrid partition table for 32bit live iso images * if firmware="bios" is set the offset and table setup was incomplete, which results in a broken hybrid persistent partition if the iso was used as disk on e.g a USB stick This fixes (bnc #841392) -- 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.