MrTing

Thanks for this and thank you @Endling , it's working perfectly. I have no idea what these changes do, but it looks like it shouldn't be problematic long term?

Turns out it was a Western Digital pcie Gen 4 drive 😅. Couldn't find an obvious firmware page for it, but I'm hoping the switcharoo worked. I'll report back in a month. ty for all yall help!

Ok turn its out it wasn't growing. BUT, I read this forum, and turns out I also had a Samsung cache drive in the second M.2 slot. Both of the slots are rated at the same speed so I thought it didn't matter, but I didn't even consider the CPU vs Chipset connection being an issue. This HAS to be the issue (I pray).

So it crashed for the first time again since my last message. My docker image is set to 30gb, and I added up the total of what I have, and it is now 31gb, which would explain the crash. Here are the sizes of my images. Seems like torrent/usenet clients and the ARRs are taking the most. Is it the logs or something? I think I remember there being something that I can add to reduce the docker image increasing so much. This may not be the issue though as before I had the docker image size to 50gb, so we shall see.

I remember this happened a long time ago, which I changed my NVMe. It usually crashed when the mover moves, so I'll to try again when I download a lot of stuff. After restoring the config from last week's backup, it hasn't happened yet though.

This is what I've already inputed, is this correct?

With the Appdata Backup plugin. There is an option to backup the flash drive, so I thought maybe the option to restore the config was referring to the config folder in the usb

The syslog before rebooting is there. In the logs folder, it's named syslog-previous.txt

Yes, I restart the server to get it to work again. Eventually it'll crash. Another thing I just did the "restore config" in Back up and Restore. hoping it meant for the flash

I had a power outage the other day and when the power came back, the server didn't recognize the USB. So I reinstalled the USB and replaced the default config folder with the folder that was prior on the USB. The issue keeps occurring, this is what I've tried: Deleted docker image and reinstalled the containers Increased the docker image size, deleted the docker image and reinstalled the containers Added "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" in syslinux.cfg after "append initrd=/bzroot" under the Unraid OS label. I did chkdsk on the USB on windows and it reported no errors. Is the usb corrupted? The errors will be in the syslog-previous diagnostics-20250329-1854.zip

Will report back in 24 hours 🫡

omg, so I did already do this, but i put it under the safemode section. I've now put that under the "unraid os" and "unraid os gui mode" label, for it to look like this: label Unraid OS menu default kernel /bzimage append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Docker has been crashing. Before this was happening randomly but now this has been happening multiple times a day. And it gets fixed when I restart. Things I've tried: Deleting docker image Extended SMART scan on cache - no errors. However when the test finishes, it says "no test logged on disk". Scrubbing BTFRS - no errors found Balancing BTFRS In syslinux.cfg added edit the append part so its "append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off,/bzroot-gui unraidsafemode" Latest big block of errors: Nov 28 18:09:01 Cloud kernel: btrfs_dev_stat_inc_and_print: 38633 callbacks suppressed Nov 28 18:09:01 Cloud kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 57, rd 15445690, flush 0, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: blk_print_req_error: 20328 callbacks suppressed Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 17161070, flush 1, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 57, rd 15445691, flush 0, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 8929080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 17161071, flush 1, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 57, rd 15445692, flush 0, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 17161072, flush 1, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 1576696 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 17161073, flush 1, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 57, rd 15445693, flush 0, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 17161074, flush 1, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 57, rd 15445694, flush 0, corrupt 0, gen 0 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 8929080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 8929080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 28 18:09:01 Cloud kernel: I/O error, dev loop2, sector 5872120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 diagnostics-20241128-1813.zip WD_BLACK_SN770_500GB_241604802919-20241128-1846.txt

After doing that, the writes stopped occurring when the docker was off. When I turned the docker back on, it returned. It was a bit weird, but after going by container by container, I found that it was Nextcloud and Sabnzbd writing logs. And I remembered previously I changed their settings from changing /mnt/cache/appdata/binhex-sabnzbdvpn to /mnt/user/appdata/binhex-sabnzbdvpn, because i read that have it as /mnt/cache isnt proper. So after changing it back to /mnt/cache, all is good. Ty for helping me

Yes. The primary storage for all the shares is the cache, the mover is not running, and the docker is off. So I'm having trouble finding out what is being read & written to the array/parity drive.