First hack of what is likely to become many over time. This one was done because we had an HFS+ filesystem at work that had become corrupted to the point that fsck and DiskWarrior wouldn’t fix it. The problem was that the journal had become corrupted, and fsck.hfs doesn’t know how to actually fix the journal. DiskWarrior probably would’ve worked just fine, but due to the large size of the volume (1.4TB) and the number of files (> 11 million), we repeatedly ran out of memory when trying to use DiskWarrior.

Now, of course, we have a backup of the data. But, copying 1.4TB of data is sloooow. Plus, our backup was located in another state, so we had to make a copy of the backup to send up here. Did I say slow?

So, while waiting for the backup to copy, I investigated a bit further. After looking at the system.log, I found this:

jnl: open: journal magic is bad (0x1fd17 != 0x4a4e4c78)
hfs: late jnl init: failed to open/create the journal (retval 0).
hfs(3): Journal replay fail. Writing lastMountVersion as FSK!
jnl: is_clean: journal magic is bad (0x1fd17 != 0x4a4e4c78)
hfs: late journal init: volume on disk3s3 is read-only and journal is dirty. Can not mount volume.

That’s when I realized that the journal was corrupt. Quickly searching on google, I found that you can turn off the journal on an HFS filesystem — if it is already mounted. Ouch.

So, I turned to the filesystem spec. Looks like there are two fields in the header that journaling uses — one that has a bit for journaling, the other that says which block the journal is located in. Ah-ha!

I did some experimentation on some HFS+ disc images, and found that I could successfully turn off journaling by setting that bit to zero and resetting the journal location to zero as well. I wrapped that into a quick little hack, crossed my fingers, and ran it on the corrupted filesystem. And it mounted. Just for safety, I also ran fsck on it again, and then later re-enabled journaling.

So, while this worked fine in this instance, I don’t know if there were any other side effects. One potential side effect is that the old journal is still reserved — that space might be gone forever. I haven’t looked it, but really, the journal shouldn’t be taking too much space out of 1.4TB.

Here is the code to that hack — feel free to use it, but please don’t come after me if it kills the filesystem. This should really only be used if you either have a good backup or you have no backup and you’ve tried everything else to get your data back. Also, I should point out that if your journal isn’t corrupt, this isn’t likely to do anything for you.

Update Dec 8 2007:

