korhojoa

After attaching a file, it looks like typing more into the input, it seems to lose the text sometimes. I edited in the text soon after posting: It looks like the scrub operation fixed the 'errors' by writing the corrupt data from 'sdg1' (the disk with the loose cable) to 'nvme0n1p1', essentially corrupting the valid data. VM disks and docker image are corrupt, so they won't run. Is there a way to get back at least that data from the drive I removed from the pool earlier (Samsung_SSD_870_QVO_2TB_S5RPNF0T615547D)?

kuutio-diagnostics-20260403-1329.zip edit: I don't know what happens to the messages I type. It looks like the scrub operation fixed the 'errors' by writing the corrupt data from 'sdg1' (the disk with the loose cable) to 'nvme0n1p1', essentially corrupting the valid data. VM disks and docker image are corrupt, so they won't run. Is there a way to get back at least that data from the drive I removed from the pool earlier (Samsung_SSD_870_QVO_2TB_S5RPNF0T615547D)?

Scrub complete: UUID: 88139840-0e20-48a6-b8dc-b69dcea7bed9 Scrub started: Thu Apr 2 18:42:40 2026 Status: finished Duration: 0:13:48 Total to scrub: 392.35GiB Rate: 485.23MiB/s Error summary: verify=93024 csum=791170 Corrected: 884194 Uncorrectable: 0 Unverified: 0

Checked the cables, sata cable was slightly unplugged, even though using a cable with locking connector. Here you go. kuutio-diagnostics-20260402-1650.zip

Three things: 1) 'Local TLD' is incorrect according to the plugin. (something in the style of a.example.com) 2) 'Local TLD' is in unraid settings, but that setting seems to also mean 'DNS suffix'/'search domain'. 3) I created an issue https://github.com/unraid/fix.common.problems/issues/5 Just fixing this in 'fix common problems' still leaves the naming which is confusing. TLD and DNS suffix aren't really interchangeable terms. It would be nice if it could be changed to be eg. 'Domain', which would be clearer.

Okay, tried it.kuutio-diagnostics-20260401-1919.zip The cache pool now says (after reimport + start array). Unmountable: unsupported or no filesystem

kuutio-diagnostics-20260401-1650.zip I'm attaching one more diagnostics archive, just because while the btrfs dev remove missing /mnt/cache was running (close to finishing, it exited soon after, exit code 0 though), I was looking at the syslog, and started seeing link drops, timeouts and btrfs errors from one of the cache drives. Am I still OK to reimport (remove, recreate with same name and devices)?

Understood, normal mode: kuutio-diagnostics-20260401-1300.zip

kuutio-diagnostics-20260401-1249.zip edit: Huh, message disappeared. That let the array start.

Here you go: root@kuutio:~# btrfs fi show warning, device 1 is missing Label: none uuid: 88139840-0e20-48a6-b8dc-b69dcea7bed9 Total devices 3 FS bytes used 196.12GiB devid 2 size 894.25GiB used 73.00GiB path /dev/sdg1 devid 3 size 953.87GiB used 132.03GiB path /dev/nvme0n1p1 *** Some devices missingsidenote: isn't that in btrfs-usage.txt?

Hi, I removed one cache drive as it was reporting errors. I tried to add two drives to replace it, but instead of doing so, it seems like there's some unhappy state the pool is stuck in. I can't start the array with them, I can't remove the drives, setting them to 'no device' pops up the same 'Wrong Pool State, cache - invalid expansion' message. kuutio-diagnostics-20260331-2013.zip