November 3, 2025Nov 3 I did reinstall the vdisk deleting all my previous dockers and installed on just the array - which gave the same issue.Where would I find the drive logs?Thank you for your help.eui.6479a7462f0012ff-2025-06-18 system_cache (nvme1).txteui.6479a7462f000f7e-2025-06-18 system_cache2 (nvme0).txtI cant extract the USB, the filename is to long! Edited November 3, 2025Nov 3 by SmokeyColes
November 3, 2025Nov 3 USB:text error warn system array login Nov 2 15:31:53 CSC-NAS kernel: sd 6:0:0:0: [sda] 60088320 512-byte logical blocks: (30.8 GB/28.7 GiB)Nov 2 15:31:53 CSC-NAS kernel: sd 6:0:0:0: [sda] Write Protect is offNov 2 15:31:53 CSC-NAS kernel: sd 6:0:0:0: [sda] Mode Sense: 43 00 00 00Nov 2 15:31:53 CSC-NAS kernel: sd 6:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUANov 2 15:31:53 CSC-NAS kernel: sda: sda1Nov 2 15:31:53 CSC-NAS kernel: sd 6:0:0:0: [sda] Attached SCSI removable diskNov 2 15:32:42 CSC-NAS emhttpd: online: SanDisk_Ultra_Fit_0101a620f4f6428130f2a6b068fbfd2bc64adf0bb8e1ced8814de91aaa709 (sda) 512 60088320Nov 2 15:32:43 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:32:43 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:32:43 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:32:43 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:32:43 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:32:43 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:32:43 CSC-NAS emhttpd: import 32 flash device: (sda)Nov 2 15:32:43 CSC-NAS emhttpd: read SMART /dev/sdaNov 2 15:32:53 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:32:53 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:32:53 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:32:53 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:32:53 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:32:53 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:32:53 CSC-NAS emhttpd: import 32 flash device: (sda)Nov 2 15:37:31 CSC-NAS emhttpd: read SMART /dev/sdaNov 2 15:37:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:37:44 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:37:44 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:37:44 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:37:44 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:37:44 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:37:44 CSC-NAS emhttpd: import 32 flash device: (sda)Nov 2 15:41:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:41:44 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:41:44 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:41:44 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:41:44 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:41:44 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:41:44 CSC-NAS emhttpd: import 33 flash device: (sda)Nov 2 15:41:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:41:55 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:41:55 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:41:55 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:41:55 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:41:55 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:41:55 CSC-NAS emhttpd: import 33 flash device: (sda)Nov 2 15:42:38 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:42:38 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:42:38 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:42:38 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:42:38 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:42:38 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:42:38 CSC-NAS emhttpd: import 34 flash device: (sda)Nov 2 15:42:56 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:42:56 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:42:56 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:42:56 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:42:56 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:42:56 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:42:56 CSC-NAS emhttpd: import 34 flash device: (sda)Nov 2 15:43:22 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:43:22 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:43:22 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:43:22 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:43:22 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:43:22 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:43:22 CSC-NAS emhttpd: import 34 flash device: (sda)Nov 2 15:43:41 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:43:41 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:43:41 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:43:41 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:43:41 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:43:41 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:43:41 CSC-NAS emhttpd: import 34 flash device: (sda)Nov 2 15:43:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:43:55 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:43:55 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:43:55 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:43:55 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:43:55 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:43:55 CSC-NAS emhttpd: import 34 flash device: (sda)Nov 2 15:44:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/sda 2>&1Nov 2 15:44:55 CSC-NAS emhttpd: disk sda 30765219840Nov 2 15:44:55 CSC-NAS emhttpd: part sda1 2048 30763122688Nov 2 15:44:55 CSC-NAS emhttpd: device sda data partition: sda1 type: dos start: 2048 size: 30042112, code: 0xc (7) Nov 2 15:44:55 CSC-NAS emhttpd: /sbin/blkid /dev/sda1 2>&1Nov 2 15:44:55 CSC-NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="3C15-098F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0328b4fd-01"Nov 2 15:44:55 CSC-NAS emhttpd: import 34 flash device: (sda)
November 3, 2025Nov 3 Nov 2 15:31:53 CSC-NAS kernel: nvme1n1: p1Nov 2 15:31:53 CSC-NAS kernel: BTRFS: device fsid da5398ac-c763-4b3b-aa28-8b396e61ad3f devid 1 transid 2441919 /dev/nvme1n1p1 (259:3) scanned by udevd (1571)Nov 2 15:32:33 CSC-NAS rc.local: SMART: /dev/nvme1n1 ACTIVE (43588cacbe) done in 74ms.Nov 2 15:32:42 CSC-NAS emhttpd: online: Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HT (nvme1n1) 512 1953525168Nov 2 15:32:43 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:32:43 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:32:43 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:32:43 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:32:43 CSC-NAS emhttpd: import 30 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:32:43 CSC-NAS emhttpd: read SMART /dev/nvme1n1Nov 2 15:32:53 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:32:53 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:32:53 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:32:53 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:32:53 CSC-NAS emhttpd: import 30 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:33:01 CSC-NAS emhttpd: #011devid 1 size 931.51GiB used 595.03GiB path /dev/nvme1n1p1Nov 2 15:33:01 CSC-NAS kernel: BTRFS info (device nvme1n1p1): first mount of filesystem da5398ac-c763-4b3b-aa28-8b396e61ad3fNov 2 15:33:01 CSC-NAS kernel: BTRFS info (device nvme1n1p1): using crc32c (crc32c-intel) checksum algorithmNov 2 15:33:02 CSC-NAS kernel: BTRFS info (device nvme1n1p1): enabling ssd optimizationsNov 2 15:33:02 CSC-NAS kernel: BTRFS info (device nvme1n1p1): enabling free space treeNov 2 15:33:02 CSC-NAS kernel: BTRFS info (device nvme1n1p1 state M): turning on async discardNov 2 15:37:31 CSC-NAS emhttpd: read SMART /dev/nvme1n1Nov 2 15:37:44 CSC-NAS kernel: BTRFS info (device nvme1n1p1): last unmount of filesystem da5398ac-c763-4b3b-aa28-8b396e61ad3fNov 2 15:37:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:37:44 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:37:44 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:37:44 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:37:44 CSC-NAS emhttpd: import 30 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:41:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:41:44 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:41:44 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:41:44 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:41:44 CSC-NAS emhttpd: import 30 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:41:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:41:55 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:41:55 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:41:55 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:41:55 CSC-NAS emhttpd: import 30 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:42:38 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:42:38 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:42:38 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:42:38 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:42:38 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:42:56 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:42:56 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:42:56 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:42:56 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:42:56 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:43:22 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:43:22 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:43:22 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:43:22 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:22 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:43:41 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:43:41 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:43:41 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:43:41 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:41 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:43:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:43:55 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:43:55 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:43:55 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:55 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:44:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme1n1 2>&1Nov 2 15:44:55 CSC-NAS emhttpd: disk nvme1n1 1000204886016Nov 2 15:44:55 CSC-NAS emhttpd: part nvme1n1p1 2048 1000203837440Nov 2 15:44:55 CSC-NAS emhttpd: device nvme1n1 data partition: nvme1n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:44:55 CSC-NAS emhttpd: import 31 pool device: (nvme1n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1003HTNov 2 15:44:59 CSC-NAS emhttpd: #011devid 1 size 931.51GiB used 595.03GiB path /dev/nvme1n1p1Nov 2 15:44:59 CSC-NAS kernel: BTRFS info (device nvme1n1p1): first mount of filesystem da5398ac-c763-4b3b-aa28-8b396e61ad3fNov 2 15:44:59 CSC-NAS kernel: BTRFS info (device nvme1n1p1): using crc32c (crc32c-intel) checksum algorithmNov 2 15:45:00 CSC-NAS kernel: BTRFS info (device nvme1n1p1): enabling ssd optimizationsNov 2 15:45:00 CSC-NAS kernel: BTRFS info (device nvme1n1p1): enabling free space treeNov 2 15:45:00 CSC-NAS kernel: BTRFS info (device nvme1n1p1 state M): turning on async discardNVME 2Nov 2 15:31:53 CSC-NAS kernel: nvme0n1: p1Nov 2 15:31:53 CSC-NAS kernel: BTRFS: device fsid da5398ac-c763-4b3b-aa28-8b396e61ad3f devid 2 transid 2441919 /dev/nvme0n1p1 (259:2) scanned by udevd (1556)Nov 2 15:32:33 CSC-NAS rc.local: SMART: /dev/nvme0n1 ACTIVE (6491e21d43) done in 91ms.Nov 2 15:32:42 CSC-NAS emhttpd: online: Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WN (nvme0n1) 512 1953525168Nov 2 15:32:43 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:32:43 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:32:43 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:32:43 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:32:43 CSC-NAS emhttpd: import 31 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:32:43 CSC-NAS emhttpd: read SMART /dev/nvme0n1Nov 2 15:32:53 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:32:53 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:32:53 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:32:53 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:32:53 CSC-NAS emhttpd: import 31 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:33:01 CSC-NAS emhttpd: #011devid 2 size 931.51GiB used 595.03GiB path /dev/nvme0n1p1Nov 2 15:37:31 CSC-NAS emhttpd: read SMART /dev/nvme0n1Nov 2 15:37:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:37:44 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:37:44 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:37:44 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:37:44 CSC-NAS emhttpd: import 31 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:41:44 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:41:44 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:41:44 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:41:44 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:41:44 CSC-NAS emhttpd: import 31 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:41:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:41:55 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:41:55 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:41:55 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:41:55 CSC-NAS emhttpd: import 31 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:42:38 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:42:38 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:42:38 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:42:38 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:42:38 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:42:56 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:42:56 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:42:56 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:42:56 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:42:56 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:43:22 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:43:22 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:43:22 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:43:22 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:22 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:43:41 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:43:41 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:43:41 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:43:41 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:41 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:43:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:43:55 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:43:55 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:43:55 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:43:55 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:44:55 CSC-NAS emhttpd: /bin/lsblk -lnbo TYPE,NAME,START,SIZE,PARTLABEL /dev/nvme0n1 2>&1Nov 2 15:44:55 CSC-NAS emhttpd: disk nvme0n1 1000204886016Nov 2 15:44:55 CSC-NAS emhttpd: part nvme0n1p1 2048 1000203837440Nov 2 15:44:55 CSC-NAS emhttpd: device nvme0n1 data partition: nvme0n1p1 type: dos start: 2048 size: 976761560, code: 0x83 (4) Nov 2 15:44:55 CSC-NAS emhttpd: import 32 pool device: (nvme0n1) Seagate_FireCuda_510_SSD_ZP1000GM30031_7W1002WNNov 2 15:44:59 CSC-NAS emhttpd: #011devid 2 size 931.51GiB used 595.03GiB path /dev/nvme0n1p1Nov 3 19:19:28 CSC-NAS kernel: block nvme0n1: the capability attribute has been deprecated.
November 3, 2025Nov 3 Community Expert This one might require its own forum post to get the right eyes on it. If/When you do please make sure to include the diagnostics
December 5, 2025Dec 5 Hello! I've been having the same problem for over 6 months and still nothing. Everything is on fiber optic, 10GB internet, 1GB full speed, and this slowness only occurs during container updates, very strange. Still no solution. Could someone from support help us with this issue?
December 13, 2025Dec 13 I have the issue too, and it seems all the affecting Docker which are hosted on Github ghcr.io or LinuxServer.io lscr.io (which as far as I know often which often points to ghcr.io too). Could this be the issue - Github?
December 13, 2025Dec 13 3 hours ago, gilladur said:I have the issue too, and it seems all the affecting Docker which are hosted on Github ghcr.io or LinuxServer.io lscr.io (which as far as I know often which often points to ghcr.io too). Could this be the issue - Github?But it only happens sometimes! And for the GitHub part, it is only affected when going through unraid. When using other solutions then the speed is normal
January 9Jan 9 I have the exact same issue since around 6 months. Super slow downloads of different images and the whole GUI goes down to a crawl. Although there is almost no CPU usage at all when checking htop.
January 15Jan 15 Just starting to look for a fix, but I'll also chime in that this is happening to me often, same timeframe of past several months. With me it's intermittent. Today updates are taking forever. Some layers download just fine, others are really slow.
January 28Jan 28 Checking traceroute and mtr to hub.docker.com shows that when my downloads are slow, my whole network is getting a pretty insane amount of packet loss (20-60% loss) from several of the hops, with more than a few timing out entirely. Other threads I've seen about slow docker layer downloads (non-Unraid posts) all seem to be investigating that and getting similar results to mine.I got faster results from a traceroute today and my containers updated very fast. This could be a coincidence, but logically it follows.The non-Unraid posts elsewhere have said this could be an issue with your ISP, something you would have to take up with them. I have not spoken to mine yet but wanted to post this information in case it helped anyone.Are the layers hosted anywhere but Docker Hub? With Github I AM getting a lot of timed out hops and packet loss. It could be depending on where the layer or data is pulled from it is very slow. I don't know enough about the infrastructure to know which are hosted privately.mtr and traceroute to linuxserver.io and github.com are both giving me similar packet loss to what I had earlier when I was checking hub.docker.com so part of the intermittent issue, for me at least, is when it is pulling from multiple sources, each have their own latency (for various reasons).I guess do your own network tests and contact your ISP if you think it will help. I think that is my next step if the slow downloads continue. Edited January 28Jan 28 by ezgoodnight
February 3Feb 3 On 1/28/2026 at 9:45 AM, ezgoodnight said:Are the layers hosted anywhere but Docker Hub? With Github I AM getting a lot of timed out hops and packet loss. It could be depending on where the layer or data is pulled from it is very slow. I don't know enough about the infrastructure to know which are hosted privately.It all depends on the image. Images can be hosted on any number of docker registries of which Docker Hub is the default and most common. The way to tell for a particular image is to look at the image name. The image name format is typically <registry-url>/<namespace>/<image>:<tag> i.e lscr.io/linuxserver/plex:latest. If the image name omits the <registry-url> i.e. linuxserver/plex:latest then the default registry is docker hub. Some other widely used container registries are ghcr.io (Github Container Registry) and quay.io. The linuxserver.io images are special they use lscr.io which is not itself a container registry but rather a redirection services that forwards you to whichever of the big container registries they are currently using. Last i was aware they were by default using ghcr.io, though they also keep images up to date in several registries and may do some sort of failover if on is down.
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.