Hi

 

I've been a happy unraid user for over a year, until a few days ago... Windows (Win 7 64) started saying "There is a problem accessing ....", where the path always is a unraid share. This is during writing of 1GB+ single files to the unraid share. The symptom is that the transfer rate is normal at the start of the file copy but crawls down to a halt after a variable amount of time. I'm running 4.5.6 Pro.

 

I've searched the forum, without finding a solution. The only thing out of the ordinary in my syslog are these lines (no other errors reported in the web gui) :

 

Aug 24 22:55:38 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Aug 24 22:55:38 Tower kernel: ata4.00: failed command: READ DMA EXT

Aug 24 22:55:38 Tower kernel: ata4.00: cmd 25/00:00:47:8e:3a/00:04:8e:00:00/e0 tag 0 dma 524288 in

Aug 24 22:55:38 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Aug 24 22:55:38 Tower kernel: ata4.00: status: { DRDY }

Aug 24 22:55:38 Tower kernel: ata4: hard resetting link

Aug 24 22:55:38 Tower kernel: ata4: softreset failed (device not ready)

Aug 24 22:55:38 Tower kernel: ata4: applying SB600 PMP SRST workaround and retrying

Aug 24 22:55:38 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Aug 24 22:55:38 Tower kernel: ata4.00: configured for UDMA/133

Aug 24 22:55:38 Tower kernel: ata4.00: device reported invalid CHS sector 0

Aug 24 22:55:38 Tower kernel: ata4: EH complete

 

The problem is that these lines do not always show up in the syslog when the problem occurs. As far as I can tell ata4 is my /dev/sdd, which is my parity drive (parity device: pci-0000:00:11.0-scsi-3:0:0:0 host4 (sdd) WDC_WD15EADS-00R6B0_WD-WCAVY0083763)). I'm using user shares, but have tried copying to the individual drive shares with the same result.

 

Reading from the shares seems to be working as normal. I'm currently running av parity-check (which is slower than normal) and at 24% it has not reported any errors, and nothing in the syslog.

 

Is this an indication that there is something wrong with my parity drive? smartctl shows nothing that would indicate this...

Just an update on the parity-check.

 

Now at 30%, running at very variable speeds. As low as 136KB/sec. Still no errors and nothing in the syslog.

Is your parity drive forced via jumper for 1.5 GB rather than 3GB?  What motherboard or controller card is it connected to?  Just trying to determine if there is a reason why it would be configured for 1.5 rather than 3.

 

In general, there does appear to be a problem with drive 4, whether it is a loose cable or a problem with the drive itself I don't know.  Its up to you whether you want to wait until parity calc is complete or halt it and troubleshoot the drive.  In either case, I'd turn off the machine, check and reseat the cables attached to the drives and run a SMART test on the parity drive.

I aborted the parity-check when it went down to 58 KB/s and stayed there.

 

No jumpers. Drive 4 is connected to the motherboard controller. It's a Gigabyte MA74GM-S2H board. I have now opened the server and checked the cables. Everything seemed fine. I'll boot it now and do some more tests.

Did you ever get any resolution to your issue?  I am having the same "there is a problem accessing ..." while trying to write 1gb+ files to the unRaid server. Like sometimes it freezes or becomes temporarily unavailable.

 

 

Same problem here.

 

It fails when copying large files or a great number of files.

 

Windows 7 backup fails a lot of times saying the destination path is not available.