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 Administration 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 ...
| |||||||
| Register | 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 |
| ||||
| PE2DOC wrote: > 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 happened to me when I tried to u/g my BIOS remotely. There is a recovery procedure but it requires physical access to the v20z. From Sun support: --- Procedure how to go back to the factory settings of the operating system of the Service Processor. Open the Sun Fire[TM] V20z chassis and connect the pins 1 and 2 at jumper 19. This will send the console output of the service processor to the serial port. Where to locate jumper 19 on the motherboard is described in document 817-5248 Sun Fire V20z and Sun Fire V40z Servers User Guide, which you can find here: http://www.sun.com/products-n-soluti...Sun_Fire_V20z/ -> chapter 4.5 Sun Fire V20z Indicators, Switches, and Jumpers Connect a PC or a laptop with a communication program like "CU" or "Minicom" for Linux or "Hyperterm" for MS Windows with a null-modem serial cable to the serial port on the V20z at the back (how to use/install Minicom). Important: The baud rate of the communication program must be set to 115200. Boot the service processor by using the [//] button on the back. Immediately look onto the serial port session of your communication program, because the interrupt of the boot process is only 4 sec. A prompt will be displayed on the console output. At the prompt type the command "spfactory" and hit [Enter]. Then reset the service processor by typing "reset" at the prompt and hit [Enter]. Look at the operator panel/LCD panel and follow the steps described in document 817-5246 Sun Fire V20z and Sun Fire V40z Servers Installation Guide, which you can find here: http://www.sun.com/products-n-soluti...Sun_Fire_V20z/ -> chapter 2. Configuring the Service Processor. on how to configure the Service Processor. Finally remove the Connector from Jumper 19 to get the output of the system to the serial port instead of the service processor which is the default. --- After I did the reset, I was able to try the BIOS u/g again. This time it worked (since I had to be onsite :-(). Good luck! -- Sak Wathanasin Network Analysis Limited http://www.network-analysis.ltd.uk |