[Pkg-sysvinit-devel] Bug#552248: initscripts: checkfs.sh fails with "device doesn't exist" on ext4 /home partitions (two different computers)

[thveillon]

Package: initscripts
Version: 2.87dsf-6
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.5-perso64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  coreutils                     7.4-2      The GNU core utilities
ii  debianutils                   3.2.1      Miscellaneous utilities specific t
ii  libc6                         2.9-25     GNU C Library: Shared libraries
ii  lsb-base                      3.2-23     Linux Standard Base 3.2 init scrip
ii  mount                         2.16.1-4   Tools for mounting and manipulatin
ii  sysv-rc                       2.87dsf-6  System-V-like runlevel change mech
ii  sysvinit-utils                2.87dsf-6  System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs                     1.41.9-1   ext2/ext3/ext4 file system utiliti
ii  psmisc                        22.8-1     utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information


On two different Squeeze amd64 systems, with custom kernel or Stock Debian
ones, the boot process fails when checkfs.sh kicks in. This is on ext4
filesystem (one laptop, one raid1 desktop), tried with UUID and /dev/ style identifications in fstab with
the same result, fsck.ext4 aborts with "special device [name/uuid]  doesn't
exist" and drops to a rescue shell.
>From the rescue shell it's impossible to run fsck or mount the /home
partition (always the "special device doesn't exist" message), so boot
process can't be completed, only reboot (temporarily) solves the problem.

The /home partitions are in good shape, running fsck.ext4 from live-cd or from
runlevel 1 doesn't show any problem.