Only one of three SATA drives detected

prior_philip

Cadet
Joined
Jul 30, 2017
Messages
6
Dear all,
I planned a drive replacement in the 4 bay hdd case which is connected to a N54 HP Microserver G3 via SATA cable.
First I updated from 11-stable to 11.2-U6, works fine after a few hickups.
Configuration:
HP Microserver G3 n54 with 4x4TB drives in RAIDZ1
Silverstone 4 bay case with 4x 2tb HDDs attached via SATA to HD MicroServer, configured as a second RAIDZ1 pool

Since upgrading to 11.2 only one disk in this external HDD case is detected when connecting via SATA. When connecting with USB all four are detected but serialnumber are reported as 000000000000 and they gets detached.

Is there something that I can do to solve this?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Have a look at the output of gmultipath list
 

prior_philip

Cadet
Joined
Jul 30, 2017
Messages
6
gmultipath list does not give back anything.

newton# gmultipath list
newton#

But camcontrol devlist:
As you see, last entry only lists one 6GB drive. 3 are docked into the case.
newton# camcontrol devlist
<WDC WD40EFRX-68WT0N0 82.00A82> at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD40EFRX-68WT0N0 82.00A82> at scbus1 target 0 lun 0 (pass1,ada1)
<WDC WD40EFRX-68WT0N0 82.00A82> at scbus2 target 0 lun 0 (pass2,ada2)
<WDC WD40EFRX-68WT0N0 82.00A82> at scbus3 target 0 lun 0 (pass3,ada3)
<WDC WD60EFAX-68SHWN0 82.00A82> at scbus4 target 0 lun 0 (pass4,ada4)
<SanDisk Ultra Fit 1.00> at scbus7 target 0 lun 0 (pass5,da0)
newton#
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
I had thought it may be multipath hiding the additional drives as some external cases don't support bifurcation.

It may come down to the external case not supporting the pass-through of multiple drives.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
That's normal, gmultipath only lists drives that are found via complex controller setup, simple SATA port connections won't appear there.
 

prior_philip

Cadet
Joined
Jul 30, 2017
Messages
6
Strange behavior. W10 reads the drives out correctly but FreeNAS doesnt. Is there an eSATA diagnostic tool available or any kernel debug messages Im not aware of?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
That will be because the driver in Windows 10 can handle the port multiplier feature which does the bifurcation.

I don't think the FreeBSD driver will give you a lot of help with that.

As a general rule, eSATA enclosures aren't a great idea for FreeNAS.
 

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
I wonder if there might have been a driver rollback in ahci or ada in upstream FreeBSD that would cause port multiplication to be unsupported or broken on your specific chipset.

If possible I would suggest filing a bug report with iXsystems through the Jira tracker and then rolling back to an 11.1 based build.
 

prior_philip

Cadet
Joined
Jul 30, 2017
Messages
6
It seems server BIOS has been set back to default, so Multipath has been disabled.
11.2 now detects the drives in external disk cage.

Another question:
I had a RAIDZ1 pool inside the server which I like to move to the external disk cage, the drive numbers would change. How can I tell the pool to look for ada4-da07 instead of ada0-ada03 for example?
 
Top