Replies

Thank you for that suggestion, but in my copy of Windows 10 1903 that option is not available anymore.

Thank you for your post. I wound up replacing all of my Seagate drives with Western Digital Elements 4 tb drives. Since then everything is working just fine. I hypothesize that there is something going on with how Seagate responds to the Windows 10 supplied USB drivers. You can see more in a post I made below…

Hello,

Thank you for that suggestion. However, drive letter assignment hasn’t been a problem for me. All of my attached drives have always retained their assigned drive letter.

You can see my ultimate solution to the problem in a post I made below…

Hello,

Thank you for that suggestion.
You can see my ultimate solution to the problem in a post I made below…

Edit: Please do not duplicate posts.
see Lounge Rules

Well, when all else fails …..

I hypothesized that the problem might just be specific to the physical drive and the way it interacts with Windows 10.  The physical drive being just fine, the interface software/hardware/ROM (whatever) was not playing nice with the Windows 10 provided driver.

So I replaced all of my Seagate drives with Western Digital Elements 4 tb drives.  Last night was the 1st night that the implementation was in place.  This morning all backups had run fine and there were no entries in the Event Log relating to the device “healthy”.

I consider this problem solved, albeit at a $$$ cost.  I’m not disparaging Seagate drives, I’ve used them for years, but somewhere along the way I think Microsoft made changes that impacted the Seagate interface.  Or vice versa, Seagate made changes.  I’ll continue to use the replaced Seagate drives on an ad hoc basis.  Just not for nightly backups.  Oh well…

1 user thanked author for this post.

cyberSAR

Well, so much for the job schedule being the source of my problem.  The 1st night after I fixed the schedule each copy job ran with no problem.  But last night one of the two troubled jobs failed with the usual error of “device not found”.

Scanning the System event log I find the following logged entries:

Volume N: (\Device\HarddiskVolume21) is healthy.  No action is needed.

and

Volume O: (\Device\HarddiskVolume23) is healthy.  No action is needed.

These entries relate to the two drives where the problem occurs.  These entries appear with some frequency in the System event log.  There are no entries for any of the other two drives attached to the USB hub.

I’ve searched the web for these entries and the only information I get is from some questions to Microsoft support where they suggest a 3rd party application is causing the problem and they recommend a “Clean Boot” to resolve the issue.  But I don’t get why.  Also, I have experienced the “beep boop” sound you get where a USB device is disconnected and then reconnects.  That was mentioned in some peoples posts.  But I don’t see why this would happen to two drives and not others on the same USB 7 port hub.

Really frustrating……..

Last night’s backup still had the problem with the disk drive not found.

So I’ve said it’s not my Novalogic backup software, and I still think that, but when everything else is ruled out you must consider alternatives.  This morning I started reviewing my windows event logs.  I found entries for the start and finish of the copy jobs.  And in reviewing the time stamps I saw that the logs for the failing drive not found error was about the same time as the drive that worked.  Background …. I’ve set the 4 copy jobs to be one hour apart … 12 midnight, 1 am, 2 am and 3 am to prevent timing problems.   Or so I thought…. I went into the job scheduler and found that the jobs for the two drives that alternately come up “not found” are both scheduled for 1 am.  One should be 1 am and the other 2 am.  So I’ve fixed the schedule and we’ll see what happens going forward…

BIG FOREHEAD SLAP!!!!!  DUH!

So after replying to the two suggestions above, I went back into Device Manager and double checked my Power Management settings for the USB Hubs.  Don’t cha know … I found some hub entries that still had Power Management enabled…  I’d swear I examined every entry in there one by one.  Empirically I was wrong.  Let’s see how things go the next couple of nights.

1 user thanked author for this post.

Elly

Hello,

The USpeed 7 port USB 3.0 hub does have it’s own separate power supply.  It is connected directly to a USB 3.0 port off the main board on my Maingear Shift desktop computer.  The problem occurs to the same two drives even when I move the drive’s connection to a different port on the hub.  Yet two of the drives consistently work fine.  The problem appears to be drive specific.  The drives always retain the same drive letter assignments.