Hangs on boot without message

[UWP]

Binary package hint: e2fsprogs

In fact, the bug might not be a problem of fsck itself.

But first I'll try to describe it. We got VMs here and one user reported after changing /etc/fstab it doesn't boot anymore.
It wasn't easy to see, but he wrote

/dev/mapper/volg1/logv1 /data ext4 defaults 0 2

instead of

/dev/mapper/volg1-logv1 /data ext4 defaults 0 2

With this wrong line in /etc/fstab the boot-process had been hanging (see attached image). When you look exactly you'll notice that /data is missing. But it's not easy to track missing stuff. And now think about this user wouldn't boot after this work in /etc/fstab. Assume he's doing different things and boots maybe next week. In my opinion we would never have found this problem. We wouldn't even search in /etc/fstab. Conclusion: I'd like to have a more verbose output what's been going on here, maybe some kind of error message, like: No filesystem found. Or anything like that. Maybe there are some boot-options which make fsck talk more about what it's doing?

This was at ubuntu server 10.4 (lucid) 64 bit. Maybe it's because someone installed an X-Server onto it, which might change the boot-screens? Thanx for any further help with this topic!

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: e2fsprogs 1.41.11-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.42-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-server x86_64
Architecture: amd64
Date: Thu Sep 9 16:35:57 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
SourcePackage: e2fsprogs