Hi,
I too are seeing the fsck problem since Feisty upgrade but not on every re-boot
(just on most). Appear to be identical apart from last digit of /dev/.tmp-254-7
and no problem with system clock.
Contents of fstab are:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda9 -- converted during upgrade to edgy
UUID=b783f1ef-825e-441f-a1c7-c5347a845ce7 / ext3
nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# /dev/hda2 -- converted during upgrade to edgy
UUID=c1f0eb56-d865-41d5-939b-7024f878d000 /boot ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda5 -- converted during upgrade to edgy
UUID=65637ffb-91f5-43d3-a352-98572d5da2c7 /home ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/sda1 -- converted during upgrade to edgy
UUID=ccb1b982-7c67-409c-9ea6-34d3f7b40920 /mnt/backup ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda10 -- converted during upgrade to edgy
UUID=c02dd68d-b574-4934-bcc5-19f35d46d68d /mnt/music ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda7 -- converted during upgrade to edgy
UUID=f86f293f-ce60-4307-b14d-3c0734f5e7f2 /mnt/oldmusic ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda6 -- converted during upgrade to edgy
UUID=963bd4dc-7188-4b20-ac3a-c832a183969d /mnt/oldroot ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda8 -- converted during upgrade to edgy
UUID=7ff546c5-58de-4b0c-8712-8eb40f7fc827 /mnt/pictures ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/sda2 -- converted during upgrade to edgy
UUID=a2cddaab-4024-4f17-9146-962cc29f801b /mnt/video ext3
nouser,defaults,atime,auto,rw,dev,exec,suid 0 2
# /dev/hda1 -- converted during upgrade to edgy
UUID=0CE03ECEE03EBDB0 /windows/c ntfs
defaults,nls=utf8,umask=0222,uid=0,gid=46,auto,ro,nouser 0 1
# /dev/hda3 -- converted during upgrade to edgy
UUID=1e2e8acf-ae46-481e-acd2-764b662b9296 none swap sw 0 0
# DVD ROM and DVD RW
/dev/scd0 /media/cdrom udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
/dev/scd1 /media/dvdrw udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
Text of the log file from fsck
fsck 1.40-WIP (14-Nov-2006)
/dev/evms/sda2: clean, 37/96384 files, 53274/192780 blocks
/home has been mounted 30 times without being checked, check forced.
/home: 32140/1311552 files (9.9% non-contiguous), 1167339/2622603 blocks
Backup: clean, 2992/1310720 files, 332655/2620595 blocks
/mnt/video: clean, 3489/4374528 files, 4072960/8735335 blocks
/mnt/music: clean, 3468/2443200 files, 4323987/4883752 blocks
/: clean, 159119/1311552 files, 1309670/2622603 blocks
fsck.ext3: No such file or directory while trying to open /dev/.tmp-254-7
/dev/.tmp-254-7:
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>
video: clean, 1040/26214400 files, 31579281/52428127 blocks
fsck died with exit status 8
All appear OK and I've tried working through each of the file systems in
turn (using -n to avoid any changes) and they all appear to check OK.
Don't know where to go on further diagnostics.
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
