veemann

Ah-ha! Makes sense. Thanks for that. V

Ok thanks for the response. That stuff is over my head so if you says that's not unusual, I will take your word for it.

No, your sequence, was my sequence.

I recently cleared, formatted to xfs and added to the array a new WD 8T drive. I just noticed after I started a copy to the new drive that it showed a space usage of 55G. Anyone have any idea how I would have that much disk usage after a 'clear' and format, before I sent data to it? Disk-Clear doesn't actually take up disk space does it? Thanks for the help. V

Thank you JorgeB. V

Thank you for the response. Then drives can be physically removed at any point? Even reformatted to a different file system the drive is still not 'cleared'? Thanks again. V

Good evening, I could use some clarification on the 'Shrink Array' documentation under 'Unraid v6.2 and later' procedures. At what step in the procedure for "The "Remove Drives Then Rebuild Parity" Method" do you physically remove the drives? Secondly, in the "The "Clear Drive Then Remove Drive" Method", if you clear the drive via reformatting, do you still have to run the script? Couldn't you just jump from step 4 to 9? Thank you for the help. V

Ok thanks guys for the guidance. I did a clean install and shuffled the config files around as directions dictate and all is working well. Thanks again. V

Yes, I had looked at it previous. Nothing in particular is standing out.

Did this and stuck on the reboot. Method 1 - using command line Use console or telnet session to log into your unRAID-5 server. Use 'wget' command to fetch the unRAIDServer.plg file: Code: [select] wget --no-check-certificate https://raw.githubusercontent.com/limetech/unRAIDServer/master/unRAIDServer.plg Then perform the upgrade by typing this command: Code: [select] installplg unRAIDServer.plg When upgrade has completed, reboot your server.

I am attempting to upgrade from v5 to v6 via the plugin and everything went well until the reboot. It lands on an 'ERROR: No configuration file found No DEFAULT or UI configuration directive found.' Not sure where to go from here. I checked the bios and the flash is first boot drive, so I am lost now. Help would be appreciated. Thanks, V

Noted. Thank you very much for all your help trurl. It looks like everything is sorted and back to normal. Though I just don't really know what happened to begin with. I will be going through the original disk9 and seeing if I can find anything though I don't expect to. As to the failed replacement, who knows what I'll do with that.... maybe target practice. Thanks again, V

Ok thanks. So ordinarily the monthly checks would be correcting? V After a data disk rebuild is the one time it probably makes sense to do a non-correcting parity check. Then if there are any sync errors parity is still the same and you can decide to rebuild the data disk again.

Disk9 is rebuilt green balled and running. Now I would like to run a parity check as its been a long time since its been clear. Do I initiate with 'write corrections to parity disk' checked or unchecked? Thanks, V

New pre-cleared disk is currently rebuilding. After that is finished my intent is to start a parity check which is exactly the point my last 3 failures have occurred. V