I’ve made some changes to make this compatible with Leopard — I had two problems. One was that I wasn’t checking the return value from mmap() correctly, which was masking the other problem I had which was my offset to mmap() wasn’t a multiple of page size. Instead of trying to figure up a multiple to use, I instead just set the offset to zero and adjusted where I was reading and writing to. I tested with a HFS+ disk image and not a real disk, but it should still work in theory. Same warnings as above — I hope it works for you, but really only use this if it’s your last hope or you like living dangerously with your data.


  1. Hi

    Firstly – thank you.

    I’m not a mac user, generally working on linux and windows, but I was recently enlisted to try and fix an associate’s massively corrupted mac filesystem.

    Thanks to this useful piece of code, a friend of mine and I were able to do so – we appreciate you posting this online.

    We had to work around one major problem with the code in resolving the problem, though. I’m posting info here in the hopes it helps someone else.

    Recent versions of OSX don’t seem allow you to mmap a disk device such as /dev/diskXsY. The mmap call in the referenced code thus fails. We tried the /dev/rdisk* files too.

    By the way – because of the cast to the mmap to an unsigned varchar, the code doesn’t catch the mmap failure, and simply “segfaults” when it tries to validate it’s reading an hsfs+ disk.

    This is on an intel chipset, by the way with the latest osx as at 3 March 2007 – I don’t know what version that is.

    So to anyone that wants to use this code, you’re going to have to enlist someone that knows all about the “dd” command, to get them to help you with the below.

    NOTE: be very very careful with dd – you can completely obliterate years of work by accidentally switching “i” and “o” in the command line..

    1) make a complete disk image of your drive BEFORE doing anything.

    2) read the first few kb of the partition to a file using the “dd” command

    3) compile disable_journal (cc -o disable_journal disable_journal.c)

    4) run ./disable_journal against the file you created with dd, and check you get a success message.

    5) then write the updated first few kb BACK to the disk, again using the dd command.

    Best of luck to others in a similar predicament.


  2. Hi Oskar — glad it was a help for you. That is very odd about not allowing the mmap for a disk device — I personally have not seen that, but I have seen other behavior that is different for the Intel macs.

    As for the dd command, all you should need to copy is the first 4 sectors — the following dd command should work (warning, even though I think this will work, please check it over before blindly running it on your hard drive — it might just erase everything):

    $ sudo dd if=/dev/diskXsY count=4 bs=512 of=foo
    $ ./disable_journal foo
    $ sudo dd if=foo count=4 bs=512 of=/dev/diskXsY

    Yes, I realize that the default value of bs is 512, but sometimes it doesn’t hurt to be a little more explicit.

    As for backing up the drive, that is always very good advice. You can use the dd command again for that, but you have to be very careful — the following should work:

    $ sudo dd if=/dev/diskXsY of=image_file.img

    Of course, you need to make sure that you have enough space available on your target drive to store this image — it will be the size of your bad drive.

    If anyone has any questions regarding this, please feel free to leave a comment — better to ask than to wipe out your drive 🙂

  3. Hi,

    Your program saved my 500gb disk.
    It took me quite long to find your page with google, more people might profit if it would be ranked higher..

    I think I will never use hfs journaling again on external hard disks. Probably I will switch to UFS…

    Thank you very much :))


  4. dmunsie:

    Could you please explain how to compile and use disable_journal.c? I have a HFS+ filesystem which refuses to mount because of an error replaying the journal, and have had no luck trying various other methods. I understand the hack may kill the filesystem, but I plan to reformat the volume after mounting it.

    Thanks in advance,

  5. Hi Liza —

    As long as you have the developer tools installed on your machine, you should be able to do the following:

    gcc -o disable_journal disable_journal.c

    That should give you an executable that you can run on the device for the disk — for example, on my machine the root filesystem is on /dev/disk2. On another machine it’s /dev/disk0s2. Unless you are running a RAID or it’s not your root filesystem, it’s most likely /dev/disk0s2 — though please verify using Disk Utility first.

    Also, if you are on an Intel Mac, check out the comments above. There are some differences between the PPC and Intel Macs beyond just changing the CPU.

    good luck!

  6. […] course, for some people, it’s not so simple: disable_journal.c was written by an Apple user who couldn’t get even DiskWarrior to fix the problem, so instead […]

  7. Hi there,

    your article and program saved a fairly full (and not backed up) Xserve RAID today as a last resort solution.
    Double thumbs up and many thanks for posting this.


  8. Hey Dennis…

    Do you think your hack will work for this error returned from Apple’s Disk Utility:
    “Invalid content in Journal”

    I have a 2-partition external hard drive. One partition mounts, the troubled one does not. DU says it “Repaired” the volume but after being “repaired” it still will not mount.

    From what you’ve said, I’m not sure if Disk Warrior will be able to correct (because it’s a problem with the journal). Also, since i just need to mount the volume – so I can copy the data and then re-initialize – your option may be a good one.

    Also, are there any bare bones instructions as to how to use your hack. I’m not a developer, but I do venture into Terminal when I have explicit instructions.

  9. Oliver — glad to hear it worked for you. Hopefully you won’t be in the situation where you need to use it again 🙂

    Rick — In my case, I think the reason DiskWarrior failed was because of the then large size of the volume. I would probably give DiskWarrior a try before resorting to this hack — unless you just don’t have the money for DiskWarrior or are willing to live with the possibility of losing your data.

    As for running it, you need to have the Developer Tools for OS X installed. They are on the OS install discs — if you have a DVD install, it should be on that disc. With CD installs, it’s usually on another disc. If all you have is the restore discs that came with your Mac, it will usually be on one of the discs — just look around for Developer and you should find an Installer package.

    Once you have them installed, you should be able to open a Terminal window, and navigate to the directory that you downloaded the code to and do the following (replace diskXsX with the device file for your drive — it should be listed in the System Profiller under USB or FireWire — you want the BSD name for the volume you are trying to fix):

    $ gcc -o disable_journal disable_journal.c
    $ ./disable_journal /dev/diskXsX

    Hopefully at this point, the journal is disabled, and you should be able to repair and mount the filesystem as normal. If you are successful, I highly recommend making a backup and then restoring that backup to a fresh format of the partition. This will insure that you don’t have anything nasty hanging around that might bite you later on.

    Also, I have only tested this under Tiger. In theory, it should also work in other versions of OS X, but it has not been tested. Also, I do not know if this is still necessary with Leopard, so if you are running Leopard, try using the built in tools first.

    Good luck!


  10. Hey Dennis,

    Looks like I have this problem now on an external FW drive. Was working fine for quite some time, upgraded to Leopard, Time Machine ran for a while but now it won’t mount and Disk Utility complains of the invalid journal contents. It doesn’t seem too interested in actually trying to fix it though.

    Unfortunately your neat little fixer fails with a segmentation fault under 10.5.1:

    OS Version: Mac OS X 10.5.1 (9B18)

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffffffff
    Crashed Thread: 0

    Thread 0 Crashed:
    0 disable_journal 0x00001d44 main + 184

    Thread 0 crashed with PPC Thread State 32:
    srr0: 0x00001d44 srr1: 0x0000d030 dar: 0xffffffff dsisr: 0x40000000
    r0: 0xffffffff r1: 0xbffff970 r2: 0xffffffff r3: 0xffffffff
    r4: 0x00000400 r5: 0x00000003 r6: 0x00000001 r7: 0x00000003
    r8: 0x00000000 r9: 0x00000400 r10: 0x8fe04e3c r11: 0xa0274898
    r12: 0x9158fcdc r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
    r24: 0x00000000 r25: 0x00000000 r26: 0xbffffa24 r27: 0x0000000c
    r28: 0x00000000 r29: 0x00000000 r30: 0xbffff970 r31: 0x00001ca4
    cr: 0x82000028 xer: 0x00000000 lr: 0x00001d14 ctr: 0x9158fcdc
    vrsave: 0x00000000

    Binary Images:
    0x1000 – 0x1ffe +disable_journal ??? (???) /Users/brett/Desktop/disable_journal
    0x8fe00000 – 0x8fe309d3 dyld 95.3 (???) /usr/lib/dyld
    0x91464000 – 0x9146fffb libgcc_s.1.dylib ??? (???) /usr/lib/libgcc_s.1.dylib
    0x91583000 – 0x9171cfe3 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
    0x94a03000 – 0x94a08ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
    0xffff8000 – 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

    I’ve still got Tiger running on some old G4s so I’ll connect the drive to one of those and give it another shot.

  11. Hi Brett —

    I’m curious as to how you ran this program — you didn’t post it above.

    I’m also checking on Leopard myself to see if it works or not — I’ll post up more when I find out.

  12. Brett —

    I just updated the utility for Leopard — tested on both Intel and PPC. Give it a try on your end, and let me know how it works.


  13. Sorry Dennis – should’ve also mentioned I was running on an iMac G5. Not segmentation fault this time, just this:

    Sophie:Desktop brett$ ./disable_journal /dev/disk2s3
    mmap: Invalid argument

    However it worked when I used dd as you explained earlier:

    Sophie:Desktop brett$ sudo dd if=/dev/disk2s3 count=4 bs=512 of=foo
    4+0 records in
    4+0 records out
    2048 bytes transferred in 0.014393 secs (142290 bytes/sec)

    Sophie:Desktop brett$ ./disable_journal foo
    open: Permission denied

    Sophie:Desktop brett$ sudo ./disable_journal foo
    attributes = 0x00006000
    journal has been disabled.

    Sophie:Desktop brett$ sudo dd if=foo count=4 bs=512 of=/dev/disk2s3
    4+0 records in
    4+0 records out
    2048 bytes transferred in 0.020187 secs (101452 bytes/sec)

    I then opened Disk Utility again and tried to mount it. No joy. So I tried to repair the disk – this time no error about invalid journal content:

    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking multi-linked directories.
    Checking volume bitmap.
    Checking volume information.
    The volume Tara appears to be OK.

    And it then automatically mounted and Time Machine kicked back into action after all these weeks. And I can now also retrieve my FLACs on that drive from the Pearl Jam show I went and saw on my birthday in Adelaide.

    Happy happy joy joy! Much appreciated Dennis!

  14. You guys have helped me to save my backup HD! Thanks a lot Dennis and everyone who contributed.

  15. Brett —

    I think the failure you got when you ran it directly on the device was because you didn’t use sudo. Only root has the permissions to write directly to the device. But, even still, it’s probably safer to make a copy of those sectors and then work on the copy.

    Stefman —

    Glad to have helped out!

  16. Is there any way to use this if I don’t have developer tools installed?
    I’m using Leopard 10.5.1 on a Core 2 duo Powerbook.


  17. Martin —

    I highly recommend installing the Developer Tools if you can, but I have compiled a universal binary version that I have uploaded to here – http://munsie.net/bin/macosx/disable_journal.gz — simply download it, double click on it to expand it, and then run it from the terminal as specified above.

  18. Hi,
    I’m probably just missing something unbelievably stupid, but when I run the code, this is what I get:

    Biblioteka:Downloads Saulius$ sudo ./disable_journal /dev/disk4s3
    sudo: ./disable_journal: command not found

    P.S. I am using the UB version and don’t have the developer tools installed

    Thanks a lot!

  19. Well, nvm I just buckled down and found my OS X disks, installed the developer tools, then took the dd root and I’m well on my way to recovering files. thank god for this piece of code!

  20. Hi Saul —

    Glad to hear that you got things working — I can’t be sure, but I suspect the problem might be related to the version of OS X you are running. I am suspecting that you are not running Leopard, which is the version I used to compile against.

    I will try to compile a universal version against the 10.4 SDK at some point, and post that instead. That should make it run on Tiger as well. Anything before Tiger is not likely to happen by me, so I would recommend for those users that they install the developer tools if they can and compile a version for themselves.

  21. surprisingly, I am running leopard, so that probably isn’t it.

  22. I had the same error when I initially unziped the program. It turned out to be a permissions problem.

    chmod 755 disable_journal

    This should make the program executable and resolve the issue.

  23. I forgot to mention that your program saved my bacon, not to mention preventing much rending of cloth and gnashing of teeth. This posting was kind of obscure within the google search I performed. There wasn’t even mention of the problem on Apple’s site, and only sparsely on one or two forums. Is this not a common problem, or are we the only ones that were gullible enough to enable journaling? I am having more problems with mac software than I have ever had in before, and I have been using them since my days in college (I refuse to date myself at this point). Maybe I was just lucky or spoiled in the past, but my mac experience is beginning to feel more like a windows experience all the time.

    Thanks again for the help here.

  24. Al —

    Thanks for the tip. I quickly tried changing permissions on my end, because that was my first thought as well, but I got a permission denied and not the command not found that Saul got. So, I just figured that it was more likely there was some other compatibility issue on his end — of course, that could still be the case since we don’t have all the info. But, I am glad to know that the binary I posted at least worked for someone.

    As for the problem at hand, I’ve personally only ran into it one time (knocks on wood…) — and this is even after working at a company where we had 100% of our users on OS X and about 30-40 machines total. At home, I have quite a few Macs for myself and the rest of the family, and all of them have journaling turned on. Again, haven’t ran into a problem yet.

    I tend to think that the cause of the problem is probably pretty rare — that’s why we haven’t seen much about it on the web. But, since fsck_hfs can’t fix a corrupted journal, the problem becomes even worse when it does come up.

  25. Oh WOW! Once again, thank you ALL for all your contributions to this page/thread! That has saved my bacon as well! Only 300 gigs standing to be lost, but it was an important 300 gigs (a gig here, a gig there, pretty soon we’re talking about some REAL space). One question… Will journalling now be disabled for good on my second partition (the one on which I ran this process)? So that this can never happen again?

  26. One more question…. My officemate (a linux person) says, well, won’t I experience performance degradation on searches with journalling turned off? I don’t understand the whole theory behind journalling enough to know what the implications of turning it off are. Should I be re-enabling it somehow and just keep your hack in my back pocket for when this happens again?

  27. Tyson –

    Glad it was useful to you!

    Journaling will remain off unless explicitly turn it on again. You should be able to use the hfs.util command line tool to turn it on again — the J option and the mount point (most likely either / or somewhere in /Volumes) are the only options you’ll need to pass. You will need to do this as root — use the sudo command for this.

    As for what journaling does, it has nothing to do with searches — it is basically a way for the filesystem to be properly cleaned up in the case of a crash. The journal can be replayed as necessary to bring the filesystem up to date. I would recommend taking a look at the wikipedia page on Journaling file systems — http://en.wikipedia.org/wiki/Journaling_file_system .

  28. I’m having similar issues with an internal drive on a (newest gen) MacBook Pro. For the last two days, my computer has been reduced to a really nice Windows XP machine. Anyone out there have any suggestions as to how I can get this fixed? Luckily, worst-case, I can access the partition via MacDrive from XP & copy it off, but I’m really trying to avoid having to reinstall the OS.

  29. Found the following in an Apple forum discussion thread.

    This is a Terminal command, and you should change “disk0s2” to the correct one for your disk (enter DiskUtility, select the volume and hit the “info” button to have the correct name).

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

    This seems to do the same thing that your hack (sets the journal bit on disk to false)

  30. Thanks a bundle for this page.
    I had an “Journal replay returned error = 22”.
    After disabling it with -N (thanks apple for not making this available in DiskUtility)
    it would neither verify nor repair in DU.
    I could mount it using
    /System/Library/Filesystems/hfs.fs/hfs.util -m disk0s2 /mnt fixed readonly suid dev
    (there is also -M to force mounting, I didn’t need to)
    I got a message about the FS not being repairable and being made available with limited functionality and am now recovering the 3 days since the last backup.

    Regards to everybody who contributed.

  31. I also just wanted to say thanks — this saved a friend of mine’s Macbook whcih wouldn’t boot without a kernel panic. Really appreciated!

  32. Thanks for your program, it saved a RAID disk. We were about to give up and format and restore so we thought what the heck.

    I ran into the problem described for mmap above, so I replaced the mmap with read, then later lseek and write. Worked fine.

    I hope this Catch22 situation (cannot mount, therefore cannot disable journal) is fixed in recent OS/X releases.

  33. I was just about to buy DiskWarrior when I came across this page. My Seagate 750GB external disk just refused to mount, and DiskUtility would find nothing wrong with it. I thought that was it: I was hit by the Seagate Plague! Then I saw that “journal magic is bad” message in the log.

    I tried hfs.util -N and recovered my disk instantly, with all its contents intact. Too bad this nifty little program is burried away where no one would ever think of looking for it.

    Big thanks to dmunsie for putting us all on the right path!

  34. Hello. I just wanted to thank you for the info and the program. I needed to write some info on a hfsplus partition, but couldn’t do so since I’m using a PC with Ubuntu GNU/Linux and it doesn’t enable write permissions when journaling is active. I took the source and did some minor modifications as to make it compile and work for me, but since I don’t understand very well how the whole program works – and I know my “hack” is a very dirty one – I’d appreciate any help of anyone kind enough as to make it really reliable for everybody. I posted about that in http://loquerasparalinux.blogspot.com/2009/02/hfsplus-desactivando-journaling-sin.html


  35. Utterly fantastic!

    Saved my bacon!

    I downloaded the compiled version, used the dd based instructions, and it worked perfectly!

    As soon as it finished I clicked repair in DiskUtil and it actually did some repairing, and a few seconds later I could mount it as normal.

    Thank you very much for sharing this!

  36. HELP

    Im such a n00b. I just can’t work out how to run this.

    I downloaded the compiled gz file, and uncompressed it. I have no idea what to do now. It’s on my desktop. How do I actually run it and make it do what it’s meant to do?

    Sorry Im such a beginner when it comes to the terminal!


  37. OK, I think I worked it out…. got the exec file in my user folder… and ran this:

    scott$ sudo ./disable_journal /dev/disk4

    then put my password in, then got this:

    mmap: Invalid argument

    HELP!! LOL

  38. Hi Scott —

    Please take a look at the 2nd comment. With recent versions of OS X, you can no longer directly use this utility with the device, so you will need to use the dd command to extract a portion of the filesystem from the device, run the tool, and then use dd to replace that portion. Please be very careful with these commands, since they have the ability to cause a lot of damage if used incorrectly.


  39. Thank you so much! This post saved a 1 terabyte XServe RAID array.

  40. Hello!

    While I suspect that I have a dead HD on my G4 powerbook, I’m trying just to be sure…

    In target disk mode, this is the information I get about firewire:
    FireWire Bus:

    Maximum Speed: Up to 400 Mb/sec

    Target Disk Mode:

    Manufacturer: AAPL
    Model: 0x54444D
    GUID: 0x1124FFFECC17B0
    Maximum Speed: Up to 800 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Target Disk Mode Unit:
    Unit Software Version: 0x10483
    Unit Spec ID: 0x609E
    Firmware Revision: 0x0
    Product Revision Level: 0000
    Target Disk Mode SBP-LUN:

    The only thing I can see that looks like a disk ID is ” Unit Spec ID: 0x609E”

    Am I even close, or is this drive totally unresponsive?

    Luckily, I’ve got recent backups, but I need to figure if I need to purchase & install another drive.

    Thank you for answering my beginner’s question!


  41. Dennis! Thanks. This is a great tip. I hoped that maybe in case of bad blocks, your solution may help, so I went ahead and tried, but no luck. Put this on macosxhints.com if you want, may help tons of people. Thanks again.

  42. Hi, I really want to try this code to get my two maxtor one touch 300gb externals mounted again, but I am getting a “dd: /dev/disk2s3: resource busy” response when I try this. What do think I might be doing wrong? I am using Leopard on an intel macbook pro. I have developer tools installed.

  43. Another disk saved!

    Now how do I re-enable journalling – or perhaps it did that automatically?

    Samui:~ alex$ sudo diskutil enableJournal /Volumes/Scuba
    Journaling was already enabled for volume Scuba on disk4s1

    Samui:~ alex$ sudo diskutil disableJournal /Volumes/Scuba
    An error occured journaling the filesystem: The underlying task reported failure on exit (-9972)

    Seems something is messed up.

    It’s a backup drive, so not a huge deal, but I’d like to make sure journalling is enabled.


  44. Thanks a million! Had to do the dd workaround, but it worked! Have a G5 Xserve running Panther Server with an XServe RAID, and mirroring some of the arrays using SoftRAID. Between all those layers I thought I was out of luck when things got messed up in a thunderstorm a few days ago. SoftRAID could still see the volume (case sensitive HFS+ journaled) and thought it was fine, but any time I tried to mount it got the dreaded journal magic errors in the system log. Trying to disable journaling from within SoftRAID resulted in an error. Disk Utility could see the disk, but no volumes. Running a version of your code I compiled directly on the drive gave the mmap error, but the dd workaround went smoothly. Now showed up as case sensitive, but no longer journaled in SoftRAID. Mounting resulted in silent failure. Still no volume visible in Disk Utility. Ran fsck_hfs -f on the disk, said repaired, restarted softRAID, mounted, and my NFS shares are back! Haven’t decided yet if I’m going to try and turn journalling back on yet. Thanks again! Great Hack!

  45. do you have a pre-compiled UB version of disable_journal available to download. i don’t have 2gb+ freespace to install xcode. the link http://munsie.net/bin/macosx/disable_journal.gz no longer works.


  46. Thanks for the article and the code. It allowed me to mount a 4T Drobo that wouldn’t mount due or repair due to “Invalid content in journal”. Yes, I had backups of the most important data, but recovering is usually preferable than restoring, right?

    Thanks again.

  47. Thanks for the hints. Just to share my experience: I had an “invalid content in journal” on a 4T Drobo as well, which was resolved by a) hfs.util -N /dev/disk b) activating the drobo volume in DU (was then successfully mounted but w/o journaling, check DU’s info for this) and c) (Re)activating Journaling in DU (i assume pressing that green button is equal to hfs.util -J /dev/… but i’m not sure about that). You may want to check the volume after b) and c) with DU. No errors here. Other specs: OS X 10.6.2. I forgot to note the exact disk capacities for a before/after comparison. However, the data is accessible again. Hope this helps. Keep rocking and thanks again.

  48. I had a “journal magic is bad” problem today but could fix it by using the following commands:

    sudo mount_hfs -j DEVICENODE MOUNTDIR
    sudo diskutil disableJournal MOUNTDIR
    sudo diskutil enableJournal MOUNTDIR

    The first command mounts the volume without journaling.

  49. Virtual memory,to me, is something that I seemingly will never have enough of. It’s as if megabytes and gigabytes have become a permanent part of my every day existence. Ever since I bought a Micro SD Card for my NDS flash card, I’ve been on permanent watch for large memory at cheap prices. I feel like I’m going insane.(Submitted by Nintendo DS running R4i Qezv2)

  50. how i compile the code for ubuntu

  51. In terminal, typing “sudo ./disable_journal foo” results in command not found. I tried this link: http://munsie.net/bin/macosx/disable_journal.gz but it’s no longer working. Please help me.

  52. […] my disk on? After a couple of minutes I came across a post on the Ubuntu forum which linked to this blog. The author has a C code that turns journalling off. A fixed version of this code can be found […]

  53. Wow, you are amazing. I have running disk utility for a few days without success. Its fixed!. 1TB World Book Raid 1. Genius

  54. It appears u understand plenty related to this topic and this exhibits via
    this unique blog, termed “Hacks 0x626C6F67”.
    Thanks -Dino

  55. Hey I compiled on gcc on a lion and when I run it states open: Bad address. Do you know what could be the reasons?

  56. If you are going for finest contents like myself, just visit this web site daily since it gives feature contents, thanks|

  57. Hello there, I found your site by the use of Google even as looking for a comparable topic, your
    site came up, it seems great. I have bookmarked it in my google bookmarks.

    I am no longer sure the place you’re getting your info, however good topic. I must spend a while learning more or working out more. Thank you for fantastic info I used to be looking for this information for my mission.

  58. Yes! Finally something about mike tyson.

  59. Hi! This is kind of off topic but I need some help
    from an established blog. Is it very hard to set up your own blog?
    I’m not very techincal but I can figure things out pretty fast.
    I’m thinking about setting up my own but I’m not sure where to start.
    Do you have any tips or suggestions? Thanks

  60. Hello, I have similar problem. My 9 gig Lacie (raid) says in disk utility “invalid content in journal”. I’m running latest maverick and very new with coding and stuff. Could someone PLEASE help me to get this code in right place etc. I would really appreciate this since all the stuff in external HD are really valuable. Hundreds of work hours. I thought that the raid system will cover me from disasters, but…this…

    I cannot mount the HD anymore aven though my disk utility sees it.

  61. I’m really impressed with your writing skills and also with
    the layout on your weblog.Is this a paid theme or did you
    customize it yourself? Either wayy keep up the excellent quality
    writing, it’s rare to see a nice blog like this one today.

  62. Very good information. Lucky me I found your blog by accident (stumbleupon).
    I have saved as a favorite for later!

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Monthly Archives

%d bloggers like this: