10-07-2009
i hav already changed the scsi hard disk, hardware raid card, ram, scsi cd drive.. but it's still not working.........
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below:
/pci@8,600000/SUNW,qlc@2
LiD HA LUN --- Port WWN --- ----- Disk description -----
0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies
2. SCO
hi all
i use sco open server reliseas 5 on my system i get an image from system hard disk to another hard disk with acronis software and start system with new(backup)hard disk, but during the boot process some errors generate as follow
warning:hd:noroot disk controler was found
hd:a boot-time... (2 Replies)
Discussion started by: mehran_malek
2 Replies
3. HP-UX
Replace an unknown status controller on HP FC60 disk array
Author:JoyOnline JoyChangLu@gmail.com
Trouble description:
The users detected that the status of controller at A is unknown.
Analysis and diagnostic:
Physical observed all leds on enclosure of disk array is normal.
The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies
4. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
5. Solaris
hi all
i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies
6. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
7. Solaris
I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all.
How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. Solaris
Hi
The scenario in the oracle t4-1 hardware with solaris 10 is as follows:
1. The initial install on the server was performed with an incorrect disk layout.
2. New disks were ordered and slot into the server.
3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 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)