https://bugzilla.novell.com/show_bug.cgi?id=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c1 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #1 from Neil Rickert 2013-07-11 19:06:25 UTC --- I am seeing the same problem with: openSUSE-Factory-KDE-Live-x86_64-Build0575-Media.iso -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c3 dale ritchey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mergan14846@gmail.com --- Comment #3 from dale ritchey 2013-08-06 16:51:51 UTC --- last attempt build 644 copying /boot to /hybrid/boot before installation works as a work around -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c5 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |ms@suse.com InfoProvider|ms@suse.com | --- Comment #5 from Marcus Schaefer 2013-08-07 13:11:11 UTC --- sorry, what ? I'm confused I built a test image using factory kiwi and build for 12.3 because I don't have 13.1 at hand but it should not matter to reproduce this: kiwi --build suse-12.3-JeOS -d /tmp/mytest I got: LimeJeOS-openSUSE-12.3.x86_64-1.12.3.iso and booted it with: qemu-kvm -cdrom LimeJeOS-openSUSE-12.3.x86_64-1.12.3.iso the system boots up and the contents of /boot are: ls -l /boot/ total 39815 -rw-r--r-- 1 root root 1484 Feb 26 14:34 boot.readme -rw-r--r-- 1 root root 136028 Mar 1 11:39 config-3.7.10-1.1-default -rw-r--r-- 1 root root 0 Aug 7 12:56 do_purge_kernels drwxr-xr-x 3 root root 29 Aug 7 12:57 grub2 lrwxrwxrwx 1 root root 5 Aug 7 12:57 grub2-efi -> grub2 lrwxrwxrwx 1 root root 25 Aug 7 12:57 initrd -> initrd-3.7.10-1.1-default -rw-r--r-- 1 root root 26987354 Aug 7 12:57 initrd-3.7.10-1.1-default -rw-r--r-- 1 root root 621056 Aug 7 12:57 message -rw-r--r-- 1 root root 241420 Mar 1 13:01 symvers-3.7.10-1.1-default.gz -rw-r--r-- 1 root root 409 Mar 1 13:01 sysctl.conf-3.7.10-1.1-default -rw-r--r-- 1 root root 2446078 Mar 1 12:48 System.map-3.7.10-1.1-default -rw-r--r-- 1 root root 5561332 Mar 1 13:00 vmlinux-3.7.10-1.1-default.gz lrwxrwxrwx 1 root root 26 Aug 7 12:56 vmlinuz -> vmlinuz-3.7.10-1.1-default -rw-r--r-- 1 root root 4773814 Mar 1 15:21 vmlinuz-3.7.10-1.1-default which looks pretty ok to me the system is mounted via overlayfs cat /proc/mounts | grep read /dev/loop7 /read-only squashfs ro,relatime 0 0 /dev/ram1 /read-write ext3 rw,relatime,data=ordered 0 0 overlayfs / overlayfs rw,relatime,lowerdir=/read-only,upperdir=/read-write 0 0 which is also ok, so could you compare the 13.1 booted live iso and check if all I mentioned above is still true ? I also have no idea why this bug talks about a live ISO and installation is this because one used the yast live installer ? and maybe the bug is not referencing the live system but the result of the installation ? please clarify thanks -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c7 --- Comment #7 from dale ritchey 2013-08-07 15:29:06 UTC --- (In reply to comment #5)

sorry, what ? I'm confused

I built a test image using factory kiwi and build for 12.3 because I don't have 13.1 at hand but it should not matter to reproduce this:

kiwi --build suse-12.3-JeOS -d /tmp/mytest

I got:

LimeJeOS-openSUSE-12.3.x86_64-1.12.3.iso

and booted it with:

qemu-kvm -cdrom LimeJeOS-openSUSE-12.3.x86_64-1.12.3.iso

the system boots up and the contents of /boot are:

