chrishorton7

Are you able to walk me through the steps here so I don't royally fuck anything up? For example when I go to New Config - what do I select in preserve current assignments? Should I disconnect completely the two drives that are showing in the unassigned list, or leave these connected? I have two brand new drives that have arrived that I am going to use once I've got this back into shape - 1 will be parity, the other a data drive - do I run through the new config, get all other ok disks running with no parity set, then add the two new drives and set one as parity?

Interesting thing just happened - I reconnected all drives and booted up with the intention to look at the new config. When booting the same two drives (Parity & Disk2) were showing as unassigned - I have removed Disk8 physically from the server as the clicking sounds definitely dont sound right to me. This time though Disk5 was showing in the unassigned list with grey Array box. I then tested the power splitter to the HD which was fine, and experimented by swapping to a different spare sata splitter end - I think I tried two or three different power ends and then the disk showed up fine as Disk5. Before I do the new config, could this potentially point to a different issue than the disks failing? I have ordered all new SATA cables which will be here tomorrow just incase any of those are at fault - so will try all new cables across all drives and boot it up, but now wondering whether it could be something with the splitter cables of PSU? It is a Seasonic Focus GX-750 Modular PSU and I have 4x RB55 cables (6 pin Module to PSU and 4 power cables on it).

So any advice on how I would look to try and rebuild & try and retain as much data as possible given I have: Parity - 16TB - Potentially failed Disk 1 - 16TB - Ok Disk 2 - 16TB - Potentially failed Disk 3 - 16TB - Ok Disk 4 - 6TB - OK Disk 5 - 6TB - Ok Disk 6 - 6TB - Ok Disk 7 - 6TB - Ok Disk 8 - 6TB - Potentially failed - the device that was making clicking sounds and slowing boot etc

ok - maybe I'm clutching at straws here but struggling to understand how 3 drives would just fail overnight. Before I panic and spend a load to buy new drives - any suggestions on anything I can do to try and retain the data?

From a quick google of some of the errors I've seen recommendations to run smartctl -a /dev/sd[x] which I have done, I am getting the following: === START OF INFORMATION SECTION === Model Family: Seagate Exos X16 Device Model: ST16000NM001G-2KK103 Serial Number: ZL2KGVCC LU WWN Device Id: 5 000c50 0dbe4c3e2 Firmware Version: SN03 User Capacity: 16,000,900,661,248 bytes [16.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.3/5601 ATA Version is: ACS-4 (minor revision not indicated) SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Dec 7 13:31:58 2024 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled Read SMART Data failed: scsi error badly formed scsi parameters === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error badly formed scsi parameters SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Log Directory failed: scsi error badly formed scsi parameters Read SMART Error Log failed: scsi error badly formed scsi parameters Read SMART Self-test Log failed: scsi error badly formed scsi parameters Selective Self-tests/Logging not supported The above only provides legacy SMART information - try 'smartctl -x' for more

