JunkoZane

Hi there, unfortunately I'm getting SDE (one of cache pool drives) errors again... If not cable, what else could it be? MB, the drive itself? Thank you in advance the-beast-diagnostics-20230503-2348.zip

I somehow misinterpreted info in that link... Also, it's kind'a strange that after running scrub with "repair corrupted blocks" enabled I got a bunch uncorrectable blocks. But after second time I did same thing - I have cache pool with 0 uncorrectable blocks the-beast-diagnostics-20230418-2152.zip

Does that mean I'll have to reconfigure all my docker containers? If so, could it be possible to use very first drive that I took out of the system (256gb SSD)? Actually I already tried that, but cache pool just displayed error: UNMOUNTABLE: NO POOL UUID

Hi there, "Docker Service failed to start." after changing cables. I'm starting to feel guilty for bothering you... Could yo uplease help me to get my server back ? :) the-beast-diagnostics-20230414-2112.zip

Happy Easter to all who celebrate it Could you please help me out with one more case? Recently I got a warning that my syslog is 100% full, turns out that it got spammed with BTRFS errors... Is it related to my previous problem, or should I change the sata cable that connects sdg to the motherboard? the-beast-diagnostics-20230409-2143.zip

It worked out fine, not sure why I had problems the first two times. Anyways, thank you for your time and help! Appreciate it

the-beast-diagnostics-20230404-1853.zip

I don't understand next step... Yesterday I posted new diags after assigning old (256gb ssd) to be the only cache pool device. Or should I assign the other 256GB ssd?

Here's diags with sdg the-beast-diagnostics-20230403-2229.zip

You're talking about sdg? Yes, my cache pool was raid1 mirrored and consisted 2 * 256gb ssd's

I haven't, unless stopping and starting array has same effect. btrfs-select-super -s 1 /dev/sdg1 warning, device 2 is missing using SB copy 1, bytenr 67108864 I do suspect that problems started at the very beginning when I removed first 256GB drive. Maybe I should try using it as my only cache pool device and later build mirror to my new 1TB SSD from it?

I still have both 256GB drives untouched, maybe first one that I took out would be more helpful? I have stopped the array yesterday and started it today, but no reboot was performed since this error occurred (since I don't know what's happening, I figured I'll better mention it...) Label: none uuid: ad3a33bd-dcf5-4a1a-bdd2-6d499aaecb25 Total devices 2 FS bytes used 2.36TiB devid 1 size 1.82TiB used 1.73TiB path /dev/sdb1 devid 2 size 1.82TiB used 1.73TiB path /dev/sdf1

Hello, again. Same problem occurred when I tried to remove 256GB drive (sdg): 1TB drive shows same error "UNMOUNTABLE: NO FILE SYSTEM" As you mentioned, I attach logs before rebooting the-beast-diagnostics-20230401-2216.zip

Thank you

I'm confused. I did exactly that the first time...

Yes

I have my old cache pool working Should I now set all shares not to use cache pool and invoke mover? Or is there other way to uploading my new magazine of SSD's?

Ofcourse! Label: none uuid: ad3a33bd-dcf5-4a1a-bdd2-6d499aaecb25 Total devices 2 FS bytes used 2.36TiB devid 1 size 1.82TiB used 1.73TiB path /dev/sdb1 devid 2 size 1.82TiB used 1.73TiB path /dev/sdf1 Label: none uuid: 630416da-0948-4846-a062-d6c0b6e30614 Total devices 2 FS bytes used 140.57GiB devid 1 size 238.47GiB used 159.03GiB path /dev/sdg1 *** Some devices missing

No valid Btrfs found on /dev/sde1 ERROR: open ctree failed using SB copy 1, bytenr 67108864

Label: none uuid: ad3a33bd-dcf5-4a1a-bdd2-6d499aaecb25 Total devices 2 FS bytes used 2.36TiB devid 1 size 1.82TiB used 1.73TiB path /dev/sdb1 devid 2 size 1.82TiB used 1.73TiB path /dev/sdf1

Hello fellow unraiders, recently I did a stupid thing. Instead of following any of the guides how to upgrade cache drives I did it the way I imagined it should work... Situation: I have 2x256gb cache ssd's in raid1 configuration. Since I ran out of memory I purchased 2x1tb ssd's I've stoped the array, unassigned one of the cache drives and started the array. Added 1 of new ssd's (1tb) to the cache pool and started the array again. Left it overnight to do its thing. Then stoped the array, unassigned second 256gb ssd from cache pool and started array. Now I have one 1tb cache ssd that has error "Unmountable: No file system" instead of capacity shown. Since all my dockers live in cache, I can't do a thing with my unraid server now. Tried running btrfs rescue zero-log /dev/sde (since 1tb ssd for sure is sde) with no luck: I do have both 256gb ssd's untouched thou. But don't know how to re-add them ( or at least one of them) just to get my server up and running... Any help is much appreciated, Thank you in advance! the-beast-diagnostics-20230321-2028.zip