Benches macOS

15

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

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

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!! <<<<<<<

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    waj3

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    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!

  2. 0

    Community User

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    TechTool Pro 4.6.1 might better handle a corrupt journal, but it is harder to deal with I think and this article suggests it won't succeed. They also had a copy of Drive Genius (which was updated for Leopard).

    http://www.edn.com/blog/400000040/post/1670013967.html

    A sector copy would be worth trying.

    Backups. at least two in case one goes south or you end up copying bad data over good.

    Rather than wait and then face $89 for Disk Warrior, it has been worth the cost and the upgrade with each new OS. I keep TTP handy 'just in case.' A car mechanic (or dentist) wouldn't have only one tool for every case.

  3. 0

    waj3

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    By the way... the -N flag disables the journal on a raw device (as opposed to the -U flag for mounted filesystems). I had basically tried it as a last resort, since I was not about to spend any money on one of the commercial recovery tools.

  4. 0

    mtu

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the tips.

    But unfortunately nothing did help for me.

    I also tried the ddrescue (
    http://ddrescue.darwinports.com/). .dmg is created but i can not open it (errorMsg something like "file in error").

    In the end, I gave up and formated the disk! Luckily I had a second backup so I lost just some pictures.

  5. 0

    DrewGD

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Had the same problem with an external USB 250GB: "Invalid content in Journal"

    Diskwarrior (for leopard) fixed it in 1 click. I'd recommend trying. Hope it works for you!

  6. 0

    paulcone

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    if the drive won't mount, then how can hfs.util see it?

  7. 0

    paulcone

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    never mind, duh, i found the answer in Disk Utility by hitting the i button...

  8. 0

    stevewhitemd

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Had the same exact problem on a WD 500GB Firewire800/400/USB drive. Wouldn't mount, and Disk Utility 'repaired' it without fixing the problem. I tried waj3's trick, figuring that if it didn't work I'd go buy Diskwarrior. I copied the line into the Terminal application (my drive was 'disk1s2') and hit return.

    Ta-da! It worked perfectly. I'm in the process of copying the files, all of which I can now see, to another backup.

    Thank you!

  9. 0

    Jhary

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you, this worked perfectly for me, as well. I found out the disk designation by getting info in Disk Utility. I also had to be root (or, I assume that sudo would work as well) in order for the command to run.

    This saved 300 gigs of content. Thanks.

  10. 0

    ddev2000

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Your trick:

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

    Also worked for me (Leopard 10.5.2 on a MacBook Pro.

    This seems to be the same hack that the one mentionned here:

    http://dmunsie.wordpress.com/code/hacks/

    But the last one is surely more instructive (source code included!).

    Many thanks,

    Daniel

  11. 0

    krystaleyn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    THANK YOU. I have a question though - does the drive last after doing this? I'm no longer getting an error when trying to repair the drive, but disk utility gave me this big red warning about how it was letting me use the disk but with limited functionality, and I should get my data off there quickly. Should I be reformatting the drive?

    Unfortunately, I've now had both my 500GB WD hard drives with serious problems - one overheats, and the other (brand new) is having this journalling problem. No more WD for me...

  12. 0

    crnflakeboi75

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You ROCK! This was the second time this happened to me because I had unplugged the external drive's power source unexpectedly before ejecting it from the Mac. The first time I had to use DataRescue (which is great) at some expense to get the info. This time around, your insight saved me a lot of time. Wish I had found this the first time!

  13. 0

    Elembytes

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can't believe this- you helped me fix my problem too. Lighting had knocked our power out briefly and I had been using my external Iomega 250 Gig hard drive to do video editing. Well, Apparently it goofed it up to where it wouldn't mount either. I thought I was a dead duck. Thank you to all who posted I entered the Terminal Program, copied the line mentioned in the post threads on this topic and bang- it worked and I am able to back up the video files and will reformat my external drive and do this all over again. Apple should really make it so that Disk Utility truly does FIX the problem. It said it fixed the issues but it never did and the images would NOT mount. Now they are so I can fix the problems. WOW! BLESS YOU ALL! Hope APPLE wakes up and fixes things better so their clients don't lose everything. So much for backup's! This was truly a close scenario!

  14. 0

    sstoll

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you, this worked also perfectly for me.

    Other Tools could't rapair this damage!

    Thanks again!

  15. 0

    Fumes

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm trying the command line trick on this and I get "can't open: /dev/rdisk2s3 (Permission denied)

    "

    Anyone know what that is?

    I took the drive out of my WD MyBook for a last ditch effort.