Two drives in "Unassigned Devices" that have "Array" grayed out

[ZiRiuS]

Hello there nice folks at Unraid.

 

I have a problem that started when I replaced one of my drives without removing the old one from the array first. I of course turned everything off and all, but I should have done things differently. But when I did that two drives started acting out and I couldn't mount them back on and they had errors and hazzle and xfs_repair did nothing. I suspect it was some kind of conflict from the other drive. After some googling I saw a post where someone just made a new config, figuring I didn't have anything to lose I just did it. That didn't really do anything so I'm going to you guys with this. I have diagnostics from after the new config, maybe that can shed some light?

 

Thank you so much guys.

 

cybertron-diagnostics-20220714-1804.zip

[dlandon]

The gray 'Array' showing on the UD disks is because Unraid does not recognize them as Unassigned Disks.  Try clicking on the double arrows in the upper right of the UD page.  That will tell Unraid to re-evaluate Unassigned Disks.

[ZiRiuS]

8 hours ago, dlandon said:

The gray 'Array' showing on the UD disks is because Unraid does not recognize them as Unassigned Disks.  Try clicking on the double arrows in the upper right of the UD page.  That will tell Unraid to re-evaluate Unassigned Disks.

 

I tried to press the refresh arrows like you suggested but it only said "Success" but nothing happened.

I just finished the parity check and I restarted the server (tried the arrow refresh thing again, still nothing). It booted up with the array offline and it looked like this:

But when I tried to add them to the array they became like this again:

I checked the logs on the disks and this is what comes up on the top one:

Quote

Jul 15 08:25:25 Cybertron kernel: ata3: EH complete
Jul 15 08:25:25 Cybertron emhttpd: error: ckmbr, 2274: Input/output error (5): read: /dev/sdd
Jul 15 08:25:25 Cybertron kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 15 08:25:25 Cybertron kernel: ata3.00: irq_stat 0x40000001
Jul 15 08:25:25 Cybertron kernel: ata3.00: failed command: READ DMA
Jul 15 08:25:25 Cybertron kernel: ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 26 dma 4096 in
Jul 15 08:25:25 Cybertron kernel: ata3.00: status: { DRDY SENSE ERR }
Jul 15 08:25:25 Cybertron kernel: ata3.00: error: { ABRT }
Jul 15 08:25:25 Cybertron kernel: ata3.00: configured for UDMA/133 (device error ignored)
Jul 15 08:25:25 Cybertron kernel: sd 3:0:0:0: [sdd] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jul 15 08:25:25 Cybertron kernel: sd 3:0:0:0: [sdd] tag#26 Sense Key : 0x5 [current]
Jul 15 08:25:25 Cybertron kernel: sd 3:0:0:0: [sdd] tag#26 ASC=0x21 ASCQ=0x4
Jul 15 08:25:25 Cybertron kernel: sd 3:0:0:0: [sdd] tag#26 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Jul 15 08:25:25 Cybertron kernel: blk_update_request: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul 15 08:25:25 Cybertron kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Jul 15 08:25:25 Cybertron kernel: ata3: EH complete
Jul 15 08:25:25 Cybertron emhttpd: read SMART /dev/sdd

The bottom one:

Quote

Jul 15 08:25:25 Cybertron kernel: ata5: EH complete
Jul 15 08:25:25 Cybertron emhttpd: error: ckmbr, 2274: Input/output error (5): read: /dev/sde
Jul 15 08:25:25 Cybertron kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 15 08:25:25 Cybertron kernel: ata5.00: irq_stat 0x40000001
Jul 15 08:25:25 Cybertron kernel: ata5.00: failed command: READ DMA
Jul 15 08:25:25 Cybertron kernel: ata5.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 9 dma 4096 in
Jul 15 08:25:25 Cybertron kernel: ata5.00: status: { DRDY SENSE ERR }
Jul 15 08:25:25 Cybertron kernel: ata5.00: error: { ABRT }
Jul 15 08:25:25 Cybertron kernel: ata5.00: configured for UDMA/133 (device error ignored)
Jul 15 08:25:25 Cybertron kernel: sd 5:0:0:0: [sde] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jul 15 08:25:25 Cybertron kernel: sd 5:0:0:0: [sde] tag#9 Sense Key : 0x5 [current]
Jul 15 08:25:25 Cybertron kernel: sd 5:0:0:0: [sde] tag#9 ASC=0x21 ASCQ=0x4
Jul 15 08:25:25 Cybertron kernel: sd 5:0:0:0: [sde] tag#9 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Jul 15 08:25:25 Cybertron kernel: blk_update_request: I/O error, dev sde, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul 15 08:25:25 Cybertron kernel: Buffer I/O error on dev sde, logical block 0, async page read
Jul 15 08:25:25 Cybertron kernel: ata5: EH complete
Jul 15 08:25:25 Cybertron emhttpd: read SMART /dev/sde

 

Any ideas what's going on?

[JorgeB]

Looks like the disks are bad, they don't even give a valid SMART report, try swapping the cables with two other disks just to make sure but doubt it will help.

[ZiRiuS]

16 minutes ago, JorgeB said:

Looks like the disks are bad, they don't even give a valid SMART report, try swapping the cables with two other disks just to make sure but doubt it will help.

I will try it when I get off work. I have a SATA PCI-E card connected but I don't remember what disks are connected to it, could that have anything to do with this?

[JorgeB]

Both are connected to the onboard SATA ports.

[ZiRiuS]

1 hour ago, JorgeB said:

Both are connected to the onboard SATA ports.

 

I had one of the drives act up like that before and I just formatted it and it was fine after that. I just thought this was some conflict or something.