Assigning Drives Not Working

[Dr. Ew]

no change in my install other than switching from trial to Unraid pro. After purchasing, restarting, I can't assign drives.

 

I had a drive showing emulated after I booted Unraid pro. Nothing wrong with the drive, as far as I can tell. 

 

I followed directions to re-enable drive. Selected to load new config, maintaining parity and cache. 

When I went back to main, all drives were unassigned. 

 

Now as I try to assign a drive, the ui either doesn't refresh, or takes 10 minutes to refresh. 

 

There is no way to assign all drives. Some of the drives I did wait the 10 minute period to assign, but they have written in Red all content will be erased upon starting array. 

 

Something has gone seriously awry. I have been functioning just fine. Now something is seriously wrong. 

 

What can I do?

[JorgeB]

Please post the diagnostics: Tools -> Diagnostics

[Dr. Ew]

6 hours ago, johnnie.black said:

Please post the diagnostics: Tools -> Diagnostics

Here you go.

nar1-diagnostics-20190428-1319.zip

[JorgeB]

There's a strange device detected as a 100MB drive:

 

Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: Direct-Access     ATA      ASMT109x- Config  5   PQ: 0 ANSI: 5
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: SATA: handle(0x0023), sas_addr(0x500304800113e04d), phy(13), device_name(0x0000000000009080)
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: enclosure logical id (0x50030442523a2033), slot(9)
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: atapi(n), ncq(n), asyn_notify(n), smart(n), fua(n), sw_preserve(n)
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: Power-on or device reset occurred
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: Attached scsi generic sg22 type 0
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] 204800 512-byte logical blocks: (105 MB/100 MiB)
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Write Protect is off
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Mode Sense: 73 00 00 08
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Attached SCSI disk

This is flooding the syslog with errors, try updating the LSI firmware since it's on an ancient release.

[Dr. Ew]

22 hours ago, johnnie.black said:

There's a strange device detected as a 100MB drive:

 

Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: Direct-Access     ATA      ASMT109x- Config  5   PQ: 0 ANSI: 5
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: SATA: handle(0x0023), sas_addr(0x500304800113e04d), phy(13), device_name(0x0000000000009080)
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: enclosure logical id (0x50030442523a2033), slot(9)
Apr 26 23:19:26 nAR1 kernel: scsi 4:0:14:0: atapi(n), ncq(n), asyn_notify(n), smart(n), fua(n), sw_preserve(n)
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: Power-on or device reset occurred
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: Attached scsi generic sg22 type 0
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] 204800 512-byte logical blocks: (105 MB/100 MiB)
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Write Protect is off
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Mode Sense: 73 00 00 08
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 26 23:19:26 nAR1 kernel: sd 4:0:14:0: [sdu] Attached SCSI disk

This is flooding the syslog with errors, try updating the LSI firmware since it's on an ancient release.

thank you. I was wondering what that ASMT109x was. How do you know it is from the LSI HBA? I could have sworn tha popped up here and there before putting in the new controller, but I could be wrong.

 

I'm working on updating the firmware. Is it possible to use sas2flash within unraid? If not, could you link me to instructions on how to upgrade the firmware? For LSI RAID controllers, I would boot into the management utility or use pre-boot CLI. WIth the HBA that isn't possible. I've been reading all morning, and I still don't have a clue as to the best method, other than creating a dos bootloader, which isn't quite going smoothly.

[JorgeB]

4 minutes ago, Dr. Ew said:

How do you know it is from the LSI HBA?

It's not, but it's connected somehow to it, ASM should be something Asmedia, like a port multiplier form an external enclosure.

 

5 minutes ago, Dr. Ew said:

Is it possible to use sas2flash within unraid?

No, you need to boot to DOS or put the HBA in a windows PC, then just run sas2flash -o -f firmware.bin (sas2flash in Windows)

[Dr. Ew]

5 hours ago, johnnie.black said:

It's not, but it's connected somehow to it, ASM should be something Asmedia, like a port multiplier form an external enclosure.

 

No, you need to boot to DOS or put the HBA in a windows PC, then just run sas2flash -o -f firmware.bin (sas2flash in Windows)

Got it. Yeah, I thought it was an asmedia device. It's very peculiar. I don't have any asmedia devices on this particular server. The internal controller doesn't have an asmedia controller, neither does the LSI, the only other devices in the server are Mellanox NIC and 5 NvME to PCIe cards; none of which have asmedia chips, as far as i know. I will double check that.

 

I updated LSI firmware and I am still having the same problem. I am thinking I may need to scrap this UnRAID install and start again. 

 

My bootloader backs-up 3 times per week, so I should be able to recover the entire config. Worst case, I lose the customizations for the server. All of the data on the array is replicated on two other UnRAID servers, so even if I lose the data, i'm covered. Although, I;d rather not have to re-load tera's of data if not necessary.

 

Hopefully, I can launch a completely new config, reassign the drives, and turn out ok. 

 

What's the recommedation for next step? Anything else i can try before scrapping the array?

[JorgeB]

Do you have any external devices connected? Like a dock station or similar? The ASMT109x is definatly a device with an Asmedia chip, and appears to be connected to the LSI, if you can't find it disconnect everything from the LSI and then connect one device at a time until you do.

[Vr2Io]

As @johnnie.black founding.

ASMT109x was some kind SATA RAID solution in enclosure.

 

On 4/28/2019 at 1:20 PM, Dr. Ew said:

no change in my install other than switching from trial to Unraid pro.

Pls double check on disk enclosure and any switch have change.

Edited April 30, 2019 by Benson

[Dr. Ew]

I did figure out the only as media device I have is a starch dual 2.5" to 3.5" raid box. I believe two of my cache drives are in it. Is there a way to ping the hdd light on the server that will show me which bay the device is in?

[Vr2Io]

You may try access LSI HBA BIOS and use it to locate which 3.5 device is target.

[Dr. Ew]

thanks. I identified the enclosure, pulled it, all clear since then.