Jump to content
indy90

Drive Show under SCSI Devices, but not in the drop down....

15 posts in this topic Last Reply

Recommended Posts

I'm new to UNRAID. I am in the trial period and have 15 days remaining. So far I like what I've seen and really find it simple enough to use. I have 8 SAS drives attached to a Areca ARC-1680 in JOBD mode. This works in windows 10 and presents as a group of 8 individual disks. In UNRAID, they show in the SCSI Devices, but not showing in the drop down to be assigned in the array. Any ideas would be great. Thanks! Attached Diagnostics file and here is what is showing in SCSI Devices.

 

SCSI Devices

[0:0:0:0]disk VendorCo ProductCode 2.00 /dev/sda 15.7GB - UNRAID USB

[1:0:1:0]disk HITACHI HUS723030ALS640 R001 /dev/sdb 3.00TB - NOT SHOWING IN DROP DOWN

[1:0:1:1]disk HITACHI HUS723030ALS640 R001 /dev/sdc 3.00TB - NOT SHOWING IN DROP DOWN 

[1:0:1:2]disk HITACHI HUS723030ALS640 R001 /dev/sdd 3.00TB - NOT SHOWING IN DROP DOWN

[1:0:1:3]disk HP MM1000FBFVR R001 /dev/sde 1.00TB - SAS ON ARC CARD SHOWING IN DROP DOWN

[1:0:1:4]disk HITACHI HUS723030ALS640 R001 /dev/sdf 3.00TB - SAS ON ARC CARD SHOWING IN DROP DOWN

[1:0:1:5]disk HITACHI HUS723030ALS640 R001 /dev/sdg 3.00TB - NOT SHOWING IN DROP DOWN

[1:0:1:6]disk HITACHI HUS723030ALS640 R001 /dev/sdh 3.00TB - NOT SHOWING IN DROP DOWN

[1:0:1:7]disk HP MM1000FBFVR R001 /dev/sdi 1.00TB - SAS ON ARC CARD SHOWING IN DROP DOWN

[2:0:0:0]disk ATA TOSHIBA MK5061GS 2E /dev/sdj 500GB - SATA ON MB SHOWING IN DROP DOWN

[2:0:1:0]disk ATA WDC WD2003FYYS-1 1D05 /dev/sdk 2.00TB - SATA ON MB SHOWING IN DROP DOWN

[3:0:0:0]disk ATA Hitachi HTS72755 A0E0 /dev/sdl 500GB - SATA ON MB SHOWING IN DROP DOWN

[3:0:1:0]disk ATA WDC WD2003FYYS-1 1D05 /dev/sdm 2.00TB - SATA ON MB SHOWING IN DROP DOWN

[4:0:0:0]disk ATA WDC WD2003FYYS-1 1D05 /dev/sdn 2.00TB - SATA ON MB SHOWING IN DROP DOWN

[5:0:0:0]disk ATA WDC WD2003FYYS-1 1D05 /dev/sdo 2.00TB - SATA ON MB SHOWING IN DROP DOWN

tower-diagnostics-20181126-1847.zip

Share this post


Link to post

For some reason there's a problem getting the ID of all but of the HUS723030ALS640 disks, disconnect those 5 disks to confirm if the other will show up then.

 

Nov 26 18:28:21 Tower emhttpd: device /dev/sdd problem getting id
Nov 26 18:28:21 Tower emhttpd: device /dev/sdb problem getting id
Nov 26 18:28:21 Tower emhttpd: device /dev/sdc problem getting id
Nov 26 18:28:22 Tower emhttpd: device /dev/sdh problem getting id
Nov 26 18:28:22 Tower emhttpd: device /dev/sdg problem getting id

 

Share this post


Link to post

I think the problem is the Areca controller is identifying all 6 HGST disks the same, likely because those disks have a generic logical unit ID with lots of zeros in the end (0x001b4d2000000000), different from the other SAS disks, e.g. the 1TB HP is 0x001b4d2029840ae9, so the first one is recognized by Unraid but since the other ones have the same ID they won't work, Unraid needs a different ID for each disk, maybe it possible to change that in the Areca config utility/bios, though your best bet would be to use an HBA instead of RAID controller.

Share this post


Link to post

Here is the output. 

 

lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-Hitachi_HTS727550A9E364_J3360081G2L5KC -> ../../sdl
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-Hitachi_HTS727550A9E364_J3360081G2L5KC-part1 -> ../../sdl1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-TOSHIBA_MK5061GSY_72QDP7X9T -> ../../sdj
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-TOSHIBA_MK5061GSY_72QDP7X9T-part1 -> ../../sdj1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00374594 -> ../../sdo
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00374594-part1 -> ../../sdo1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00376600 -> ../../sdn
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00376600-part1 -> ../../sdn1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00378612 -> ../../sdm
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00378612-part1 -> ../../sdm1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00393798 -> ../../sdk
lrwxrwxrwx 1 root root 10 Nov 26 18:28 ata-WDC_WD2003FYYS-18W0B0_WD-WCAY00393798-part1 -> ../../sdk1
lrwxrwxrwx 1 root root  9 Nov 26 19:27 scsi-2001b4d2000000000 -> ../../sdf
lrwxrwxrwx 1 root root 10 Nov 26 19:27 scsi-2001b4d2000000000-part1 -> ../../sdf1
lrwxrwxrwx 1 root root  9 Nov 26 19:27 scsi-2001b4d2029840ae9 -> ../../sdi
lrwxrwxrwx 1 root root 10 Nov 26 19:27 scsi-2001b4d2029840ae9-part1 -> ../../sdi1
lrwxrwxrwx 1 root root  9 Nov 26 19:28 scsi-2001b4d2029948be0 -> ../../sde
lrwxrwxrwx 1 root root 10 Nov 26 19:28 scsi-2001b4d2029948be0-part1 -> ../../sde1
lrwxrwxrwx 1 root root  9 Nov 26 18:27 usb-VendorCo_ProductCode_92070968DD794732554-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 26 18:27 usb-VendorCo_ProductCode_92070968DD794732554-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x50000394227882a6 -> ../../sdj
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x50000394227882a6-part1 -> ../../sdj1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x5000cca689c12cfc -> ../../sdl
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x5000cca689c12cfc-part1 -> ../../sdl1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x50014ee2071ed0dd -> ../../sdm
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x50014ee2071ed0dd-part1 -> ../../sdm1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x50014ee25c748bf6 -> ../../sdn
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x50014ee25c748bf6-part1 -> ../../sdn1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x50014ee25c74fb93 -> ../../sdk
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x50014ee25c74fb93-part1 -> ../../sdk1
lrwxrwxrwx 1 root root  9 Nov 26 18:28 wwn-0x50014ee2b1c99d89 -> ../../sdo
lrwxrwxrwx 1 root root 10 Nov 26 18:28 wwn-0x50014ee2b1c99d89-part1 -> ../../sdo1

Share this post


Link to post
10 hours ago, johnnie.black said:

For some reason there's a problem getting the ID of all but of the HUS723030ALS640 disks, disconnect those 5 disks to confirm if the other will show up then.

 


Nov 26 18:28:21 Tower emhttpd: device /dev/sdd problem getting id
Nov 26 18:28:21 Tower emhttpd: device /dev/sdb problem getting id
Nov 26 18:28:21 Tower emhttpd: device /dev/sdc problem getting id
Nov 26 18:28:22 Tower emhttpd: device /dev/sdh problem getting id
Nov 26 18:28:22 Tower emhttpd: device /dev/sdg problem getting id

 

I had missed that completely. Thanks for pointing that out.

Share this post


Link to post
On 11/27/2018 at 10:36 AM, limetech said:

Please open Terminal window and post output of this command:


v /dev/disk/by-id

 

Please advise. Not sure what to try next. I have disconnect the drives and introduced them back one at a time. Same results. 

 

Thanks in advance for any help.

Share this post


Link to post

Did you check if all the HGST have the same identifier? if yes maybe there's a way to change them on the Ateca controller, if not best bet would be to use a plain HBA, that would pass the disk's serial numbers to Unraid and so not a problem.

Share this post


Link to post

The bug is that /dev/disk/by-id is not being filled in by udev subsystem for this controller for some reason.

Share this post


Link to post

Hello, I had this same issue with an ARC-1880. I just flashed the latest firmware to it, seems to have fixed it. It was exhibiting the same behavior described above, for me with some WDC drives that are same make/model.

When the card is in RAID mode and you are presenting some passhrough disks for UNRAID to manage, by default they will be assigned different SCSI LUNs by  on the same SCSI_ID. The trick appeared to be to assign separate SCSI_ID's. Unfortunately on this card, you are limited to a certain number of passthrough disks in RAID mode.

 

I was also encountering this problem in JBOD mode but there's no way to assign SCSI ID's in this mode. I've put my card back into JBOD mode after the firmware update, and everything seems to be behaving itself now. UNRAID now sees the disk serial number postfixed to the drive ID.  I updated to 1.55. I believe I was at 1.47

Hopefully this helps someone.

Share this post


Link to post

Is this issue/bug going to be fixed?  I'm experiencing the same issue with 2 identical USB 4-bay enclosures. Both enclosures/drives are identified and seen by the system but one enclosure does not appear in the drop-down.  Just seeing if this will be fixed in the future or not.

Share this post


Link to post
11 minutes ago, civic95man said:

I'm experiencing the same issue with 2 identical USB 4-bay enclosures.

Nobody else in this thread has mentioned USB enclosures, so perhaps saying you have the same issue is jumping to conclusions.

 

In any case, USB, though allowed, is not recommended for drives in the array or cache pool, because some implementations are unreliable.

Share this post


Link to post
12 minutes ago, trurl said:

because some implementations are unreliable.

And some, use exactly the same identifiers for disks when more than one enclosure is used, which appears to be @civic95manproblem, in that case you can't use both with Unraid since each disk needs to have a different identifier for Unraid to keep track of them.

Share this post


Link to post
9 minutes ago, trurl said:

Nobody else in this thread has mentioned USB enclosures, so perhaps saying you have the same issue is jumping to conclusions.

You are correct.  I have been hopping around between different posts trying to figure out my problem and must have confused it with another similar one where they were using USB for the interface.  

 

With all of that said, I have a very similar issue as the OP and getting nearly identical results as they had - just with different drive names and identifiers.  When it was mentioned that there might be a bug in the way /dev/disk/by-id was being populated by udev, i wondered if there was confirmation of this or any other news.

 

As for not using USB to connect drives - I understand the issues and concern; however I have no other means to add drives at this time.  So it boils down to USB or nothing.

Share this post


Link to post
6 minutes ago, johnnie.black said:

And some, use exactly the same identifiers for disks when more than one enclosure is used

 Yes, that is what I figured the problem was.  I was just really wishing to find a fix to allow me to use 2 enclosures.  The box's ID/serial number is appended to the end of the hdd (wd red) so all four look the same in the enclosure with the exception of the port and bay (maybe) identifier after that.  Anyway, thanks

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.