hi
i can't boot my sun server by iso solaris 10 sparc dvd that i did download from oracle site.
my hardware is sun T5220.
i receive these after running boot cdrom -s :
whould u help me?
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 03-02-2019 at 11:59 AM..
Reason: Added CODE tags.
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
I have an x86 Sun server, with no CDROM drive and no OS currently loaded on it. I need to install CentOS on it... trying to figure out how to do that.
I've heard there are ways to connect to the serial management port, and mount a laptop's CDROM drive as a drive the server will recognize to... (0 Replies)
Hi Guyz,
I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso.
When trying to boot at the ok> boot cdrom
i get the following error:
-----------------------------------------------------------------------
Boot device:... (2 Replies)
Hello,
Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Hi everyone,
I have searched on google and sun documentation but it's still not clear for me; how do we boot a sun Solaris server?
I know what to do but only from this step:
1- start /SYS
2- start /SP/console
The system go to to the prompt OK, then we use the BOOT command.
My... (9 Replies)
One of our T5220 servers fail to boot due to following error:
ERROR: The following devices are disabled:
XAUI1
XAUI0
I can't see any disabled components in SP console, any idea what is the problem? (1 Reply)
I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode.
I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management.
Tinkering around I... (4 Replies)
Hi,
I want to install Solaris-11 on T5220. I created USB from sol-11_4-text-sparc.usb by usbcopy on another Solaris-11 servers, which looks like a good one.
I tried did "reset-all" and still same issue. Can I get some help on this.
{0} ok reset-all
Sun Netra T5220, No Keyboard
Copyright... (8 Replies)
Discussion started by: solaris_1977
8 Replies
LEARN ABOUT NETBSD
ndbootd
NDBOOTD(8) BSD System Manager's Manual NDBOOTD(8)NAME
ndbootd -- Sun Network Disk (ND) Protocol server
SYNOPSIS
ndbootd [-s boot2] [-i interface] [-w windowsize] [-d] boot1
DESCRIPTION
ndbootd is a server which supports the Sun Network Disk (ND) Protocol. This protocol was designed by Sun before they designed NFS. ND sim-
ply makes the raw blocks of a disk available to network clients. Contrast this with the true namespace and file abstractions that NFS pro-
vides.
The only reason you're likely to encounter ND nowadays is if you have an old Sun 2 machine, like the 2/120 or 2/50. The Sun 2 PROMs can only
use ND to boot over the network. (Later, the Sun 3 PROMs would use RARP and TFTP to boot over the network.)
ndbootd is a very simple ND server that only supports client reads for booting. It exports a disk that the clients consider to be /dev/ndp0
(ND public unit zero). The disk is available only to clients that are listed in /etc/ethers and have valid hostnames. (Sun 2 PROMs don't do
RARP, but they do learn their IP address from the first ND response they receive from the server.)
boot1 is a file containing the mandatory first-stage network boot program, typically /usr/mdec/bootyy. The layout of the exported disk is:
o block 0: normally a Sun disklabel (but ignored by the PROM)
o blocks 1-15: the first-stage network boot program
With the -s boot2 option, ndbootd will also make a second-stage network boot program available to clients, typically /usr/mdec/netboot. When
boot2 is a filename, that file is the single second-stage network boot program to be served to all clients.
When boot2 is a directory name, typically /tftpboot, ndbootd finds a client's second-stage network boot program by turning its IP address
into a filename in that directory, in the same manner later Sun 3 PROMs do when TFTPing (i.e., if a client has IP address 192.168.1.10,
ndbootd expects to find /tftpboot/C0A8010A.SUN2 ).
When used in this last manner with an ND-aware first-stage boot program, ndbootd serves the same purpose in the Sun 2 netboot process as
tftpd(8) serves in the Sun 3 netboot process.
Any second-stage network boot program always begins at block 16 of the exported disk, regardless of the length of the first-stage network
boot program.
All first- and second-stage network boot programs must have all executable headers stripped off; they must be raw binary programs.
The remaining options are:
-i interface
Only listen for ND clients on interface interface. Normally ndbootd listens for clients on the first non-loopback IP interface
that is up and running.
-w windowsize
This adjusts the window size of the ND protocol. This is the number of 1-kilobyte packets that can be transmitted before waiting
for an acknowledgement. Defaults to 6.
-d Run in debug mode. Debugging output goes to standard error and the server will not fork.
FILES
/etc/ethers
/etc/hosts
SEE ALSO tftpd(8)BUGS
Whether or not there is a second-stage network boot program, the exported disk appears to all clients to have infinite length. The content
of all blocks not used by the first- or second-stage network boot programs is undefined. All client reads of undefined blocks are silently
allowed by the server.
BSD May 9, 2001 BSD