Hi all. I'm new to unRAID and need a bit of help getting things going.

 

I have repurposed an old gaming machine with the following specs:

Motherboard = Asus P5N32-E SLI Plus

Memory = 2GB RAM

CPU = Intel Q6600 Core2 Quad 2.4GHz

Cache disk = 250GB Samsung SSD

Disk 1 = 3TB WD Green HDD

Boot = 32GB Cruzer Edge USB stick

Graphics = Asus NVidia GTX 560Ti

 

The HDD and SSD are new. I stick them in the machine and assign them to data disk 1 and cache disk via the web UI and everything appears to work as expected. I can install some plugins and dockers fine.

 

I plug in an external HDD, mount as unassigned drive, and copy over some movies to /mnt/user/movies/. This is done via ssh from a terminal window. It starts copying data but always drops out pretty quickly with input/output errors.

 

e.g.

Dec 17 10:38:55 Tower kernel: md: disk1 write error, sector=1303960

Dec 17 10:43:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/movies Input/output error

 

On the unRAID web UI I can see worrying stats on the HDD:

Reads: 140,733,801,461,264

Writes: 34,177,702,359,547,252

Errors: 7400

 

The ssh session freezes up and the drive becomes inaccessible until I reboot the machine. After a reboot it all appears fine (no crazy read / write counts and no errors) until I try copying the folders over again. I have tried precleaning the disk and reformatting but I get the same problem. I have attached a syslog.

 

Any ideas?

tower-syslog-20151217-1117.zip

When you look at your main page what is the filesystem for disk1?

xfs

Go to tools > diagnostics and post complete zip.

Thanks johnnie.black.

 

Here's the diagnostics zip from the machine in its errored state. Let me know if it would be useful to get the same after a reboot.

tower-diagnostics-20151217-1300.zip

Your WD drive completely dropped off line (no smart results at all for it)  Good chances that its merely a bad sata cable, or its slightly loose.  Reseat everything

 

Also, not sure if this is you that caused this or not, but you may want to investigate:

 

Dec 17 11:11:03 Tower sshd[15001]: Address 193.203.82.26 maps to condor2-2.sohonet.co.uk, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!

Thanks for taking a look at the diagnostics.

 

So I've just tried changing sata cables, motherboard sata ports, and hdd power cables. The error repeats every time I start a significant data transfer going to disk 1. I've attached another diagnostics log from when the array is functioning normally to compare. You can see the WD drive does show up in this case.

 

Is it likely that it's just a dodgy disk?

tower-diagnostics-20151217-2118.zip