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.