Bug#375342: Additional regression in version 0.60

[Sam Morris <sam@robots.org.uk>]

With initramfs-tools 0.53c the error message is fairly straightforward:

        Begin: Running /scripts/local-top ...
        device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
        cdrom: open failed.
          /dev/cdrom: open failed: No medium found
          Can't expand LV: Snapshot support missing from kernel?
          0 logical volume(s) in volume group "main" now active
        Done.
        ALERT! /dev/mapper/main-root does not exist. Dropping to a shell!
        
        # modprobe dm-snapshot && vgchange -ay && exit

An admin with access to the console can hopefully work out the commands
to run without too much difficulty.

With version 0.60, however, the errors are much more verbose and less
helpful:

        Begin: Running /scripts/local-top ...
        device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
        cdrom: open failed.
        device-mapper: unknown target type
        device-mapper: error adding target to table
          device-mapper: reload ioctl failed: Invalid argument
          1 logical volumes(s) in volume group "main" now active
        Done.
        stdin: error 0
        Begin: Running /scripts/local-premount ...
        Done.
        Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] [-o <modname>] <modname> [parameters...]
        modprobe -r [-n] [-i] [-v] <modulename> ...
        modprobe -l -t <dirname> [ -a <modulename> ...]
        mount:
        Cannot read /etc/fstab: No such file or directory
        Begin: Running /scripts/log-bottom ...
        Done.
        Done.
        Begin: Running /scripts/init-bottom ...
        mount: Mounting /root/dev on /dev/.static failed: No such file or directory
        Done.
        mount: Mounting /sys on /root/sys failed: No such file or directory
        mount: Mounting /proc on /root/proc failed: No such file or directory
        Target filesystem doesn't have /sbin/init

The system is now in some weird state where devices such
as /dev/mapper/main-root and /dev/mapper/main-root-real exist, however
reading from them immediately results in an EOF.

        # modprobe dm-snapshot && vgchange -ay && exit
        Target filesystem doesn't have /sbin/init
        # mount /dev/main/root /root && exit

The boot then continues normally.

So the regressions are that the messages displayed to the console are
longer and less useful, and that there is no attempt to mount the root
filesystem once the shell is exited.

-- 
Sam Morris
http://robots.org.uk/

PGP key id 5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078