You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Invalid content in Journal - how to mount? how to backup?

Hello all,

Can mount my second HD anymore (no Icon on the dsktop).

Disk Tool reports the follows:
Started verify/repair volume (filesystem) on disk disk0s3 HD2
*Invalid content in Journal*
Checking Journaled HFS Plus volume
Checking Extents Overflow file
Checking Catalog file
... and so on ...

Repairing shows success, but it's not really successfull because if I run the verify a second
time, the error apears again and the disk is still unmountable.

Did a lot of reading in the www.
Found this:
http://dmunsie.wordpress.com/code/hacks/
but did not help for me.

Some hints goes to DiskWarrior. But just for a try, 100$ is quite a lot.

Tryed to create a dmg with command:
dd bs=65k if=/dev/disk0s3 of=/Volumes/Macintosh\ HD/Backup/HD2.dmg conv=noerror,sync
it works (need 14 hours!) bit I can not open the dmg (error: file damaged).


Does anyone have a hint for me.
Thanks very much
Michael

From the SysProfiler: (sorry in german!)

ST3500630AS:

Kapazität: 465.76 GB
Modell: ST3500630AS
Version: 3.AAK
Seriennummer: 9QG1RTER
Wechselmedien: Nein
Absteckbares Laufwerk: Nein
BSD-Name: disk0
Protokoll: ata
Einheiten-Nummer: 0
Socket-Typ: Serial-ATA
Name des Schachts: "A (upper)"
Treiber für Mac OS 9: Nein
Partitionstabellentyp: APM (Apple Partition Map)
S.M.A.R.T.-Status: Überprüft
Volumes:
HD2:
Kapazität: 465.64 GB
Beschreibbar: Ja
Dateisystem: Journaled HFS+
BSD-Name: disk0s3
Mount-Point: <<<<< Mount-Point lost!! <<<<<<<

G5, Mac OS X (10.5.2)

Posted on Feb 19, 2008 2:00 PM

Reply
Question marked as Top-ranking reply

Posted on Feb 29, 2008 12:59 PM

I just had this problem on my daughter's Macbook. I eventually resolved it by running:

/System/Library/Filesystems/hfs.fs/hfs.util -N /dev/disk0s2

Though I see in your case it would be disk0s3 instead. 🙂 Hope this helps!
36 replies

Jul 27, 2008 10:28 PM in response to waj3

THANK YOU for the tip to disable journaling and then mount in Disk Utility. Seems to be working like a charm.

My problems started around the time I set up an Airport Extreme earlier this week with Airdisks for the first time. I think I ended up causing this drive to hang one time too many and then turning it off without ejecting it first. They always warn about the possibility of file corruption from this, but it's the first time I've seen it happen.

Anyway, the disk mounted fine in Disk Utility after running the command line in Terminal, but I did get the "Don't count on this" warning, so I'm doing a file-level copy to another disk (don't want a true image, in case that copies over the journal errors), then will reformat the flaky one and see if it holds up over time.

Someone else mentioned not trusting WD drives because of this, but it seems to me - in my case at least - it's probably not a hardware issue. I hope.

Oct 4, 2008 8:30 AM in response to stevewhitemd

Yup, thanks i thought my life waas over when i woke up one morning and saw my hard drive not mounted, i tried drive genius but came up with the same result as dixk utility (Invalid content in Journal), then i copied the code into the terminal "disk2s3", pressed enter and my life was filled with joy again.

just one question will this affect me in the future would it be wise to back up now, incase it corrupts my HD for life?

Thanks
BPizzo

Oct 22, 2008 1:14 AM in response to waj3

his solution is spelled out nicely here:
http://www.macfixit.com/article.php?story=20080627103757208

Summary:
{quote}
Fix First, with the problematic drive connected, run the following command in the terminal:

* diskutil list

This will list the volumes on the drive, and give you their identifiers. Locate the drive's volume name, and get the identifier for that drive, and then run the following command to remove the journal on the device:

* /System/Library/Filesystems/hfs.fs/hfs.util -N /dev/IDENTIFIER

NOTE: The "IDENTIFIER" should be something like "disk0s3"

After these commands have been run, try mounting the drive again with Disk Utility. You should be able to re-enable journaling on the volume after it mounts. {quote}

Nov 1, 2008 7:02 AM in response to sstoll

Shazamm! I'm a new man. It worked for me to. Had to use the "sudo" before the command then found that I was off a digit on the identifier. I had to run it twice but on the second time I got all of my pictures back - thousands of them. I am off to the store to buy a second back up. Thank you, Thank you. Still having trouble with a second partition but I got the main stuff I wanted. Today is the first day of the rest of my life.

Nov 14, 2008 1:23 AM in response to ddev2000

Thank You SO much for the additional information...

I tried the /System/Library/Filesystems/hfs.fs/hfs.util -N /dev/disk1 buisness but without being able to get a list of the current drives I had no luck! You Little Ripper!!! I now have al my data back and am backing it onto another drive.... you're a lifesaver!
Cheers!!

Nov 22, 2008 4:38 PM in response to j2thaB

Hello, could I get some assistance for a novice here (me)? I have the same "invalid content in journal" issue on my daughter's iBook G4 running 10.5.5. I get a kernel panic during the boot and have to shut down. If I boot with the Leopard Install disk I can get to Disk Utility, but as been mentioned before, repairing the disk appears to work, but really doesn't.
I've never used Terminal and don't even know how I would get there since I can't boot the computer. I don't own the current TTP or DW so I'm looking for a different option. Any help would be appreciated, please use "non-technical" terms or I probably won't get it. Thanks. Larry

Jan 22, 2009 5:36 PM in response to waj3

Is there any way to turn journaling back on? I tried running the same command with the -J option instead of -U but it says the volume is not an HFS+ volume. However, when I get info on the volume in Disk Utility it says that its MacOS Extended.

After doing some research I discovered that I have one of those Seagate drives with the bad firmware that causes the drive to stop responding for several minutes. I disabled the journaling thinking there was a problem with the disk, but it turns out its just a bug in the firmware. I'd like to turn Journaling back on without having to reformat...

Invalid content in Journal - how to mount? how to backup?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.