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
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)