dolphinspanker

Thanks to everyone for their help - I think i am on the right path now. Have created the array, with parity - running the parity check now (I'm surprised that it has taken 14 hours, when there is nothing to check - oh well...) Have removed the second drive from the 'Data' pool, and its happy running in single drive mode. This hdd will be removed eventually to join the array. Found an article about turbo write. Once the parity has been setup correctly, will enable this and start sending data to the array directly (not to the cache first). Feel like i am on the right path now. Thanks again.

Hi JorgeB, I have , after much fluffing about, managed to get all my data off the pool drives. Opening up all the directories /locations that i placed data shows nothing there. Consolidated all my data across multiple hdds outside the server. (basically back to where it came from). The external drives with the data show everything located there. And freed up one of the 8tb hdds i have pegged for the array, formatted as xfs. No parity at this stage until i move the pool disks over. So next steps, as far as I can tell. 1 - dismantle the data pool. (2 x 8tb) - No need for this once i setup the array (which is what i meant to do the first time!) 2 - reallocate 1 as parity, and the second as data for the array. This will yield 1 x 8tb as parity, and 2 x 8tb as data. So - I attempt to remove the second hdd from the pool 'data' to force it to single drive mode to let it rebalance, and it throws this error, and wont let me progress. So - Find the instructions to rectify this error - remove a pool and re-add it back. Have done this and now the second drive reports as 'Not installed" I'm starting to think that I should just reallocate the second drive that is reporting as not installed into the array, reformat it as parity, and go from there. The folder structure should appear as available in the array, so I can start to copy data back. campbellot-diagnostics-20260705-1731.zip

I've been trying to understand how the Unraid parity setup is different from a Raid 1 pool. What I am trying to achieve is fairly simple (I think). Place to store data (mostly media) that has redundancy incase a HDD fails. Basically a Plex server at this point. Once I have that setup right, Ill look at other things - one step at a time. Low write speeds are fine, will be using various hdd sizes, but using docker containers to run bits a bobs. Containers at this stage will be Plex and torrent, considering the arr collection, krusader, reverse proxy for remote access, local cloud storage and a family planner of sorts for future use. Looking about, it seems that the UnRaid parity setup would be the best option - hence why I think i have mucked this up. In order to move the data pool I have in place currently over to the Unraid Array, with parity. 1 - move any data I want to keep off the data pool to external location ( currently doing - 4 hours to go) 2 - delete the shares I have created 3 - remove the disks from the pool and add back to the unraoid array, with the biggest disk (8tb) as the parity and anything else as data disks. 4 - recreate the shares, folder structure for media, and repoint Plex to the new media locations. I think thats it. Have I missed anything?

Ive been looking at a few of SpaceINvaderOne videos, its where i found the info that suggested id setup things wrong ! and i thought I had attached my diags above - attached again campbellot-diagnostics-20260705-0904.zip AS for rebalancing, i have attempted to do that several times - by forcing it using the rebalance button in the main menus, plus running scrub also. And i have also let the server sit and run asking nothing from it overnight to let the scheduled rebalance occur. No dice unfortunatly. As you suggest, that data pool is in Raid 1 - that explains why i can still access the data even though its listed as degraded.

HI Folks Have just started off with unraid, and thought I was having success. Created a cache pool (2 x 4tb SSD) Created a data pool (2 x 8tb hdd) was in the process of transferring my media over and found the data transfer speeds slow - looking to speed up if possible found threads talking about removing parity - so i take out my second drive from the data pool. Errors get thrown, and i attempt to revert to two drives in the data pool after I find further info that says you have to pay the parity price at some time - I decide it may as well be now. Have to reinstall the docker containers as everything breaks.... Successfully reinstall docker containers, and get plex running. Data pool, despite my attempts however remains degraded. Further reading indicates that I may have got the setup VERY wrong. Before I pull all my data back off, upset Plex, delete everything and try again. 1 - Can anyone confirm that I have royally mucked up the setup - I don't have parity setup or my data HDDs (data array) in the correct section i think. 2 - Can I recover from here without moving my data back off the server to spare HDDs and without advanced skills/wizardry? At this point I feel that my best option here is to recover my data back off the server onto some spare hdd I have, delete everything, and start again correctly. blergh! campbellot-diagnostics-20260705-0904.zip image of array running image with array stopped