[Bug 827520] New: No kernel in /boot or /boot is empty after installation
https://bugzilla.novell.com/show_bug.cgi?id=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c0 Summary: No kernel in /boot or /boot is empty after installation Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: 64bit OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Live Medium AssignedTo: coolo@suse.com ReportedBy: mergan14846@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 After the live kde I find that the /boot directory is empty I can recover by booting the live iso and mount /dev/sda2 mount --bind /dev /mnt/dev mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc chroot /mnt run yast in a terminal and reinstalling the kernel I also notice during the installation that the /mnt/sys and /mnt/proc is empty I have tested file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0505-Media.iso file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0506-Media.iso file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0510-Media.iso file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0513-Media.iso file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0514-Media.iso file:///var/run/media/dale/Home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0515-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0527-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0530-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0535-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0536-Media(1).iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0536-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0538-Media.iso file:///home/dale/Downloads/openSUSE-Factory-KDE-Live-x86_64-Build0544-Media.iso all with the same results Reproducible: Always Steps to Reproduce: 1.download the iso 2.copy to usb with imagewriter 3.install and reboot no kernel Actual Results: nasty note from grub Expected Results: working 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#c1 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #1 from Neil Rickert <nrickert@ameritech.net> 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#c2 --- Comment #2 from Neil Rickert <nrickert@ameritech.net> 2013-07-14 02:54:13 UTC --- This seems to have something to do with the way the caching file system works when a USB is used for the live media. When I am booted to the live system on USB, I see a "/read-only" which is a loop mount from an image on the boot media. And I see a "/read-write" which is the copy-on-write partition on the USB. I also see the root file system under "overlayfs", so I assume that is supposed to overlay the parts. The "/boot" subdirectory of "/read-only" has the kernels. The "/boot" subdirectory of "/read-write" is empty. The main "/boot" directory, which presumably should be an overlay of the two parts, is empty or near empty. -------- If, instead, I run "isohybrid" in the iso, and then use the "live-fat-stick" script, booting that gives the correct "/boot" content. I am guessing, but have not tested, that if I write the original iso to a DVD and boot that, it also works properly. And I'm guessing that's why coolo could not repeat the problem (see factory email). Note: I ran "isohybrid" because the live-fat-stick script does not seem to like UEFI formatted isos. I did not use the "--uefi" option to isohybrid. -- 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 <mergan14846@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mergan14846@gmail.com --- Comment #3 from dale ritchey <mergan14846@gmail.com> 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#c4 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ms@suse.com --- Comment #4 from Stephan Kulow <coolo@suse.com> 2013-08-07 13:19:46 CEST --- Marcus, any idea why this is needed now? -- 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 <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |ms@suse.com InfoProvider|ms@suse.com | --- Comment #5 from Marcus Schaefer <ms@suse.com> 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#c6 --- Comment #6 from Neil Rickert <nrickert@ameritech.net> 2013-08-07 14:23:58 UTC --- Created an attachment (id=551614) --> (http://bugzilla.novell.com/attachment.cgi?id=551614) Typescript of command output showing the problem This is a typescript of commands run immediately after booting a live USB for 13.1M3. The live image used was: openSUSE-Factory-KDE-Live-x86_64-Build0575-Media.iso After login to the live system, I used ALT-F2, and entered the "xterm" command. Next I did "su" Next, I mounted a FAT partition ("/dev/sda5") at "/mnt" Next I did "cd /mnt" followed by "script" The script shows the output of "ls -l /boot" (it is empty) ls -l /read-only/boot (it contains all of the files that should be in /boot) There is also the output of "mount" showing the overlay mounting. -- 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 <mergan14846@gmail.com> 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#c8 Christoph Feck <christoph@maxiom.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christoph@maxiom.de --- Comment #8 from Christoph Feck <christoph@maxiom.de> 2013-08-09 14:27:34 UTC --- Reproduced when trying to boot openSUSE-Factory-KDE-Live-Build0651-i686.iso after fresh install. The only file in /boot/ (using grub's "ls /boot/" command) is the saved mbr. -- 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 <nrickert@ameritech.net> 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#c10 --- Comment #10 from Neil Rickert <nrickert@ameritech.net> 2013-08-09 23:27:31 UTC --- Some strangeness here. This follows on from #9 above. When I did "ls /boot" after booting the live USB, the file names all (or almost all) showed up as red. I normally turn off that color-ls as distracting, so I'm not sure what the colors mean. Instead of removing the hybrid partition, this time I just did "rmdir boot" in the top directory of the hybrid partition (I did that off-line). On booting the live USB, after removing that "boot" directory, "/boot" again looked populated. And, this time, "ls /boot" gave a variety of colors. So there was probably something broken when everything showed as red. And now, on reboot, everything is still fine. I do not have to repeat that removal of the "boot" directory in the hybrid partition. I'm not sure what this means, but I hope it will be useful for tracing the problem. -- 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 <nrickert@ameritech.net> 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#c12 --- Comment #12 from Neil Rickert <nrickert@ameritech.net> 2013-08-10 18:57:08 UTC --- Created an attachment (id=552107) --> (http://bugzilla.novell.com/attachment.cgi?id=552107) transcript showing ls of hybrid partition (seen offline) I mounted the hybrid partition (the live media not running). This transcript includes a few "ls" commands. I then did "rmdir" on the "boot" directory of the hybrid partition. -- 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 <nrickert@ameritech.net> 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#c14 --- Comment #14 from dale ritchey <mergan14846@gmail.com> 2013-08-11 10:39:22 UTC --- I have played around with /read-write/boot (hybrid/boot) which gives me a grub2 install but not an uefi secure boot. booting the live kde and removing /boot which is empty and copying /read-only/boot (loop device/boot) to / allows for an uefi secure install with no error messages. -- 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 <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |GeoBaltz@gmail.com --- Comment #15 from Michael Chang <mchang@suse.com> 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#c16 --- Comment #16 from Neil Rickert <nrickert@ameritech.net> 2013-09-20 01:46:55 UTC --- This problem (no kernels in "/boot") is still there for 13.1Beta when used from a 64bit USB. For 32bit, there is a more severe problem (see bug 841392). As before, the workaround is to boot the live USB. Then remove the "boot" subdirectory from the hybrid partition. Then reboot. It looks as if it is okay to remove that boot directory while booted to the live USB. Simply, as root, do # rmdir /read-write/boot That "rmdir" is only needed once. On the next boot, the directory is recreated, and will thereafter be non-empty so "rmdir" would generate an error if the work-around has already been applied. -- 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 <dimstar@opensuse.org> 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#c Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- 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 <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |ms@suse.com Flag|SHIP_STOPPER? |SHIP_STOPPER+ --- Comment #17 from Stephan Kulow <coolo@suse.com> 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#c18 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #18 from Marcus Schaefer <ms@suse.com> 2013-09-27 12:06:37 UTC --- I'll try to reproduce this, currently I have no clue why we run out of space here -- 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 <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Marcus Schaefer <ms@suse.com> 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#c20 --- Comment #20 from Stephan Kulow <coolo@suse.com> 2013-09-27 16:52:08 CEST --- /boot is not empty, but it contains tons of truncated files that do not make a good installation. the squashfs looks like this: coolo@gertrude#Lives>ls -l /media/boot/ insgesamt 14828 lrwxrwxrwx 1 root root 1 18. Sep 03:16 boot -> . -rw-r--r-- 1 root root 1484 6. Sep 18:24 boot.readme -rw-r--r-- 1 root root 140333 16. Sep 18:07 config-3.11.1-1.g1383321-desktop -rw-r--r-- 1 root root 0 18. Sep 03:13 do_purge_kernels drwxr-xr-x 2 root root 259 18. Sep 03:16 grub drwxr-xr-x 4 root root 48 18. Sep 03:16 grub2 lrwxrwxrwx 1 root root 32 18. Sep 03:13 initrd -> initrd-3.11.1-1.g1383321-desktop -rw-r--r-- 1 root root 176760 14. Aug 22:52 memtest.bin -rw-r--r-- 1 root root 621056 18. Sep 03:16 message -rw-r--r-- 1 root root 261791 16. Sep 19:00 symvers-3.11.1-1.g1383321-desktop.gz -rw-r--r-- 1 root root 516 16. Sep 19:00 sysctl.conf-3.11.1-1.g1383321-desktop -rw-r--r-- 1 root root 2695891 16. Sep 18:49 System.map-3.11.1-1.g1383321-desktop -rw-r--r-- 1 root root 6074056 16. Sep 19:00 vmlinux-3.11.1-1.g1383321-desktop.gz lrwxrwxrwx 1 root root 33 18. Sep 03:13 vmlinuz -> vmlinuz-3.11.1-1.g1383321-desktop -rw-r--r-- 1 root root 5208616 16. Sep 20:31 vmlinuz-3.11.1-1.g1383321-desktop -- 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 <nrickert@ameritech.net> 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.
https://bugzilla.novell.com/show_bug.cgi?id=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c22 --- Comment #22 from Neil Rickert <nrickert@ameritech.net> 2013-09-27 15:29:52 UTC ---
/boot is not empty, but it contains tons of truncated files ( c#20 )
On the first boot of a newly created live USB, "/boot" contains truncated files. On a second boot of that same live USB, "/boot" is empty. However, if the "/boot" subdirectory of the hybrid partition is removed, then all future boots of that live USB look good (and that removed directory has been recreated). Deleting the hybrid partition ( "/dev/sdX3" ) from the USB restores it to newly created state, with the same problems repeated. -- 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