WizADSL

Currently I have drive 5 rebuilding. Disk disk is currently disabled/emulated during the rebuild. I don't believe there is anything wrong with disk 6, when disk 5 is done rebuilding how do i get disk6 to rebuild? Presumably the disabled status needs to be reset.

It could be either of those but it's an EVGA 1600 watt PSU and a 24 bay SAS backplane, I can find another PSU but not sure what I can do about the backplane other than to make sure the SFF cables are well seated but since those are have clips they are probably seated well. It is likely very dusty on the inside, is that a possibility (maybe a controller or somgetting else getting hot due to dust)? Also, I did stop the rebuild of disk 5 once disk 6 was dropped, when I boot it back up will disk 6 have the error condition reset and can I restart the rebuild of disk 5 without having to do a new config?

On the 1st of August my scheduled parity check kicked of and maybe an hour into it a disk was dropped from the array. I replaced the disk and allowed it to rebuild which it did successfully. Today I decided to run a non-correcting parity check to make sure everything was fine and about 30 minutes into the check I have a disk drop from the array, it was an old drive but had not issues in the smart report and I should have maybe stopped there but I decided to replace it since it was plausible that it had failed. About 2 hours into the rebuild another drive dropped. Obviously something else is wrong. I'm attaching a diagnostic zip file that should include today's failure and the rebuild I started and then the additional failure. At this point I am running memtest86+ but so far no errors. The system has 3 LSI controllers in it and I'm starting to wonder if it's not one of those. Any help would be appreciated. Diags.zip

Could someone please post the smartmon tools output for a Samsung 870 EVO 2TB? Probably any of the variants would be fine (1 TB - 4TB) but the 2TB is the one I'm specifically interested in. If you are looking in the UNRAID web UI I'm specifically looking for the contents of the Identity tab. Thank you.

Ok, so where's Red Dwarf then?

After the preclear runs, you are given the option of sending back statistics through Google forms. If you confirm the dialog it will come back as say it was sent, however the XHR request that is made(against StatsSender.php) fails with the following error returned in the XHR response: <br /> <b>Warning</b>: array_merge() expects at least 1 parameter, 0 given in <b>/usr/local/emhttp/plugins/statistics.sender/StatsSender.php</b> on line <b>26</b><br /> I am on unraid 6.4.0_rc14 and the plugin version is 2017.11.14. I know this does not affect the functionality of the plugin but since it is an error someone is unlikely to find I thought you'd want to know. In case it has any bearing on the issue, I precleared the same disk twice and this occurred after the second preclear. I wasn't looking and don't know if the first stats report succeeded or failed.

I just updated by Crashplan Docker and I'm having the same problem.

I've just noticed that if I use rsync to copy files from a non-array location (it may not matter where the files are coming from, but this is the case for me) to a disk on the array that is being monitored by the file integrity plugin no checksums are being added to the written files. The rsync command I am using is: rsync -avHAX --progress /mnt/SomeDrive/ /mnt/disk1/Destination/ Also, would it be possible to add additional locations outside the array to have checksums added/checked? It would be great if I could monitor all of the files on my system.

I'm using the rsync method to move from RFS to XFS on UnRaid 6.0.1. The command line I am using is: rsync -avX --progress --remove-source-files /mnt/diskXX/ /mnt/diskXX/ In my case I've added the X flag to preserve extended attributes (although I'm not sure I need it, I seem to recall that RFS extended attributes are used to store some samba attributes). The reason for my post is that the version of rsync this is installed in 6.0.1 is 3.1.0 and I noticed after copying a 3TB drive that although the "a" (archive) flag preserves the timestamps on copied files, it does not do this for directories. I decided to install the latest version of rsync (3.1.1) and it DOES preserve directory timestamps. There is a flag (-O, --omit-dir-times) available in order is disable the behavior; since this flag is present in 3.1.0 and 3.1.1 then I assume the directory dates not being set was a bug in 3.1.0. If anyone is interested I got version 3.1.1 from http://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/rsync-3.1.1-x86_64-1.txz Please keep in mind that when using the rsync command as illustrated above the entire directory structure from the source will be created on the destination disk with the current date/time and only after the directory's contents have been copied will the timestamp be updated.