July 30, 2025Jul 30 Reboot > Docker broken > Settings > Docker > [x] delete vdisk file > [Delete] > Enable Docker "No" > [Apply] > Enable Docker "Yes" > [Apply] > "No Docker containers installed" > Apps > Previous apps > Oh don't forget to create the "proxynetwork" > Terminal > docker network create proxynetwork > Previous apps > Docker > Select All on page > Install > Wait... Wait... Wait... (no idea if this can be done in the background?) > Start docker compose stack > Wait > Start another stack > wait > start the last stack > Donesupermicro-diagnostics-20250730-1949.zip Edited July 30, 2025Jul 30 by eXorQue
July 30, 2025Jul 30 Community Expert Jul 30 19:40:30 supermicro kernel: BTRFS info (device sdf1): bdev /dev/nvme0n1p1 errs: wr 644107708, rd 532154023, flush 17285202,The NVMe device has been dropping offline; try adding to syslinux:nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=offThen scrub the pool.
August 1, 2025Aug 1 Author I already have that added to my syslinux.cfg/syslinux/syslinux.cfg```default menu.c32menu title Lime Technology, Inc.prompt 0timeout 50label Unraid OSmenu defaultkernel /bzimageappend initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=offlabel Unraid OS GUI Modekernel /bzimageappend initrd=/bzroot,/bzroot-guilabel Unraid OS Safe Mode (no plugins, no GUI)kernel /bzimageappend initrd=/bzroot unraidsafemodelabel Unraid OS GUI Safe Mode (no plugins)kernel /bzimageappend initrd=/bzroot,/bzroot-gui unraidsafemodelabel Memtest86+kernel /memtest``` Edited August 1, 2025Aug 1 by eXorQue
August 1, 2025Aug 1 Author Scrub completed```UUID: 38dc75e4-1cf6-45cd-bb76-e15d45da80d9 Scrub started: Fri Aug 1 12:13:48 2025 Status: finished Duration: 0:21:02 Total to scrub: 469.60GiB Rate: 381.03MiB/s Error summary: verify=38140 csum=30545648 Corrected: 30583788 Uncorrectable: 0 Unverified: 0```
August 1, 2025Aug 1 Community Expert Recommend recreating the system share with COW set to auto; it's using the old NO default, which also disables checksums and will prevent btrfs from knowing if it's giving the correct data if a device drops and then comes back online.Also recommend resetting the btrfs stats and then enabling the pool monitoring script to get a warning if the device drops again, and if that happens, post new diags immediately.https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582
August 7, 2025Aug 7 Author I will try that. In the mean time I had another issue. Server wasn’t rebooted (at least not by me) and docker failed to start even though it was on before. I’ve taken diagnostics before rebooting supermicro-diagnostics-20250807-1006.zip
August 7, 2025Aug 7 Community Expert Aug 5 04:40:06 supermicro kernel: BTRFS error (device sdf1): error writing primary super block to device 2Aug 5 04:40:06 supermicro kernel: BTRFS warning (device sdf1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)Aug 5 04:40:06 supermicro kernel: BTRFS error (device sdf1): error writing primary super block to device 2Aug 5 04:40:06 supermicro kernel: BTRFS warning (device sdf1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)Aug 5 04:40:06 supermicro kernel: BTRFS error (device sdf1): error writing primary super block to device 2looks like an NVMe device dropped again, cannot see the beginning of the issue since the syslog already rotated.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.