Sponsored Content
Operating Systems AIX Problem after updating the firmware! Post 302851873 by Mohannad on Tuesday 10th of September 2013 01:25:18 AM
Old 09-10-2013
Problem after updating the firmware!

Hello AIX experts,

I have 7038-6M2 server, its operating system is AIX 5.2, and its firmware is 3K041021
After some searching on net, I tried to update its firmware level to 3K080425, so I downloaded the required rpm, and followed the steps.
After rebooting the server, it stopped and an error code appeared on its LED, the error code is: E1F0
I rebooted it again, it stopped some minutes on the same error, then some green texts appeared then I choose to login into single user mode.
Then I rebooted it for the third time, but no response!!

What is happened?! and what is the solution?!
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Problem in updating .profile file in HP-UX B.11.00 machine

Hello All, I am using a HP-UX machine and I want to update the .profile file so that after login to my userID that will be applicable to my ID also. What I am trying to do is : In .profile file I am trying to write in /home/userID folder: export PATH=$PATH:$HOME:. so that whenever I will... (3 Replies)
Discussion started by: abhishek0071
3 Replies

2. Shell Programming and Scripting

Updating System Firmware

Alright we have a strange problem that i never encountered. We have a V445 Sun Fire we are trying to install it via a tadpole laptop (jumpstart laptop) the v445 takes the flash just fine, but we get an error upon reboot saying unable to locate boot device. Well our SUN guru said we need to... (2 Replies)
Discussion started by: deaconf19
2 Replies

3. Shell Programming and Scripting

awk updating one file with another, comparing, updating

Hello, I read and search through this wonderful forum and tried different approaches but it seems I lack some knowledge and neurones ^^ Here is what I'm trying to achieve : file1: test filea 3495; test fileb 4578; test filec 7689; test filey 9978; test filez 12300; file2: test filea... (11 Replies)
Discussion started by: mecano
11 Replies

4. Solaris

Error updating Firmware in X4500

I have X4500 machine with solaris 10 OS and software version 5.10. The firmware version is 1.1.1 and I am planning to upgrade the firmware. C H A P T E R 1 - Flash Upgrading Your Server to Software Release 1.2 I referred to the above link to do so. But, I do not understand what is the... (6 Replies)
Discussion started by: bharu_sri
6 Replies

5. Solaris

Problem with Upgrading firmware on X4500

I have X4500 running solaris 10 with 5.10 version. The ILOM version is 1.1.1 and I want to upgrade the firmware. I setup the TFTP server on my machine using the following link. A P P E N D I X C - Updating the Firmware I could install the tftp server and could transfer a file as well. When I... (1 Reply)
Discussion started by: bharu_sri
1 Replies

6. BSD

Firewall Build: Problem Updating, Patching

In building a firewall, I need to update and patch the operating system after the initial install. However, the compiler and sources should never be on a firewall PC. So what is the best way to do this ? This firewall PC has 2 identical drives; I was thinking of performing 2 installs, updating... (2 Replies)
Discussion started by: larsuuber
2 Replies

7. Shell Programming and Scripting

Problem Executing Firmware Command using Shell Script

Guys, I have a script that should change one of the configuration Parameter in a http accelerator, this config change which will halt http traffic into device. So I have designed a script which should do these changes. But after executing this script, found that one of the input variable is not... (8 Replies)
Discussion started by: raghunsi
8 Replies

8. AIX

Problem updating AIX 4.3.3 ML0 to ML11 - Error 0503-248

I am trying to apply Maintenance Level 11 to one of our older AIX machines that is currently at ML0. When I try to install the bos.rte.install for ML11 it gives the error 0503-248 stating: Verifying requisites... 0503-248 installp: Error: A fileset has parts that are different from one or more... (0 Replies)
Discussion started by: DMcNutt
0 Replies

9. UNIX for Beginners Questions & Answers

HP UX firmware

Does unix servers need firmware updation regularly for smooth functioning? (2 Replies)
Discussion started by: manjeeteast
2 Replies
UPSLUG2(8)						      System Manager's Manual							UPSLUG2(8)

