I have two completely different types of drives showing free space is available, yet I can't ever write to them. Copying files always fails without even writing any data.

 

Free: 12.0 GB

Seagate Barracuda 7200.11

ST31500341AS

 

Free: 6.64 GB

SAMSUNG SpinPoint F4 EG (AF)

SAMSUNG HD204UI

 

I checked the logs, but I don't see anything.

 

Running 5.0.6.

 

Thank you,

Adrian

I have two completely different types of drives showing free space is available, yet I can't ever write to them. Copying files always fails without even writing any data.

Exactly what do you mean by that? Is an error being returned?

 

Post your syslog.  Your drive's file systems may be set to read only status (corrupted file system)

 

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

I have two completely different types of drives showing free space is available, yet I can't ever write to them. Copying files always fails without even writing any data.

Exactly what do you mean by that? Is an error being returned?

 

Post your syslog.  Your drive's file systems may be set to read only status (corrupted file system)

 

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

 

I went back and tried other methods of coping/moving and I got it working with TeraCopy, so there seems to be an issue with DOpus and one of the Samsung drives. I still need to go and test/locate the other drive that I was having issues with. Some sort of timeout perhaps? I'll send an email off to DOpus support to see if they've encountered any issues like this and see if they have any settings I can change.

 

ok, I found the other drive that issues and Teracopy definitely can't write to it. I've attached the syslog.

 

This is the drive I'm having issues writing to:

Disk 13  ST4000DM000-1F2168_W300S9HN (sdk) 3907018532

 

Thanks,

Adrian

syslog.zip

The syslog looks clean as far as drive errors.  There is a ton of avahi errors which are network related.  Not sure about the cause however.

 

Are you trying to copy directly to drive 13 or are you using user shares?  What errors are showing up

The syslog looks clean as far as drive errors.  There is a ton of avahi errors which are network related.  Not sure about the cause however.

 

Are you trying to copy directly to drive 13 or are you using user shares?  What errors are showing up

 

Yes, I was trying to copy directly to drive 13. The errors reported by both Teracopy and DirectoryOpus don't really say much other than there was a failure. I could try contacting DOpus support and they may be able to tell me how to enable/access logs that might have more information.