Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Every night my WD Harddrive starts to freeze..

Elliot7777

Elliot7777

macrumors newbie
Original poster
Mar 26, 2016
5
1
Around 3am every night, sometimes earlier, sometimes a little later, if i am on, my external WD 1230 My Book external drive starts to act weird. Took my awhile to figure out it was that drive. And so any night I am on that late, at some point it starts to do this thing, and then finder will freeze, suddenly everything starts going like mollases, and even other downloads to other drives slow down. It will last hours, unless I unplug my WD Drive and suddenly everything is fine again. I have tried running diagnostics on it, everything is fine.
Someone mentioned to me they thought it might be the spotlight process, finding indexes or whatever for mac, having some weird conflict with the WD drive. So when i turned off that process it seemed to go away, but then i cannot do searches in finder anymore, not really any solution.

Anyone seen anything like this before. I have a imac 27-inch late 2013, running OS X El Capitan version 10.11.6 3.2 GHz intel Core i5
Memory 8GB


Yea, at this point I almost feel like nothing has worked, and I don't really think the shop will be able to debug it, and I cannot really do without my computer for a week while they finally try to test it at night.. If ever, since I never have seen the behavior at any other time but really late. Usually when i am trying to get something done for work either really late, or waking up at 4am, only to find my mac freeze, and having to roll the dice and pull the plug on my harddrive which is really scary. Otherwise though I cannot even reboot my computer, because 1 it takes like 20 mins because everything is so slow at that point, and 2 because if I reboot the computer it just comes back. If I reboot the harddrive it goes away.

Anyway, any help, I would definitely super appreciate it at this point...

Clint

One last note - I even bought Kaspersky software to make sure it was not a virus etc, but it finds nothing as well...
 
what is on that drive? backups?

rather than turning spotlight off completely, you can set it to ignore just that drive.
if you want to be able to search that drive I recommend a little app called EasyFind. in a lot of ways, it's better and faster than Spotlight.
 
Have you tried to log out and log back in ? in apple icon on top left , try to log out and log in as "guest" and then log out of "guest" and back to "admin" or whatever you use ..... I have this problem too and I can't even eject my external ... sometimes this way works
 
That sounds like the daily (actually, nightly) maintenance script running. You can check for sure by opening Console. In Terminal you can check when it was last run by looking at its log file date: type "ls -la /var/log/*.out". Type "cat /var/log/daily.out" to see that log.
 
HamidZ said:
Have you tried to log out and log back in ? in apple icon on top left , try to log out and log in as "guest" and then log out of "guest" and back to "admin" or whatever you use ..... I have this problem too and I can't even eject my external ... sometimes this way works
Click to expand...
[doublepost=1470493321][/doublepost]No, but i will next time. If i try to restart it will take forever to close the programs,like 10-15 mins.

I am curious how to stop using spotlight on that drive. Where can i find instructions on how to do that correctly, safely?
[doublepost=1470493433][/doublepost]
MC6800 said:
That sounds like the daily (actually, nightly) maintenance script running. You can check for sure by opening Console. In Terminal you can check when it was last run by looking at its log file date: type "ls -la /var/log/*.out". Type "cat /var/log/daily.out" to see that log.
Click to expand...

Cool i will try that next time to find out...
[doublepost=1470493984][/doublepost]
thats all folks said:
what is on that drive? backups?

rather than turning spotlight off completely, you can set it to ignore just that drive.
if you want to be able to search that drive I recommend a little app called EasyFind. in a lot of ways, it's better and faster than Spotlight.
Click to expand...

I use it mostly as my working drive now, do not store anything on it i want backed up properly. I have two nas working as well, oke with 2x2 tb and another qnas with 4 bays, but only using 2x4tb.

Is there a safe or proper way to remove a drive from that spotlight search? I like the idea of easyfind as i find spotlight rather unpleasant anyway, seems pretty bad compared to other os systems for finding files. I will try removing that drive from spotlight, and use easyfind. Is there anything else that uses spotlight for system levels stuff, or is it just used for searching. I was worried spotlight might be tied into how the disk is maintained or something. Hopefully not...
 
Had this issue recently although it wasn't at a certain time, it was "often". Took some time but I found out my rsync was somehow corrupt (CCC, Time Machine). So I deleted all the prefs and reset backups to something more manageable and I never saw the issue again.
 
Elliot7777 said:
I use it mostly as my working drive now, do not store anything on it i want backed up properly. I have two nas working as well, oke with 2x2 tb and another qnas with 4 bays, but only using 2x4tb.

