coldhammer

Just a quick FYI for anyone getting the error 13 failed to install. I was able to fix it by changing my primary vdisk bus type to USB.

I got the failed to install error 13 as well. tried numerous configurations of loaders and pat files centOS vs Ubuntu. The issue was my primary vdisk bus was set to vritIO. changed to bus type USB and the install proceeded. in the end followed the exact guide above, set primary vdisk bus to USB and used DS3615xs 1.02b with DSM_DS3615xs_15047.pat to work on my machine.

Ive set my my parity schedule to run once a week. However its seems to be running randomly. 2-4 times in a rolling 7 day period. been doing this now for about 2 months. Thoughts?

yes still using the sas2lp card. signature is incorrect. will update now. error counts vary widely per run. 20ish - 180. last three runs were (127,192,65)

Is it common for unpaid to find and correct errors on every parity check? I run parity check once a week for several years now and I dont think I have ever had a run that didn't result in finding and correcting errors.

*Solved* there were two issues. 1) I had output set to a sub directory within the storage path. Seeing the post above by Djoss that storage was readonly it made me think that the read only permissions were applying to the subdirectory as well. Moved the output folder to a level above the storage folder allowed it to write the output file. 2) within the GUI the destination directory shows as being set to a "folder" named output. it is not clear that this folder name is actually just a pointer to the folder selected in the output path of the docker. Showing the name of the user selected output folder within the GUI would be a good improvement to the UX of the docker.

I installed the docker and ran a test and it wrote a file to the selected directory. I then created a new directory for output files, edited the output path in the docker and got "unable to write" to directory error. I have reset permissions on the directories and that did not make a difference. I uninstalled and reinstalled several times and set the path during initial and post installation and that has not fixed the issue. I can also no longer write to the directory that it was successful writing to on the first install.

hah. that brings the testing to a screeching halt. not much i can do about the board. ill just rebuild with the new setup and then try and sync parity again.

ran a memtest. 20 passes no errors. what should i look at next?

attached. tower-diagnostics-20170612-0805.zip

hardware as in bad parity disk or hardware as in sas controllers, mobo, memory or other hard drives? is it possible to figure out where the hardware issue lies?

rebuilt disk, ran parity 0 errors. immediately ran a second parity check (no new activity on the array was conducted before during or in between parity checks). Second parity check turned up 5572 errors. if the first check had 0 errors and there was no new disk activity how could the second check have 5572 errors?

swapped out another cable and was able to complete an extended smart test on the parity drive. says test completed with no errors. new log attached. tower-diagnostics-20170607-0855.zip

dont have any virtual machines setup. yes it dropped off in the middle of the smart report. not sure about it being a bad disk though. its a pretty new drive. ran multiple preclears on it with no issues. at this point i now have no parity disk assigned to the array. which means parity needs to be rebuilt. i have a complete new board/cpu setup for this machine. ive been waiting until i got everything up and running correctly with the array before upgrading the parts. I seem to have multiple hardware failures going on with the current setup. Since i no longer have any parity would i be alright to just go ahead and put in the new hardware then create a new config and let the parity rebuild? This approach would at least remove alot of the hardware related issues hopefully.

swapped in a new cable to the parity drive. rebooted, parity was still disabled, started an extended smart test after a few minutes parity drive just completely disappeared. now shows no device. log attached. tower-diagnostics-20170605-2115.zip