Sponsored Content
Operating Systems HP-UX hp 9000 k class server not booting Post 302152264 by Perderabo on Wednesday 19th of December 2007 09:27:39 AM
Old 12-19-2007
First, read Owner’s Guide K Class HP9000 Enterprise Servers.

Your comment about the keyboard doesn't make sense. The keyboard comes with the terminal. But any ascii terminal will do, including a pc running hyperterminal. "INIT", as mentioned in the manual, means it is initializing. If it is set up to check all of memory this can take a very long time. Keep your hands in your pockets and leave it alone until it says something else. HP can decode the C440 to tell you exactly what it is doing, but I happen to know that the C in the code stands for "checking".
 

10 More Discussions You Might Find Interesting

1. HP-UX

D Class HP 9000 Server Setup

I work for a school and just received a set of HP-UX machines. I did ok with the Vizualize workstations in that they had video cards and all, but I am attempting to set up the D Class (D250) servers that we received and they are terminal only. I have the terminals and keyboards for them, but am... (11 Replies)
Discussion started by: NoHope
11 Replies

2. Solaris

Booting Up Servers from the Terminal Server.

All, I have a problem with booting up of servers. I am involved in application programming(Perl/Shell), but don't have much hardware knowledge about the Sun Solaris Server's we use. Our Development Servers are located at a remote place from the Development Centre. Every time there is a Power... (1 Reply)
Discussion started by: rahulrathod
1 Replies

3. Filesystems, Disks and Memory

HBA compatible on Emulex Lightpulse 9000 with IBM 8840 PKU X346 server.

Hi there, does anybody knows/info on compatiblity on Emulex Lightpulse 9000 with IBM 8840 PKU X346 server. Regards. (0 Replies)
Discussion started by: gagasan_makmur
0 Replies

4. UNIX for Dummies Questions & Answers

HP 9000 rp7420 server

Hi all, I'm trying to find out info on HP 9000 rp7420 server. 16-way rp7420 server - what does 16-way stand for? There is 32-way rpxxxx also. I searched www.hp.com site but no luck. Can anyone put some light in it pls. Thanks in advance (3 Replies)
Discussion started by: mhbd
3 Replies

5. HP-UX

urgent help needed on HP 9000 rp3410 server for a newbie

Hi friends i dont know whether it is the right forum to ask this or not. if its not please excuse me and please give me the link for such a forum. i am novice about HP 9000 rp3410 server and its things but i had to install and configure it. I came to know that it doesnot comes with builtin... (4 Replies)
Discussion started by: bnaravinda
4 Replies

6. Solaris

Server is not booting

I have setup NIS+ server and Client on my server and after I reboot. It is not booting. What may be the problem? (3 Replies)
Discussion started by: mokkan
3 Replies

7. UNIX for Dummies Questions & Answers

Sun Server: loop while booting

Hello Everyone, First: English is not my native language, sorry. I was given today on the work of a SUN Enterprse 220r, then I was going to install Debian-sparc, but the server remains in the boot process in a loop of the Fork interpreter depends (begin to load with power-up) starts the... (4 Replies)
Discussion started by: snap
4 Replies

8. Solaris

Sun E420R server not booting

Hi all, I am getting boot time message for sun E420R server. I need urgent help. Hardware Power ON CPU Offline (not present) Master CPU : 0000.0001.0055.11a0 CPU Offline (not present) CPU Offline (not present) Master E$ : 0000.0000.0040.0000 Button Power ON (0 Replies)
Discussion started by: PUSHPARAJA
0 Replies

9. Solaris

Zones not booting after server reboot

Hello guys This is my first post. I have very little experience and I woud appreciate your input on this problem. I have a server running Solaris 10. In that server I have 2 zones that work perfectly fine, however, if I reboot the server, the zones don't boot and I have to do it manually. i... (12 Replies)
Discussion started by: designbc
12 Replies

10. Solaris

Sun Server not booting into OS

Hello I have an old sun fire v250 server that I am trying to revive. I am trying to boot it from cdrom to install the OS (Solaris 10). The original data in the disk is corrupt and I am trying to do a new clean install. However I encounter the following errors. Does it look like the disk itself... (1 Reply)
Discussion started by: br1an
1 Replies
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy