Bug#535513: daily fails to generate ramdisk because / not mounted
Package: installation-reports
Severity: serious
I just tried a daily image on ARM and it failed because the ramdisk
cannot be generated. Apparently this is because / is not mounted in
the chroot.
Jul 2 17:57:58 in-target: Setting up linux-image-2.6.26-2-orion5x (2.6.26-17) ...
Jul 2 17:58:02 debconf: Obsolete command TITLE Configuring linux-image-2.6.26-2-orion5x called
Jul 2 17:58:04 in-target:
Jul 2 17:58:04 in-target: Hmm. The package shipped with a symbolic link /lib/modules/2.6.26-2-orion5x/source
Jul 2 17:58:04 in-target: However, I can not read the target: No such file or directory
Jul 2 17:58:04 in-target: Therefore, I am deleting /lib/modules/2.6.26-2-orion5x/source
Jul 2 17:58:04 in-target:
Jul 2 17:58:04 in-target: Running depmod.
Jul 2 17:58:08 in-target: Finding valid ramdisk creators.
Jul 2 17:58:08 in-target: Using mkinitramfs-kpkg to build the ramdisk.
Jul 2 17:58:08 in-target: Deprecation WARNING: use update-initramfs(8)
Jul 2 17:58:09 in-target: readlink:
Jul 2 17:58:09 in-target: missing operand
Jul 2 17:58:09 in-target:
Jul 2 17:58:09 in-target: Try `readlink --help' for more information.
Jul 2 17:58:09 in-target: mkinitramfs-kpkg failed to create initrd image.
Jul 2 17:58:09 in-target: Failed to create initrd image.
Jul 2 17:58:10 in-target: dpkg: error processing linux-image-2.6.26-2-orion5x (--configure):
Jul 2 17:58:10 in-target: subprocess installed post-installation script returned error exit status 9
It fails because $root is empty
++ awk '/\/dev\// {if ($3 == "/") {print "root=" $1 "\nFSTYPE=" $5; exit}}'
++ mount
+ eval ''
+ '[' '' = /dev/root ']'
++ readlink -f
readlink: missing operand
Try `readlink --help' for more information.
+ root=
which is because / is not mounted in the chroot:
~ # mount
rootfs on / type rootfs (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
tmpfs on /dev type tmpfs (rw,mode=755)
none on /dev/pts type devpts (rw,gid=5,mode=620,ptmxmode=000)
/dev/sda2 on /target type ext3 (rw,errors=remount-ro,data=ordered)
/dev/sda1 on /target/boot type ext2 (rw,errors=continue)
/dev/sda6 on /target/home type ext3 (rw,errors=continue,data=ordered)
/dev/sda2 on /dev/.static/dev type ext3 (rw,errors=remount-ro,data=ordered)
tmpfs on /target/dev type tmpfs (rw,mode=755)
~ # chroot /target
sh-3.2# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
sh-3.2#
sh-3.2# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda2 during installation
UUID=d5f957fc-6c81-4a88-891c-d1f542de0fa3 / ext3 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=0471103b-39b3-4ed0-9eda-7b85ce0199c9 /boot ext2 defaults 0 2
# /home was on /dev/sda6 during installation
UUID=e44f917b-64a3-4d65-a25a-10dfd33f8b15 /home ext3 defaults 0 2
/dev/sda5 none swap sw 0 0
sh-3.2#
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: