I wanted to have fewer bigger drives on the server, so I swapped some 6/8 TB drive for 16 TB drives.

I swaped them one by one and unraid did the disk rebuild.

Then I used unbalanced plugin to move data from the drives that will be permanty removed.

 

when that was done I made a new config and did not include the 2 drives that will be removed, I also did a parity rebuild.

 

When I came home from work today I saw that disc 3 had a lot of errors, over 1 million..  I decided to stop the parity rebuild, because i saw that no data was written to the parity disc.

 

Then i rebooted the server and unraid was not able to find disc 3

serverlol-diagnostics-20250514-1434.zip

Am i screwed? It was ~9TB data on disc 3

6 minutes ago, lals said:

stop the parity rebuild, because i saw that no data was written to the parity disc.

Single parity can't be built when you have a missing/disabled disk, so that is correct.

 

Check connections, see if you can see the disk in BIOS.

sorry, should have written that I have change around on both the power cable and sata cable.

Bios can see the drive tho.

May 14 14:16:01 serverlol kernel: ata5.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
May 14 14:16:01 serverlol kernel: ata5.00: irq_stat 0x40000008
May 14 14:16:01 serverlol kernel: ata5.00: failed command: READ FPDMA QUEUED
May 14 14:16:01 serverlol kernel: ata5.00: cmd 60/08:28:80:ff:bf/00:00:46:07:00/40 tag 5 ncq dma 4096 in
May 14 14:16:01 serverlol kernel:         res 43/00:08:80:ff:bf/00:00:46:07:00/00 Emask 0x400 (NCQ error) <F>
May 14 14:16:01 serverlol kernel: ata5.00: status: { DRDY SENSE ERR }
May 14 14:16:02 serverlol kernel: ata5.00: configured for UDMA/133
May 14 14:16:02 serverlol kernel: sd 5:0:0:0: [sdd] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
May 14 14:16:02 serverlol kernel: sd 5:0:0:0: [sdd] tag#5 Sense Key : 0xb [current] 
May 14 14:16:02 serverlol kernel: sd 5:0:0:0: [sdd] tag#5 ASC=0x9 ASCQ=0x4 
May 14 14:16:02 serverlol kernel: sd 5:0:0:0: [sdd] tag#5 CDB: opcode=0x88 88 00 00 00 00 07 46 bf ff 80 00 00 00 08 00 00

 

This is detected but failing to identify, if you have already swapped both cables, it's likely a bad disk.

i thought so, was hoping that I could do some voodoo to restore the data on the disc. just ordered a new one now, hope i will get it before the weekend