Comment 36 for bug 1003309

Revision history for this message
tdn (spam-thomasdamgaard) wrote :

I tried mounting rootfs in /mnt and boot in /mnt/boot
Then I mounted proc, sys, and so on as described on:
https://wiki.archlinux.org/index.php/Change_Root

Then I ran:
apt-get update
apt-get dist-upgrade

This is the complete output:
http://p.adora.dk/P2409.html

Highligted output:
Found linux image: /boot/vmlinuz-3.2.0-24-generic
Found initrd image: /boot/initrd.img-3.2.0-24-generic
Found linux image: /boot/vmlinuz-3.2.0-23-generic
Found initrd image: /boot/initrd.img-3.2.0-23-generic
Found memtest86+ image: /memtest86+.bin
  /var/lock/lvm: mkdir failed: No such file or directory
  File-based locking initialisation failed.
done
[...]
Not updating initrd symbolic links since we are being updated/reinstalled
(3.2.0-24.38 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(3.2.0-24.38 was configured last, according to dpkg)
[...]
Found initrd image: /boot/initrd.img-3.2.0-23-generic
Found memtest86+ image: /memtest86+.bin
  /var/lock/lvm: mkdir failed: No such file or directory
  File-based locking initialisation failed.
done
[...]
Found memtest86+ image: /memtest86+.bin
  /var/lock/lvm: mkdir failed: No such file or directory
  File-based locking initialisation failed.
done
[...]

What now?