Re: Consistent kernel panic on volume mount
Re: Consistent kernel panic on volume mount
- Subject: Re: Consistent kernel panic on volume mount
- From: David Gatwood <email@hidden>
- Date: Thu, 20 Jan 2005 13:09:40 -0800
On Wed, 19 Jan 2005, Carsten G Pedersen
<email@hidden> wrote:
Andrew Gallatin <email@hidden> wrote on 01/19/2005 10:07:48 PM:
I looked at this a bit earlier. This code seems to get called when
replaying the journal. Would it work to simply mount the filesystem
read-only (so as to avoid writes), and then to disable journaling
using hfs.util? Or will the kernel insist on replaying the journal
even with a read-only fs?
Unfortunately yes it does seem to be called when mounting read-only
too -
I get the same panic when doing a mount_hfs -o rdonly -j
Instead of mounting the volume, try just doing
fsck_hfs -f -n /dev/disk#s#
with # being the appropriate numbers for the volume in question. This
will cause
the journal to be ignored and disable any writes. See what errors it
returns. If it
doesn't show any serious errors, you might remove the -n. This
-should- cause the
journal (which sounds like it is corrupt) to be discarded, and at that
point, you
should be able to mount the disk. If that doesn't occur, something
Really Weird(tm)
is going on.
That said, as someone else already mentioned, I'd be tempted to do a
block-level
backup of the drive to a file on a larger disk using dd before I ran
fsck_hfs
just to be safe.
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden