Device is Disabled, Contents Emulated

[updatenil]

Hello

 

Woke up to one of my drives reporting that it's disabled and the contents are emulated. I'm relatively new to servers and having such an event.

 

A few days ago I was working inside the computer to install a GPU and I'm not sure if I could have knocked a plug loose?

 

Or should I be preparing to shop for a new drive?

 

Thanks for any insights in advance.

 

Quote

Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] 4096-byte physical blocks
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] Write Protect is off
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] Mode Sense: 00 3a 00 00
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] Preferred minimum I/O size 4096 bytes
Dec 15 15:18:28 Atlus kernel: sdr: sdr1
Dec 15 15:18:28 Atlus kernel: sd 48:0:0:0: [sdr] Attached SCSI removable disk
Dec 15 15:18:54 Atlus emhttpd: ST12000VN0008-2PH103_ZL2H589W (sdr) 512 23437770752
Dec 15 15:18:54 Atlus kernel: mdcmd (14): import 13 sdr 64 11718885324 0 ST12000VN0008-2PH103_ZL2H589W
Dec 15 15:18:54 Atlus kernel: md: import disk13: (sdr) ST12000VN0008-2PH103_ZL2H589W size: 11718885324 
Dec 15 15:18:54 Atlus emhttpd: read SMART /dev/sdr
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#0 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#0 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#0 CDB: opcode=0x88 88 00 00 00 00 05 00 4e c2 b8 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21479998136 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#1 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#1 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#1 CDB: opcode=0x88 88 00 00 00 00 05 00 4e de 58 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480005208 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=54s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#2 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#2 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#2 CDB: opcode=0x88 88 00 00 00 00 01 80 4b fc 88 00 00 00 20 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 6447430792 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=54s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#3 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#3 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 80 4b fc d0 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 6447430864 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=54s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#5 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#5 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#5 CDB: opcode=0x88 88 00 00 00 00 02 00 00 00 a0 00 00 00 20 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 8589934752 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#8 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#8 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#8 CDB: opcode=0x88 88 00 00 00 00 05 00 4e e6 20 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480007200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#10 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#10 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#10 CDB: opcode=0x88 88 00 00 00 00 05 00 4f 2a b8 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480024760 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#11 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#11 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#11 CDB: opcode=0x88 88 00 00 00 00 05 00 4f 85 b8 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480048056 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#12 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#12 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#12 CDB: opcode=0x88 88 00 00 00 00 05 00 4f f9 d0 00 00 00 08 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480077776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=53s
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#13 Sense Key : 0x2 [current] 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#13 ASC=0x4 ASCQ=0x21 
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] tag#13 CDB: opcode=0x88 88 00 00 00 00 05 00 5d ed b0 00 00 00 40 00 00
Dec 18 06:19:45 Atlus kernel: I/O error, dev sdr, sector 21480992176 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] Synchronizing SCSI cache
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] Stopping disk
Dec 18 06:19:45 Atlus kernel: sd 48:0:0:0: [sdr] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK

 

[updatenil]

I'd just wanted to add that another disk also has a similar message.

 

Quote

Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] 4096-byte physical blocks
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] Write Protect is off
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] Mode Sense: 00 3a 00 00
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] Preferred minimum I/O size 4096 bytes
Dec 15 15:18:28 Atlus kernel: sdq: sdq1
Dec 15 15:18:28 Atlus kernel: sd 47:0:0:0: [sdq] Attached SCSI removable disk
Dec 15 15:18:54 Atlus emhttpd: ST12000VN0008-2PH103_ZTN0DENF (sdq) 512 23437770752
Dec 15 15:18:54 Atlus kernel: mdcmd (13): import 12 sdq 64 11718885324 0 ST12000VN0008-2PH103_ZTN0DENF
Dec 15 15:18:54 Atlus kernel: md: import disk12: (sdq) ST12000VN0008-2PH103_ZTN0DENF size: 11718885324 
Dec 15 15:18:54 Atlus emhttpd: read SMART /dev/sdq
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#1 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#1 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#1 CDB: opcode=0x88 88 00 00 00 00 05 00 4e c2 b8 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21479998136 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#2 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#2 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#2 CDB: opcode=0x88 88 00 00 00 00 05 00 4e de 58 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21480005208 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#3 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#3 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#3 CDB: opcode=0x88 88 00 00 00 00 05 00 4e e6 20 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21480007200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#4 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#4 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#4 CDB: opcode=0x88 88 00 00 00 00 05 00 4f 2a b8 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21480024760 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#5 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#5 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#5 CDB: opcode=0x88 88 00 00 00 00 05 00 4f 85 b8 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21480048056 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=72s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#6 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#6 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#6 CDB: opcode=0x88 88 00 00 00 00 04 ff ff ff f0 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21474836464 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=95s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#7 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#7 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#7 CDB: opcode=0x88 88 00 00 00 00 05 00 5d ed b0 00 00 00 40 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21480992176 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=72s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#10 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#10 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#10 CDB: opcode=0x88 88 00 00 00 00 05 00 00 00 00 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21474836480 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=72s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#11 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#11 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#11 CDB: opcode=0x88 88 00 00 00 00 05 00 00 00 50 00 00 00 08 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21474836560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=72s
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#12 Sense Key : 0x2 [current] 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#12 ASC=0x4 ASCQ=0x21 
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] tag#12 CDB: opcode=0x88 88 00 00 00 00 05 02 f7 d9 70 00 00 00 20 00 00
Dec 18 06:20:27 Atlus kernel: I/O error, dev sdq, sector 21524633968 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] Stopping disk
Dec 18 06:20:27 Atlus kernel: sd 47:0:0:0: [sdq] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK

 

