View Single Post
Old 10-30-2016, 02:17 PM   #9
docmartn
Member
docmartn began at the beginning.
 
docmartn's Avatar
 
Posts: 13
Karma: 10
Join Date: Aug 2016
Location: Houston
Device: Android and PC
Quote:
Originally Posted by BetterRed View Post
Can you confirm you mean rename (as in something like "Main Data Drive") rather assigning a new drive letter e.g. D: to F:. AFAIK drive names don't mean much to anything other than us mere humans.

Indeed, it would be odd for all three to be flaky - unless there's a gremlin in the infrastructure they share.
Are the three drives internal or external?

If they're external try a different usb port or 'drive housing'. And if they are external it could be the usb controller that's at fault. If latter and it's a desktop you could get a USB 3.x adapter for not very much.
BR
By rename I changed the label from Seagate F Drive to F - Seagate Drive
I didn't change the drive assignment.

All three drives are external and each uses a different USB controller.

I've got 3 different controllers on this PC -
• Two in back - each as 4 ports
• One in front - 2 ports

Each device was connected to a different controller - I didn't do this on purpose it just turned out that way.

This morning I moved the drive where the Calibre Library is stored (along with some of my un-catalogued books) to a different USB controller. I was then able to books from each of the 3 hard drives including the one were Calibre is stored and so far I'm able to add and save without errors.

This leads me to believe that there’s either something wrong with the USB port or possibly the drive although if it were the drive I’d think I’d still be having issues. As for the USB port in question I have two other drives on it which seem to be fine. (Yes, I have several external drives and yes I know this probably isn’t the best solution - unfortunately I can't afford a petabyte drive which is what I really need)

I’ll keep messing around with the drives and ports to see what happens. I appreciate everyone’s input and trouble shooting help.

@theducks I understand what you said about the Calibre drive vs. the add drives. It makes perfect sense. I wasn’t thinking that a record is immediately created on the Calibre drive regardless of the add drive which explains why I was getting the error regardless of the drive I was adding from. I also reverted back to an older version 2.68) of Calibre but in hindsight I don't think that was needed. I'm also going to check all the drives with SMART.

You’ve all be great as usual. I wish I could buy you a beer. Wish me luck. JCM
docmartn is offline   Reply With Quote