Is there a safe or proper way to remove a drive from that spotlight search? I like the idea of easyfind as i find spotlight rather unpleasant anyway, seems pretty bad compared to other os systems for finding files. I will try removing that drive from spotlight, and use easyfind. Is there anything else that uses spotlight for system levels stuff, or is it just used for searching. I was worried spotlight might be tied into how the disk is maintained or something. Hopefully not...
Click to expand...
you can tell spotlight to not index an individual drive or folder, etc. through System Preferences. In the Spotlight control panel, select the "privacy" tab and just add that drive there. there should be no consequences from that otherwise. but I don't think spotlight is your issue. still, try this and see what happens. if that does make the problem go away, you could try removing it from privacy then, as that action deletes the entire index for the drive. putting it back under spotlight forces an index rebuild, which could take a while.
https://support.apple.com/en-us/HT201716

The consistency of the timing of the issue is what is confusing to everyone. without that, I would give the odds to a bad hard drive. maybe the timing is simply related to that representing you being on the computer long enough for the drive to heat up and stop working. as MC6800 mentioned, the system does run it's own maintenance that would normally o off late at night, but that shouldn't lock down your computer because of an external drive. that should only be concerned with the system drive.

I am a fan of WD for bare drives and cheap portables but have been much less impressed with their consumer desktop models. I've tossed a lot of bad power supplies and cooked a lot of controller boards (though several years ago now). do you have another power supply you can try to run it on? those drives also have a tendency to put themselves to sleep faster than I appreciate. Do you have the WD software installed? Its no where near necessary, but if you already do, maybe something in there is set, sleep parameters?

but again, my top contender for the issue is a physically dying hard drive that starts locking up once it gets hot (from use), unless turning off spotlight fixes it, than that was at the top.
 
Sry for such a late reply. I was just not up late working for awhile, so the issue did not come up for me. It did tonight at just after 2:30 Some of the logs I had around that time were the following, If any of them look interesting would love to hear and answer. By the way the logging in and out again was not even possible this time, as I could not even open the menu to logout, finder was completely, and my mouse wheel was in that constant working state with the rainbow colored wheel displayed. It started when I was watching a movie....

