Amaya, Thanks for taking care of this. I wasn't sure about how to assign the bug as there was more than one related package.
Regards, Miguel Amaya <am...@debian.org> wrote: > reassign 625843 util-linux > thanks > > Miguel, > > This seems to be a bug in either fsck (util-linux) or udev, so I am > reassigning this bug there and let maintainers take a look at it. > Thanks! > > Miguel Filgueiras wrote: > > Subject: base: fsck fails after upgrade; race condition with udev? > > Package: base > > Severity: important > > Tags: sid > > > > I made a dist-upgrade of unstable and now fsck fails during the > > boot sequence with the errors in the log below. Entering as root > > after this failure and invoking fsck from > > the shell for each drive it completes with no errors. I also > > noticed that the list of clean filesystems at the end of the log is > > not always the same. > > > > I tried to find bug reports on similar problems and it seems there > > were some cases where fsck was started before udev finished. Other > > reports mentioned the need to remake the initramfs what I did but > > without solving the problem. > > > > > > # less /var/log/fsck/checkfs > > Log of fsck -C -V -R -A -a > > Fri May 6 11:21:17 2011 > > > > fsck from util-linux-ng 2.17.2 > > Checking all file systems. > > [/sbin/fsck.ext3 (1) -- /usr] fsck.ext3 -a -C0 /dev/hda3 > > fsck.ext3: No such file or directory while trying to open /dev/hda3 > > /dev/hda3: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the > > superblock is corrupt, and you might try running e2fsck with an > > alternate superblock: e2fsck -b 8193 <device> > > > > [/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/hda5 > > fsck.ext3: No such file or directory while trying to open /dev/hda5 > > /dev/hda5: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the > > superblock is corrupt, and you might try running e2fsck with an > > alternate superblock: e2fsck -b 8193 <device> > > > > [/sbin/fsck.ext3 (1) -- /baks] fsck.ext3 -a -C0 /dev/hda6 > > fsck.ext3: No such file or directory while trying to open /dev/hda6 > > /dev/hda6: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the > > superblock is corrupt, and you might try running e2fsck with an > > alternate superblock: e2fsck -b 8193 <device> > > > > [/sbin/fsck.ext3 (1) -- /user2] fsck.ext3 -a -C0 /dev/hda7 > > fsck.ext3: No such file or directory while trying to open /dev/hda7 > > /dev/hda7: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the > > superblock is corrupt, and you might try running e2fsck with an > > alternate superblock: e2fsck -b 8193 <device> > > > > [/sbin/fsck.ext2 (1) -- /media/store5] fsck.ext2 -a -C0 /dev/sdb1 > > fsck.ext2: No such file or directory while trying to open /dev/sdb1 > > /dev/sdb1: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the > > superblock is corrupt, and you might try running e2fsck with an > > alternate superblock: e2fsck -b 8193 <device> > > > > [/sbin/fsck.ext2 (1) -- /media/store6] fsck.ext2 -a -C0 /dev/sdb2 > > /dev/sdb2: clean, 1340/9781248 files, 362222/19531023 blocks > > [/sbin/fsck.ext2 (1) -- /media/store7] fsck.ext2 -a -C0 /dev/sdb3 > > /dev/sdb3: clean, 101090/9781248 files, 8189283/19531023 blocks > > [/sbin/fsck.ext2 (1) -- /media/store8] fsck.ext2 -a -C0 /dev/sdb5 > > /dev/sdb5: clean, 12/9781248 files, 320190/19531015 blocks > > [/sbin/fsck.ext2 (1) -- /media/store9] fsck.ext2 -a -C0 /dev/sdb6 > > /dev/sdb6: clean, 79374/9781248 files, 9628858/19531015 blocks > > [/sbin/fsck.ext2 (1) -- /media/store10] fsck.ext2 -a -C0 /dev/sdb7 > > /dev/sdb7: clean, 166107/12222464 files, 9717743/24440881 blocks > > fsck died with exit status 8 > > > > Fri May 6 11:21:17 2011 > > ---------------- > > > > > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers unstable > > APT policy: (500, 'unstable') > > Architecture: i386 (i686) > > > > Kernel: Linux 2.6.31.6 > > > > > > > > > > > > > > _______________________________________________ > > Virtual-pkg-base-maintainers mailing list > > virtual-pkg-base-maintain...@lists.alioth.debian.org > > http://lists.alioth.debian.org/mailman/listinfo/virtual-pkg-base-maintainers > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
