Comment 6 for bug 118397

Same problem here. This appears to have happened recently, however I don't reboot too often. Here is the log from /var/log/fsck/checkfs

Log of fsck -C -R -A -a
Sun Sep 16 09:36:44 2007

fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: No such file or directory while trying to open /dev/.tmp-254-0
/dev/.tmp-254-0:
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>

fsck died with exit status 8

Sun Sep 16 09:36:45 2007
----------------