zfs discuss - May 2012 - Dell PERC H200: drive failed to power up

Hi,

I''m getting weird errors while trying to install openindiana 151a on a
Dell R715 with a PERC H200 (based on an LSI SAS 2008). Any time the OS
tries to access the drives (for whatever reason), I get this dumped into
syslog:

genunix: WARNING: Device
/pci at 0,0/pci1002,5a18 at 4/pci10b58424 at 0/pci10b5,8624 at 0/pci1028,1f1e at
0/iport at 40/disk at w50000c0f01004ebe,0
failed to power up
genunix: WARNING: Device
/pci at 0,0/pci1002,5a18 at 4/pci10b58424 at 0/pci10b5,8624 at 0/pci1028,1f1e at
0/iport at 80/disk at w50000c0f01064e9e,0
failed to power up

(these are two WD 300GB 10k SAS drives)

When this log message shows up, I can see each drive light up the drive
LED briefly and then it turns off, so apparently the OS tried to
initialize the drives, but somehow failed and gave up.

Consequently, when I try and access them in format(1), they show up as
an unknown type and installing openindiana on them fails while the
installer is trying to do fdisk.

Has anybody got any idea what I can do to the controller/drives/whatever
to fix the "failed to power up" problem? One would think that a LSI
SAS
2008 chip would be problem free under Solaris (the server even lists
Oracle Solaris as an officially supported OS), but alas, I have yet to
succeed.

Cheers,
--
Saso

Hi,

are those DELL branded WD disks? DELL tends to manipulate the firmware of
the drives so that power handling with Solaris fails. If this is the case
here:

Easiest way to make it work is to modify /kernel/drv/sd.conf and add an
entry
for your specific drive similar to this

sd-config-list= "WD     
WD2000FYYG","power-condition:false",
                "SEAGATE
ST2000NM0001","power-condition:false",
                "SEAGATE
ST32000644NS","power-condition:false",
                "SEAGATE
ST91000640SS","power-condition:false";

Naturally you would have to find out the correct drive names. My latest
version for a R710 with a MD1200 attached is:

sd-config-list="SEAGATE
ST2000NM0001","power-condition:false",
        "SEAGATE ST1000NM0001","power-condition:false",
        "SEAGATE ST91000640SS","power-condition:false";


Are you using the H200 with the base firmware or did you flash it to LSI IT?
I am not sure that Solaris handles the H200 natively at all and if then it
will not have direct drive access since the H200 will only show virtual
drives to Solaris/OI will it not?

Kind regards,
   JP

PS: These are not my findings. Cudos to Sergei (tehcook at gmail.com) and
Niklas Tungstr?m.

Von:  Sa?o Kiselkov <skiselkov.ml at gmail.com>
An:  zfs-discuss <zfs-discuss at opensolaris.org>
Betreff:  [zfs-discuss] Dell PERC H200: drive failed to power up
> Hi,
> 
> I''m getting weird errors while trying to install openindiana 151a
on a
> Dell R715 with a PERC H200 (based on an LSI SAS 2008). Any time the OS
> tries to access the drives (for whatever reason), I get this dumped into
> syslog:
> 
> genunix: WARNING: Device
> /pci at 0,0/pci1002,5a18 at 4/pci10b58424 at 0/pci10b5,8624 at
0/pci1028,1f1e at 0/iport at 40/d
> isk at w50000c0f01004ebe,0
> failed to power up
> genunix: WARNING: Device
> /pci at 0,0/pci1002,5a18 at 4/pci10b58424 at 0/pci10b5,8624 at
0/pci1028,1f1e at 0/iport at 80/d
> isk at w50000c0f01064e9e,0
> failed to power up
> 
> (these are two WD 300GB 10k SAS drives)
> 
> When this log message shows up, I can see each drive light up the drive
> LED briefly and then it turns off, so apparently the OS tried to
> initialize the drives, but somehow failed and gave up.
> 
> Consequently, when I try and access them in format(1), they show up as
> an unknown type and installing openindiana on them fails while the
> installer is trying to do fdisk.
> 
> Has anybody got any idea what I can do to the controller/drives/whatever
> to fix the "failed to power up" problem? One would think that a
LSI SAS
> 2008 chip would be problem free under Solaris (the server even lists
> Oracle Solaris as an officially supported OS), but alas, I have yet to
> succeed.
> 
> Cheers,
> --
> Saso
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20120516/036be729/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6443 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20120516/036be729/attachment-0001.bin>

