RobJ

I would not be at all in favor of equating a single small increase in reallocated sectors with drive failure (although it could be for that specific drive model ST3000DM001!). A continuous increase is certainly a bad sign, but not a single small increase. There are thousands more spares available. It's more like a symptom of aging, we're all failing a bit each day that passes, once we pass our teen age years. What I WOULD agree with, after any increase in reallocated sectors or any change (even for the better) in Current Pending sectors and of course any non-zero Current Pending sectors, is a statement that another Preclear or two is recommended. You want to detect whether it's stable now, or continuing to reallocate (which WOULD be bad).

Thank you! I've revised it, would appreciate another review, make sure I got it right! By the way, what rsync command would others use?

Requesting review for accuracy of a simple question, found here.

Thanks! Somehow, I remembered more peaks, less 'double-vision' !

Attached is a copy of an older LimeTech banner. What I would like is a copy of the earlier LimeTech mountain one, Colorado Rockies with lots of snow. Anyone have a copy?

I believe I've seen similar in the Docker world here, make sure your DNS is configured and working. One test is to ping google.com at a command prompt.

Thanks, it works fine for me now.

I can confirm exactly what the others are reporting, and from the very first version of System Buttons. Almost always, the big yellow banner appears immediately, with shutting down or Rebooting, and no pop up, no shutting down, no messages on console, and no messages in syslog. Ctl-Alt-Del then works fine. I didn't report it, as it seemed to be one more time my Firefox with NoScript (everything related is enabled) was mis-behaving. Only once, the popup window appeared, the correct shutting down messages appeared, and it shut down nicely.

If your v5 flash is setup in a standard way, all customizations are in the standard places, then yes, you should be able to upgrade safely using the upgrade plugin.

That's only one of several reasons why it might fail to boot. My recommendation would be to not even try this upgrade, unless you or a trusted representative is present. Reasons it could fail - * needs updated syslinux support [boot stops before unRAID boot menu] (run make_bootable with updated syslinux files) * new kernel selects different network chipset if more than one [no networking, so you're disconnected] (either connect cable to other NIC or disable wrong one) * BIOS changes boot order [no boot, can't find bootable disk (should not happen if flash not removed)] (correct boot order in BIOS settings) * A very few reports that first boot was not successful, so they had to boot a second time, this time successfully [reason unknown] These are all uncommon, with the syslinux update the most likely. I would not attempt it without someone present. I would also keep the Upgrading to UnRAID v6 guide handy, especially the troubleshooting section.

One more thing I'm pretty sure you will have to do is stop and restart the array. The User Shares file system is only created at array start, so a restart is probably needed to pick up the move (I think!).

Which function are you referring to ? Sorry, thought there was function like that available to you, bad assumption on my part. Perhaps the reggierat loop instead, to spin them all up?

bonienl, it might be good to call Tom's function to spin up all drives when waking up, to reset what the system knows about current drive state.

Thank you, bonienl! Much appreciated. I seem to be one of the 'stupid' people who find the current steps 'difficult'. As soon as I found the Confirmations screen, I turned them off, as I don't seem to be as susceptible to clicking the wrong thing as others. But for me, and for others with memory issues, there's a huge chasm between the Stop button and the Power down button, a wait of several minutes (may be shorter for others?), which is way way way too long to remember what you were doing. Especially in a lightning situation, when I need to get to other machines downstairs and can't, and can't remember to keep checking to see if the power down buttons have appeared yet. But we won't rehash that subject again. I'm with trurl on the need to call powerdown instead, if the plugin is installed. And some sort of verification functionality would be nice, for those who need it. To be honest, I'll use the buttons some of the time, but for now still prefer the keyboard powerdown (Ctl-Alt-Del) because it saves the syslog. Except for saving the syslog, the buttons are just as effective for me, because as far as I know I have NEVER had a webGui hang. Makes it hard to commiserate with those having that issue. It's hard to tell how widespread that problem is. My current sense is that between 5% and 30% are experiencing it, a ridiculously inexact number!

The 'unWife' support group?

Yes, I have it disabled. When I enable real-time, then I do see the temps after a varying interval of 5 to 10 seconds (always, even on the Main page). The same 5 pages almost never show the temps immediately, whereas all other pages do.

Seems to happen a bit randomly. I've made a change in the display function and testing it now, so far so good ... Btw the change is in system temp itself not in v6.1 I'm sorry, but I'm not seeing any significant improvement. Just to confirm, the System Temp plugin was updated from 2015.04.28 to 2015.06.27. Is that correct?

Drive looks great!

At first I thought browser refresh fixed that for me, but it seems it just takes a little longer to appear on some pages than it used to. Interesting. When I tried before, I could not get it to show on any of the mentioned pages, except possibly once on the Plugins page, but since I couldn't get it to repeat on the Plugins page, I thought my eyes had fooled me. I tried again now, and it does now show up some of the time on the Dashboard, Plugins, and Docker pages, more of the time on the Stats page, and never yet on the Main page. If it is going to display, it displays immediately, before the rest of the page is complete. If it doesn't appear then, it never shows up. This is a table of 10 or more refreshes on each page, and roughly how many times the temps were displayed. Pages not listed seem to always show the temps. 0/20 Main 2/10 Dashboard 3/10 Plugins 5/10 Stats 4/10 Docker

Stop and restart the array to create a brand new User Shares system, to see if that stops them. Check the full syslog, where the messages begin. You generally only want to see the very beginning of an error condition, not all of the garbage that follows while still in an error state. Perhaps it starts when the Mover last run?

Running the new 6.1-rc1, and the temps are not showing on the Main, Dashboard, Docker, Plugins (neither sub-page), and Stats (neither sub-page). They are showing everywhere else, including all other tabs, sub-tabs, and any drive from the Main page.

Requesting a final review. I've added an Upgrade or Clean Install? section, which could probably be formatted better. Wish I could shorten it. I think the guide is basically done, but I'm sure it can be improved.

It's good, needed. I'm going to steal from it for the new related FAQ entry. I did fix a typo, and while there messed with the formatting and headings. You once commented on all the bullet points. I rarely think of them as bullet points, I think of them as great info organizers, but I've learned I rarely think like normal people do, so I've learned I HAVE to listen to others advice. Do you like the formatting better this way?

No, upgrade straight to the latest v6, referring to the Upgrading to UnRAID v6 guide when necessary. You WILL need to run the New Permissions tool, once you have upgraded.

Thank you!