Have tried swapping power and sata cables around on a drive that is showing correctly with the drives that are showing in the unassigned disk devices with grey array box. Same result whether I do this via hot swap or with a full reboot. The device still shows up in the unassigned disk devices section - the disk that was working correctly before is shown as missing. So it seems to correctly identify the disk whatever power cable or SATA cable i use - but for Parity and Disk2 whenever it finds them (whatever power cable or SATA cable I seem to use) it shows as unassigned disk devices with grey array box. I only just noticed the disk log information icon next to the drive in the unassigned disk devices, when selecting this I get: Dec 7 13:24:33 Tower2 kernel: ata5: SATA max UDMA/133 abar m2048@0x51739000 port 0x51739300 irq 131 Dec 7 13:24:33 Tower2 kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 7 13:24:33 Tower2 kernel: ata5.00: ATA-11: ST16000NM001G-2KK103, SN03, max UDMA/133 Dec 7 13:24:33 Tower2 kernel: ata5.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 7 13:24:33 Tower2 kernel: ata5.00: Features: NCQ-sndrcv Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] 4096-byte physical blocks Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] Write Protect is off Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] Preferred minimum I/O size 4096 bytes Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:88:00:00:00/00:00:00:00:00/40 tag 17 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:30:00:00:00/00:00:00:00:00/40 tag 6 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:a0:00:00:00/00:00:00:00:00/40 tag 20 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: sdd: unable to read partition table Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] Attached SCSI disk Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:30:80:ff:bf/00:00:46:07:00/40 tag 6 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#6 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:a8:80:ff:bf/00:00:46:07:00/40 tag 21 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:90:80:ff:bf/00:00:46:07:00/40 tag 18 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:33 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 Sense Key : 0x3 [current] Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 ASC=0x11 ASCQ=0x4 Dec 7 13:24:33 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:33 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:24:33 Tower2 kernel: ata5: EH complete Dec 7 13:24:33 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0 Dec 7 13:24:33 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:33 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:33 Tower2 kernel: ata5.00: cmd 60/08:b8:80:ff:bf/00:00:46:07:00/40 tag 23 ncq dma 4096 in Dec 7 13:24:33 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:33 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:34 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 Sense Key : 0x3 [current] Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 ASC=0x11 ASCQ=0x4 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:34 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:34 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:24:34 Tower2 kernel: ata5: EH complete Dec 7 13:24:34 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0 Dec 7 13:24:34 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:34 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:34 Tower2 kernel: ata5.00: cmd 60/08:98:80:ff:bf/00:00:46:07:00/40 tag 19 ncq dma 4096 in Dec 7 13:24:34 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:34 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:34 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#19 Sense Key : 0x3 [current] Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#19 ASC=0x11 ASCQ=0x4 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#19 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:34 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:24:34 Tower2 kernel: ata5: EH complete Dec 7 13:24:34 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0 Dec 7 13:24:34 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:34 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:34 Tower2 kernel: ata5.00: cmd 60/08:a8:80:ff:bf/00:00:46:07:00/40 tag 21 ncq dma 4096 in Dec 7 13:24:34 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:34 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:34 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 Sense Key : 0x3 [current] Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 ASC=0x11 ASCQ=0x4 Dec 7 13:24:34 Tower2 kernel: sd 5:0:0:0: [sdd] tag#21 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:24:34 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:34 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:24:34 Tower2 kernel: ata5: EH complete Dec 7 13:24:49 Tower2 wsdd2[1385]: starting. Dec 7 13:24:56 Tower2 emhttpd: ST16000NM001G-2KK103_ZL2KGVCC (sdd) 512 31251759104 Dec 7 13:24:56 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0 Dec 7 13:24:56 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:56 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:56 Tower2 kernel: ata5.00: cmd 60/20:a0:00:00:00/00:00:00:00:00/40 tag 20 ncq dma 16384 in Dec 7 13:24:56 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:56 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:56 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 Sense Key : 0x3 [current] Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 ASC=0x11 ASCQ=0x4 Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 Dec 7 13:24:56 Tower2 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Dec 7 13:24:56 Tower2 kernel: ata5: EH complete Dec 7 13:24:56 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x0 Dec 7 13:24:56 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:24:56 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:24:56 Tower2 kernel: ata5.00: cmd 60/08:50:00:00:00/00:00:00:00:00/40 tag 10 ncq dma 4096 in Dec 7 13:24:56 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:24:56 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:24:56 Tower2 emhttpd: error: ckmbr, 2290: Input/output error (5): read: /dev/sdd Dec 7 13:24:56 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#10 Sense Key : 0x3 [current] Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#10 ASC=0x11 ASCQ=0x4 Dec 7 13:24:56 Tower2 kernel: sd 5:0:0:0: [sdd] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Dec 7 13:24:56 Tower2 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:24:56 Tower2 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Dec 7 13:24:56 Tower2 kernel: ata5: EH complete Dec 7 13:24:56 Tower2 emhttpd: read SMART /dev/sdd Dec 7 13:24:56 Tower2 wsdd2[1385]: 'Terminated' signal received. Dec 7 13:24:56 Tower2 wsdd2[1385]: terminating. Dec 7 13:24:59 Tower2 root: /usr/sbin/wsdd2 -d -4 Dec 7 13:24:59 Tower2 wsdd2[5333]: starting. Dec 7 13:25:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0 Dec 7 13:25:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:25:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:25:01 Tower2 kernel: ata5.00: cmd 60/08:90:80:ff:bf/00:00:46:07:00/40 tag 18 ncq dma 4096 in Dec 7 13:25:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:25:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:25:01 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 Sense Key : 0x3 [current] Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 ASC=0x11 ASCQ=0x4 Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:25:01 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:25:01 Tower2 kernel: ata5: EH complete Dec 7 13:25:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x0 Dec 7 13:25:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:25:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:25:01 Tower2 kernel: ata5.00: cmd 60/08:78:80:ff:bf/00:00:46:07:00/40 tag 15 ncq dma 4096 in Dec 7 13:25:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:25:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:25:01 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#15 Sense Key : 0x3 [current] Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#15 ASC=0x11 ASCQ=0x4 Dec 7 13:25:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#15 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:25:01 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:25:01 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:25:01 Tower2 kernel: ata5: EH complete Dec 7 13:26:02 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0 Dec 7 13:26:02 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:26:02 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:26:02 Tower2 kernel: ata5.00: cmd 60/08:a0:80:ff:bf/00:00:46:07:00/40 tag 20 ncq dma 4096 in Dec 7 13:26:02 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:26:02 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:26:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 Sense Key : 0x3 [current] Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 ASC=0x11 ASCQ=0x4 Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#20 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:26:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:26:02 Tower2 kernel: ata5: EH complete Dec 7 13:26:02 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0 Dec 7 13:26:02 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:26:02 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:26:02 Tower2 kernel: ata5.00: cmd 60/08:90:80:ff:bf/00:00:46:07:00/40 tag 18 ncq dma 4096 in Dec 7 13:26:02 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:26:02 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:26:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 Sense Key : 0x3 [current] Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 ASC=0x11 ASCQ=0x4 Dec 7 13:26:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:26:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:26:02 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:26:02 Tower2 kernel: ata5: EH complete Dec 7 13:27:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0 Dec 7 13:27:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:27:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:27:01 Tower2 kernel: ata5.00: cmd 60/08:80:80:ff:bf/00:00:46:07:00/40 tag 16 ncq dma 4096 in Dec 7 13:27:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:27:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:27:01 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:27:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:27:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#16 Sense Key : 0x3 [current] Dec 7 13:27:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#16 ASC=0x11 ASCQ=0x4 Dec 7 13:27:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#16 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:27:01 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:27:01 Tower2 kernel: ata5: EH complete Dec 7 13:27:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0 Dec 7 13:27:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:27:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:27:01 Tower2 kernel: ata5.00: cmd 60/08:40:80:ff:bf/00:00:46:07:00/40 tag 8 ncq dma 4096 in Dec 7 13:27:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:27:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:27:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:27:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:27:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 Sense Key : 0x3 [current] Dec 7 13:27:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 ASC=0x11 ASCQ=0x4 Dec 7 13:27:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:27:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:27:02 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:27:02 Tower2 kernel: ata5: EH complete Dec 7 13:28:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Dec 7 13:28:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:28:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:28:01 Tower2 kernel: ata5.00: cmd 60/08:88:80:ff:bf/00:00:46:07:00/40 tag 17 ncq dma 4096 in Dec 7 13:28:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:28:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:28:01 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 Sense Key : 0x3 [current] Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 ASC=0x11 ASCQ=0x4 Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#17 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:28:01 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:28:01 Tower2 kernel: ata5: EH complete Dec 7 13:28:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0 Dec 7 13:28:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:28:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:28:01 Tower2 kernel: ata5.00: cmd 60/08:40:80:ff:bf/00:00:46:07:00/40 tag 8 ncq dma 4096 in Dec 7 13:28:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:28:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:28:01 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 Sense Key : 0x3 [current] Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 ASC=0x11 ASCQ=0x4 Dec 7 13:28:01 Tower2 kernel: sd 5:0:0:0: [sdd] tag#8 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:28:01 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:28:01 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:28:01 Tower2 kernel: ata5: EH complete Dec 7 13:29:02 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0 Dec 7 13:29:02 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:29:02 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:29:02 Tower2 kernel: ata5.00: cmd 60/08:90:80:ff:bf/00:00:46:07:00/40 tag 18 ncq dma 4096 in Dec 7 13:29:02 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:29:02 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:29:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 Sense Key : 0x3 [current] Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 ASC=0x11 ASCQ=0x4 Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#18 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:29:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:29:02 Tower2 kernel: ata5: EH complete Dec 7 13:29:02 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Dec 7 13:29:02 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:29:02 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:29:02 Tower2 kernel: ata5.00: cmd 60/08:00:80:ff:bf/00:00:46:07:00/40 tag 0 ncq dma 4096 in Dec 7 13:29:02 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:29:02 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:29:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x4 Dec 7 13:29:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:29:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:29:02 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:29:02 Tower2 kernel: ata5: EH complete Dec 7 13:30:01 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0 Dec 7 13:30:01 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:30:01 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:30:01 Tower2 kernel: ata5.00: cmd 60/08:b8:80:ff:bf/00:00:46:07:00/40 tag 23 ncq dma 4096 in Dec 7 13:30:01 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:30:01 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:30:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 Sense Key : 0x3 [current] Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 ASC=0x11 ASCQ=0x4 Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#23 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:30:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Dec 7 13:30:02 Tower2 kernel: ata5: EH complete Dec 7 13:30:02 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 Dec 7 13:30:02 Tower2 kernel: ata5.00: irq_stat 0x40000008 Dec 7 13:30:02 Tower2 kernel: ata5.00: failed command: READ FPDMA QUEUED Dec 7 13:30:02 Tower2 kernel: ata5.00: cmd 60/08:08:80:ff:bf/00:00:46:07:00/40 tag 1 ncq dma 4096 in Dec 7 13:30:02 Tower2 kernel: ata5.00: status: { DRDY SENSE ERR } Dec 7 13:30:02 Tower2 kernel: ata5.00: error: { UNC } Dec 7 13:30:02 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#1 Sense Key : 0x3 [current] Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#1 ASC=0x11 ASCQ=0x4 Dec 7 13:30:02 Tower2 kernel: sd 5:0:0:0: [sdd] tag#1 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00 Dec 7 13:30:02 Tower2 kernel: I/O error, dev sdd, sector 31251758976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 7 13:30:02 Tower2 kernel: Buffer I/O error on dev sdd, logical block 3906469872, async page read Dec 7 13:30:02 Tower2 kernel: ata5: EH complete

