philvidler

Thank you so much @trurl this was the answer !!! So happy that this is now working again, thanks again.

For Context, Have now removed the first cache device as errors where showing and moved second drive to first lowering total drives to 1. (also aware disk 1 is showing missing am re-building currently, issues where the same when this was present) Upgraded to 6.9.2 again, Still unable to launch docker service however VM's load and can browse all cache folders etc. Have tried to delete docker image and re-create in different share, still unable to launch docker service. Logs show "mount error" when trying to launch docker service. After deleting docker image, rolling back to 6.8.5 (working configuration) no longer works, as now CA requires 6.9 min am unable to re download docker images! Hope one of you amazing people can help find the solution 🤞

tower-diagnostics-20211106-1842.zip

Hi Just wondering if there's any reason why after updating past 6.8.3 my BTRFS Raid 1 Cache pool is no longer detected? Have tried a few times but on every occasion unraid is unable to see my cache pool and therefore Dockers / VM's etc... Have ended up rolling back after every previous attempt and was happy to leave, however with CA now requiring minimum 6.9.0 looks like I will have to revisit this issue. Not keen to keep trying to upgrade and rolling back, without at least an idea of steps to try and take. Cheers all!

Changed Status to Solved

Thanks so much Squid, this fixed it !! didn't realise I still had it installed, thought I got rid of it a while ago.

Love the new WireGuard plugin Even better if there was a unraid supported Dark Mode

Hi Guys Thanks very much for the quick reply's, sorry for my description its quite late in the evening here! At the start I had 1 parity drive, 1 cache and 4 data drives. Am confident the parity drive was ok did not run a specific test at the time but have had no errors from that drive before. I also remember which drive the parity is and what order they where in. It was the 4th data drive that failed, I got this from webgui before I shut down the system to replace the drive. Like the sound of the new configuration idea and ticking "parity is already valid" was unsure on this before posting after reading: http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily with it stating ..."It should NEVER be used if you have a failed disk or are in the process of replacing a failed disk." Thanks again for your thoughts so far Phil

Hi Hopefully someone here can point me in the right direction. I was previously running 6.1.9 when I updated unraid plugin to 6.2.0. Before getting round to restarting my system one of the array drives failed. Upon exchanging my HDD and returning home I discovered an issue with unraid 6.2.0 where it will not the gui will not start with only a cache drive present and as my array was off line I followed instructions on manually updating my installation (downloading latest release, replace bzimage and bzroot files on usb stick) After following this instruction webgui started great !! However now unraid does not remember my configuration and all drives are coming up as unassigned. This wouldnt be an issue was I not in the middle of replacing a drive however now I am unsure on how to precede and keep the data hopefully using the cache to rebuild the faulty drives data as well. Any help would be really appreciated Phil