here is part of the logs that seemed interesting around just before 2:30... (#### == I just replaced something for privacy...)



____

Hopefully this is the most interesting from the system.log around the time it started freezing... NOTE: Can tell in the below log that i actually turned off one of my external drives to get control back, it seemed to work once, then not again....


cat /var/log/system.ini ....
Code: 
Aug 26 01:59:56 ####-iMac WindowServer[190]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x1b56b412 device: 0x7f9a8bc17420  isBackBuffered: 1 numComp: 3 numDisp: 3

Aug 26 02:00:17 ####-iMac AAM Updates Notifier[1142]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.6 instead of 10.11.6. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

        Call location:

Aug 26 02:00:17 ####-iMac AAM Updates Notifier[1142]: 0   CarbonCore                          0x9336fe3d ___Gestalt_SystemVersion_block_invoke + 135

Aug 26 02:00:17 ####-iMac AAM Updates Notifier[1142]: 1   libdispatch.dylib                   0x988f471b dispatch_once_f + 78

Aug 26 02:00:17 ####-iMac AAM Updates Notifier[1142]: 2   libdispatch.dylib                   0x988f5fa5 dispatch_once + 31

Aug 26 02:00:17 #####-iMac AAM Updates Notifier[1142]: 3   CarbonCore                          0x932eb8e1 _Gestalt_SystemVersion + 1047

Aug 26 02:00:17 #####-iMac AAM Updates Notifier[1142]: 4   CarbonCore                          0x932eb08a Gestalt + 154

Aug 26 02:00:17 ####-iMac AAM Updates Notifier[1142]: 5   UpdaterCore                         0x06a11b40 _ZN3esd11SystemUtils20GetOSPlatformVersionEv + 48

Aug 26 02:00:17 #####-iMac AAM Updates Notifier[1142]: 6   UpdaterCore                         0x069628e3 _ZN25ThreadGetAvailableUpdates16ThreadWebFeedURL12GetOSVersionEb + 193

Aug 26 02:03:25 #####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:03:25 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:04:13 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:04:13 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:04:17 ####-iMac Mail[287]: tcp_connection_destination_perform_socket_connect 66 connectx to ####:####:777e:c00::7c.992@0 failed: [65] No route to host

Aug 26 02:05:35 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:05:35 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:05:37 ###-iMac kernel[0]: ALF: ifnet_get_address_list_family error 12

Aug 26 02:05:44 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:05:44 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:06:32 ####-iMac kernel[0]: Google Chrome He[1158] triggered unnest of range 0x7fff95c00000->0x7fff95e00000 of DYLD shared region in VM map 0x72ad03deb7eaa113. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Aug 26 02:06:53 ####-iMac syslogd[45]: ASL Sender Statistics

Aug 26 02:07:32 #####-iMac CalendarAgent[305]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

Aug 26 02:08:02 --- last message repeated 1 time ---

Aug 26 02:09:17 #####-iMac Mail[287]: tcp_connection_destination_perform_socket_connect 67 connectx to 2607:####:####:###::##.###@0 failed: [65] No route to host

Aug 26 02:11:11 ####-iMac WindowServer[190]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x1b56b412 device: 0x7f9a8bc17420  isBackBuffered: 1 numComp: 3 numDisp: 3

Aug 26 02:11:41 --- last message repeated 1 time ---

Aug 26 02:11:41 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:11:41 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 2 Memory pressure state: 0

Aug 26 02:12:30 #####-iMac kernel[0]: poll: added pid 1169 to excludes

Aug 26 02:12:30 ####-iMac kernel[0]: poll: added pid 1170 to excludes

Aug 26 02:12:37 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:12:37 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 1 Memory pressure state: 0

Aug 26 02:12:40 #####-iMac kernel[0]: Google Chrome He[1171] triggered unnest of range 0x7fff95c00000->0x7fff95e00000 of DYLD shared region in VM map 0x72ad03debadce7db. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Aug 26 02:12:45 ####-iMac kernel[0]: Sandbox: kav(89) System Policy: deny(1) forbidden-kas-info

Aug 26 02:12:54 #####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:12:55 ####-iMac WindowServer[190]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x1b56b412 device: 0x7f9a8bc17420  isBackBuffered: 1 numComp: 3 numDisp: 3

Aug 26 02:13:06 #####-iMac WindowServer[190]: disable_update_timeout: UI updates were forcibly disabled by application "VLC" for over 1.00 seconds. Server has re-enabled them.

Aug 26 02:13:20 ####-iMac WindowServer[190]: disable_update_likely_unbalanced: UI updates still disabled by application "VLC" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

Aug 26 02:13:25 ###-iMac kernel[0]: USB device 1058123014A00000 - will be reset!

Aug 26 02:13:25 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E30313531343938 0x1058 0x1230 0x1050, 3

Aug 26 02:13:25 ####-iMac cfprefsd[139]: BUG in libdispatch: 15G31 - 1718 - 0x0

Aug 26 02:13:25 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.

Aug 26 02:13:55 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:13:59 ####-iMac loginwindow[101]: -[SFLListManager(ServiceReplyProtocol) notifyChanges:toListWithIdentifier:] Notified of item changes to list with identifier com.apple.LSSharedFileList.RecentApplications

Aug 26 02:14:11 ####-iMac VLC[1176]: Can't find app with identifier com.spotify.client

Aug 26 02:14:17 #####-iMac Mail[287]: tcp_connection_destination_perform_socket_connect 68 connectx to 2607:f8b0:400e:c05::6c.993@0 failed: [65] No route to host

Aug 26 02:14:25 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:14:55 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:14:57 ####-iMac com.apple.xpc.launchd[1] (com.apple.quicklook.satellite.EAE572FC-23B8-4E9B-9E6A-9AED8022D5A6[1099]): Service exited due to signal: Killed: 9

Aug 26 02:15:13 ####-iMac com.apple.CDScheduler[271]: Thermal pressure state: 0 Memory pressure state: 0

Aug 26 02:15:13 ####-iMac com.apple.CDScheduler[46]: Thermal pressure state: 0 Memory pressure state: 0

Aug 26 02:15:24 #####-iMac spindump[549]: Saved hang report for VLC version 2.2.2 (2.2.2) to /Library/Logs/DiagnosticReports/VLC_2016-08-26-021524_Clintons-iMac.hang

Aug 26 02:15:25 #####-iMac WindowServer[190]: CGXGetConnectionProperty: Invalid connection 133359

Aug 26 02:15:26 --- last message repeated 2 times ---

Aug 26 02:15:26 #####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:15:38 ####-iMac spindump[549]: Saved hang report for VLC version 2.2.2 (2.2.2) to /Library/Logs/DiagnosticReports/VLC_2016-08-26-021538_Clintons-iMac.hang

Aug 26 02:15:53 #####-iMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x23d984c79d0bff53

Aug 26 02:15:54 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/Media

Aug 26 02:15:54 #####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  posting to KEA EINPROGRESS for /Volumes/Media

Aug 26 02:15:54 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Media

Aug 26 02:15:54 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:15:54 ####-iMac KernelEventAgent[103]: tid 54485244 received event(s) VQ_NOTRESP (1)

Aug 26 02:15:54 ####-iMac KernelEventAgent[103]: tid 54485244 type 'afpfs', mounted on '/Volumes/Media', from '//;AUTH=No%20User%20Authent@LS220D08E._afpovertcp._tcp.local/Media', not responding

Aug 26 02:15:54 ####-iMac KernelEventAgent[103]: tid 54485244 found 1 filesystem(s) with problem(s)

Aug 26 02:15:56 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:16:09 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 60.

Aug 26 02:16:09 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:16:09 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 64.

Aug 26 02:16:09 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  sleep for 1 seconds and then try again

Aug 26 02:16:10 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:16:10 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 64.

Aug 26 02:16:10 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  sleep for 2 seconds and then try again

Aug 26 02:16:12 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:16:12 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 64.

Aug 26 02:16:12 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  sleep for 4 seconds and then try again

Aug 26 02:16:16 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:16:16 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 64.

Aug 26 02:16:16 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  sleep for 8 seconds and then try again

Aug 26 02:16:24 ###-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/Media

Aug 26 02:16:24 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  connect on /Volumes/Media failed 61.

Aug 26 02:16:24 ####-iMac kernel[0]: ]

Aug 26 02:16:24 ####-iMac kernel[0]: AFP_VFS afpfs_DoReconnect:  posting to KEA to unmount /Volumes/Media

Aug 26 02:16:24 ####-iMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 72 error 89 reqID 20682 flags 0x29 afpCmd 0x11 so 0x23d984c79d0bff53

Aug 26 02:16:24 ####-iMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 73 error 89 reqID 20683 flags 0x29 afpCmd 0x22 so 0x23d984c79d0bff53

Aug 26 02:16:24 ###-iMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 74 error 89 reqID 20684 flags 0x29 afpCmd 0x22 so 0x23d984c79d0bff53

Aug 26 02:16:24 ###-iMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 75 error 89 reqID 20685 flags 0x29 afpCmd 0x22 so 0x23d984c79d0bff53

Aug 26 02:16:24 ####-iMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 1 on so 0x23d984c79d0bff53

Aug 26 02:16:24 ####-iMac KernelEventAgent[103]: tid 54485244 received event(s) VQ_DEAD (32)

Aug 26 02:16:24 ####-iMac KernelEventAgent[103]: tid 54485244 type 'afpfs', mounted on '/Volumes/Media', from '//;AUTH=No%20User%20Authent@LS220D08E._afpovertcp._tcp.local/Media', dead

Aug 26 02:16:24 ####-iMac KernelEventAgent[103]: tid 54485244 force unmount //;AUTH=No%20User%20Authent@LS220D08E._afpovertcp._tcp.local/Media from /Volumes/Media

Aug 26 02:16:24 ####-iMac kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Media, flags 524288, pid 103

Aug 26 02:16:24 ####-iMac KernelEventAgent[103]: tid 54485244 found 1 filesystem(s) with problem(s)

Aug 26 02:16:26 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:16:35 ####-iMac kernel[0]: poll: removed pid 1128 from excludes

Aug 26 02:16:55 ####-iMac WindowServer[190]: CoreAnimation: timed out fence 20ba7

Aug 26 02:16:55 ###-iMac syslogd[45]: ASL Sender Statistics

Aug 26 02:16:56 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:16:56 ####-iMac kernel[0]: disk1s1: I/O error.

Aug 26 02:16:56 ###-iMac kernel[0]: process Finder[336] caught causing excessive wakeups. Observed wakeups rate (per sec): 160; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 54833

Aug 26 02:16:57 ###-iMac com.apple.xpc.launchd[1] (com.apple.ReportCrash[1187]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash

Aug 26 02:16:57 ###-iMac ReportCrash[1187]: Invoking spindump for pid=336 wakeups_rate=160 duration=282 because of excessive wakeups

Aug 26 02:17:00 ####-iMac kernel[0]: Google Chrome He[1188] triggered unnest of range 0x7fff95c00000->0x7fff95e00000 of DYLD shared region in VM map 0x72ad03deb81964f3. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Aug 26 02:17:07 ###-iMac Google Chrome Helper[1188]: CGAffineTransformInvert: singular matrix.

Aug 26 02:17:26 ###-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.

Aug 26 02:17:26 ###-iMac kernel[0]: disk1s1: I/O error.

Aug 26 02:17:27 ###-iMac com.apple.xpc.launchd[1] (org.videolan.vlc.73312[1176]): Service exited due to signal: Killed: 9

Aug 26 02:17:27 ####-iMac spindump[549]: Timed out waiting for system stats microstackshots after 30 seconds

Aug 26 02:17:27 ###-iMac spindump[549]: No microstackshots found

Aug 26 02:30:13 ### bootlog[0]: BOOT_TIME 1472203813 0

Aug 26 02:30:42 localhost syslogd[45]: Configuration Notice:

        ASL Module "com.apple.AccountPolicyHelper" claims selected messages.

        Those messages may not appear in standard system log files or in the ASL database.

Aug 26 02:30:42 localhost syslogd[45]: Configuration Notice:

        ASL Module "com.apple.Accounts" claims selected messages.

        Those messages may not appear in standard system log files or
__________

also from install.log around that same time....

Code: 
Aug 26 02:16:19 ####-iMac installd[419]: PackageKit: Adding client PKInstallDaemonClient pid=472, uid=501 (/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd)

Aug 26 02:16:19 ####-iMac storeassetd[472]: SUAppStoreUpdateController: authorize

Aug 26 02:16:19 ####-iMac installd[419]: PackageKit: Adding client PKInstallDaemonClient pid=282, uid=200 (/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated)

Aug 26 02:16:19 ####-iMac storeassetd[472]: SUAppStoreUpdateController: install later for <none>

Aug 26 02:16:19 ####-iMac softwareupdated[282]: No keys specified for install-later registration

Aug 26 02:31:04 ###-iMac softwareupdate_firstrun_tasks[96]: Host swscan.apple.com isReachable = YES

Aug 26 02:31:28 ####-iMac loginwindow[101]: IASGetCurrentInstallPhaseList: no install phase array set

Aug 26 02:31:28 ####-iMac loginwindow[101]: IASGetCurrentInstallPhase: no install phase set

Aug 26 02:31:34 ###-iMac softwareupdate_firstrun_tasks[96]: BuildTagCache: Building tag cache if necessary using catalog host swscan.apple.com
_____


Anyway if it would help to see another log just let me know which... It could be spotify from what I see above, it could be some disk clean, or maybe some software auto install... I really cannot tell, hoping someone might have some incite. I was I could have looked at the logs when it was happening, but everyting freezes in finder and I can not launch a terminal...

Thanks for help. Sry for long time away, usually working late at least once a week... just happened to be not for awhile, but I will be working late again more often so any help would be so appreciated....
[doublepost=1472207550][/doublepost]Oh actually, this also interesting... I have no idea what LaterAgent is.. but this is about the right timing as well..

from the /var/log/commerce.log

...

Aug 26 01:47:42 ####-iMac storeassetd[472]: DAAPClient: pollForUpdate did not load items because localVersion=latestVersion (1472023###=1472023###), forcedUpdate=0

Aug 26 02:16:19 ####-iMac storeassetd[472]: UserNotificationCenterDelegate: Notification audit info is {

runDate = "2016-08-26 04:54:08 +0000";

}

Aug 26 02:16:19 ####-iMac storeassetd[472]: AuthorizationController: Non-interactive authorization succeeded

Aug 26 02:16:19 ####-iMac storeassetd[472]: AuthorizationController: authorizing PKInstallClient and SUAppStoreUpdateController

Aug 26 02:16:19 ####-iMac storeassetd[472]: UpdateController: Adding OS updates to Do It Later array - (

)

Aug 26 02:16:19 ####-iMac storeassetd[472]: UpdateController: Adding App updates to Do It Later manifest - (

"<CKUpdate: 0x7feec314f950>: bundleID:com.apple.garageband10 itemID:682658836 bundleVersion:10.1.2 staged:0",

"<CKUpdate: 0x7feec31f68a0>: bundleID:com.apple.iWork.Keynote itemID:409183694 bundleVersion:6.6.2 staged:0",

"<CKUpdate: 0x7feec34e3320>: bundleID:com.apple.iWork.Numbers itemID:409203825 bundleVersion:3.6.2 staged:0"

)

Aug 26 02:16:19 ####3-iMac LaterAgent[736]:



--------------------------------------------------------- Begin --


System Version 10.11.6 (Build 15G31)

"LaterAgent" Version 1.0 (463.9)


-------------------------------------------------------------------

Aug 26 02:16:19 ####-iMac LaterAgent[736]: ARMED (mode=1)

