Hi,

 

Can any one help me?. Suddenly my server shown as disk disabled and the same disk (sdn) is shown in Unassigned with different Name (sds).

 

I just restarted the server then it shows as 2 disks missing and both shown in unassigned.  I did new config and assigned the devices as before (Parity drives) and data disks. Now its says errors on the 2 disks .

 

Can some one help me why it happened. 

 

netplex-diagnostics-20220921-1628.zip

Might as well cancel parity rebuild.

 

Shutdown, check connections including power. Reboot and post new diagnostics

Looks more like a power/connection issue:

 

Sep 21 16:26:33 NetPlex kernel: pm80xx0:: mpi_sata_completion  2455:IO failed device_id 18439 status 0xf tag 95
Sep 21 16:26:33 NetPlex kernel: pm80xx0:: mpi_sata_completion  2490:SAS Address of IO Failure Drive:50000d1109b27a9e
Sep 21 16:26:33 NetPlex kernel: sas: sas_to_ata_err: Saw error 135.  What to do?

 

But not familiar with these controllers and their errors.

What is the correct way to deal with a disk removed from the array after a reboot?

As you can see from the attached images showing the array list before and after reboot. 

 

Disk 3 was removed and all the drive letters have changed although the remaining disks seem to be in the same order.

 

How to i get the disk back into the array with out loosing the data on the disk that was removed from the array (disk 3)?

 

-----------------

I restarted the server as i removed a plug-in "CA Dynamix Unlimited Width" and I removed a disk that failed pre clearing.

 

 

Edited September 24, 20223 yr by wow001

Start the array and post new diagnostics

You need to rebuild it, first start the array with the missing disk to see if the emulated disk is mounting and contents look correct.

 

P.S. seeing some issues with disk1 in the last diags, looks like power/connection issue.

If i start the array with the missing disk i get the message the "All existing data on this device will be OVERWRITTEN when array is Started"

as per the attached image.

 

So the steps are:

1. Add the missing disk back to location disk 3 and start the array,

2. The data on disk 3 is overwritten/wiped.

3. Unraid rebuilds the data on disk 3 from the two Parity disks.?

 

 

 

Unassign disk3 then start the array and post new diagnostics.

1 hour ago, JorgeB said:

start the array with the missing disk

Start the array with the disk still missing (not assigned)

I have unassigned disk 3 and array has restarted with no notifications but it says in the array list Disk 3 not installed.

Edited September 22, 20223 yr by wow001

That's expected, did the emulated disk mount? Or post diags.

1 hour ago, trurl said:

post new diagnostics.

 

2 minutes ago, JorgeB said:

did the emulated disk mount?

(That screenshot might have showed us what we wanted to see if you hadn't clipped it on the right.)

Yes Unraid has emulated the disk mount and shows the same quantity of folders and files as the missing disk 3.

As seen in image 1.

 

Image 2 shows the data on the missing disk 3 mounted via unassigned devices.

 

Edited September 24, 20223 yr by wow001

Now stop the array, re-assign disk3 and start the array to begin rebuilding, during the rebuild monitor the log for any disk related errors, similar to these:

 

Sep 22 14:12:46 wowserver02 kernel: sd 18:0:4:0: attempting task abort!scmd(0x00000000b2e31524), outstanding for 15103 ms & timeout 15000 ms
Sep 22 14:12:46 wowserver02 kernel: sd 18:0:4:0: [sdm] tag#7355 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Sep 22 14:12:46 wowserver02 kernel: scsi target18:0:4: handle(0x000d), sas_address(0x4433221105000000), phy(5)
Sep 22 14:12:46 wowserver02 kernel: scsi target18:0:4: enclosure logical id(0x500605b00b101dd0), slot(6)
Sep 22 14:12:46 wowserver02 kernel: scsi target18:0:4: enclosure level(0x0000), connector name(     )
Sep 22 14:12:48 wowserver02 kernel: sd 18:0:4:0: [sdm] tag#3975 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=18s
Sep 22 14:12:48 wowserver02 kernel: sd 18:0:4:0: [sdm] tag#3975 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 78 00 00 00 08 00 00
Sep 22 14:12:48 wowserver02 kernel: I/O error, dev sdm, sector 15628053112 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Sep 22 14:12:48 wowserver02 kernel: sd 18:0:4:0: task abort: SUCCESS scmd(0x00000000b2e31524)
Sep 22 14:12:49 wowserver02 kernel: sd 18:0:4:0: Power-on or device reset occurred

 

If you see them there are still issues, probably power/connection related.

Thank you for the help, 

Data rebuild has started and projected for 5 hours.

 

Will keep an eye on the logs and see if i get the power issue again.

On Main - Array Devices, you should see lots of Writes to the rebuilding disk, lots of Reads from all other disks, and nothing in the Errors column for any disk

The disk was rebuilt with no errors.

Thanks trurl and JorgeB array is now back to normal.

I found the issue that caused the disk to go missing for the array.

It is the back plane of one of the hot swap IcyBox enclosures that i use to house the array.

As suggested it was a power issue that kept turning off just one bay/disk