On 05/16/2012 09:45 AM, Koopmann, Jan-Peter wrote:
> Hi,
> 
> are those DELL branded WD disks? DELL tends to manipulate the
> firmware of the drives so that power handling with Solaris fails.
> If this is the case here:
> 
> Easiest way to make it work is to modify /kernel/drv/sd.conf and
> add an entry for your specific drive similar to this
> 
> sd-config-list= "WD     
WD2000FYYG","power-condition:false",
> "SEAGATE ST2000NM0001","power-condition:false",
"SEAGATE
> ST32000644NS","power-condition:false", "SEAGATE
> ST91000640SS","power-condition:false";
> 
> Naturally you would have to find out the correct drive names. My
> latest version for a R710 with a MD1200 attached is:
> 
> sd-config-list="SEAGATE
ST2000NM0001","power-condition:false",
> "SEAGATE ST1000NM0001","power-condition:false",
"SEAGATE
> ST91000640SS","power-condition:false";
> 
> 
> Are you using the H200 with the base firmware or did you flash it
> to LSI IT? I am not sure that Solaris handles the H200 natively at
> all and if then it will not have direct drive access since the H200
> will only show virtual drives to Solaris/OI will it not?
They are Dell branded WD disks and I haven''t done anything to the
HBA''s firmware, so that''s stock Dell as well. The drives are,
specifically are WD3001BKHG models. The firmware actually does expose
the disks unless they''re part of a RAID group, so that should actually
work. I''ll try te power-condition workaround you mentioned.

Cheers,
--
Saso

On 05/16/2012 09:45 AM, Koopmann, Jan-Peter wrote:
> Hi,
> 
> are those DELL branded WD disks? DELL tends to manipulate the firmware of
> the drives so that power handling with Solaris fails. If this is the case
> here:
> 
> Easiest way to make it work is to modify /kernel/drv/sd.conf and add an
> entry
> for your specific drive similar to this
> 
> sd-config-list= "WD     
WD2000FYYG","power-condition:false",
>                 "SEAGATE
ST2000NM0001","power-condition:false",
>                 "SEAGATE
ST32000644NS","power-condition:false",
>                 "SEAGATE
ST91000640SS","power-condition:false";
> 
> Naturally you would have to find out the correct drive names. My latest
> version for a R710 with a MD1200 attached is:
> 
> sd-config-list="SEAGATE
ST2000NM0001","power-condition:false",
>         "SEAGATE ST1000NM0001","power-condition:false",
>         "SEAGATE ST91000640SS","power-condition:false";
> 
> 
> Are you using the H200 with the base firmware or did you flash it to LSI
IT?
> I am not sure that Solaris handles the H200 natively at all and if then it
> will not have direct drive access since the H200 will only show virtual
> drives to Solaris/OI will it not?
> 
> Kind regards,
>    JP
> 
> PS: These are not my findings. Cudos to Sergei (tehcook at gmail.com) and
> Niklas Tungstr?m.
One thing came up while trying this - I''m on a text install image
system, so my / is a ramdisk. Any ideas how I can change the sd.conf on
the USB disk or reload the driver configuration on the fly? I tried
looking for the file on the USB drive, but it isn''t in the rootfs
(perhaps it''s tucked away in some compressed filesystem image). Thanks!

--
Saso

On 05/16/2012 10:17 AM, Koopmann, Jan-Peter wrote:
>> 
>> 
>> One thing came up while trying this - I''m on a text install
>> image system, so my / is a ramdisk. Any ideas how I can change
>> the sd.conf on the USB disk or reload the driver configuration on
>> the fly? I tried looking for the file on the USB drive, but it
>> isn''t in the rootfs (perhaps it''s tucked away in some
compressed
>> filesystem image). Thanks!
> 
> I am by no means a Solaris or OI guru and live from good advice of
> other people and Mr. Google. So sorry. I have no clue?
I got lucky at Googling after all and found the relevant command:

# update_drv -vf sd

The PERC H200 card had nothing to do with it, it was all in the crappy
firmware in the HDDs. Simply adding

sd-config-list = "WD     
WD3001BKHG","power-condition:false";

to my /kernel/drv/sd.conf (as you suggested) and reloading the driver
using update_drv solved it and I could then proceed with the
installation. The installer was even smart enough to install the
customized sd.conf into the new system, so no further tuning was
necessary.

Thanks for the pointers, you saved my bacon.

Cheers,
--
Saso