Aug 26 02:16:19 ####-iMac LaterAgent[736]: LACentralizedTaskObserver: Registered com.apple.lateragent.overnight CTS tasks for power-nap Do It Later

Aug 26 02:16:19 ####-iMac LaterAgent[736]: LACentralizedTaskObserver: Installed expected invocation date timer to fire at Friday, August 26, 2016 at 6:00:00 AM Pacific Daylight Time

Aug 26 02:16:19 ####-iMac LaterAgent[736]: LACentralizedTaskObserver: Installed manual start timer to fire at Friday, August 26, 2016 at 4:00:00 AM Pacific Daylight Time

Aug 26 02:31:28 ####-iMac nbagent[262]:



--------------------------------------------------------- Begin --


System Version 10.11.6 (Build 15G31)

"nbagent" Version 1.0 (1)


-------------------------------------------------------------------

Aug 26 02:31:28 ###-iMac nbagent[262]: NoticeboardUpdateOperation: No Store Client object specified

Aug 26 02:31:28 ###-iMac nbagent[262]: ISURLOperation: No Store Client object specified

Aug 26 02:31:28 ####-iMac nbagent[262]: ISURLOperation: WARNING - <ISURLOperation: 0x7fc822d3bb00> has no storeClient set for <ISURLRequest:0x7fc822d3cc00 https://swscan.apple.com/content/ca...iceboard-10.9-noticeboard.merged-1.sucatalog>

