openam

Every time I delete some and re-run it appears to get worse.

Oh man. I've been deleting them out of /mnt/user instead of /mnt/cache

I was down to just 6, but delete it and ran again, and now it's showing 71. Do I just keep playing whack-a-mole?

You're right, but it says they uncorrectable. Apparently I don't how to read that summary.

It finished the scrub, and didn't find anything I did however see this in the syslog. I'm guessing I might just be able to delete that file? Dec 19 21:59:25 palazzo webGUI: Successful login user root from 10.0.0.127 Dec 19 23:31:36 palazzo monitor: Stop running nchan processes Dec 20 01:41:50 palazzo kernel: BTRFS warning (device sdk1): csum failed root 5 ino 207444295 off 572157952 csum 0x6d807861 expected csum 0xbda7158d mirror 1 Dec 20 01:41:50 palazzo kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 0, flush 0, corrupt 56, gen 0 Dec 20 01:41:50 palazzo shfs: copy_file: /mnt/cache/tv/parents/Show Name/Season 01/Show Name.01x05.Episode Name.mkv /mnt/disk5/tv/parents/Show Name/Season 01/Show Name.01x05.Episode Name.mkv.partial (5) Input/output error Dec 20 01:41:50 palazzo kernel: BTRFS warning (device sdk1): csum failed root 5 ino 207444295 off 572157952 csum 0x6d807861 expected csum 0xbda7158d mirror 1 Dec 20 01:41:50 palazzo kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 0, flush 0, corrupt 57, gen 0 Dec 20 01:41:50 palazzo kernel: BTRFS warning (device sdk1): csum failed root 5 ino 207444295 off 572157952 csum 0x6d807861 expected csum 0xbda7158d mirror 1 Dec 20 01:41:50 palazzo kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 0, flush 0, corrupt 58, gen 0 Dec 20 01:41:50 palazzo kernel: BTRFS warning (device sdk1): csum failed root 5 ino 207444295 off 572157952 csum 0x6d807861 expected csum 0xbda7158d mirror 1 Dec 20 01:41:50 palazzo kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 0, flush 0, corrupt 59, gen 0 Dec 20 01:41:50 palazzo kernel: BTRFS warning (device sdk1): csum failed root 5 ino 207444295 off 572157952 csum 0x6d807861 expected csum 0xbda7158d mirror 1 Dec 20 01:41:50 palazzo kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 0, flush 0, corrupt 60, gen 0 Dec 20 02:20:03 palazzo kernel: PMS LoudnessCmd[971]: segfault at 0 ip 000014ad5e111080 sp 000014ad595240c8 error 4 in libswresample.so.4[14ad5e109000+18000] likely on CPU 6 (core 2, socket 0) Dec 20 02:20:03 palazzo kernel: Code: 01 cf 4c 39 c7 72 e3 c3 cc cc 8d 04 49 48 98 4d 89 c1 49 29 c1 48 63 c2 48 63 c9 49 39 f9 76 75 f2 0f 10 05 02 05 ff ff 66 90 <0f> bf 16 0f 57 c9 f2 0f 2a ca f2 0f 59 c8 f2 0f 11 0f 0f bf 14 06 Dec 20 02:21:36 palazzo kernel: PMS LoudnessCmd[4247]: segfault at 0 ip 000014ef176be080 sp 000014ef120790c8 error 4 in libswresample.so.4[14ef176b6000+18000] likely on CPU 7 (core 3, socket 0) Dec 20 02:21:36 palazzo kernel: Code: 01 cf 4c 39 c7 72 e3 c3 cc cc 8d 04 49 48 98 4d 89 c1 49 29 c1 48 63 c2 48 63 c9 49 39 f9 76 75 f2 0f 10 05 02 05 ff ff 66 90 <0f> bf 16 0f 57 c9 f2 0f 2a ca f2 0f 59 c8 f2 0f 11 0f 0f bf 14 06

What do you mean by a scrub of the cache drive? How do I go about that?