[JorgeB]

Please post the diagnostics.

[updatenil]

atlus-diagnostics-20231218-0925.zip

[JorgeB]

Looks more like a power/connection issue, but since there were ATA errors for two disks it can also be the controller, unless they share a power splitter or similar.

[updatenil]

Thank you. I will double check the connections later to make sure I didn't pull something out.

[updatenil]

After I check the connections and start everything up again, how do I re-enable the drive in question?

 

Are these instructions still good: https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

Edited December 18, 2023 by updatenil

[JorgeB]

Yes, but make sure the emulated disk is mounting before rebuilding on top.

[updatenil]

Recap

 

I upgraded a part in my server and potentially loosened a plug to a drive.

 

After checking the plugs to each of the drives and the controllers, I followed the below steps from the link above to re-enable the effected drive. Depending on your set up, this process could take a few days.

 

Thank you to @JorgeB as always for your help.

 

Steps:

 

Rebuilding a drive onto itself

 

There can be cases where it is determined that the reason a disk was disabled is due to an external factor and the disk drive appears to be fine. In such a case you need to take a slightly modified process to cause Unraid to rebuild a 'disabled' drive back onto the same drive.

 

Stop array

 

Unassign disabled disk

 

Start array so the missing disk is registered

 

Important: If the drive to be rebuilt is a data drive then check that the emulated drive is showing the content you expect to be there as the rebuild process simply makes the physical drive match the emulated one. If this is not the case then you may want to ask in forums for advice on the best way to proceed.

 

Stop array

 

Reassign disabled disk

 

(optional) Tick the box to start in Maintenance mode. If you start the array in Maintenance mode you will need to press the Sync button to trigger the rebuild. The advantage of doing this in Maintenance mode is that nothing else can write to the array while the rebuild is running which maximises speed. The disadvantage is that you cannot use the array in the meantime and until you return to normal mode cannot see what the contents of the disk being rebuilt will look like.

 

Click Start to initiate the rebuild process and the system will reconstruct the contents of the emulated disk.

 

[updatenil]

@JorgeB If you have a moment to take a look at this issue again, I would appreciate it very much.

 

I believe the same drive is noted as failed, and the parity has kicked in. I'll include the diagnostics and I think this time I'll make plans to get a new drive.

 

Since you mentioned back in Dec that there were two drives that were questionable, I'm just wondering if I should brace myself to get two drives instead of just one.

 

Thank you!

atlus-diagnostics-20240605-1028.zip

Edited June 5 by updatenil
add diagnostic

[JorgeB]

This looks more like a power/connection issue, or controller, but the disk dropped offline, so there's no SMART, reboot and post new diags after array start.

[updatenil]

At a break here, I shut down the server and just pressed each power plug into the drives. After booting it up everything appears to be connected again. 

 

Big sigh. Now I'll have to set aside time to properly label all my drives and cables.

[updatenil]

Alright. So it's me again. For a while there I thought I was back in business and even added an extra parity drive for extra peace of mind. 

 

I traced the problem from the 2 drives to the cables in question: A "Y" type cable that is connected back to power with some daisy chained molex cables. I checked the connections and powered it back up, but it seemed fine. I didn't take the risk though so I changed them out. 

 

Since then I included an extra parity drive for some extra peace of mind which took quite some time. 

 

Enter the Problem:

 

I decided I wanted to switch out a 12 TB drive with a new 20 TB drive so I opened up the PC. I installed the new drive and started the rebuild process last night. But, I suspect the molex cables in question are pressed by the PC panel when I close up the unit once more.

 

I checked to see the rebuilt progress and everything appeared fine until this morning.

 

Now the rebuild has stopped for the larger drive, plus the two drives in question appear with issues. 

 

What is the procedure to recover from this situation?

 

If I do recover from this situation then I'll have to re-evaluate how I'm running those molex cables. Or I avoid completely closing that panel and slowly figure out if I want to move on to a new case one day. 

atlus-diagnostics-20240714-0854.zip

[updatenil]

Well for lack of a better idea on my time off, I shut down the computer and looked over the cables.

 

Sure enough I found a lightly cracked molex connector and readjusted the pins. I'll have to buy another one for the future.

 

In the meantime I booted the computer back up and it seems the new drive I was trying to install, along with the 2 drives connected to the defective molex cable are seen and I started the array.

 

Now Unraid says that I have 3 unmountable disks present, and it looks like it started some kind of data rebuild which seems to be going rather quickly.

 

Afterwards, everything is backed up elsewhere. Is there any easy way to recover the 3 disks in question or should I just format them and start from scratch?

atlus-diagnostics-20240714-1353.zip

Edited July 14 by updatenil

[JorgeB]

There are three invalid disks, so they cannot be emulated with two parity disks, if you think the issue is resolved, you can try to force enable the last two disabled disks and then try to rebuild disk6 again, this will only work if parity is still valid:

 

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk6
-Start array (in normal mode now) and post new diags.

 

 

[updatenil]

@JorgeB Thanks for always being there even for fools like me.

 

Rather than wait, I tried searching for a solution on my own and found this link: https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/

 

I followed the check procedure described on the two drives (sdr and sds) and there were a number of errors found. I followed the procedure and then started the array once more. Unfortunately, the drives mounted as pretty much fresh drives with no used data. I tried looking at the Lost and Found, but there were many folders and I wasn't sure I wanted to dig through all of them. 

 

I chose to commit to starting from the beginning on these drives and they're presently being rebuilt. 

 

I'm still choked that I suffered the most from what's probably an $8.00 cable. But, life is still moving, and I still have to keep it moving. 

 

Thanks again.