[Info-vax] P400 on DS10/DS15
Eberhard Heuser
information at dvdwrite.de
Sun Aug 16 15:17:58 EDT 2020
Before you use drvcfg -s try to type in drvcfg without any arguments. Then you'll see which parameters are meaningful.
Eberhard
Am 16. August 2020 19:35:35 MESZ schrieb "John H. Reinhardt via Info-vax" <info-vax at rbnsn.com>:
>On 8/13/2020 8:18 AM, Rod Regier wrote:
>> P410 using ORCA should work on your I64.
>>
>
>Unfortunately, it doesn't. The P410 is in "HBA Mode" and won't start
>ORCA when the ZX6000 boots. So I found you have to set it to "RAID
>Mode" and then it works. The way to set it is to run saupdate.
>However I get this:
>
>fs0:\> saupdate set_mode p410 raid
>
>WARNING:Changing controller mode could result in DATA LOSS!!!
>Key in 'YES' to continue or 'NO' to quit:yes
>
>SAUPDATE supports changing of controller mode only for P410i and P411
>controllers.The controller at 0:61:0:0 is not a P410i or a P411, hence
>its mode cannot be changed
>
>fs0:\> saupdate list
>
>********************************************************************************
> Smart Array Offline Firmware Update Utility
> Version 2.11.08.00
>
> (C) Copyright 2009 Hewlett-Packard Development Company, L.P.
>********************************************************************************
>
> Searching and Connecting Smart Array Controllers...
>
>********************************************************************************
> Smart Array Offline Firmware Update Utility
> Version 2.11.08.00
>
> (C) Copyright 2009 Hewlett-Packard Development Company, L.P.
>********************************************************************************
>
> Seg Bus Dev Func Description Version Build
> (WWN)
>
> 0 61 0 0 HP Smart Array P410 6.64 0
> (0x0000000000000000)
>
>
>
>fs0:\> saupdate get_mode 0:61:0:0
>
>SAUPDATE supports querying of controller mode only for P410i and P411
>controllers.The controller at 0:61:0:0 is not a P410i or a P411, hence
>its current mode cannot be obtained
>
>
>So apparently saupdate can't handle a plain P410. I'm using the
>saupdate that comes with the firmware upgrade that you linked to for
>the 6.64 Smart Array.
>
>Another post said that the drvcfg utility in EFI would do it so I tried
>that
>
>
> T D
>D Y C I
>R P F A
>V VERSION E G G #D #C DRIVER NAME IMAGE NAME
>== ======== = = = == == ===================================
>===================
>11 00000010 B - - 7 13 PCI Bus Driver PciBus
>1C 00000358 B X X 1 5 Smart Array SAS Driver v3.58 PciRom
>Seg=00000000
>
>fs0:\> drvcfg -s 98 1C
>drvcfg: Invalid handle 98
>
>But that doesn't work either.
>
>All of this is a moot point as now the ZX6000 will not start up. It
>runs for a about 45 seconds and powers back down with this message in
>the System Logs:
>
>Waiting for new events...
>01 Jan 1998 14:05:18
>Alert Level 3: Warning
>Keyword: Type-02 040601 263681
>Fan speed lags
>Logged by: Baseboard Management Controller;
> Sensor: Fan - Fan 1R (Power)
>Data1: Performance Lags
>0x2034ABA29E020740 FFFF0106E8040300
>
>01 Jan 1998 14:05:18
>Alert Level 3: Warning
>Keyword: Type-02 040601 263681
>Fan speed lags
>Logged by: Baseboard Management Controller;
> Sensor: Fan - Fan 1L (Power)
>Data1: Performance Lags
>0x2034ABA29E020750 FFFF0106E9040300
>
>
>So apparently I have an issue with the power supply fans. It has only
>one power supply so I'm not sure where the 1R and 1L come from. That
>nomenclature doesn't match the other fans in the chassis which are 1A,
>1B, 2 and 3. I have two used power supplies on order but won't be here
>for a week.
>
>
>
>--
>John H. Reinhardt
>_______________________________________________
>Info-vax mailing list
>Info-vax at rbnsn.com
>http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
More information about the Info-vax
mailing list