steelrat

Thank you - that solved the issue 👍 Wanted to add the Drive as a pass through for testing and had not thought about the fact, that it was an old cache disk... best regards

Here's the output @JorgeB - thank you for taking the time to look into this. Label: none uuid: 798fccc9-4a1e-418e-85e0-2604502228a3 Total devices 1 FS bytes used 340.00KiB devid 1 size 20.00GiB used 536.00MiB path /dev/loop2 Label: none uuid: 8e6e94bd-7ef0-4028-b032-b5b8adc15c8e Total devices 1 FS bytes used 412.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 Label: none uuid: 4eba87b2-c286-475c-8d30-08f41b74e75c Total devices 2 FS bytes used 602.34GiB devid 1 size 465.76GiB used 97.00GiB path /dev/sdh1 devid 2 size 931.51GiB used 662.03GiB path /dev/sde1 devid 3 size 931.51GiB used 662.03GiB path /dev/sdb1

Is there anything I can look for myself in the diagnostic logs? The 2 Cache Drives are supposed to be btrfs in raid 1 if that helps.

After downsizing my main Array and described by SpaceInvaderOne here (New Config > Preserve current assignments: all > then removing the device I didn't need anymore) I now get the error "unmountable: no pool uuid" on the cache drives. To be clear - I did not change the cache drives in that process. Any Ideas what happened here? The array is fine and all the data is there - it's just the cache that has issues... Best regards and a happy new year! primogenitus-diagnostics-20230101-1941.zip