26179 2011-08-27 23:18:48 +0400 wrong path to memtest when /boot/ is on a separate partition 2013-11-27 00:13:52 +0400 1 1 4 Development Sisyphus grub2-pc unstable all Linux CLOSED DUPLICATE 29460 P3 normal --- 26178 1 imz mike aen boyarsh sbolshakov vitty qa-sisyphus oldest_to_newest 124562 0 imz 2011-08-27 23:18:48 +0400 +++ This bug was initially created as a clone of Bug #26178 +++ # tail -30 /boot/grub/grub.cfg ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/39_memtest ### menuentry "Memtest86+-3.5" { insmod part_msdos insmod ext2 set root='(/dev/sda,msdos2)' search --no-floppy --fs-uuid --set=root ac12087e-a82d-413e-8abc-7a9fc1f62ea5 linux16 /boot/memtest-3.5.bin } menuentry "Memtest86+-4.20" { insmod part_msdos insmod ext2 set root='(/dev/sda,msdos2)' search --no-floppy --fs-uuid --set=root ac12087e-a82d-413e-8abc-7a9fc1f62ea5 linux16 /boot/memtest-4.20.bin } ### END /etc/grub.d/39_memtest ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### # rpm -qf /etc/grub.d/39_memtest grub2-1.99-alt7 # This doesn't work in my case, because in my case /boot/ is on a separate partition, and hence the path to memtest is wrong: # mount | fgrep /boot /dev/sda2 on /boot type ext4 (rw,nosuid,nodev,noexec,relatime,user_xattr,acl,barrier=1,data=ordered) # Some more info: # rpm -qa 'memtest*' memtester-4.2.1-alt1 memtest86+-4.20-alt1 memtest86-3.5-alt2 # 134430 1 mike 2012-11-03 18:38:38 +0400 Забираю. 134440 2 mike 2012-11-03 19:32:50 +0400 Just in case you're interested in fixing up 39_memtest, patches (or hacks) are welcome -- it's not a part of upstream so didn't actually change in 2.00 package yet. 143928 3 mike 2013-11-27 00:13:52 +0400 Оказывается, об этой грабельке уже сообщалось... *** This bug has been marked as a duplicate of bug 29460 ***