08-08-2015
In my experience most "long beeps" are generated by the hardware's BIOS and indicate memory problems. I would recommend you re-seat all the RAM memory first (in case of a simple poor connection between the memory module and the motherboard), followed by selected removal and testing of a subset of memory modules until the beeps cease. Of course, I could be completely wrong.
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi friends,
i am getting the following error while booting my system which has SCo UNIX .
=========================
H iinit
PANIC: srmountfun-Error 22
mounting of rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages.
Dump not completed.
safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies
2. SCO
hi, i m a newbie and installed sco unix on my machine. Also i installed win-xp. i tried to modify the boot.ini file but it does not give me a choice in the begining.
please guide me on this. do we get a boot loader for unix like LILO or GRUB?
:confused: (3 Replies)
Discussion started by: 187final
3 Replies
3. SCO
anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Discussion started by: format
5 Replies
4. HP-UX
I am new to HP-UX. I have a external SCSI drive with HP-UX on it. I was trying to clone it to another external scsi drive. I added the new drive to existing LVM. Then I used dd command. But it failed with I/O error. Now I cannot boot it from original drive. It's saying panic: LVM: Configuration... (11 Replies)
Discussion started by: forhad
11 Replies
5. SCO
Hi i have a problem after boot with N1 disk and putting N2 disk and pressing the enter in this message:Insert N2(filesystem) floppy and press after by this(pressing enter) the system is reboot!! why??? :confused:
my old pc is a Pentium II 333mhz 3gb hd 64mb ram
please help!! :( (3 Replies)
Discussion started by: panos_pit
3 Replies
6. SCO
Our system is not booting up properly. It keeps going to this screen:
Enter Run Level (0-6, s or S):
I tried to hit all nos# 0-6 is just goes to hung state.
Tried s or S & it brings me to single user mode. I've checked the file systems & found out that all three had 98%. I tried to... (86 Replies)
Discussion started by: jedimaster
86 Replies
7. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
8. SCO
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
9. UNIX for Advanced & Expert Users
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
10. SCO
hi
i have image SCo Unix 5.0.6 and I want transfer on my HP ML350 G5
after Transfer show this message :
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
this hp server used smart array E200i and P400 and sco not recognized HDD
tanks (7 Replies)
Discussion started by: moein.mojtaba
7 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