I have a WD My Passport 650GB (with Firewire and USB). I'm using it for almost a year now and it always worked fine. While underway I simply plug it in via Firewire - at home I connect it to my Airport Extreme to have it available as a network storage. Today I connected the HDD to my MacBook Pro (via firewire) and NOTHING. The HDD is starting (clearly making a sound and the power-indicator is flashing) but it won't appear in Finder. I also tried it with USB - no sign.

I ran Disk Utility and tried to repair the disk. At first try I got a red error line saying that something is wrong with the 'headers'. However the repair completed with a success message saying that everything is OK.

Oct 10, 2014 - I own a one terabyte passport for mac external hard drive, and I installed. And plugged back in my external hard drive many times, but it still wont. This is what shows up when I go to play Assassins Creed II which is on my. Unless the game writes it's own data files on the root which then may be shared.

I also verified the HDD. Also with a success message. I did that a few times again and unplugged it in between. Never got the error with the headers again - it's always completing and saying everything is OK. However I can't mount the drive. That is what Disk Utility is showing.

However I might need help with mounting my harddrive with terminal. I found this post where it is explained step by step. However once I get to the last step and run sudo mount -t hfs -o rdonly /dev/disk2s3 /Volumes/My Passport terminal always outputs the message usage: mount [-dfruvw] [-o options] [-t external_type] special node mount [-adfruvw] [-t external_type] mount [-dfruvw] special node So somehow I might call the wrong params or so when trying to mount the drive.

Best software for capturing video from screen free mac. Any ideas on that? – Jun 6 '12 at 8:11 •. The commands i use would be 'diskutil mount /dev/disk0s2' *please note you may has to list the volumes to find out if your hard drive is recognized as 'disk0s2' as it may change depending on what other volumes are mounted.

Through 'diskutil' you can repair the disc etc. Much like disk utilities which you have used but at root level. Also i would do a filesystems disk check, eg. 'fsck_hfs -f /dev/disk0s2' again you'll need to verify the name of the volume, you may use this command 'df -hl' – Jun 6 '12 at 8:32 •. Disk Utility says the format is Mac OS Extended (Journaled). I do actually have it plugged into my TimeCapsule and I use it normally as Network Drive.

However I got a new usb hub and unplugged the device from the TimeCapsule and connected the drive to the new hub instead of directly to the one and only usb slot on the time capsule. I tried it and everything seemed to work. However on the same evening I wanted to browse the external drive through my network and I couldn't access it - so I unplugged it and now I'm trying to fix it. Right now it's plugged into my mac directly. – Jun 6 '12 at 8:57. I just debugged a practically identical issue.

After hours of trying various stuff, I finally found an answer, after closely examining system.log in Console. I found this: 3.1.13. 21.42.42,090 sudo[622].: TTY=ttys001; PWD=/Users/.; USER=root; COMMAND=/usr/sbin/diskutil mount readOnly /dev/disk2s2 3.1.13.

21.42.42,000 kernel[0]: jnl: disk2s2: is_clean: journal magic is bad (0xdead00ab!= 0x4a4e4c78) 3.1.13. 21.42.42,000 kernel[0]: hfs: late journal init: volume on disk2s2 is read-only and journal is dirty. Can not mount volume.

21.42.42,000 kernel[0]: hfs_mounthfsplus: hfs_late_journal_init returned (22) 3.1.13. 21.42.42,000 kernel[0]: hfs_mounthfsplus: encountered errorr (22) 3.1.13. 21.42.42,000 kernel[0]: hfs_mountfs: encountered failure 22 3.1.13. 21.42.42,000 kernel[0]: hfs_mount: hfs_mountfs returned 22 The issue seemed to be with bad journal. So I disabled journaling and the mount then worked just fine. Afterwards I enabled journaling again, all fine.

I'm surprised that Disk Utility was not able to detect this during Verify Disk (which reported that all is fine). Terminal option to disable journaling is: sudo diskutil disableJournal force /dev/diskXsX with diskXsX replaced to whatever is appropriate for your case. This command above will report error at exit, but just ignore it.