johnieutah

Well yes, these options have been there since the dawn of time. The original necessity for the powerdown package was it didn't just take care of stopping the array, it closed file handles cleanly, it created a log file etc... All things that I would expect Unraid itself to do. Also, nitpicking, but I want one button. You think I can say to my good lady friend, "um well first you need to click stop array, then make sure the check box is checked..., then you need to click..." (or whatever). Ah forget it, sorry does not work. Why not one button "Shut down server" that does it all?? Why would people argue against this? Also what about the case whereby I can't reach the web UI (which can be quite often). I need to hit the power button on the server itself? - would that cleanly shut down the server were it not for the fact that I have the powerdown script installed? Just saying, I thought with Unraid 6 Limetech were taking steps to make the Web UI a bit more user friendly... Rant over. Although maybe I am in the minority, I only ever start up my Unraid server to a). listen to music b). watch a film c). do a backup. All other times it is shutdown not using any electricity.

What's wrong with the two buttons that are there already? Already there? I'm lost, I don't see any such options on my Unraid 6.0.1 setup. Maybe there has been a recent update and I haven't seen it yet...

THIS. Why not incorporate this? Seems like a worthy addition to me. Been saying the same thing for the seven years I have been using Unraid. I cannot think of any reason why it wouldn't be incorporated, but since it hasn't thus far, there must be some reason. Almost every one new to Unraid will not know about things like "shutting the array down cleanly" etc... why such preventative measures aren't built-in is beyond me. Also @Limetech, whilst you're at it incorporating clean powerdown functionality, pretty please add 2 buttons or a drop-down on the dashboard of the Web UI: Powerdown | Reboot server. Simple. That would be great.

I am having major problems when running this plugin, it seems to kill the Web UI within about 5 minutes. I am still able to access Samba shares and SSH into the server. I originally started a thread here about not being able to access the Web UI during a parity scan: http://lime-technology.com/forum/index.php?topic=40727.0 Long story short, with this plugin completed removed, Unraid 6 Web UI is completely stable. @gfjardim Is there any logging - other than a syslog - I can provide which will aid any debugging? syslog.txt

Update: I removed both plug-ins; powerdown & unassigned devices, as well as disabling docker. All went well, Web UI reacted and performed as one would expect. Added docker back in and a few containers No changes, everything still going great Powerdown reinstalled Again, everything fine after more than a week of playing around and no lock-ups Last couple of days, reinstalled the unassigned devices plugin 5 minutes of navigating various menus, changing some settings etc... and bam, Web UI is down again I see on there are various other users facing Web UI-responsiveness issues on the front page of General Support. How can I provide more debugging / help on this issue?

Cheers. Seems to work well. Not sure how to get back out after finishing up, i.e. do I need to close the connection cleanly somehow or can I just close the tab in IE?

Bump. Would like to know this as well as the value isn't mentioned in the instructions but cannot be removed.

Thanks. Gary once again your presumption is correct Yes, in the future, I will be using the pre-clear script for sure. I had used it before and for whatever reason forgot that the array would be unavailable. Anyhow, I was expecting something around 4-5 hours for a 750GB drive, this looks to be clocking in at 20 or so! One further question: if I want to change disk numbers around afterward, can I do a new config and then use Trust parity? Will that work ok after such a clearing finishes?

So I just added a new drive to my Unraid 6 setup. When I say new, I mean to this server. Previously the drive had been used in an Unraid 5 build, formatted in ReiserFS (of course). So first question is, I was surprised to be told that I need to clear the drive. I'm pretty sure for a couple of the other drives, I didn't need to clear them first. Second question, how slow is the clearing process? (through the web UI, i.e. this is not the pre_clear script running separately from the command line). This 750GB Samsung drive is only 60% through after 13.5 hours... Is this normal? toaster-syslog-20150619-0818.zip

Update on this. I believe the parity check finished so I restarted the server. Everything appeared to be in order, yet after starting to rsync some data back on to the server, the web UI is hanging again. So I guess it must be one of the plugins that is playing up. Either assigned devices or powerdown. Any help appreciated. syslog_2.txt

Ok, thanks. The parity check is still on going, I presume I should wait for this to finish first? And "safe" mode - how do I do that? - I have no monitor attached.

See attached. Web UI still not reachable. Let me know if you need anything else. syslog.zip

Would it not be worth now to start recommending that on v6.0 that the 'diagnostics' command is run as this is no more effort and provides more than just the syslog? It also creates a ZIP file which is convenient for uploading to the forum. He says "webUI is hanging" meaning he probably can't get to that Diagnostics tool. Besides probably the syslog is enough to tell the tale in this case. Correct I can't reach the Web UI at all, either last night or this morning. SSH is no problem.

Will sort this out tonight. I would say in general though, my (limited) experience with Unraid 6 is that the Web UI flakes out a lot more than with 5.

So I started a parity check last night and it immediately became apparent that the Web UI was hanging. It's still running this morning but still no access... Looking around I can runfrom the command line: /root/mdcmd status | egrep "mdResync|mdState|sbSync But from that I have no idea how long is left. Any ideas? @Limetech support: I see I am not the only one with this issue with the Web UI hanging on parity check: http://lime-technology.com/forum/index.php?topic=37442.msg346205#msg346205 & on Unraid 5: http://lime-technology.com/forum/index.php?topic=35539.msg331008#msg331008 http://lime-technology.com/forum/index.php?topic=26989.msg236528#msg236528

Yes sounds about right Oh well, you live and learn.

Ok, that sounds about right. I didn't start the array, so Unraid thinks that it is new and is now computing parity. Makes sense. As for the sync errors corrected, it's basically saying "parity is incorrect, I need to fix it", right?? Edit: one more thing. I have completely lost contact to the web interface, telnet still works. Bloody annoying...

Now getting a load of 'sync error corrected'... hmm something not right with this whole process. I presume the formatting didn't help the cause... Total size: 3 TB Elapsed time: 27 minutes Current position: 44,4 GB (1,5 %) Estimated speed: 28,6 MB/sec Estimated finish: 1 day, 4 hours, 41 minutes Sync errors corrected: 10820680

Ok, that I understand. So in future when I re-insert a drive, which potentially won't have a file system, how do I get Unraid to rebuild from parity? As I looked at the various options and did not see something like "rebuild".

Sure, well the drive was "zero'd" so it had no format. Since I'd already used the drive in the server I would have expected this to be recognised and then asked to recreate data on to it, once the drive had a valid disk format.

Hmm this is funny. I reinstalled the drive in its original slot. Started the server and it states 'disk format unknown' (or something to that effect). So of course I opted to format the drive (which took longer than expected TBH), and now the array is started and parity is valid. I would have expected to be asked if I want to recreate the drive from parity...

Maybe a firmware update on the drive...?!? Thanks for all the help.

It will be missing I guess (I have yet to turn the server back on). So yes, I will do a data rebuild. Here are the exported values from Disk Checkup: *** DiskCheckup V3.3 Build: 1000 Report *** SysInfo DLL Version: SysInfo v1.0 Build: 1090 Time of export: 18:17:57 16-Jun-2015 Device information: Device ID: 1 Interface: USB Device Capacity: 1907726 MB Serial Number: WD-WMAZA1718008 Model Number: WDC WD20EARS-00MVWB0 SMART ATTRIBUTES: ID Description Status Value Worst Threshold Raw Value TEC --------------------------------------------------------------------------------------------------------------------------------------------- 1 Raw Read Error Rate OK 198 197 51 1447 N.A. 3 Spin Up Time OK 242 169 21 2858 N.A. 4 Start/Stop Count OK 99 99 0 1126 N.A. 5 Reallocated Sector Count OK 200 200 140 0 N.A. 7 Seek Error Rate OK 200 200 0 0 N.A. 9 Power On Time OK 97 97 0 2432 N.A. 10 Spin Retry Count OK 100 100 0 0 N.A. 11 Calibration Retry Count OK 100 100 0 0 N.A. 12 Power Cycle Count OK 99 99 0 1000 N.A. 192 Power off Retract Count OK 200 200 0 18 N.A. 193 Load Cycle Count OK 179 179 0 63367 N.A. 194 Temperature OK 119 107 0 31 C N.A. 196 Reallocation Event Count OK 200 200 0 0 N.A. 197 Current Pending Sector Count OK 1 1 0 65535 N.A. 198 Uncorrectable Sector Count OK 200 200 0 0 N.A. 199 UltraDMA CRC Error Count OK 200 200 0 4 N.A. 200 Write Error Count OK 199 199 0 373 N.A.

Ok, results from Passmark attached... Server is literally off most of the time - I only spin it up to make backups, watch a film, listen to music etc... So I can certainly try re-installing it in the array, turn off spin down and see how things are in 24 hours. BTW, what's the best way to go about reinserting this, I guess I let Unraid do a data recreate upon starting the array??

Man they don't make this easy do they?! Will check it again tonight using Passmark. Cheers.