Proffles

Woohoo. All done. thank you

Thank you both for your help. I followed the instructions again, and this time it appears to now be working, i can see a lot of writes on the pool and a BTRFS operation is running. Hopefully it goes smoothly from this point on!

Ok thanks. I clicked the button! It now looks like this: Can I safely attempt the upgrade again now? What is the GlobalReserve "not partition" bit, does that not need to also be RAID1?

Looking at the details page of one of the cache drives, i can see this balance option If i set the dropdown to "Convert to raid1 mode" and click Balance, will this handle it? for all partitions? What about the other cache drive, how does it know what to do with it? Thanks!

Ok, thank you. Evidently I'm not familiar enough with this topic. Reading your reply and trying to understand it in terms of more familiar filesystems, am i correct in thinking that effectively "partitions" are RAID1 instead of whole drives. BTRFS uses some partitions to work properly, and thus all partitions need to be set to RAID1 mode. If this is correct, do you mind helping me understand how to check what partitions there are, what they are currently set to, and how to set them to RAID1 mode? Thank you!

Great! thank you yes now looks like things are back to how they were to begin with. Phew! But now, I am back to how I was to begin with, with the new cache drives waiting to be used. Do you know why following the instructions on this FAQ page did not work? Can you suggest a revised procedure to use, as it seems the one listed is somewhat risky for some reason. Thank you for your help! 🙂 server-diagnostics-20240926-1316.zip

Cheers, this is the output:

okiedokie:

Ok thanks, here:

Reading through this thread, it seems very similar. I am wary of running the commands listed, they seem quite "deep", and i have only a shallow understanding of the underlying systems here. It seems I'm not the only one who has fallen foul of following the instructions ☹️ Fortunately, unlike those people I have not rebooted, so the diagnostics posted maybe can be more helpful?

Also, in case it helps, i ran btrfs fi show I don't know why it says some devices missing. They're both there as far as I can tell. Argh

I have found in my unraid flash drive (a backup taken a while ago) that the pool was indeed raid1, at least according to config/pools/cache.cfg line 3: diskFsProfile="raid1"

In my server I have 2 512gb SSDs, they were running as a cache pool. I was sure it was in RAID1 mode, but TBH I don't know how to check this. I installed 2 new 1tb NVMe drives, intending to use them as a new cache pool. (all 4 drives are installed at the same time). After booting Unraid, cache running as before on the SSD drives, 2 new NVMe drives showing unassigned. So far so good. I proceeded to follow the instructions found here https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#comment-480419 - I stopped the array - I changed Cache 2 drive to point to one of the NVMe drives. - I started the array No sign of any brtfs device replace beginning or any pool activity. The cache is offline, it shows as Unmountable: Unsupported or no file system. The SSD that was removed from the cache shows as unassigned. Hmm. I tried putting things back to how they were. - I stopped the array - I changed Cache 2 device to the now unassigned SSD. - I started the array The cache is still offline, showing as Unmountable: Unsupported or no file system. Following the instruction here https://forums.unraid.net/topic/141562-cache-unmountable-unsupported-or-no-file-system-after-update/?do=findComment&comment=1280258 - I stopped the array - I changed Cache device to no-device - I changed Cache 2 device to no-device - I started the array (checking the no cache warning checkbox) Array starts without any cache, as expected. I then restored it: - I stopped the array - I changed Cache device to the SSD it was set to originally - I changed Cache 2 device to the SSD it was set to originally - I started the array Array starts, cache is still offline, showing as Unmountable: Unsupported or no file system. Please help! At this point I would settle just to have things back to how they were, all my dockers are gone etc. 😢 server-diagnostics-20240925-2007.zip

Ok thank you. But I am not sure that'd be the issue. If anything, overnight it would get less use I would have thought. I'll keep an eye on it I guess

I've had a few issues with my unraid server over the last few days. It ran a normal pairity drive (it was 8TB) check on the 1st of the month, as it does every month. That came back with zero errors. But almost immediately afterwards, the parity drive was marked "disabled" with a red cross, and parity protection was gone. Hmm. I followed instructions to stop the array, remove, start, re-add the parity drive, start. This didn't work, the drive remained disabled. I assumed there was a faulty drive, and ordered a replacement disk. I figured i'd use this time to increase the size of the parity disk, so I ordered a 16tb drive. When that arrived, I put it into the array, and was still having the same problem. In the end after much trial and error, I think the SATA cable was at fault, somehow just reversing it fixed the problem. The new parity drive was picked up and sync restarted without issue. But! It was syncing really slowly. It's been running at only 25mb/sec overnight. See pic 1. I came to post here, so I ran diagnostics export (attached). Then i re-checked the sync status and it's now running at ~200mb/sec. See pic 2. Ok.. good. but why was it slow before? Any ideas what's going on? Thanks! server-diagnostics-20240705-0827.zip

Hello, Just to chime in, I am also occasionally having this issue i think. CPU maxes out (not on all cores), docker containers become unresponsive, memory seems to be all used up. I am just doing a reboot when i notice that it's happened. but obviously this is a crappy workaround. Does anyone have any working solution? Cheers!