[Bug 118397] Re: checkfs fails at startup while trying to check /dev/.tmp-XXX
Launchpad Bug Tracker
118397 at bugs.launchpad.net
Tue Dec 4 04:18:45 UTC 2012
[Expired for sysvinit (Ubuntu) because there has been no activity for 60
days.]
** Changed in: sysvinit (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/118397
Title:
checkfs fails at startup while trying to check /dev/.tmp-XXX
Status in “sysvinit” package in Ubuntu:
Expired
Bug description:
Binary package hint: initscripts
When starting, checkfs checks the filesystem and fails while trying to
check something in /dev/.tmp-XXX . The strange thing is that
sometimes, it starts correctly, sometimes not. When it fails, I have a
shell access which $PATH is not correct (/bin:/sbin), so it complains
about not finding less, apt-get & stuff. If I run /etc/init.d/checkfs
start again, it does not complain. I simply hit ^D and the system
starts correctly.
Here's the log:
Log of fsck -C -a -t ext3 /dev/hda1
Sat Jun 2 15:46:02 2007
fsck 1.40-WIP (14-Nov-2006)
/: clean, 171660/1221600 files, 870791/2441872 blocks
Sat Jun 2 15:46:02 2007
----------------
nicole at mamuntu:~$ sudo cat /root/checkfs
Log of fsck -C -R -A -a
Sat Jun 2 15:46:04 2007
fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: No such file or directory while trying to open /dev/.tmp-254-2
/dev/.tmp-254-2:
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
Sat Jun 2 15:46:04 2007
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397/+subscriptions
More information about the foundations-bugs
mailing list