ok, *think* I might be getting closer to figuring it out. I wasnt getting one of the drives show up in the BIOS - have unplugged this drive and now the BIOS and Unraid are booting through much quicker (before when that drive was plugged in I was getting lots of clicking sounds etc and it took a while to get to the BIOS setup screen and to load Unraid. So I am guessing that the drive is fault and I will need to replace which is fine. Now though, when I get into Unraid there are still 3 devices showing as missing (2x 16TB HDs - parity & disk2 and 1x 6TB HD - disk8 - the suspected faulty one). Parity and disk 2 drives are showing in the Unassigned Disk Devices section with a grey box with Array written in it. I'm unable to reselect these devices to assign them to the correct locations (Parity, Disk2). I haven't changed the order of Sata slots when investigating this, so not sure why this is. Attaching a screenshot of the GUI for reference

All of a sudden last night my Unraid server went offline. I rebooted it and now when it loads into OS there are 3 disks missing. Diagnostics attached incase any one can get any clues from this tower2-diagnostics-20241206-1937.zip

still getting the same issue despite limiting the Plex docker to 8GB RAM (see attached diagnostics) tower2-diagnostics-20231130-1129.zip

sorry I completely missed the field, I see it now - have updated, will see if this resolves the issue tomorrow morning

I do not see the Extra Parameters field in my docker - I notice that you are using binhex - I am using Hotio docker. There is a field titled additional requirements??

after adding the extra paramater to the docker container yesterday I had the same issue this morning with the OOM error (see attached diagnostics and screenshot of the extra parameter settings tower2-diagnostics-20231129-1225.zip

The logins right before the OOM are a mystery to me as they are at 4am or 6am so I would have been asleep - looking at the IP address on my router it appears to be an Apple device - I'm not sure which device, but unclear why an Apple device is logging in at that time?? stupid question - how do you limit a container to a certain amount of RAM? For reference I am using Hotio docker container

They are scheduled to start at 2am and finish at 5am

As per title, over the last few days I've started to get some out of memory errors on my machine. I have 32GB RAM and never had any issues previously (this unraid build is just over a year old). Hoping someone with deeper knowledge might be able to shine a bit more light reviewing the diagnostics tower2-diagnostics-20231127-2053.zip

Ok as an update, I have started with a fresh install of Unraid on the USB stick and copied over the following files: -disk.cfg -docker.cfg -ident.cfg -super.dat -share.cfg -config/psswd -config/shadow -config/smbpasswd -Docker templates from plugin folder Everything appears to be working now, so must have been one of the plugins, I am guessing unless anyone can shed any further light (would be good to understand what caused the issue). What doesnt add up for me is that I tried running in safe mode without the plugins originally and it was still having the same issue which made me think it wasnt a plugin issue. Anyway, I am going to try installing each of the plugins one by one and testing which may help identify the cause

Ok so tested something this morning. 1 - I formatted the usb drive and copied over clean install of Unraid and then copied entire config folder - same result with unable to connect error 2 - I re-formatted the usb drive to a clean install of Unraid (not copying over anything from my backup config folder) and was able to load the GUI when booting that, so that confirms to me theres not an issue at the router or cabling etc. Question though, what files do I need to copy over from the config folder to retain shares, disk order, dockers etc - happy to reinstall plugins etc if required, but ideally don't want to have to redo shares or docker. Note that I am still currently on a trial licence (was just about to purchase the full licence)

Yep no change following removing dynamix.unraid.net.plg plugin Is anyone able to suggest anything following read through of the latest diagnostics I posted?

Have tried leaving it a good 45 mins and no change, updated diagnostics attached. I have then removed the dnamix.unraid.net.plg plugin and started into GUI mode - initially getting the same 'unable to connect' error - but will leave it a few mins and report back. Hopefully the updated diagnostics might help shine light tower2.0-diagnostics-20211204-1559.zip

Hi, I have recently been building a new server. Everything has been fine for last week or so, last night though I shutdown unraid to install a new hard drive. Upon reboot I am unable to access the Unraid GUI remotely via the IP or directly on the server in GUI mode. I am getting an error of localhost unable to connect. As far as I'm aware no settings have been adjusted to have impacted this, and server has been running fine until this reboot. A few things to note: - Cable - have double checked that the cable (directly connected to router) is working fine on other devices - Static IP - I have a static IP setup for the server within my router - I have tested removing this and let it dynamically get its own IP address but still same end result - I am able to access the terminal fine and login via root account - I have also tested pinging the servers IP from another machine and all seems fine - I have noticed that on boots through all my testing an IPv4 address is assigned but for IPv6 I get 'address not set' - I can't remember if that is typical or not -USB thumb drive is a Samsung Bar Plus USB 3.1 Flash Drive 32GB (as recommended by SpaceInvaderOne) - again have had no issues with this for last month while getting this server running -the USB drive has been to date in a USB 3 slot and running fine, I have also tested this in a USB 2 slot and same results -The motherboard BIOS is set to boot legacy, I have also tried to boot UEFI and same result Diagnostics are attached. Hoping this is something fairly simple - I've seen a few people mention in threads to remove the network.cfg and network-rules.cfg files from the usb drive - I have tried this but same result. tower2.0-diagnostics-20211204-1009.zip

ok thanks, I guess I am looking more for best performance rather than redundancy - as will be looking to use the appdata backup plugin and dont use VMs. From my limited reading atomic moves seems to be good way to go performance wise - but as far as I can tell I would be using 2 NVMEs in a pool with redundancy or what I had originally planned (before learning about atomic moves) was to use 1 NVME drive for appdata and 1 for Downloads. Trying to understand which is going to bring best performance in terms of tv/movie downloads from usenet which is primary use for the server

Was running latest version but really hadn’t done much to the server in all that time so just had a standard ssd (non nvme) as a single cache. Have just built brand new server and have 2x 500gb samsung nvmes and trying to work out how best to setup the whole new thing. I don’t use vms- could in the future possibly - but it’s solely used for Plex/sonarr/Radarr etc

Thanks, guess what I’m trying to understand is pros and cons of either using the two 500gb nvme drives I have as one pool as you have with atomic moves guide or to use each separate with one for appdata and one for downloads

That does help but apologies for follow up questions as although I've ran unraid for 10 years, its been a simple setup with 1 cache before atomic moves was talked about. I'm just setting up brand new server so hoping to try and get as optimal as possible. When you say the 2 drives installed as a cache in RAID configuration, do you mean in Unraid you added the 2 NVME drives as a single pool?