Hi Yann,
On 07/04/12 19:56, Yann Dirson wrote:
>>> 2. the output of "strace -p <pid>"
>>>
>>
>> root@ppcl007:~# strace -p 3648
>> Process 3648 attached - interrupt to quit
>> read(11,
>
> In that case, we'll need to know what's hidden behind file descriptor
> 11. You can use "ls -l /proc/<pid>/fd/" to find out.
>
root@nobody:~# ls -al /proc/8460/fd
total 0
dr-x------ 2 root root 0 Jul 5 13:23 .
dr-xr-xr-x 8 root root 0 Jul 5 13:22 ..
lrwx------ 1 root root 64 Jul 5 13:24 0 -> /dev/pts/0
lrwx------ 1 root root 64 Jul 5 13:24 1 -> /dev/pts/0
lr-x------ 1 root root 64 Jul 5 13:24 10 -> pipe:[640169]
lr-x------ 1 root root 64 Jul 5 13:24 11 -> pipe:[638542]
lr-x------ 1 root root 64 Jul 5 13:24 12 -> pipe:[640170]
lrwx------ 1 root root 64 Jul 5 13:23 2 -> /dev/pts/0
lrwx------ 1 root root 64 Jul 5 13:24 3 -> /dev/pts/0
lrwx------ 1 root root 64 Jul 5 13:24 4 -> /var/cache/debconf/config.dat
lrwx------ 1 root root 64 Jul 5 13:24 5 -> /var/cache/debconf/passwords.dat
lrwx------ 1 root root 64 Jul 5 13:24 6 -> /var/cache/debconf/templates.dat
l-wx------ 1 root root 64 Jul 5 13:24 8 -> pipe:[638541]
lrwx------ 1 root root 64 Jul 5 13:24 9 -> /dev/pts/0
> You can also get info from debconf itself. Setting
> DEBCONF_DEBUG=developer while running dpkg can help.
>
root@ppcl007:~# dpkg -i /var/cache/apt/archives/memtest86+_4.20-1.1_amd64.deb
(Reading database ... 241701 files and directories currently installed.)
Preparing to replace memtest86+ 4.20-1.1 (using
.../memtest86+_4.20-1.1_amd64.deb) ...
Unpacking replacement 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 memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
grub-probe: error: no such disk.
done
Setting up memtest86+ (4.20-1.1) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is memtest86+
debconf (developer): starting /var/lib/dpkg/info/memtest86+.config configure
debconf (developer): <-- INPUT medium shared/memtest86-run-lilo
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): starting /var/lib/dpkg/info/memtest86+.postinst configure
debconf (developer): <-- GET shared/memtest86-run-lilo
debconf (developer): --> 0 false
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 memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
grub-probe: error: no such disk.
done
Maybe some information about the disk layout helps, too:
/dev/sda is the only disk installed.
/dev/sda1 /boot ext4
/dev/sda2 encrypted physical volume for lvm2:
/dev/mapper/pv00 physical volume
/dev/mapper/vg00-root / filesystem ext4
/dev/mapper/vg00-swap swap
/dev/mapper/vg00-root2 empty ext4
/dev/mapper/vg00-export empty ext4
Hope this helps
Regards
Harri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
