10-08-2011
Sun fire 4270 reset BIOS settings after reboot
Hello,
I am trying to perform Suse 10 SP3 installation via network in 6 Sun Fire 4270 M2 servers.
The problem is that even if i set first prio boot device the hard disk the system always try to boot from network.And after the first restart the BIOS setting has been lost(and PXE come first ptio boot device as the default settings)...
Have you ever met a similar situaton?
Thanks in advance for any help.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I'm lost and can't figure this problem out.
I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies
2. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
3. Filesystems, Disks and Memory
Hello,
I wanted to share an experience I had today which was quite a learning experience and perhaps useful for others who may run into the issue at some point in the future.
Basically, the scenario involves a OS which was installed on a machine which hardware-wise, had a SATA Drive. The... (0 Replies)
Discussion started by: septima.pars
0 Replies
4. Solaris
Hi,
I want to know if there is a command available for obtaining the BIOS Serial Number on a Sun Fire V240 machine? Or is it a known issue that it cannot be obtained through any command?
Thanks,
Vineet (4 Replies)
Discussion started by: vineetd
4 Replies
5. Hardware
Hi I have the above machine, which is exhibiting the classic cpu fan pulsing issue. It seems I need to apply a BIOS update to the machine, from a CD that was formerly a free download from Sun, but now Oracle has taken over you need a support contract to get it. This machine is now very out of... (4 Replies)
Discussion started by: ZaphodB
4 Replies
6. Solaris
So I have a lot of equipment in San Diego racks and there was a recent county-wide black out. Our data racks are supposedly on diesel generators. Most everything made it through the outage just fine without any issue.
But for whatever reason, one of our X4540's developed a quirky habit of... (3 Replies)
Discussion started by: genkuro
3 Replies
7. Solaris
==============================
ALOM BOOTMON v1.3.1
ALOM Build Release: 001
Reset register: f0000000 EHRS ESRS LLRS SWRS
ALOM POST 1.0
Dual Port Memory Test, PASSED.
TTY External - Internal Loopback Test
TTY External - Internal Loopback Test, PASSED.
TTYC - Internal Loopback Test
TTYC -... (4 Replies)
Discussion started by: Sameer Naik
4 Replies
8. Solaris
Hi Guys,
I need to reboot one Server as the newly inserted disk is not getting detected in system , I have also confirmed with Sun Support and finally it was the reboot which was required after doing all troubleshooting stuff.
So I have disassembled the mirror and kept working disk's single... (3 Replies)
Discussion started by: manalisharmabe
3 Replies
9. Solaris
I switched on the power to the server. But, the server did not power on i.e., none of the 3 LEDs on the front panel is lighted.
(Power supplies are showing only amber LEDs with "Ready to remove" sign).
I tried to turn on the power supplies via System Controller menu (platform shell), but it... (6 Replies)
Discussion started by: solind
6 Replies
10. Solaris
Hello,
I have purchaced an old SUn fire x2270 server .
I wanted to make ILOM upgrade to the latest version of software :
ILOM 3.0.9.18.a r126592
BIOS vers. 2.09
Server 2.2.3
(10-Aug-2018)
Because my version is very outdated.
But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)