March 5, 201115 yr I've reported in another thread issues with being able to copy some files to my UnRAID server through Windows 7 (timeout errors on first attempt but then no issue on 2nd attempt) but today I've reached a new level of frustration. No matter what I do, I can't seem to keep disk 3 from timing out. I'm in the middle of a preclear on another disk; otherwise, I would check the cable connection. Is it wront to assume that I wouldn't be able to browse the disk contents from Windows Explorer if the cable was loose? I keep getting a network timeout with this disk when trying to write a file. I also noticed that the reads for the disk are jumping in increments of 30k for each attempt. Syslog also shows UnRAID trying to spinup the disk even though it's already spun up?! Smart report doesn't show any issues with the drive and I'm able to complete a short test without issue. Any other thoughts until tomorrow afternoon when I can shutdown the server and check connections? Mar 5 14:39:05 Tower kernel: mdcmd (20): spinup 3 (Routine) Mar 5 14:39:05 Tower kernel: (Routine) Mar 5 14:39:35 Tower kernel: mdcmd (21): spinup 3 (Routine) Mar 5 14:39:35 Tower kernel: (Routine) Mar 5 14:41:41 Tower kernel: mdcmd (22): spinup 3 (Routine) Mar 5 14:41:41 Tower kernel: (Routine) Mar 5 14:50:47 Tower kernel: mdcmd (23): spinup 3 (Routine) Mar 5 14:50:47 Tower kernel: (Routine)
March 6, 201115 yr Author Update: I just tried copying the file (banner artwork for a tv series so only 120 KB) again and got an error code 0x8007003B indicating a network issue. After a lot of head scratching, I tried to copy a larger file (25 MB) to a different directory and the copy went fine. I then was able to copy the 120 KB file to the same directory and move it to the correct location. This sure feels like an issue with how UnRAID handles file transfers with Windows but who knows...
March 6, 201115 yr I've noticed something similar when I moved to 4.7. Seemed related to writing to a spun down disk. It took so long to respond that Windows gave an error. The file started to get created on the array and then Windows was trying to remove it which also caused problems. I found if I spun up the data and parity drives that this doesn't happen.
March 6, 201115 yr Author Info requested attached. The strange thing is that the disk was already spun up. My profile is setup to keep the disk spun up from boot for at least 5 hours. The other strange this is that I was able to copy the file to the root directory of the drive but not the subdirectory. Directory structure is as follows: /root/media/TV/Show/Season/file.jpg Is there any character length limitation on the directory structure? Just something I thought about as I was trying to troubleshoot this issue. Thanks for trying to help me with this issue! syslog.txt Smart_Report.txt
March 6, 201115 yr What is the size of disk3, and how full is it? I have see similar issues when writing to 2T disks that are nearly full.
March 6, 201115 yr Author Was parity spun up too? Yes, like I said in the first post, I've had issues in the past with transferring files from Windows 7 to UnRAID. I've tried upgrading the driver of the NIC on the Win 7 machine but still have intermittent issues. This is the first time that I wasn't able to initiate a write after the first failed attempt. I've also reported other (somewhat similiar) issues between Win 7 (also Vista) and UnRAID in the following threads: http://lime-technology.com/forum/index.php?topic=8713.0 http://lime-technology.com/forum/index.php?topic=10180.msg97325#msg97325 What is the size of disk3, and how full is it? I have see similar issues when writing to 2T disks that are nearly full. 34.4 GB of 2T free on disk 3 and 3.16T free in an 11TB array.
March 6, 201115 yr The syslog does not seem to capture the event. Did it happen during the duration of the log? If not, post one again after it happens.
March 6, 201115 yr Author The event happened between 14:39:05 and 14:50:47. The syslog shows a couple of "spinups" but what's weird is the disk was already spun up. After clicking "retry" a bunch of times I was given a 0x8007003B errror code from Windows 7 x64.
March 15, 201115 yr I just got my unRAID 4.7 system setup and online and attempted to write to a user share from a Windows 7 64-bit PC. I encountered the same thing...the transfer would timeout after less than 20 seconds. I logged into the Admin interface and spun-up the drive and attempted to copy the file again...so far so good. I'm about 7gb transferred so far of the 14gb file. My unRAID is pretty "plain jane" right now...just a single 2TB hard drive, no parity drive yet. The 2TB is a Samsung F4. I applied the firmware update and pre-cleared it without any issues. I haven't tried a transfer from another OS yet (not sure I'm running anything other than Win7 64-bit). Is this simply an issue with the drive not spinning up? I don't mind having to manually spin the drive up for writes, but will the same thing happen when I try to read?
Archived
This topic is now archived and is closed to further replies.