Turbobuickguy

I'm running 6.3.3 Complete diagnostics attached. tower-diagnostics-20170503-0412.zip

I wanted to clear a drive to remove from my array, a 2 TB WD green, using the clear_an_array_drive script. I was unsure if I wanted to run it from the plug-in or command line. I originally started it from the plug-in, but it appeared to be moving very slowly... I cancelled it, and then started it from the command line in a screen. It did not seem to be any quicker, so I changed my mind once again, and wanted to stop the script in the screen, and just remove the drive and rebuild parity. I was unsure of how to close the script from within screen, and wrongly assumed if I killed the screen, the script would stop. I went to power down the server, to remove the drive, and the GUI froze after stopping some services, but the system never powered down. The screen I started the script in is now gone, killed. I am no longer able to access the web GUI, although UnMenu is still working, and shows activity still going. I can see the write number increasing for both the drive I am removing, and the parity drive ~ 680,000,000,000. Additionally, I see the read number increasing for all other drives in the array. (reconstruct write was turned on), and all my shares are still available. I started all of this approximately 60 hours ago. I was planning to just let things run, and thought the script may still complete itself, and hoping the system "might" just power itself down after. Is there a simple, or "safe" way to stop all of this? Or is my best option to let this continue for now? I assume the script will not be "complete" until the write number approaches 2,000,000,000,000 which could take close to another 5 days? I can attach a syslog from diagnostics when I get home, if that will help.

I was hoping this would be a quick one to track down... Each stick has passed a solo memtest for aprox 36 hours and 25 passes in slot 1 on the motherboard. Guess my next step is to try them in slot 3 the other slot that was originally occupied. Luckily I had enough hardware to throw together a temporary server while I deal with this. Although I am running out of drive capacity, and not enough space in the other case to accommodate the drive I was originally trying to preclear... ticktock, ticktock

Quick update. The continuous preclear I was running from the motherboard SATA failed. After running flawlessly for 2 days. Memtest again, and if finally failed after 4 passes. Right now I am testing the dimms one at a time. First one has completed 11 passes in 16 hours without issues... think I will let it go for about 36-48 before testing the second dimm. Good call trurl, thanks for the heads up on this one!

Thanks trurl, my thoughts exactly. I plan to continually preclear the drive off the motherboard SATA until my new cable arrives this week. Then do a 3 cycle preclear with the new cable if possible. If I am able to get good results on all of those preclears, I will feel confident that the original cable was the issue.

Using the motherboard SATA port the drive precleared perfectly. Going to grab another cable for the controller card, and retest.

Failed to preclear again... Ran another memtest as a precaution... good again. I am currently moving this drive off the Controller card (this was the first drive on my second SAS-SATA cable), and trying to use a motherboard SATA port instead.

I've got an LSI branded 9240-8i that I have previously flashed to 9211-8i p12 if I remember. If i am looking to update to a newer firmware, is there a preferred firmware version, and which procedure should I follow with a card that hass already been cross-flashed?

No issues with memtest. Ran 2 cycles. Looked like my SATA cable into the drive cage may not have been seated fully. I reseated everything from RAM to SATA controller card to SATA connections. Restarted my preclear... and crossed my fingers. Will post back results.

Got a new WD 4TB Red WD40EFRX connected through an LSI Controller. Pre SMART test (short) looked good. Tried to use the preclear plugin for the first time. Preclear failed on post-read. Here is the log the plugin uploaded. "Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 2 --cycles 3 --no-prompt /dev/sdf Preclear Disk Version: 0.8.4-beta S.M.A.R.T. info type: default S.M.A.R.T. attrs type: default Pre-Read: dd if=/dev/sdf of=/dev/null bs=2097152 iflag=direct Pre-Read: dd pid [20863] Pre-Read: dd - read 4000787030016 of 4000787030016. : 0 Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct Zeroing: dd pid [5328] Zeroing: dd - wrote 4000784932864 of 4000787030016. Zeroing: dd command failed, exit code: 1 Post-Read: dd if=/dev/sdf bs=512 count=4096 skip=1 iflag=direct Post-Read: dd pid [16018] Post-Read: dd if=/dev/sdf bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdf/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdf/cmp_out Post-Read: dd pid [16053] Post-Read: dd - read 634730315776 of 4000787030016. Zeroing: 1 Post-Read: fail - disk not zeroed" I noticed the pre-read, zeroing and post read numbers do not match. Pre-Read: dd - read 4000787030016 of 4000787030016. Zeroing: dd - wrote 4000784932864 of 4000787030016. Post-Read: dd - read 634730315776 of 4000787030016. I ran another SMART test (extended) and the results look good. After the extended test, I uninstalled the preclear plugin, and reinstalled it. Started another preclear using the plugin this morning. With the smart tests still showing good, I am thinking this drive is fine. If the preclear plugin fails again, I will probably try through the console as I've done in the past. I am not really familiar with the logs, and am not sure how to interpret the results. Any insight would be greatly appreciated. Thanks

Is there a proper procedure to update the Unifi docker, and retain all current configuration? If not, I may just leave well enough alone

I had some errors on one of my drives recently added into my array http://lime-technology.com/forum/index.php?topic=20934.0 . The attached is the preclear report from the drive I intend to use as my replacement. preclear_start__WD-WCAV56059030_2012-06-21.txt preclear_finish__WD-WCAV56059030_2012-06-21.txt preclear_rpt__WD-WCAV56059030_2012-06-21.txt

Thanks for taking a look Joe!!

New to unraid and not quite sure how to interpret these results. Hoping someone "in the know" could take a peek. preclear_results.txt