ls -l /boot/ total 39815 -rw-r--r-- 1 root root 1484 Feb 26 14:34 boot.readme -rw-r--r-- 1 root root 136028 Mar 1 11:39 config-3.7.10-1.1-default -rw-r--r-- 1 root root 0 Aug 7 12:56 do_purge_kernels drwxr-xr-x 3 root root 29 Aug 7 12:57 grub2 lrwxrwxrwx 1 root root 5 Aug 7 12:57 grub2-efi -> grub2 lrwxrwxrwx 1 root root 25 Aug 7 12:57 initrd -> initrd-3.7.10-1.1-default -rw-r--r-- 1 root root 26987354 Aug 7 12:57 initrd-3.7.10-1.1-default -rw-r--r-- 1 root root 621056 Aug 7 12:57 message -rw-r--r-- 1 root root 241420 Mar 1 13:01 symvers-3.7.10-1.1-default.gz -rw-r--r-- 1 root root 409 Mar 1 13:01 sysctl.conf-3.7.10-1.1-default -rw-r--r-- 1 root root 2446078 Mar 1 12:48 System.map-3.7.10-1.1-default -rw-r--r-- 1 root root 5561332 Mar 1 13:00 vmlinux-3.7.10-1.1-default.gz lrwxrwxrwx 1 root root 26 Aug 7 12:56 vmlinuz -> vmlinuz-3.7.10-1.1-default -rw-r--r-- 1 root root 4773814 Mar 1 15:21 vmlinuz-3.7.10-1.1-default

which looks pretty ok to me

the system is mounted via overlayfs

cat /proc/mounts | grep read /dev/loop7 /read-only squashfs ro,relatime 0 0 /dev/ram1 /read-write ext3 rw,relatime,data=ordered 0 0 overlayfs / overlayfs rw,relatime,lowerdir=/read-only,upperdir=/read-write 0 0

which is also ok, so could you compare the 13.1 booted live iso and check if all I mentioned above is still true ?

I also have no idea why this bug talks about a live ISO and installation is this because one used the yast live installer ? and maybe the bug is not referencing the live system but the result of the installation ?

please clarify

thanks