Aug 26 02:31:28 ###-iMac storeaccountd[268]:


Not sure if that helps at all, but just in case...

Thx
[doublepost=1472208068][/doublepost]And sry, last one, from my authd.log

the time i think it started to fail was around 2:16... rebooted at 2:30am ish...

Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (12,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software' by client '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (12,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.software.mdm-provided' by client '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (12,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [419] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software.standard-user' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [419] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [419] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.app-store-software.standard-user' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [419] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.software.mdm-provided' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [419] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software.standard-user' by client '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (3,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software' by client '/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated' [282] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:16:19 ####-iMac authd[112]: Succeeded authorizing right 'system.install.apple-software.standard-user' by client '/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated' [282] for authorization created by '/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storeassetd' [472] (4,0)
Aug 26 02:30:51 localhost authd[163]: Succeeded authorizing right 'com.apple.DiskManagement.Erase' by client '/usr/libexec/diskmanagementd' [197] for authorization created by '/usr/libexec/diskmanagementstartup' [62] (B,0)
Aug 26 02:31:29 ####-iMac authd[163]: Succeeded authorizing right 'system.login.console' by client '/System/Library/CoreServices/loginwindow.app' [101] for authorization created by '/System/Library/CoreServices/loginwindow.app' [101] (3,0)
Aug 26 02:31:30 ####-iMac authd[163]: Succeeded authorizing right 'system.login.done' by client '/System/Library/CoreServices/loginwindow.app' [101] for authorization created by '/System/Library/CoreServices/loginwindow.app' [101] (2,0)
Aug 26 02:31:31 ####-iMac authd[163]: Succeeded authorizing right 'system.services.systemconfiguration.network' by client '/usr/libexec/UserEventAgent' [275] for authorization created by '/usr/libexec/UserEventAgent' [275] (0,0)
Aug 26 02:31:43 ####-iMac authd[163]: Succeeded authorizing right 'com.apple.trust-settings.admin' by client '/usr/sbin/ocspd' [196] for authorization created by '/Library/Application Support/Kaspersky Lab/KAV/Binaries/kav' [89] (3,0)
Aug 26 02:35:56 ####-iMac authd[163]: Succeeded authorizing right 'system.burn' by client '/usr/sbin/diskutil' [566] for authorization created by '/usr/sbin/diskutil' [566] (10000B,0)
Aug 26 02:35:56 ####-iMac authd[163]: Succeeded authorizing right 'system.burn' by client '/usr/sbin/diskutil' [567] for authorization created by '/usr/sbin/diskutil' [567] (10000B,0)
[doublepost=1472209010][/doublepost]Crap it happened again tonight.. the only log that updated was the system.log

Aug 26 03:36:34 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:36:53 ####-iMac Mail[361]: tcp_connection_destination_perform_socket_connect 19 connectx to ####:####:####:###::##.###@0 failed: [65] No route to host
Aug 26 03:37:05 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:37:05 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:37:06 ####-iMac mds[66]: (Volume.Normal:166) vsd:0x7fad1906e400 DisabledStore recycle:8 context:{
DisabledRecycleCount = 8;
}
Aug 26 03:37:06 ####-iMac mds[66]: (Volume.Error:577) vsd:0x7fad1a04a000 Open failed. failureCount:8 {
DisabledRecycleCount = 8;
}
Aug 26 03:37:35 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:38:05 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:38:23 ####-iMac WindowServer[185]: disable_update_timeout: UI updates were forcibly disabled by application "Sublime Text 2" for over 1.00 seconds. Server has re-enabled them.
Aug 26 03:38:23 ####-iMac WindowServer[185]: common_reenable_update: UI updates were finally reenabled by application "Sublime Text 2" after 1.02 seconds [0.98fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])
Aug 26 03:38:35 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:39:06 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:39:06 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:39:06 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:39:36 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:40:06 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:40:06 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:40:06 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:40:36 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:41:07 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:41:07 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:41:07 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:41:14 ####-iMac syslogd[45]: ASL Sender Statistics
Aug 26 03:41:37 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:41:37 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:41:53 ####-iMac Mail[361]: tcp_connection_destination_perform_socket_connect 20 connectx to ####:####:####:###::##.###@0 failed: [65] No route to host
Aug 26 03:42:07 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:42:07 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:42:08 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:42:08 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:42:38 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:43:08 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:43:38 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:44:08 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:44:38 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:44:38 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:45:09 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:45:39 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:46:09 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:46:39 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:46:40 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:46:40 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:47:07 ####-iMac kernel[0]: poll: removed pid 788 from excludes
Aug 26 03:47:10 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:47:40 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:47:40 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:47:40 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:47:57 ####-iMac Mail[361]: tcp_connection_destination_perform_socket_connect 21 connectx to ###:###:###:##:##.###@0 failed: [65] No route to host
Aug 26 03:48:10 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:48:41 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:48:41 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:48:41 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:49:11 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
Aug 26 03:49:11 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:49:31 ####-iMac CalendarAgent[291]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
Aug 26 03:49:41 --- last message repeated 1 time ---
Aug 26 03:49:41 ####-iMac kernel[0]: USB device 1058123014A00000 - will be reset!
Aug 26 03:49:41 ####-iMac kernel[0]: USBMSC Identifier (non-unique): 574D43344E3031353134#### 0x1058 0x1230 0x1050, 3
Aug 26 03:49:41 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 2.
Aug 26 03:49:41 ####-iMac kernel[0]: disk1s1: I/O error.
Aug 26 03:50:12 ####-iMac kernel[0]: USB device 1058123014A00000 - fConsecutiveResetCount = 1.
 
I think it is a problem with my usb connection to my harddrive. I tried plugging it into a different usb port, and it seems to reset it. I guess I will try it in this other port for awhile and see what happens. maybe some weird conflict or something...

It happened again and I got the USB device thing again in the system log so hopefully that is it and hopefully changing ports fixes it... I will repost later if it works or not, either way...
 
Elliot7777 said:
I think it is a problem with my usb connection to my harddrive. I tried plugging it into a different usb port, and it seems to reset it. I guess I will try it in this other port for awhile and see what happens. maybe some weird conflict or something...

It happened again and I got the USB device thing again in the system log so hopefully that is it and hopefully changing ports fixes it... I will repost later if it works or not, either way...
Click to expand...

You are apparently getting an intermittent I/O error on disk1s1, probably that WD drive. You should probably first ensure 100% of that content is backed up somewhere in case it degrades further. Then and only then run more tests on the drive.

There are various robust tests available including
ScannerZ: http://scsc-online.com/Scannerz.html
DiskTestR: http://diglloydtools.com/disktester.html

There is a drive diagnostic tool called DriveDX, available from the App Store:
https://itunes.apple.com/us/app/drivedx/id526290112?mt=12

DriveDx doesn't do surface scanning, it's more of an S.M.A.R.T reporting tool. A significant limitation is on USB drives you must install a 3rd party kernel extension to make it work. They provide details on how to do this.

Also make sure your external USB HDD is not plugged into a USB hub but directly into the Mac.
 
That's what it looks like to me too-- bad USB cable or drive. Keep an eye on it for more "disk1s1: I/O Error" messages.
 
Scannerz can test for bad cables in its diagnostic mode. An easier solution is to just try a different USB cable. If the problem continues then you know that disk1 is bad. You need to check and make sure that disk1 is the USB drive since I don't know how may drives you have connected to your system.
 
I had a WD external backup drive and the controller card busted. The USB connector just broke off one day when I was plugging it in. I figured I could order the part from WD to fix it or send it in. Either way, it would take time and money. Instead I decided to take the drive out of the case and put it in a better built external case. When I plugged the drive in the new enclosure into the system, the drive was seen as available but not formatted. I did a web search and found that the controller, at least for my MyBook, was encrypting the data. I figured since I already had clones of the volumes and this was for Time Machine to just re-format it.

The results? The drive, which was slow as molasses in the WD enclosure now screams, even thought it's a green drive. For years the WD MyBook would cause a boot delay as long as it was connected to the system of as much as 40 seconds, now it's seconds. When the system accesses the drive it's now fast. For years, I thought the drive itself was just slow as molasses because it was a green drive, but it wasn't, it was something the controller was doing that was slowing everything up.

I'm now impressed with the green drive, but I'm not impressed with the case and interface card the drive used. The case was a cheap plastic, even though the picture on the box makes it look like it's machined metal. The USB connector to the outside world was not reinforced at all and when it snapped I was barely putting pressure on it. Once out of the WD case and into a decent case, the drive itself is now great.

The morals of the story are: 1) Don't necessarily blame the drive - WD is putting these things together so cheaply anything can break, and 2) Don't be surprised if when it's in a new enclosure it's been encrypted and needs reformatting before it gets used.
 
