dgaschk

See here : http://lime-technology.com/wiki/index.php/Troubleshooting#Resolving_a_Pending_Sector

Get a SMART report.

Delete any save credentials in Windows control panels -> Credentials.

Purchase some 50 or 100 meter CAT 6 cables and run temporary connections that bypass the in wall wiring.

You must be joking. The only thing that couldn't work is the controller. The type of memory doesn't matter in this case. What matters is that TLC memory is worst choice for UNRAID, because this system doesn't have trim support. This is incorrect. The Samsung Evo SSD is a TLC device with TRIM support. TRIM is implemented in the controller. The 840 EVO’s MEX controller supports SATA 3.1 TRIM commands. TCL vs MLC refers to the bit density and has nothing to do with the controller, SATA, or TRIM.

See SYSTEM LOG in my sig.

Copy and attach the syslog then check the power and SATA cables to the drive.

The TCP trace i not enough to be useful but looks normal; 65536 is the TCP window size and 1466 is the maximum segment size. Jumbo frames is not the issue. After the speed is no longer abysmal you can investigate jumbo frames for further optimization. However, unless the networking hardware is sub-par the maximum gain is about 3% in a LAN. 3% is generally not worth the additional configuration management.

AHCI is recommended for greater performance and stability. Changing the setting should not effect the array.

Next time do NOT reboot. Collect and attach a zipped syslog. See SYSTEM LOG in my sig.

Yes. But why does power down fail as well? /tmp/unmenu_tmp/powerdown-1.02_ctlaltdel-unmenu-package.conf not installed

I get this too.

See my sig.

See my sig.

Yes.

What does \\tower\disk5 show?

See my sig.

May 5 10:35:57 Tower logger: Installing system plugins May 5 10:35:57 Tower logger: installing plugin: webGui-latest May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: May 5 10:35:57 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 May 5 10:35:57 Tower logger: xml parse error May 5 10:35:57 Tower logger: Installing user plugins May 5 10:35:57 Tower logger: Starting go script May 5 10:35:57 Tower emhttp: unRAID System Management Utility version 5.0.5 webGui-latest is incompatible with version 5.

Yes.

Show the output of "ps x | grep emhttp"

Core unlocking is never a good idea. They are locked because they failed validation testing. They may crash on every boot or they may crash only under very specific conditions or they may behave unexpectedly. All chips are manufactured as multi-core but the the manufacturing yield (and thus cost) is lowered if more single core chips are needed. Selling chips with a second valid core as single core chips make little economic sense.

See check disk filesystems in my sig.

Assign and rebuild disk 4.

Attach a screenshot of unRAID Main.

Run check disk on the flash in a Mac or PC.