NAME
upslug2 - utility to upgrade the firmware of a NSLU2 via the network SYNOPSIS
upslug2 [options] DESCRIPTION
upslug2 is a command line program intended to allow the upgrade the firmware of a Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) to new or different versions. When a NSLU2 in the local network is put in upgrade mode, upslug2 can connect to it and upload a new firmware. upslug2 will accept a full firmware image but it can also upgrade the flash from individual files holding the kernel, ramdisk and root filesystem. upslug2 provides status information during the upgrade process and verifies the written image after the upgrade. OPTIONS
-C, --Complete-reprogram Reprogram the complete flash, including the RedBoot boot loader and the SysConf partition holding configuration information. Using this option may result in the NSLU2 becoming permanently unusable! By default, upslug2 will not touch these two partitions since this allows flashing a new firmware if an uploaded firmware does not work. This is not possible if RedBoot itself is damaged. Use with caution. -d, --device The network device on the host machine connected to the network on which the NSLU2 is located. (Default: eth0). -e, --endian The endianness of the files to be uploaded. upslug2 will usually detected the endianness automatically but this option can be used to force byte swapping to occur. This option accepts three values, separated by comma: endianness of kernel, data and RedBoot FIS directory. Valid values are l (little endian), p (pdp endian) and b (big endian). (Default: ,b,b) -f, --from The MAC address of the host system. -h, --help Show summary of options. -i, --image The complete flash image to use. -j, --rootfs A root filesystem, usually of type jffs. -k, --kernel A compressed kernel zImage image. -n, --no-reboot Do not reboot after upgrade -p, --payload FIS directory payload. There are about 140 Kb in the last block (between the FIS dir and the trailer at the end) which can be used for data. -r, --ramdisk A compressed ramdisk image. -R, --ram-payload A ram paylod (replaced ramdisk). (FIXME: if it replaced the ramdisk, why cannot you just use the -r option? What's the difference) -t, --target The MAC address of the NSLU2 to upgrade. Without this option, upslug2 will only perform an upgrade if there is just one NSLU2 in upgrade mode. -U, --no-verify Do not verify the image, only upgrade. -v, --verify Do not write to flash, only verify the image. Options to specify firmware information The following options should be used when individual kernel, ramdisk and root filesystem files are specified rather than a complete firmware image. -E, --extra-version Extra version information, a 2 byte value. (Default: 0x90f7) -F, --firmware-version The firmware version, a 2 byte value. (Default: 0x2329) -P, --product-id The product ID, a 2 byte value. (Default: 1) -T, --protocol-id The protocol ID, a 2 byte value. (Default: 0) USING UPSLUG2 In order to use upslug2 the NSLU2 which is to be upgraded has to be put in upgrade mode: 1. Disconnect any disks and/or devices from the USB ports. 2. Power off the NSLU2 3. Press and hold the reset button (accessible through the small hole on the back just above the power input). 4. Press and release the power button to power on the NSLU2. 5. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset but- ton. 6. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green after step four it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull the power, reconnect it and repeat from the second step. Once the NSLU2 is in upgrade mode it will remain in this state until either the power is connected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode EXAMPLES
The most common use of upslug2 is the following: upslug2 --image NSLU2_V23R63.bin This specifies a complete firmware image which will be written to flash. Alternatively, kernel, ramdisk and root filesystem can be specified individually: upslug2 -k nslu2-zImage -r ramdisk -j root.jffs In this case, the options -E, -F, -P and -T should typically be specified as well. By default, upslug2 will search for the NSLU2 on the network on your eth0 network interface. If the network is on a different interface, you can easily specify it: upslug2 -d eth1 --image NSLU2_V23R63.bin If there are potentially more than one NSLU2 in your network which may be in upgrade mode, you can specify its MAC address: upslug2 -t 00:11:85:12:34:56 --image NSLU2_V23R63.bin SEE ALSO
slugimage(1) AUTHOR
John Bowler <jbowler@acm.org> January 2006 UPSLUG2(8)
All times are GMT -4. The time now is 09:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy