Package: memtest86+
Version: 4.20-1.1
Severity: serious

The postinst script gets stuck on builing grub.cfg:

:
Selecting previously unselected package memtest86+.
(Reading database ... 29792 files and directories currently installed.)
Unpacking memtest86+ (from .../memtest86+_4.20-1.1_amd64.deb) ...
Setting up memtest86+ (4.20-1.1) ...
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-3-amd64
Found initrd image: /boot/initrd.img-3.2.0-3-amd64
Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
File descriptor 3 (pipe:[7342]) leaked on lvs invocation. Parent PID 2698: 
/bin/sh
grub-probe: error: no such disk.
done


"done" is the last line.

ps -ef shows:

root      2158     1  0 14:57 ?        00:00:00 /usr/sbin/sshd
root      2200  2158  0 14:58 ?        00:00:00  \_ sshd: root@pts/0
root      2202  2200  0 14:58 pts/0    00:00:00  |   \_ -bash
root      2206  2202  0 14:58 pts/0    00:00:02  |       \_ aptitude
root      2252  2206  0 14:59 pts/1    00:00:00  |           \_ /usr/bin/dpkg 
--status-fd 23 --configure memtest86+:amd64
root      2253  2252  0 14:59 pts/1    00:00:00  |               \_ 
/usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/memtest86+.postinst configure
root      2259  2253  0 14:59 pts/1    00:00:00  |                   \_ 
[memtest86+.post] <defunct>
root      2861  2158  0 15:00 ?        00:00:00  \_ sshd: root@pts/2
root      2863  2861  0 15:01 pts/2    00:00:00      \_ -bash
root      2887  2863  0 15:03 pts/2    00:00:00          \_ ps -ef --forest


I have to manually kill the perl script to get out of this.
If I deinstall memtest86+, then grub works fine:

Removing memtest86+ ...
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-3-amd64
Found initrd image: /boot/initrd.img-3.2.0-3-amd64
Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
grub-probe: error: no such disk.
done
Purging configuration files for memtest86+ ...
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-3-amd64
Found initrd image: /boot/initrd.img-3.2.0-3-amd64
Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
grub-probe: error: no such disk.
done
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-3-amd64
Found initrd image: /boot/initrd.img-3.2.0-3-amd64
Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
grub-probe: error: no such disk.
done


Maybe its a problem with grub2. Please reassign if necessary.


Regards

Harri




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to