Sponsored Content
Operating Systems Solaris Failed to identify flash rom on Sunfire V240 running Solaris 10 Post 303012549 by myrpthidesis on Monday 5th of February 2018 11:52:59 PM
Old 02-06-2018
Failed to identify flash rom on Sunfire V240 running Solaris 10

Hi Guys,

I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one).
May I know what the reason of this error and how can I fix it so I can upgrade ALOM using 1.6.10 version?

OBP : OBP 4.30.4.a 2010/01/06 14:48 Sun Fire V210/V240,Netra 210/240
ALOM : Advanced Lights Out Manager v1.6.10

Working system
---------------------
Code:
root:/usr/platform/SUNW,Sun-Fire-V240/lib/images> /usr/platform/`uname -i`/sbin/scadm download alommainfw
Copying self to RAM...Done.
Jumping to RAM.
Waiting for boot protocol message...
Got OBP:bootinit msg, dat2 = 00000002
AMD flash ROM
Receiving segment 00000001
Receiving segment 00000002
Receiving segment 00000003
Receiving segment 00000004

Failed system
------------------
Code:
root # /usr/platform/`uname -i`/sbin/scadm download boot alombootfw
Copying self to RAM...Done.
Jumping to RAM.
Waiting for boot protocol message...
Got OBP:bootinit msg, dat2 = 00000001
Failed to identify flash ROM!  <---- getting this error
Waiting for boot protocol message...

I tried cold reboot the server and try to update again but still having same issue.

Thanks for any help and advise!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing Solaris 9 on Sunfire V240

Hey guys, I had a Sunfire V240 with Solaris 10 preinstalled but replaced the original 2 -73g harddrives with 2 146g drives now I'm trying to install Solaris 9 which I want to use not 10. Now I keep getting this error: Rebooting with command: boot Boot device: disk0:a File and args: The... (2 Replies)
Discussion started by: kingdbag
2 Replies

2. UNIX for Dummies Questions & Answers

Jumpstart Sunfire V240

Hi, I trying to jumpstart SunFire V240 Solaris 10, 2006_01. All the jumpstart files on jumpstart install and boot server are ok (tested on another machine Sun Ultra 10). But this system comes out with: "The file just loaded does not appear to be executable." after "boot net - install" and setting... (0 Replies)
Discussion started by: jump
0 Replies

3. Solaris

SunFire V245, External CD/DVD-ROM, Solaris Install

Hey all. Wondering - I have a pair of V245's with no internal CD/DVD-ROM drives, and I want to install the latest/greatest Solaris 10. Booting these machines with an external drive plugged in via USB does no good. Is jumpstart or installing internal drives the only alternative? I'm a... (1 Reply)
Discussion started by: b1f30
1 Replies

4. Hardware

Need Help connecting to sunfire v240

I recently acquired a sunfire v240 and I'm trying to get into it so I can install linux on it. Right now I'm still trying to get a monitor connected so I can do this. I've tried connecting to it with a crossover cable to my laptop (vista and linux equipped). I was able to get a connection... (2 Replies)
Discussion started by: QuadRunner750
2 Replies

5. Solaris

How to boot from Cd-rom in Server Sunfire v250?

Howto boot from Cd-rom in Server Sunfire v250? The system can't boot because the filesystem is corrupt. The system say: run manually fsck -F ufs /dev/rdsk/c0t0d0s5 But, I don't now how to make this. I tried use stop + a, but nothing hapend. Someone can I help? (13 Replies)
Discussion started by: vigux
13 Replies

6. Solaris

SUNFIRE V240 procedure to shutdown with safety in order to replace power cables

Question: Which commands to use to shutdown with safety the server; (2 Replies)
Discussion started by: doudou2012
2 Replies

7. UNIX for Dummies Questions & Answers

Installing Solaris 10 on sunfire v240

please help, I am a Linux newbie and I have a sunfire v240 that I got used with the hard drives removed and I am hoping to install Solaris 10 on it to learn. I bought 2 scsi hard drives which are the exact replacement for the machine. I've installed the hard drives and have downloaded Solaris 10... (9 Replies)
Discussion started by: nodgeman
9 Replies

8. Solaris

SunFire V240 CPU Heat Sink Replacement

I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies

9. Solaris

Solaris 10 luupgrade flash archive file system creation failed

Hey guys, I'm attempting to migrate us to a new box. First problem I had was the change in architecture going from sun4u to sun4v, we have a Sun M5000 and are moving to a Fujitsu M10-4. I figured out how to make the flash archive work between architectures. Now I appear to be running into an... (2 Replies)
Discussion started by: kaledragule
2 Replies

10. Solaris

Question on selling/unloading Sunfire V240

Over 6 years ago I picked up a Sunfire V240 from my employer who was unloading all of their Sun hardware. Two processors, 4GB RAM and half dozen SCSI disk drives. It doesn't have an OS or a CD Rom/DVD drive. I have a collection of SCSI drives that should work with the server. So if I can get... (2 Replies)
Discussion started by: gandolf989
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 05:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy