Turbobuickguy

Thanks a ton, now I can give the DVR service a try!

I am having the same issue some others have had, just wondering if there is something simple I am overlooking. When I attempt to use network storage and click on "NAS install" UNraid does not show as an option. Any ideas?

Thanks for your help Frank. Did a hard reset last night. After a reboot, the parity check started, less than an hour left as I head off to work, and zero errors so far. Everything is looking good!!

No dice, the server continues to run... The console at the server is currently unresponsive. System going to maintenance mode... but it isn't.. Still able to get in with putty though. Anything else to try before a hard reset?

I attempted to use the "powerdown" command when this all started, is "shutdown" different? I'll give it a go when I get home.

Sorry for the re-post, I originally posted this with the plugin support, but this issue is not really a problem with the script. 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 ~ 2,050,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 a week and a half ago. I was planning to just let things run, and thought the script might complete itself, and the system might just power itself down after. Although, the writes to the 2TB drive have now surpassed 2TB, and I am starting to think it is just going to keep going until I get things stopped. Any help getting things stopped is appreciated. tower-diagnostics-20170503-0412.zip

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 must have missed it, they show up as $199 for me.

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?