It is the result of the installation. the installed /boot directory does not get populated resulting in an unbootable 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c9 --- Comment #9 from Neil Rickert 2013-08-09 21:48:02 UTC --- Testing with 13.1M4 64bit. I used openSUSE-Factory-KDE-Live-Build0652-x86_64.iso.sha1 I wrote that to a USB device, using "dd_rescue" First boot of the USB: "/boot" is properly populated. Second boot of the USB: "/boot" is empty It looks as if there is some difference between when the hybrid partition is first created, and when it is re-used on a later boot. To test this: I booted my system to 12.3, ran "fdisk", and deleted partition 3 (the hybrid partition) from the USB. I then booted the USB again. And "/boot" was properly populated. There must be something different about the environment between creating and allocating the hybrid partition, vs. re-using an existing hybrid partition -- perhaps it's just the current working directory. Something is causing "overlayfs" to not work as expected. I have not tested this. But I think the following is actually safe. If about to install from a live USB, look at "/boot". If it appears to be populated (kernels, etc), then install. Otherwise use fdisk and remove the hybrid partition (partition 3) from the USB on which you are running. Then reboot. As far as I know, the running system will continue to use the partitioning as at the time of boot, so deleting the partition should not harm the running system. But it should give a fresh start, newly created hybrid partition, after the reboot. -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c11 --- Comment #11 from Neil Rickert 2013-08-10 18:54:46 UTC --- Created an attachment (id=552106) --> (http://bugzilla.novell.com/attachment.cgi?id=552106) transcript of terminal session showing "ls /boot" and other commands This transcript was taken shortly after booting the live USB "openSUSE-Factory-KDE-Live-Build0652-x86_64.iso" the first time. The output includes that of "ls -l /boot" which looks completely bogus (several zero-length files), and has a bogus EFI directory. This is not what overlayfs should provide. There's also output from "mount" to see what the system thinks is mounted. -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c13 --- Comment #13 from Neil Rickert 2013-08-10 19:00:01 UTC --- Created an attachment (id=552108) --> (http://bugzilla.novell.com/attachment.cgi?id=552108) transcript of live session on reboot after "rmdir boot" on hybrid This shows output of "ls -l /boot" when running the live USB. This is after I had removed the "boot" directory on the hybrid partition. This time, all looks good. This is what we should have seen for the first boot. -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c15 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |GeoBaltz@gmail.com --- Comment #15 from Michael Chang 2013-08-13 10:04:58 UTC --- *** Bug 834320 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=834320 -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Flag| |SHIP_STOPPER? -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c17 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |ms@suse.com Flag|SHIP_STOPPER? |SHIP_STOPPER+ --- Comment #17 from Stephan Kulow 2013-09-27 13:36:59 CEST --- This (from beta1 kiwi.log) seems to be the culprit: + mkdir -p /boot_bind + mount /dev/sda1 /boot_bind + cp -a /mnt/boot /boot_bind cp: error writing '/boot_bind/boot/System.map-3.11.1-1.g1383321-desktop': No space left on device cp: failed to extend '/boot_bind/boot/System.map-3.11.1-1.g1383321-desktop': No space left on device cp: cannot create symbolic link '/boot_bind/boot/boot': Operation not permitted cp: error writing '/boot_bind/boot/boot.readme': No space left on device cp: failed to extend '/boot_bind/boot/boot.readme': No space left on device cp: error writing '/boot_bind/boot/config-3.11.1-1.g1383321-desktop': No space left on device cp: failed to extend '/boot_bind/boot/config-3.11.1-1.g1383321-desktop': No space left on device cp: cannot create directory '/boot_bind/boot/grub': No space left on device cp: cannot create directory '/boot_bind/boot/grub2': No space left on device cp: cannot create symbolic link '/boot_bind/boot/initrd': Operation not permitted cp: error writing '/boot_bind/boot/memtest.bin': No space left on device cp: failed to extend '/boot_bind/boot/memtest.bin': No space left on device cp: error writing '/boot_bind/boot/message': No space left on device cp: failed to extend '/boot_bind/boot/message': No space left on device cp: error writing '/boot_bind/boot/symvers-3.11.1-1.g1383321-desktop.gz': No space left on device cp: failed to extend '/boot_bind/boot/symvers-3.11.1-1.g1383321-desktop.gz': No space left on device cp: error writing '/boot_bind/boot/sysctl.conf-3.11.1-1.g1383321-desktop': No space left on device cp: failed to extend '/boot_bind/boot/sysctl.conf-3.11.1-1.g1383321-desktop': No space left on device cp: error writing '/boot_bind/boot/vmlinux-3.11.1-1.g1383321-desktop.gz': No space left on device cp: failed to extend '/boot_bind/boot/vmlinux-3.11.1-1.g1383321-desktop.gz': No space left on device cp: cannot create symbolic link '/boot_bind/boot/vmlinuz': Operation not permitted cp: error writing '/boot_bind/boot/vmlinuz-3.11.1-1.g1383321-desktop': No space left on device cp: failed to extend '/boot_bind/boot/vmlinuz-3.11.1-1.g1383321-desktop': No space left on device + '[' -e /boot.tgz ']' + umount /boot_bind + rmdir /boot_bind -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c19 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Marcus Schaefer 2013-09-27 13:10:50 UTC --- ok I can reproduce the "no space left" case and have fixed it. But I found that even with the error I have useful data in /boot. I never was able to create an empty /boot except if the image itself doesn't have a kernel installed. Because of this please check the following in your live iso: mount -o loop live.iso /mnt # below /mnt you will see a file with name "XXXX-read-only.XXX" # this is a squashfs file, mount this as well: mount -t squashfs /mnt/XXXX-read-only.XXX /mnt now check the contents of /boot inside this squashfs image ls -l /mnt/boot umount /mnt umount /mnt you have to have some useful data there. if not your image build is missing a kernel or you have custom scripts removing /boot or something I have submitted kiwi v5.05.35 to Factory (sr: 201109) to fix the reported defect but I still feel there is something different wrong in your image because of the empty /boot if so please open another bug report with: a) the information from the test mentioned in this comment b) the /var/log/boot.kiwi file to verify if the "no space" problem is fixed Thanks closing -- 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=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c21 --- Comment #21 from Neil Rickert 2013-09-27 15:19:35 UTC ---

I have submitted kiwi v5.05.35 to Factory (sr: 201109) to fix the reported defect but I still feel there is something different wrong in your image because of the empty /boot

The empty "/boot" seems to related to how the USB hybrid partition is overlayed on what is in "/read-only". From what I can find out about overlayfs, what is seen in "/boot" should be the same as is in "/read-only/boot" unless overlayed by something in "/read-write/boot". Yet that does not happen. However, if the directory "/read-write/boot" is removed, the live USB rebooted, then a new "/read-write/boot" is created and the overlay begins to work as documented. Maybe those kiwi errors are related, but I won't be convinced until tests show that it is working on a freshly created 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.