Previous 1 86 87 88 89 90 Next 1,445 Replies Latest reply: Nov 30, 2014 2:39 AM by piddyman Go to original post Branched to a new discussion.
  • lkrupp Level 4 Level 4 (3,490 points)

    davidhq wrote:

     

     

    Some people in the thread are still not sure that Maverics won't loose their data in the future - why?

     

     

    They have no clue. It turns out almost all the issues were caused by third party software of one kind or the other. Some swore on the Bible that they had not installed such software only to find out they did indeed have it installed after running EtreCheck. This thread itself is pretty small. The number of Mavericks users affected is small. The major tech websites aren't reporting on this at all. I haven't read a single article by a known, respected Mac expert discussing this as a bug or anything else. You yourself found out it wasn't Mavericks. The simplest explanation often turns out to be the correct one. There is no problem save for individual, anecdotal, unknown causes. Occam's Razor in the flesh.

  • davidhq Level 1 Level 1 (0 points)

    OK, great...

     

    Myunderstanding is that WD tools definitelly caused some issues but sometimes it was more apps and/or interaction of those apps with WD/Mavericks problem... Mavericks itself is probably not a problem.

     

    But I will for sure get a NAS now to make my backup strategy more robust.

     

    Is this appropriate place to ask for small advice on which NAS system to get. I want mirroring and Time Machine capabilities... maybe iTunes library hosting as well... can I do all that with:

     

    http://www.wd.com/en/products/products.aspx?id=620

     

    I read something about: Drobos, Synology or QNAP - are those even more "Mac ready"?

     

    Please point me in the right direction... hopefully others will also like the idea of getting their own NAS in additon to external drives.

  • Drew Reece Level 5 Level 5 (5,225 points)

    lkrupp wrote:

     

    davidhq wrote:

     

     

    Some people in the thread are still not sure that Maverics won't loose their data in the future - why?

     

     

    They have no clue. It turns out almost all the issues were caused by third party software of one kind or the other. Some swore on the Bible that they had not installed such software only to find out they did indeed have it installed after running EtreCheck. This thread itself is pretty small. The number of Mavericks users affected is small. The major tech websites aren't reporting on this at all. I haven't read a single article by a known, respected Mac expert discussing this as a bug or anything else. You yourself found out it wasn't Mavericks. The simplest explanation often turns out to be the correct one. There is no problem save for individual, anecdotal, unknown causes. Occam's Razor in the flesh.

    Hasn't GetRealBro been documenting a slow fsck issue that affects Macs without WD software? Slow mounting disks that appear damaged on 10.9

     

    That issue demands having sound backups of any external disks that are to be used with 10.9. It also means you want to have an older OS around to backup these disks.

     

    @davidhq,

    I managed to find the pages with the find command (there is probably other background info on those pages too)…

    https://discussions.apple.com/thread/5475136?start=855&tstart=0

    https://discussions.apple.com/thread/5475136?start=1050&tstart=0

    https://discussions.apple.com/thread/5475136?start=1065&tstart=0

    https://discussions.apple.com/thread/5475136?start=1110&tstart=0

     

    The the user tip has some info too…

    https://discussions.apple.com/docs/DOC-6202

     

    The LaunchDeamon & privileged helper tool you found are the most disconcerting items, they run at the system level & frankly I don't trust WD enough to have them around to break again in the future.

     

    As for NAS's. Time Capsules are the only ones that Apple officially support, everything else is reverse engineering as far as I can tell. There are a lot of threads with TimeMachine issues that get blamed on 3rd party NAS's it's never really clear if that is the problem or if Apple changed something.

  • davidhq Level 1 Level 1 (0 points)

    I used this command:

     

    sudo find -x  /  -iname com.wdc.\* -or -iname com.westerndigital.\*

    -or -iname com.wd\*

     

    and found this:

     

    /Users/david/Library/Caches/com.wdc.smartware

    /Users/david/Library/Preferences/com.westerndigital.WD-Drive-Utilities.plist

    /Users/david/Library/Saved Application State/com.wdc.smartware.savedState

     

    strange because at least first two should have been found with my command as well... maybe I didn't notice it because there were many results.

     

    I now removed these as well.

     

    Thank you for pointing out fsck issue... Don't understand that but I'll be extra careful... Do you think they will fix this on next update?

     

    Regarding Time Capsule:

    So if others have problems that could be the best option then... I also read that it's possible to backup to external drive with TC. That's alsmost the same as RAID 1... The only thing is that I'm not sure if I can access my data from outside of my network with TC. That would be nice...

  • Farlin Laedavin Level 1 Level 1 (0 points)

    I just confirmed running EtreCheck (great utility, by the way, thanks!) has netted no WD or Seagate software installed. Also did the sudo find / search via terminal with grep and no results for either Seagate or WD. So, I tried again by plugging in the 3TB drive, attempted to format via disk utility, got about 30 seconds into it, then the drive disappeared and disk utility errored out. Attempted to reconnect the drive and it will not connect anymore unless I reboot and repeat. Mind you, I have done this several times in various configurations attempting to troubleshoot the problem. I again connected the same drive to a Windows 7 box, formatted, copied a bunch of files, no issues after a few hours of use.

     

    Interestingly enough, I connected an older 120GB external WD USB 2 drive to the iMac and it immediately worked with no issues whatsoever. I even copied 120GB of data onto the drive and copied it off for testing without problems. I also tried an 8GB USB stick and no problems there either.

     

    So, I am curious if this is only affecting larger sized drives via a USB interface? A friend of mine with 10.9.2 using a Seagate 3TB drive running on thunderbolt has not had any problems.

  • Drew Reece Level 5 Level 5 (5,225 points)

    The first command you ran…

    sudo find / | grep WD

    was case sensitive, so items 1 & 3 would have been missed. grep has the -i flag for insensitive search

     

    find '-iname' is case insensitive too.

     

    That doesn't explain why the prefs got missed.

  • Drew Reece Level 5 Level 5 (5,225 points)

    @Farlin Laedavin,

    Search out GetRealBro's posts,it sounds similar to the issue he describes.

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

  • Farlin Laedavin Level 1 Level 1 (0 points)

    @Drew Reece,

     

    Thanks, Drew. Those are interesting posts and got me thinking. I did some looking and fsck is not running in the process list. Checked the disk utility log and there are no errors reported there to indicate an fsck was fired off. So, going back to my UNIX days, I decided to check dmesg and found the below shortly after the drive is connected. It still refuses to show up in disk utility, but disk utility does not report any errors either (have not rebooted since I first connected it). Normally I would say it is a hardware issue, but if I connect the drive to a Windows 7 box, no problems. Doing some searches has netted that it seems OS X is having problems identifying that it is a USB hard drive. I am wondering if this is a drive/controller firmware problem?

     

    Error Before Reboot (shortly after attaching the drive)

     

    SBF:    The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x15000000)

    USBF:    The IOUSBFamily was not able to enumerate a device.

     

    Error After Reboot (drive not attached at boot)

     

    USBMSC Identifier (non-unique): 0x00000000 0xbc2 0xa0a4 0x100, 3

    IOUSBAttachedSCSI: device not responding, terminating

    USBMSC Identifier (non-unique): 0x00000000 0xbc2 0xa0a4 0x100, 3

    IOUSBAttachedSCSI: device not responding, terminating

    USBF:    The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 2 of Hub at 0x15000000)

     

     

    No errors or status are reported after a reboot with the drive attached. So it doesn’t even see it on boot or attempt to mount it. Reason being, when I attached the 120GB, I get the below message:

     

    USBMSC Identifier (non-unique): DEF10C664F93 0x1058 0x701 0x240, 2

    hfs: mounted 120GB on device disk2s2

  • GetRealBro Level 1 Level 1 (5 points)

    Check the fsck_hfs.log

     

    Anything longer than....

     

    /dev/rdisk2s2: fsck_hfs started at Mon Mar 24 18:55:56 2014

    /dev/rdisk2s2: /dev/rdisk2s2: ** /dev/rdisk2s2 (NO WRITE)

    /dev/rdisk2s2:    Executing fsck_hfs (version hfs-226.1.1).

    QUICKCHECK ONLY; FILESYSTEM CLEAN

    /dev/rdisk2s2: fsck_hfs completed at Mon Mar 24 18:55:56 2014

     

    is a pretty good indication of the "long fsck" issue that can cause disk mounts to be delayed for several minutes. The bigger the drive and/or the more complicated the file structure, the longer the delay. My 3T Seagate regularly took 8 minutes to mount. During that delay you can/should completely ignore any BS that Disk Utility tells you.

     

    --GetRealBro

  • LejeunePat Level 1 Level 1 (0 points)

    Hold your horses before installing Maverick: I'm having problems with a WD external 2.0TB HD I use for my Time Machine backups with 10.9.2, and you thought with 10.9.1 the problem would be solved : its not.

     

    How did my problem occur?
    . I mistakenly did not eject it properly (I thought it was & turned off the Ext HD support). This seems to be the trigger point.
    . Ever since, its not recognized, when other brand's, smaller / older external USB HDs I have tested still function (I onitially thought the USB slot may have been the problem).

    . So now, when I try plugging-in the ext 2To DW ext drive, I hear it "turning" on its base, but it never appears on my iMAC's descktop, nor can I launch Time Machine.


    I'm a bit worried, because, since Mavericks, the Finder windows have also been acting very strange : slow, and sometimes even disapearing. It seems my iMAC is dying on me ... and I cannot make a backup.

     

    Any tips on how to make my external, UDB-linked, WD HD appear again on my iMAC?
    (please note I am absolutely not a technical guy and dont understand 90% post posts here)

  • LejeunePat Level 1 Level 1 (0 points)

    I'm also having problems with a WD 2.0To external drive used via USB & tested perfectly older 120Go and 250Go external USB HD ... but unfortunately, they have become too small for the Backup I have to do (internal 1.5To drive upgrade in a 2008 4Go. iMAC not 2/3rds full to backup).

     

    I guess patience may be the best solution, Apple including a solution in the next OSX Mavericks update (I'm currently on 10.9.2) ... hoping nothing goes wrong till then.

  • inajeep Level 1 Level 1 (0 points)

    I have a 2 TB WD My Passport for my TM and went through the exact same situation.  I unplugged before I could dismount due to the slower than expected dismount and thought I screwed up that partition.   I didn't have WD software installed but it took a long time to mount and unmount. 

     

    I ran disk utiltiy three times  and Onyx and let the drive sit there for a long time on its own and it came back after a long while.    My TM is full now so it takes a while to clear the older files. I let it run and when I eject, I make sure the icon dissappears before I unplugging. 

  • Drew Reece Level 5 Level 5 (5,225 points)

    LejeunePat wrote:

     

    I guess patience may be the best solution, Apple including a solution in the next OSX Mavericks update (I'm currently on 10.9.2) ... hoping nothing goes wrong till then.

    Don't wait for a fix for a problem Apple hasn't acknowledged, it may not exist, or it may be additional software conflicts etc.

     

    The 'best solution' is to have another disk that you can use to backup the files that you need.

    You can also boot into another OS to perform backups to disks that don't work on 10.9.

     

    Hope is not a word that should be included in any backup plan.

  • davidhq Level 1 Level 1 (0 points)

    I'm trying to backup to TimeMachine external WD drive on Mavericks and it says it will need 8 hours for 50GB. And it means it... going very slow. Should I just wait this time or is this also a bad sign for the future with this drive? This drive wasn't connected when I still had WD software, so it's strange... maybe it's because the last backup was from Mountain Lion and it's "confused". Or is it better to just reformat the drive and do a clean backup from Mavericks?

  • davidhq Level 1 Level 1 (0 points)

    I interrupted it, it got stuck on 7.52 GB for 5+ minutes... strange. I'd like to know what is going on.

Previous 1 86 87 88 89 90 Next