I'm currently operating from a live CD as my /usr partition is
refusing to mount at boot.

fsck is not working - output below.

# fsck -r /dev/hda5
fsck 1.38 (30-Jun-2005)
fsck.jfs version 1.1.10, 19-Oct-2005
processing started: 4/23/2008 6.10.34
The current device is: /dev/hda5
Block size in bytes: 4096
Filesystem size in blocks: 1833410
**Phase 0 - Replay Journal Log
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 1428656128
logredo failed (rc=-242). fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
ujfs_rw_diskblocks: read 4096 of 16384 bytes at offset 1428652032
Unrecoverable error reading M from /dev/hda5. CANNOT CONTINUE.
fsck.jfs /dev/hda5 failed (status 0x8). Run manually!

the -a and -p options give the same output.


Peter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

2008/4/23 Peter Tynan <happy@sdf.lonestar.org>:
> I'm currently operating from a live CD as my /usr partition is
> refusing to mount at boot.

more info

# fsck.jfs -v /dev/hda5
fsck.jfs version 1.1.10, 19-Oct-2005
processing started: 4/23/2008 6.39.46
Using default parameter: -p
The current device is: /dev/hda5
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 1833410
**Phase 0 - Replay Journal Log
LOGREDO: Allocating for ReDoPage: (d) 4096 bytes
LOGREDO: Allocating for NoDoFile: (d) 4096 bytes
LOGREDO: Allocating for BMap: (d) 28224 bytes
LOGREDO: Allocating for IMap: (d) 18464 bytes
LOGREDO: Allocating for IMap: (d) 2048 bytes
LOGREDO: Allocating for IMap: (d) 2048 bytes
LOGREDO: Allocating for IMap: (d) 2048 bytes
LOGREDO: Allocating for IMap: (d) 2048 bytes
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 1428656128
LOGREDO: Error in volume (d) 0.
LOGREDO: I/O error attempting to read block 0x055279.
LOGREDO: bread() Read block (0x055279) failed.
LOGREDO: updatePage: bread failed (1). (rc = (d) 1)
LOGREDO: doAfter: updatePage failed. (logaddr = 0x019b73f4, rc = (d) 242)
LOGREDO: Invalid RedoPage record at 0x019b73f4.
logredo failed (rc=-242). fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
ujfs_rw_diskblocks: read 4096 of 16384 bytes at offset 1428652032
Unrecoverable error reading M from /dev/hda5. CANNOT CONTINUE.
Fatal error (-10015,30) accessing the filesystem (1,1428652032,16384,0).
processing terminated: 4/23/2008 6:40:21 with return code: -10015
exit code: 8.



Peter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Apr 23, 2008 at 06:16:36AM +0000, Peter Tynan wrote:
> I'm currently operating from a live CD as my /usr partition is
> refusing to mount at boot.
>
> fsck is not working - output below.
>
> # fsck -r /dev/hda5
> fsck 1.38 (30-Jun-2005)
> fsck.jfs version 1.1.10, 19-Oct-2005
> processing started: 4/23/2008 6.10.34
> The current device is: /dev/hda5
> Block size in bytes: 4096
> Filesystem size in blocks: 1833410
> **Phase 0 - Replay Journal Log
> ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 1428656128
> logredo failed (rc=-242). fsck continuing.
> **Phase 1 - Check Blocks, Files/Directories, and Directory Entries
> ujfs_rw_diskblocks: read 4096 of 16384 bytes at offset 1428652032
> Unrecoverable error reading M from /dev/hda5. CANNOT CONTINUE.
> fsck.jfs /dev/hda5 failed (status 0x8). Run manually!
>
> the -a and -p options give the same output.

I don't have fsck.jfs installed so I can't check the man page. I used
to run jfs and never had a problem, until I heard that IBM was dropping
support.

What does the -y option give?

Do you have backups?

What does SMART data show on this drive?

What does /var/log/syslog show? Are there any errors? IOW, is this a
hardware problem?

If you are running fsck from the liveCD, it may be incompatible with the
actual file system. Try instead to boot the real system but add to the
kernel command line: init=/bin/sh

This will bring up your kernel with only the / fs mounted ro and nothing
else done, not even init runing. You can then manually run fsck.jfs
directly (read its man page somewhere first since its on your /usr fs)
using the fsck which matches the fs.

Good luck.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org