Hide Forgot
Description of problem: after snapshotting /boot initramfs which also exists in snapshot gets decompression error during boot making copy with same name and md5 just to decouple from snapshotted copy fixes this problem
I'm afraid this report is far too short to be useful or get a useful answer. Please provide essential information such as the relevant package version(s), a description of how the problem can be reproduced and the exact error messages. You could perhaps also investigate with grub upstream to which extent they support what you are trying to do.
latest f16 btrfs subvolume snapshot /boot test_snapshot reboot exact error message you will see when you try this. as i said it's kernel unhappy about error decompressing initramfs - presumably grub reads it from wrong blocks i'm "trying" to boot f16 actually snapshot was made by yum plugin, but i don't think it matters
Could you try with upstream or with the GRUB for f17? It should be fixed now.
well, f17 installer cannot install on btrfs, but i upgraded using yum now grub2-install is crashing: # LANG=C /sbin/grub2-install /dev/sda1 /sbin/grub2-install: line 862: 21224 Segmentation fault (core dumped) "$grub_setup" ${allow_floppy} ${setup_verbose} ${setup_force} --directory="${grubdir}/${grub_modinfo_target_cpu}-$grub_modinfo_platform" --device-map="${device_map}" "${install_device}" so i left with grub2 1.99 from f16 until installer is fixed probably in f18 so sadly i can't test with newer verion atm
Could you supply a backtrace?
The crash should be detected by abrt, making it very easy to report the backtrace. But I guess the crash was with beta4 - and I guess something like the beta6 rpm from http://koji.fedoraproject.org/koji/buildinfo?buildID=322368 is needed to get the fix mentioned in comment 3. Please give that a try.
i think my crash is fixed by r4261 btw i have several cores of grub2-bios-setup, but no abrt reaction i just killed -6 /bin/less and abrt caught it. dunno what was wrong with grub cores i will try to test new version today
i cannot reboot yet, but i installed new version now it says # LANG=C /sbin/grub2-install /dev/sda1 /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-probe: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. /usr/sbin/grub2-bios-setup: warning: the device.map entry `hd0,1' is invalid. Ignoring it. Please correct or delete your device.map. Installation finished. No error reported. # cat /boot/grub2/device.map # this device map was generated by anaconda (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdc (hd3) /dev/sdd (hd0,1) /dev/sda1 ---- changing (hd0,1) to (hd0,msdos1) does not help hope it will boot nevertheless
device.map should contain partitions at all.
i think this bug is fixed now
well, i was wrong the bug still exists but it appears only after normal reboot after pressing reset button grub boots fine i can add that my boot disk is VTX3-25SAT3-120G but i have no problems with it after boot