Public bug reported:

output of /var/log/fsck/checkfs:

Log of fsck -C -R -A -a 
Sun Apr 15 16:12:15 2007

fsck 1.40-WIP (14-Nov-2006)
Replaying journal..
Replaying journal..
Replaying journal..
Replaying journal..
Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal
Blocks (total/free): 122480/104138 by 4096 bytes
Filesystem is clean
Reiserfs journal '/dev/sdd1' in blocks [18..8211]: 0 transactions replayed
Reiserfs journal '/dev/sde1' in blocks [18..8211]: 0 transactions replayed
Replaying journal..
Checking internal tree..finished
Reiserfs super block in block 16 on 0x831 of format 3.6 with standard journal
Blocks (total/free): 122480/114265 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x841 of format 3.6 with standard journal
Blocks (total/free): 122480/114265 by 4096 bytes
Filesystem is clean
Reiserfs journal '/dev/sdf2' in blocks [18..8211]: 0 transactions replayed
Reiserfs journal '/dev/sdb4' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
Reiserfs super block in block 16 on 0x852 of format 3.6 with standard journal
Blocks (total/free): 4630736/4622383 by 4096 bytes
Filesystem is clean
Replaying journal..
Reiserfs journal '/dev/sdf4' in blocks [18..8211]: 0 transactions replayed
Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal
Blocks (total/free): 122480/104138 by 4096 bytes
Filesystem is clean
Reiserfs super block in block 16 on 0x831 of format 3.6 with standard journal
Blocks (total/free): 122480/114265 by 4096 bytes
Filesystem is clean
Reiserfs super block in block 16 on 0x841 of format 3.6 with standard journal
Blocks (total/free): 122480/114265 by 4096 bytes
Filesystem is clean
Reiserfs super block in block 16 on 0x852 of format 3.6 with standard journal
Blocks (total/free): 4630736/4622383 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x814 of format 3.6 with standard journal
Blocks (total/free): 55621040/11372883 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x854 of format 3.6 with standard journal
Blocks (total/free): 55621040/11377767 by 4096 bytes
Filesystem is clean
fsck.jfs version 1.1.11, 05-Jun-2006
processing started: 4/15/2007 16.12.29

Error: Cannot open device UUID=ac9fcff8-4718-42c8-b602-ae82b4afcd57

Usage:  fsck.jfs [-afnpvV] [-j journal_device] [--omit_journal_replay]
[--replay_journal_only] device

Emergency help:
 -a                 Automatic repair.
 -f                 Force check even if file system is marked clean.
 -j journal_device  Specify external journal device.
 -n                 Check read only, make no changes to the file system.
 -p                 Automatic repair.
 -v                 Be verbose.
 -V                 Print version information only.
 --omit_journal_replay    Omit transaction log replay.
 --replay_journal_only    Only replay the transaction log.
Reiserfs super block in block 16 on 0x814 of format 3.6 with standard journal
Blocks (total/free): 55621040/11372883 by 4096 bytes
Filesystem is clean
Reiserfs super block in block 16 on 0x854 of format 3.6 with standard journal
Blocks (total/free): 55621040/11377767 by 4096 bytes
Filesystem is clean
fsck died with exit status 16

Sun Apr 15 16:12:34 2007
----------------

everytime I reboot, I either have to press ctrl + d, or enter root
password and do something, the partition is intact ...

please fix, thanks (Ubuntu Feisty, state from apr 15th 2007), mirror
at.ubuntu.com

** Affects: Ubuntu
     Importance: Undecided
         Status: Unconfirmed

-- 
checkfs & fsck command options don't work with fsck.jfs at boot
https://bugs.launchpad.net/bugs/106782
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

Reply via email to