10-29-2008
the sun ultra spark 500mhz is the server single rack module i only have one of them and its this that is giving the problem.
it definatly says .silo.conf when i type in a boot device it says its not present in the silo.conf i assume a file that has the boot devices in perhaps
when i turn on the vachume cleaner (thats what i nick named the server as its soooo loud) it takes about 10secs for the screen to come on when it does it says a sort of bios
openboot 4
silo version 1.4.10
boot device /pc@if, 0/ pci@1, 1/ide@d/disk@0,0:a
boot:
10 More Discussions You Might Find Interesting
1. Solaris
Hey All
Thanks in Advance.
Iam facing a problem with Netra T1 105 Ram issuse.I have 1 gb ram in the server but when it boots up in ok prompt or in banner it shows 768 mb Ram , if i put 512 mb Ram it show 368 mb Ram but this all ram if i connect in anthore netra server its shows 1 gb and... (1 Reply)
Discussion started by: solaris8in
1 Replies
2. Solaris
Hello,
I wrote a script which monitor the keyswitch state repeatedly each 10 minutes.
I'm extracting the keyswitch status by using prtdiag.
The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status.
unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Debian
Comments/Problems:
Machine boots from CDROM, starts SILO Version 1.4.13,
display welcome message (welcome to Debian GNU/Linux lenny!
built on 20081218-10:06 ).
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Loaded kernel version 2.6.26
Loading initial ramdisk... (3 Replies)
Discussion started by: mtk
3 Replies
5. Solaris
Looking for ideas on why I can't dial into our new Avaya CMS server (Sun Netra 210 - Sol 9) - remotely thru our ASA - site admin software.
Running R3-V13 Avaya CMS software - just did a fresh install of the CMS software - install went perfect.
The Sun supplied DB9 connector is installed... (1 Reply)
Discussion started by: drewmich
1 Replies
6. Solaris
Hi,
I have a netra t2000 running solaris 10. It is fully patched with the latest patch cluster and also patch 118833-36 and 126897-02. The SC sys_event level is set to 3.
I am running a test to show hardware log status, e.g simulating a power supply failure.Hence I unplug one of te... (3 Replies)
Discussion started by: ulemsee
3 Replies
7. Ubuntu
hello guys i bought a SPARC neutra system a couple of months ago and after failing to install solaris onto it (and leaving it as a door stop for a couple of months) decided to stick ubuntu onto it
for starters i dont own a sun keyboard i have a cheap pcline usb keyboard (it works... (3 Replies)
Discussion started by: garethmob
3 Replies
8. Solaris
Newbie question.
I've been running OpenSolaris on an Intel box for some time with great success.
I have just bought an old Sun Blade workstation with a corrupted version of Solaris 5 something on it.
The plan was to install OpenSolaris on it.
However beyond my skills, I see, as no Live CD (or... (10 Replies)
Discussion started by: lewtargett
10 Replies
9. Solaris
Hi All,
I had install the solaris 10 into the SUNFIRE V890 server, after installed, it keep rebooting.
I wish to enter the OK mode again, and install back the Solaris 10.
i had try the "break" button and "stop+A" button, but all fail.
kindly advice... (4 Replies)
Discussion started by: SmartAntz
4 Replies
10. Hardware
Hi guys,
when I power on my sun netra 240 server,
it displays these error messages:
1. Notice: cpu 0 has 2048/2048 MB of memory disabled.
2. Error : The following devices are disabled dimm1.
Please can anyone be kind enough to explain this for me?
Thanks (2 Replies)
Discussion started by: cjashu
2 Replies
LEARN ABOUT MOJAVE
installgrub
installgrub(1M) installgrub(1M)
NAME
installgrub - install GRUB in a disk partition or a floppy
SYNOPSIS
/sbin/installgrub [-fm] stage1 stage2 raw-device
The installgrub command is an -only program. GRUB stands for GRand Unified Bootloader.
installgrub installs GRUB stage 1 and stage 2 files on the boot area of a disk partition. If you specify the -m option, installgrub
installs the stage 1 file on the master boot sector of the disk.
The installgrub command accepts the following options:
-f
Suppresses interaction when overwriting the master boot sector.
-m
Installs GRUB stage1 on the master boot sector interactively.
The installgrub command accepts the following operands:
stage1
The name of the GRUB stage 1 file.
stage2
The name of the GRUB stage 2 file.
raw-device
The name of the device onto which GRUB code is to be installed. It must be a character device that is readable and writable. For disk
devices, specify the slice where the GRUB menu file is located. (For Solaris it is the root slice.) For a floppy disk, it is
/dev/rdiskette.
Example 1: Installing GRUB on a Hard Disk Slice
The following command installs GRUB on a system where the root slice is c0d0s0:
example# /sbin/installgrub /boot/grub/stage1
/boot/grub/stage2 /dev/rdsk/c0d0s0
Example 2: Installing GRUB on a Floppy
The following command installs GRUB on a formatted floppy:
example# mount -F pcfs /dev/diskette /mnt
# mkdir -p /mnt/boot/grub
# cp /boot/grub/* /mnt/boot/grub
# umount /mnt
# cd /boot/grub
# /sbin/installgrub stage1 stage2 /dev/rdiskette
/boot/grub
Directory where GRUB files reside.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
boot(1M), fdisk(1M), fmthard(1M), kernel(1M), attributes(5)
Installing GRUB on the master boot sector (-m option) overrides any boot manager currently installed on the machine. The system will always
boot the GRUB in the Solaris partition regardless of which fdisk partition is active.
24 May 2005 installgrub(1M)