Attached picture of memtest run. Did 4+ passes with 0 error. I have also rebooted and set network to ipvlan. It's running parity check again, because of unclean shutdown. I'm guessing that's because the errors that were present. It looks like some of the errors in the syslog had to do with btrfs. The only btrfs drive I have is the cache drive. Is it possible that there is just something corrupt in the docker.img. Would blowing that away, and rebuilding it be of any use? If so is are there detailed instructions for that?

My docker just stopped working. I did try adding a new docker using the TRaSH guide. Not sure if something I did in there could have caused the problems. There are some BTFRS errors in the syslog Dec 18 03:18:05 palazzo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Dec 18 03:18:05 palazzo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 There was similar issue the other day. I restarted it, and it seemed to be working fine. I think I may try restarting, and disabling the 2 new docker containers from the TRaSH guide. palazzo-diagnostics-20231218-1929.zip palazzo-diagnostics-20231215-1819.zip

Everything is back up and running thanks @JorgeB!

Everything looked good on emulated disk5, rebuild has started, says about 13hrs to complete!

Followed the steps and attaching the new diagnostics palazzo-diagnostics-20231113-1000.zip

Yes disk 3 is still showing as disabled. Disk 3 became disabled on November 7th, earlier in this thread. I haven't really had the array started much since then. palazzo-diagnostics-20231113-0816.zip

The pre-clear has finished, and I was able to find the classic bios mode. Disk 5 is not recognizable by the bios. I found where it showed the disks in the bios, unplugged all the disks and connected disk 5 to P4 on the motherboard. When I booted it back up it didn't see anything except the USB device. What's the best way to save most of the remaining data? I'm half tempted make the assumption that all the disks are fine except disk 5, and say just rebuild disk 5. Does that seem like a crazy solution? Is that even possible? preclear_disk_2EJABBEX_15770.txt

I see this over simplified bios screen. Seems like there used to be a much more standard looking bios screen. I'll play around a little more. I'm currently running a pre-clear on that renewed 8TB drive it's 56% through zeroing right now.

I don't know where to look for it in the bios. It's an old GA-Z97N-WIFI/GA-H97N-WIFI/GA-H97N mobo.

Well I originally just tried a different port on the mini-sas, and it didn't work, but then re-read, and tried plugging into a SATA port on the mobo, and still no go.

I transplanted all the internals to a new case with a new modular PSU, and now I'm missing disk 5. I had a spare unassigned device in a another port that wasn't in the array, so I tried to plug disk 5 into that SATA cable and power cable, but it's still not reading it. Is there anything else I should try to do to see if it'll come back, or I'm I just hosed at this point and need to start over?

Occasionally when I start the computer it starts spinning up, and then just powers down, and restarts. I'm making a wild guess that it's a power / short issue.

I actually bought a whole new case and modular power supply. I wanna get rid of the power splitters. It seems like they may be causing me issues. I might just swap everything over tonight.

Well I stopped the system to add the new devices and run pre-clear on it while I ran check on the parity array, and now it says disk 3 is bad. Should I just power back down, and re-check the cable and power connections again, and retry. palazzo-diagnostics-20231107-1125.zip

So should I just replace disk 3, since it shows it's failing with the seek error rate? Do I need to be worried about the previous "dirty shutdown" (2nd post) palazzo-diagnostics-20231107-0820.zip

I ran the diskspeed docker, and this is what it shows. I guess I'm a bit worried about the wavy ones now 😬.

I assumed this is what that clicking noise was coming from. Do I need to finish the parity check before replacing the drive? This is why I bought that renewed drive.

I don't have `diskspeed docker` installed, and the app store isn't available in safemode. Going to reboot.

Since the speed hasn't increased with stopping Time Machine. Should I go ahead an reboot into normal mode, and run the "diskspeed docker" (I didn't know this was a thing before)? Also disk 3 is showing error now on dashboard. Attaching new diagnostics. palazzo-diagnostics-20231106-1100.zip