WorkerBee2015 said:
I had a WD external backup drive and the controller card busted. The USB connector just broke off one day when I was plugging it in. I figured I could order the part from WD to fix it or send it in. Either way, it would take time and money. Instead I decided to take the drive out of the case and put it in a better built external case. When I plugged the drive in the new enclosure into the system, the drive was seen as available but not formatted. I did a web search and found that the controller, at least for my MyBook, was encrypting the data. I figured since I already had clones of the volumes and this was for Time Machine to just re-format it.

The results? The drive, which was slow as molasses in the WD enclosure now screams, even thought it's a green drive. For years the WD MyBook would cause a boot delay as long as it was connected to the system of as much as 40 seconds, now it's seconds. When the system accesses the drive it's now fast. For years, I thought the drive itself was just slow as molasses because it was a green drive, but it wasn't, it was something the controller was doing that was slowing everything up.

I'm now impressed with the green drive, but I'm not impressed with the case and interface card the drive used. The case was a cheap plastic, even though the picture on the box makes it look like it's machined metal. The USB connector to the outside world was not reinforced at all and when it snapped I was barely putting pressure on it. Once out of the WD case and into a decent case, the drive itself is now great.

The morals of the story are: 1) Don't necessarily blame the drive - WD is putting these things together so cheaply anything can break, and 2) Don't be surprised if when it's in a new enclosure it's been encrypted and needs reformatting before it gets used.
Click to expand...

