8 More Discussions You Might Find Interesting
1. Red Hat
Server Model
HP Proliant DL380P, Gen 8
Raid Controller= HP smart Array P420i
Operating system Installation OEl5.8
On first boot after OS installation
ERROR:
Red Hat nash Version 5.119.6 starting -300.10.1.el5uek)'
Mounting proc Filesystem
Reading all physical volume this may take... (1 Reply)
Discussion started by: sohail Jafferi
1 Replies
2. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
3. Solaris
Hi all,
i have problem when booting my sun fire V240 with solaris 10.
the errors are follow:
################################################################
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_125100-10 64-bit
Copyright... (0 Replies)
Discussion started by: faberarnold
0 Replies
4. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
5. AIX
Hi all,
I have one booting problem with an AIX machine. It is not booting.
It is showing error B1014602 on OK prompt.
Could you please tell me, what is the problem with it and its respective solution?
Thank you very much. (2 Replies)
Discussion started by: prashantchavan
2 Replies
6. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
7. UNIX for Dummies Questions & Answers
Hey all,
When loading a Sun Ultra 60 I got running Solaris 9 I get a error. This error will only happen when I have a external CD-RW drive attached.
The error is;
Failed to power up sd21, see your administrator or reboot
I have rebooted and well I am the administrator for this machine.... (5 Replies)
Discussion started by: merlin
5 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I'm getting this error when booting:
" Timeout waiting for ARP/RARP packet"
I got no idea what has been done to get it when the machine use to work fine. Put a new HDD in it, and installed Solaris 7 on it fine then when it goes to boot I get that error.
It's a Sparc Station 5... (2 Replies)
Discussion started by: merlin
2 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