My little unraid box went down last night. I'm pretty sure this was duer to overheating as its been insanely hot (for us!) here in the UK and the little guy couldn't take it.

Eitherway, after improving my cooling I went about starting up the array and found that the parity needed to be resynced. I set it off and noticed a rediculous estimated time. I then saw the reason, my modest array is made up of four 4TB disks. Three for data and one for parity. However, unraid seems to be indentifying it as 130 PETABYTES.

What have I done wrong and what can I do to avoid spending 26 thousand days waiting for it to sync?

Thanks

Edited August 14, 2025Aug 14 by Blackn
added screen grab

USB not recommended for assigned disks for many reasons.

Please post the diagnostics.

Here are the diagnostics

tower-diagnostics-20250814-1251.zip

The 130PB issue is strange; the parity disk has the wrong size on super.dat, possibly unassigning it, starting the array, reassigning would fix it, but that's not the main issue. The main problem is that the disks are dropping offline:

Aug 14 12:55:48 Tower kernel: usb 2-2: USB disconnect, device number 2

Aug 14 12:55:48 Tower kernel: sd 0:0:0:3: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=161s

Aug 14 12:55:48 Tower kernel: sd 0:0:0:3: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 93 77 f0 00 00 08 00 00 00

Aug 14 12:55:48 Tower kernel: I/O error, dev sdd, sector 9664496 op 0x0:(READ) flags 0x0 phys_seg 256 prio class 0

Aug 14 12:55:48 Tower kernel: md: disk2 read error, sector=9664432

Aug 14 12:55:48 Tower kernel: md: disk2 read error, sector=9664440

Aug 14 12:55:48 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=169s

Aug 14 12:55:48 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 93 77 f0 00 00 08 00 00 00

Aug 14 12:55:48 Tower kernel: I/O error, dev sda, sector 9664496 op 0x0:(READ) flags 0x4000 phys_seg 256 prio class 0

Aug 14 12:55:48 Tower kernel: md: disk1 read error, sector=9664432

Aug 14 12:55:48 Tower kernel: md: disk1 read error, sector=9664440

Aug 14 12:55:48 Tower kernel: sd 0:0:0:2: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=185s

Aug 14 12:55:48 Tower kernel: sd 0:0:0:2: [sdc] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 93 77 f0 00 00 08 00 00 00

Aug 14 12:55:48 Tower kernel: I/O error, dev sdc, sector 9664496 op 0x0:(READ) flags 0x4000 phys_seg 256 prio class 0

Aug 14 12:55:48 Tower kernel: md: disk3 read error, sector=9664432

Aug 14 12:55:48 Tower kernel: md: disk3 read error, sector=9664440

Aug 14 12:55:48 Tower kernel: md: disk3 read error, sector=9664448

You can try a different USB port or cable, but like mentioned, USB is not recommended for array or pool devices, though some bridges can work mostly OK.

4 hours ago, Blackn said:

What have I done wrong

Hate to say it but you're using a USB enclosure to connect your disks to unraid and that is not supported. And now you're finding out why.