I've had problems with one of those drives for years. Thanks for the tip. For me it just seems to almost lock up and it really does cause the system to boot slow. For example, during boot it's normally about 30 seconds if it's just the system. With the WD connected it almost always adds another 30 seconds to that. I'm not holding my breath expecting the green drive to be a killer performance wise, but right now it's like cold syrup.

Thanks for the tip.
 
FYI - If you're using Sierra there seem to be a lot of problems with USB drives on it. I have a USB connected via a hub and half the time when I boot Sierra the drive will never show up. I've also heard of erratic disconnects occurring with it.
 
ZVH said:
FYI - If you're using Sierra there seem to be a lot of problems with USB drives on it. I have a USB connected via a hub and half the time when I boot Sierra the drive will never show up. I've also heard of erratic disconnects occurring with it.
Click to expand...

Yep, my WD My Book Duo occasionally drops out incl. loosing all favourite folders on it in Finder.

It happens more often in sleep mode, sometimes during normal operation.

The drive automagically reconnects and reappears.

I think it's some bug.

Also do not install WDs drive utilities, it also causes disconnects.
 
WorkerBee2015 said:
I had a WD external backup drive and the controller card busted. The USB connector just broke off one day when I was plugging it in. I figured I could order the part from WD to fix it or send it in. Either way, it would take time and money. Instead I decided to take the drive out of the case and put it in a better built external case. When I plugged the drive in the new enclosure into the system, the drive was seen as available but not formatted. I did a web search and found that the controller, at least for my MyBook, was encrypting the data. I figured since I already had clones of the volumes and this was for Time Machine to just re-format it.

The results? The drive, which was slow as molasses in the WD enclosure now screams, even thought it's a green drive. For years the WD MyBook would cause a boot delay as long as it was connected to the system of as much as 40 seconds, now it's seconds. When the system accesses the drive it's now fast. For years, I thought the drive itself was just slow as molasses because it was a green drive, but it wasn't, it was something the controller was doing that was slowing everything up.

I'm now impressed with the green drive, but I'm not impressed with the case and interface card the drive used. The case was a cheap plastic, even though the picture on the box makes it look like it's machined metal. The USB connector to the outside world was not reinforced at all and when it snapped I was barely putting pressure on it. Once out of the WD case and into a decent case, the drive itself is now great.

The morals of the story are: 1) Don't necessarily blame the drive - WD is putting these things together so cheaply anything can break, and 2) Don't be surprised if when it's in a new enclosure it's been encrypted and needs reformatting before it gets used.
Click to expand...

Glad to hear that. I have one of them and the first thing I noticed was how cheaply built the case was. I had to replace the original cable with the drive because I'm fairly certain it was built by none other than Santa's elves. The photo on the box cover makes it look like it's a nice metal enclosure but everything is plastic and cheap.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back