July 2, 20224 yr hey guys i have an issue on all my devices that says they are unprotected even though i have ran a parity check and run mover multiple times. i have 2 pariity disks and a ssd for cache that i have now disabled any help would be greatly appreciated. also windows isnt showing my free space correctly on my array. im new to unraid. cheers. tower-diagnostics-20220703-0923.zip
July 2, 20224 yr Author i did have it set to no but have now changed it to prefer and im running mover again.
July 2, 20224 yr Prefer means that you prefer to keep all the data on the cache. When you run mover it will move all data on that share to the cache drive.
July 3, 20224 yr 1 hour ago, hairymongrel said: all my devices that says they are unprotected Instead of "devices" do you actually mean all your shares?
July 3, 20224 yr Having some shares not protected by parity is fine and often done for good reasons. Typically, appdata, domains, system shares will be set to stay on a fast pool (cache), usually SSD(s), instead of on the array, so docker/VM performance won't be impacted by slower parity writes, and so array disks can spin down since these files are always open. Instead of protecting these by parity, you can have a pool configured with 2 disks as btrfs raid1 mirror, so they are protected that way. Or you can have something back them up to the array such as CA Backup plugin. You can have multiple pools, and each pool can have multiple disks if formatted as btrfs. "Cache" is the traditional pool, but you can have more and name them however you want. All pools are part of user shares just as the array is, and each user share has settings to control whether, which, and how it uses a pool.
July 3, 20224 yr Author i just want my data protected by the parity drives. none of my folders are protected at the moment.
July 3, 20224 yr According to your diagnostics the ‘appdata’ and ‘system’ shares have files on the cache. The others look like they exist only on the array. You have the Use Cache=“No” set for these shares that means that new files will not get sent to the cache, but any files already there will be ignored by mover. If you want these files to be moved to the array. disable the docker and vm services under settings. This is required as these services hold files open that means they cannot be moved. change the Use Cache setting for the ‘appdata’ and ‘system’ shares to Yes. ( hint: it is worth reading the help built into the GUI to understand why) manually run mover to get the files transferred to the array. when mover finishes change the Use Cache setting for these shares to No so new files only get written to the array. reenable the docker and VM services under settings. Note that most people DO want these shares on a pool (cache) for performance reasons as having them on the array significantly slows down writes to them, and also keeps array drives spinning. They then either use plugins to periodically backup to the array or make the pool/cache multi-drive so it has built in redundancy.
July 3, 20224 yr 6 hours ago, hairymongrel said: want my data protected by the parity drives Thought I should also add, since you seem so focused on this. Parity is NOT a substitute for backups. You must always have another copy of anything important and irreplaceable.
July 4, 20224 yr Author On 7/3/2022 at 9:34 PM, trurl said: Thought I should also add, since you seem so focused on this. Parity is NOT a substitute for backups. You must always have another copy of anything important and irreplaceable. i dont know why everyone repeats this (everyone knows). yes i have my photo's backed up but it takes a long time to replace my media so if i could just get it parity protected again it would be great.
July 4, 20224 yr 9 minutes ago, hairymongrel said: i dont know why everyone repeats this (everyone knows). We still see sob stories here about people losing files, so obviously not everyone already knows, or if they know they don't do backups, so we repeat it every time someone is in a position that could result in file loss if things don't go perfectly. Parity only helps when a single (or double if 2 parity) drive fails. There are many more common ways to lose data, accidental or malicious deletion, corruption, bad RAM, PSU failure or connection with incorrect modular wires that destroys whole bunches of drives at a time, etc. It's something that needs to be kept at the forefront of data discussions, especially when people erroneously think the biggest risk to their data is something that parity can recover. If you want drive redundancy in place for the faster SSD pool as well as the main parity array, you can add a second SSD of the same size to your pool and convert it to RAID1.
July 6, 20223 yr Author On 7/5/2022 at 7:00 AM, wgstarks said: Or add the photos to a parity protected share on the array. thats why i started this thread i have no parity protected shares..... i have attached a pic to show what i mean. i have ran mover with docker stopped and cache settings changed as suggested above and tried multiple parity checks and still no change. this did happen after i added 2 disks to the array maybe i missed a step ? im unsure. the cache still has files on it that wont copy back to the array (when i run mover nothing happens). is there a way to manually move them ? open to suggestions. cheers. Edited July 6, 20223 yr by hairymongrel added
July 6, 20223 yr Author so do i have it back to front ? i thought selecting cache to yes would fill my cache ssd up ? it seems if i select cache to yes it empties my cache drive. now running mover is emptying my cache drive even though use cache is set to yes...... (very confusing). so that means that because im not running mirrored cache its coming up unprotected. hope this fixes it, fingers crossed.
July 6, 20223 yr 4 hours ago, hairymongrel said: so do i have it back to front ? i thought selecting cache to yes would fill my cache ssd up ? it seems if i select cache to yes it empties my cache drive. now running mover is emptying my cache drive even though use cache is set to yes...... (very confusing). so that means that because im not running mirrored cache its coming up unprotected. hope this fixes it, fingers crossed. The Use Cache setting determines where NEW files are placed. You should read the help built into the GUI to understand the effect of this setting, and how the settings affect mover behavior. If Unraid was starting from scratch then different words might have been used for the values. However this not the case and originally only the Yes/No options existed. Much later the Prefer and Only options were added and by this time it was too late to change the Yes/No options without confusing existing users.
July 6, 20223 yr Author i have removed the cache drive from the machine now. if i add a new share it comes up green.
July 6, 20223 yr 8 minutes ago, hairymongrel said: i have removed the cache drive from the machine now. if i add a new share it comes up green. Right. “Yes” means that new files will be added to the cache and mover will move them to the share the next time it runs. “No” means that new files are added directly to the share and mover isn’t needed. Transfer speeds are possibly slower though.
July 6, 20223 yr 12 hours ago, hairymongrel said: thats why i started this thread i have no parity protected shares..... i have attached a pic to show what i mean. i have ran mover with docker stopped and cache settings changed as suggested above and tried multiple parity checks and still no change. this did happen after i added 2 disks to the array maybe i missed a step ? im unsure. the cache still has files on it that wont copy back to the array (when i run mover nothing happens). is there a way to manually move them ? open to suggestions. cheers. Both the parity drives have red x i.e. no parity protection
July 6, 20223 yr 4 minutes ago, SimonF said: Both the parity drives have red x i.e. no parity protection Checked the earlier diagnostics and you are correct. I missed that when I looked at them and it was not that clear in the screenshots. Until parity is rebuilt there will be no protection.
July 7, 20223 yr Author 13 hours ago, itimpi said: Checked the earlier diagnostics and you are correct. I missed that when I looked at them and it was not that clear in the screenshots. Until parity is rebuilt there will be no protection. so how do i rebuild the parity ? i have ran a few parity checks so i assume its different.
July 7, 20223 yr Solution https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
July 7, 20223 yr Author 24 minutes ago, JorgeB said: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself thanks ! im not sure why it disabled the drives but i have stopped the array removed one parity drive then started the array and reassigned and now it is reconstructing. thanks heaps i owe you big time !
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.