Visit Our UNIX and Linux User Community

Operating Systems Solaris Cannot install Sun Solaris 10 on Ultra 10 Post 302406510 by incredible on Tuesday 23rd of March 2010 07:20:27 AM
Old 03-23-2010
system rebooted or panics?Im not sure if 40G disk is supported on an ultra 5 or 10. I only knew and seen of max 20G disk
 
Test Your Knowledge in Computers #1010
Difficulty: Easy
The number 200 in base 8 equals 128 in base 10.
True or False?

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Tape Drive Connected to a Sun Ultra 10/Solaris 2.7

I have a Sun Ultra 10/Solaris 2.7 with a differential SCSI card connected to a Supter DLt1 Tape Drive. When I boot the machine, and I do a probe-scsi-all in the very beginning of the boot process. It shows up correctly. If I wait for the boot process to proceed and then I do a probe-scsi-all, I get... (1 Reply)
Discussion started by: brv
1 Replies

2. UNIX Benchmarks

Sun Ultra 2 Solaris 8

Sparc Ultra2: Notes prtdiag: System Configuration: Sun Microsystems sun4u Sun Ultra 2 UPA/SBus (2 X UltraSPARC-II 296MHz) System clock frequency: 99 MHz Memory size: 768 Megabytes ========================= CPUs ========================= Run Ecache CPU CPU... (0 Replies)
Discussion started by: tnorth
0 Replies

3. UNIX Benchmarks

Sun Ultra 30 Solaris 8

Sun Ultra30 Solaris 8 Notes: ... Results: System -- SunOS box 5.8 Generic_108528-23 sun4u sparc SUNW,Ultra-30 Start Benchmark Run: Fri Sep 12 11:59:12 EDT 2003 1 interactive users. Dhrystone 2 without register variables 502087.7 lps (10 secs, 6 samples) Dhrystone 2 using... (2 Replies)
Discussion started by: tnorth
2 Replies

4. Solaris

How to install Sun Solaris 10 inside VMware Workstation 5.5

Some members asked about this way, click Here u will find what u want (1 Reply)
Discussion started by: Sound Of Wisdom
1 Replies

5. Solaris

Sun Solaris Ultra 10 Not booting!

Hello I have Sun Ultra 10 with Solaris 7 installed on it. Sometimes back after that the machine use to get hang .Even after rebooting the system was not booting. I have manually switch on /off many times from the power board itself .Once in a while it use to boot .After... (12 Replies)
Discussion started by: turki_00
12 Replies

6. Solaris

Problem after Install SUN solaris x86

after install solaris x86 on my computer success, but it can't boot. When the machine start, and i choose option 1 - default, it shows "W" on screen and system restart . Anyone can help me. My computer : dual core - 1gb ram - x86 (7 Replies)
Discussion started by: quan0509
7 Replies

7. Solaris

Sun Studio 11 install on Solaris 8 hanging

I am trying to install Sun Studio 11 on a Solaris 8 server. It gets through the install of patches then hangs with 20% of the overall install done and 0% of the software install done. It seems to be running /tmp/SolarisNativeToolkit_3.0.2_1 and is hanging. I have made multiple attempts and it... (6 Replies)
Discussion started by: jwilloughby
6 Replies

8. Solaris

SUN ULTRA 45 - Solaris

hi, my sun box hangs- KEYBOARD not found. Using hyper link it boots and then hangs without able to access or get ok promt ----SCREEN SHOT AS-------------------------------------------------- ˙Loading onboard drivers: ebus i2c i2c i2c ppm /ebus@1f,464000: flashprom rtc serial serial env-monitor... (2 Replies)
Discussion started by: mathav22
2 Replies

9. Solaris

Cannot install or run Solaris 8 on Sun Blade 150

Hi everybody, I'm having big troubles in installing Solaris 8 on a Sun Blade 150. Here are some system specs: Sun Blade 150 (UltraSPARC-IIe 550MHz) RAM: 256MB OBP 4.10.6 2003/06/06 12:30 POST 2.0.1 2001/08/23 17:13 When I try to boot from Solaris 8 CD with boot cdrom or... (10 Replies)
Discussion started by: Vortigern
10 Replies

10. Solaris

Sun Ray Install 5.4.5 on Solaris 11.3

I had an issue installing Sun Ray Server 5.4.5 on Solaris 11.3, and was unable to find an answer. However, I was able to noodle through it and got things running. So, for the benefit of the few that might be interested, here are the issues regarding installation of Sun Ray Server 5.4.5 on... (0 Replies)
Discussion started by: apljavaman
0 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)

Featured Tech Videos

All times are GMT -4. The time now is 11:27 PM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy