Previous 1 5 6 7 8 9 Next 1,445 Replies Latest reply: Nov 30, 2014 2:39 AM by piddyman Go to original post Branched to a new discussion.
  • PlotinusVeritas Level 6 Level 6 (14,710 points)

    That's interesting – and there is no WD external drive involved in your case?

     

    I indicated to you from the beginning that while WD build-quality on consumer HD is low,......a "hard drive is a hard drive"


     

    All HD,...... WD, Seagate, Toshiba, Hitachi, are all just mechanical bricks. There are only 4 conventional HD mfg. on earth.

     

    The issue here is 1. RAID, .....2. control software (if this is any case at all),.... and a 'minor' issue with 3. Firewire and Thunderbolt (firmware / SATA bridge?) as manifesting in 'sleep issues',...........

     

    ....all 3 of which aspects manifested after 10.9 OS update.

     

     

    Peace

  • slidersson Level 1 Level 1 (70 points)

    Plot, have you lost any data?

  • gifthorse Level 1 Level 1 (0 points)

    I have just another example of the update to OS X 10.9 causing hard drives to be displayed as empty.

     

    Update completed on the MacBook Pro without problem but after restarting 4 hard drives where first renamed as 'EFI' and then renamed as 'mybook'.

     

    1 drive was a WD MyBook connected via firewire. 2 where Samsung s2 portables, and 1 was a Seagate. These were connected via USB.

     

    I've copied all system logs from the period it happened which was over a few minutes.

  • coops17 Level 1 Level 1 (0 points)

    Guy i just figured out how to fix my problem!!!

    My problem was that my WD myPassport did not mount. After spending 20 + hours using Data Rescue it got my data but all the names were gone and stuff.

    So my drive would show up in disk utility but would not mount. Here is what you do: Right click the HD and click unlock drive. Then enter your password. My Drive appears in finder with all files in tact!! Hope this helps some people

  • ofquiet Level 1 Level 1 (0 points)

    Hi, I just tried what you suggested, but "Unlock Drive" does not appear as an option either in Disk Utility or the Finder when you right click on the drive. Can you be a bit more specific where you found that option? Thanks.

  • coops17 Level 1 Level 1 (0 points)

    Screen Shot 2013-10-28 at 6.34.25 PM.png

     

    Mine didn't show up in finder but it showed up is disk utility as Not mounted. Right click then unlock drive and enter password. Only works if your drive is password protected and is not mounting.

  • PlotinusVeritas Level 6 Level 6 (14,710 points)

    coops17

     

     

    Pardon, but password protected HD unlocking is not the issue at all this thread.

     

     

    Peace.

  • coops17 Level 1 Level 1 (0 points)

    I was brought to this forum because my hardrive didn't show up and shows empty because of my upgrade to mavericks. I just posted to try and help people that were maybe in the same boat as me. As for the myBook portion of the thread mine has worked perfectly since the update. I never used RAID or any WD managing software. Hope this helps.

  • ds3372 Level 1 Level 1 (0 points)

    My Passport for Mac 1TB shows up but Time Machine gets stuck "preparing backup" and I can only eject by "force eject" after Mavericks upgrade.

  • The Great Pumpkin Head Level 1 Level 1 (0 points)

    yes USB connected drives are also borked by this Apple/WD debacle

  • PlotinusVeritas Level 6 Level 6 (14,710 points)

       My Passport for Mac 1TB shows up but Time Machine gets stuck "preparing backup"

     

     

    Actually thats perfectly normal, most everyone has undergone the same thing.

     

    After new OS install, time machine has to sort thru endless 1000s of files before it starts to backup.

     

    A quick way around this is if you have another HD, you can make a NEW Time Machine backup,...will only take then a hour or so instead of endless hours (sometimes 20+ hours)

  • ofquiet Level 1 Level 1 (0 points)

    No I haven't used any WD software in many years. They were just sitting in my App folder.

  • AntonFagerberg Level 1 Level 1 (0 points)

    I might add here as well. I have similar issues. I use two WD MyBook external drives which I created a raid 0 in Mountain Lion's disk utility. After Mavericks install I'm unable to mount the raid partition even though it is recognized in disk utility and the raid is "online". I have never used any third party tools or drivers.

     

    This is the log:

    jnl: disk4: open: journal magic is bad (0x0 != 0x4a4e4c78)

    hfs: late jnl init: failed to open/create the journal (retval 0).

    hfs(3): Journal replay fail.  Writing lastMountVersion as FSK!

    hfs_mounthfsplus: hfs_late_journal_init returned (0)

    hfs_mounthfsplus: encountered errorr (22)

    hfs_mountfs: encountered failure 22

    hfs_mount: hfs_mountfs returned 22

    jnl: disk4: is_clean: journal magic is bad (0x0 != 0x4a4e4c78)

    hfs: late journal init: volume on disk4 is read-only and journal is dirty.  Can not mount volume.

    hfs_mounthfsplus: hfs_late_journal_init returned (22)

    hfs_mounthfsplus: encountered errorr (22)

    hfs_mountfs: encountered failure 22

    hfs_mount: hfs_mountfs returned 22

    jnl: disk4: open: journal magic is bad (0x0 != 0x4a4e4c78)

    hfs: late jnl init: failed to open/create the journal (retval 0).

    hfs(3): Journal replay fail.  Writing lastMountVersion as FSK!

    hfs_mounthfsplus: hfs_late_journal_init returned (0)

    hfs_mounthfsplus: encountered errorr (22)

    hfs_mountfs: encountered failure 22

    hfs_mount: hfs_mountfs returned 22

     

    I tried downgrading to Mountain Lion but the same issue persists so the disks are already corrupted even though they have never been mounted.

     

    I don't know what to do. Wait for a fix from Apple, try to repair with "first aid" or some third party tool but if the file names gets screwed up most of the data is wasted anyway...

  • putnik Level 3 Level 3 (775 points)

    Here is a way to force the GPT disk index to refresh itself.  It was used to correct disk problems in the past, so could work here too. 

     

    https://discussions.apple.com/message/23515858#23515858

  • PlotinusVeritas Level 6 Level 6 (14,710 points)

    I see your error code-----  Writing lastMountVersion as FSK

     

     

    I've seen that before and it's discussed here a bit

     

    http://www.sooperarticles.com/technology-articles/data-recovery-articles/how-res olve-mac-journal-magic-bad-error-340304.html

     

     

    MAC operating system has a feature of journaling the file system due to which the chances of fault flexibility together with providing protection to the file system preventing from the hardware failure incidents and sudden power turn off. The journal plays vital role comprising all the confidential information that are required by the MAC operating system so that it could be returned to the previous working station.

     

    These journals being vital component of the MAC operating system if gets corrupted, leads into serial results. It may turn the whole data inaccessible by means of turning the volume unmountable. Once user undergoes such disaster the only thing that leads to recover the situation is the valid backup as the data can be restored and the corrupted can be removed from the hard disk without being worried about the data loss issue.

     

    While the corruption is encountered in the HFS volume of the MAC operating system then error that is encountered with the user is stated below:-

     

    HFS(3): Journal replay fail. Writing lastMountVersion as FSK!

     

    jnl: is_clean: journal magic is bad (0x1fd17 != 0x4a4e4c78)

     

    HFS: late jnl init: failed to open/create the journal (retval 0).

     

    jnl: open: journal magic is bad (0x1fd17 != 0x4a4e4c78)

     

     

     

     

    While the corrupted HFS + volume is attempted to be mounted, the above shown error triggers on the screen. The corruption of journal being the major cause turns often turns to smash up the entire MAC volume to an extent along with damaging the command line. Although you may find the disk utility option as well as the command line application facilitated in the MAC operating system which you may use in order to get the issue resolved. If possible try disabling journal and further turning it on.

Previous 1 5 6 7 8 9 Next