This is a discussion on Problem updating bios V20Z. SP went ok, bios won't go and machines won't start anymore within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Hi, Got three V20Z's here, which needed a SP/BIOS update. All updated to 2.4.0.10 SP without problem One of ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, Got three V20Z's here, which needed a SP/BIOS update. All updated to 2.4.0.10 SP without problem One of them updated BIOS to 1.35.2.2 without problem. The other two didn't want there BIOS updated. What even makes it worse is that they won't start at all anymore! Tried all sort's of things, resetting SP, clearing CMOS, reverting SP to older versios, etc. etc. Nothing which solved it This is what it shows when I try to update localhost $ platform set os state update-bios /mnt/sw_images/platform/firmware/bios/V1.35.2.2/bios.sp This command may take several minutes. Please be patient. Bios started Error. The operation timed out. When I try to boot it gives about the same localhost $ platform set os state boot -b This command may take several minutes. Please be patient. Error. The operation timed out. localhost $ for more info: localhost $ sp get port80 0x97 localhost $ and while booting localhost $ sp get port80 -m 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x80 0x81 0x83 0x84 0x85 0x86 0x87 0xc3 0xc2 0x02 0xc8 0xc9 0x88 0x8c 0x28 0x8d 0x8e 0x90 0x94 0x98 0x95 0x97 So it seems to be stuck there.at 0x97 which is according to the docs: 97 Fix up multiprocessor tabel One of the systems has one cpu, the other has two cpus localhost $ inventory get all Name Revision Install Date Description Diagnostics V2.4.0.6 Wed Dec 24 10:52:49 1969 Server Diagnostics BIOS-V20z V1.32.7.2 Fri Sep 30 11:02:00 2005 Platform BIOS for V20z servers SP Value-Add V2.4.0.10 Mon Jul 17 11:57:27 2006 SP Value-Add Software SP Base V2.4.0.10 Mon Jul 17 11:57:27 2006 SP Base Software Name Type OEM Manufacture Date Hardware Revision Part # CPU 0 DIMM 0 memory c100000000000000 2005-03-26 020a 72D64300GBR5C CPU 0 DIMM 1 memory ce00000000000000 2004-09-02 3045 M3 12L6420EG0-CB3 CPU 0 DIMM 2 memory 2cffffffffffffff 2005-04-02 0300 18VDDF6472G-335G3 CPU 0 DIMM 3 memory c100000000000000 2005-03-26 020a 72D64300GBR5C DDR 0 VRM memvrm S-SCI448 2005-06-24 A01 S01479 CPU 0 VRM vrm S-SCI448 2005-06-26 A01 S02325 CPU 1 DIMM 0 memory c100000000000000 2005-03-26 020a 72D64300GBR5C CPU 1 DIMM 1 memory ce00000000000000 2004-09-02 3045 M3 12L6420EG0-CB3 CPU 1 DIMM 2 memory 2cffffffffffffff 2005-04-02 0300 18VDDF6472G-335G3 CPU 1 DIMM 3 memory c100000000000000 2005-03-26 020a 72D64300GBR5C DDR 1 VRM memvrm S-SCI448 2005-06-26 A01 S01479 CPU 1 VRM vrm S-SCI448 2005-06-26 A01 S02325 PIC frontpanel NA Motherboard planar S-SCI448 2005-06-29 A02 S02615 PRS Software os 2006-07-17 97.0 Power supply power ACBEL 2005-04-18 A-01 S01899 SCSI backplane scsi_backplane S-SCI448 2005-06-19 A02 S01194 localhost $ Anyone an idea what could be wrong and how to fix this? Will call Sun tommorow, see what they can do... Marc |
| Thread Tools | |
| Display Modes | |
|
|