Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Sun 280R unable to boot
Special Forums Hardware Sun 280R unable to boot Post 302468228 by soliberus on Tuesday 2nd of November 2010 06:11:20 AM
Old 11-02-2010
Sun 280R unable to boot
I have a problem with one of my Sun 280R servers.

I'm unable to boot it. I've managed to get to the {ok} prompt from the RSC card.

Please see output below

Code:
ok show-devs
/virtual-memory
/memory
/aliases
/options
/openprom
/chosen
/packages
/openprom/client-services
/packages/dropins
/packages/SUNW,debug
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,builtin-drivers
ok showdevs
showdevs ?
ok show-devs
/virtual-memory
/memory
/aliases
/options
/openprom
/chosen
/packages
/openprom/client-services
/packages/dropins
/packages/SUNW,debug
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,builtin-drivers
ok

Is my motherboard a goner?
Last edited by DukeNuke2; 11-02-2010 at 08:16 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

LaCie Big Disk configuration on SUN 280R

hi , i am trying to configure LaCie Big Disk on solaris 9 running on a 280R server . i am trying to use the USB prot to connect to the external disk . please i need help on this as i have no clue on how and from where to start . thanks for ur help . cheers (0 Replies)
Discussion started by: ppass
0 Replies

2. Solaris

unable to boot from disk1

I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted Rebooting with command: boot disk1 Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args: SunOS Release 5.10 Version Generic_118833-24 64-bit Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies

3. UNIX for Dummies Questions & Answers

Sun Fire 280R

Hello all, I'm lost and can't figure this problem out. I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies

4. Solaris

Sun 280r serial number

is there a command i can run at the ksh that will give me the serial number on solaris? solaris 8, and 9 280r servers (16 Replies)
Discussion started by: BG_JrAdmin
16 Replies

5. Solaris

Install SUN O/S 5.9 on Sparc Sunfire 280R

Hi, I' trying to install O/S 5.9 on Sparc system Sunfire 280R. I downloaded CD install and CD 2 from Sun Website but later i dowloaded CD 2 that i forgot for my installation. All CD are in ISO formats. I boot system at OK prompt then issue OK boot cdrom when it asks for CD 1, i removed... (7 Replies)
Discussion started by: lamoul
7 Replies

6. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

7. Solaris

disks - Sun Enterprise 220R and SF 280R

Hi, I have SE 220R with 2 disks mirrored using SVM and running OS - solaris 9. Because of performance issues on 220R I'd like to move the OS/application data to SF 280R. Having found that SF280R will only support Fiber channel disks, I am now wondering how to move complete data from SCSI... (3 Replies)
Discussion started by: upengan78
3 Replies

8. Hardware

Updating OBP on a Sun Sunfire 280R

Hi, I'm a newbie in the Unix world... :confused: I own a Sun Sunfire 280R computer with one 750Mhz CPU. I ordered two CPU of 900Mhz to replace it; however in the Service manual from Sun I read that to use 900Mhz CPU i will need to have a OBP of at least version 4.5.16. When I type .version in... (2 Replies)
Discussion started by: Monkey114
2 Replies

9. Red Hat

Unable to boot Fedora 10

Hello, I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning. But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies

10. Red Hat

Unable to boot up after P2V

Hi, I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
2 Replies

LEARN ABOUT SUSE

sysdef

sysdef(1M)                                                System Administration Commands                                                sysdef(1M)

NAME

       sysdef - output system definition

SYNOPSIS

       /usr/sbin/sysdef [-i] [-n namelist]

       /usr/sbin/sysdef [-h] [-d] [-i] [-D]

DESCRIPTION

       The  sysdef utility outputs the current system definition in tabular form. It lists all hardware devices, as well as pseudo devices, system
       devices, loadable modules, and the values of selected kernel tunable parameters.

       It generates the output by analyzing the named bootable operating system file (namelist) and extracting the configuration information  from
       it.

       The default system namelist is /dev/kmem.

OPTIONS

       -i              Prints  the  configuration information from /dev/kmem. This is the default and only needs to be specified if the configura-
                       tion information from both /dev/kmem and the system file specified with the "-n namelist" option is needed.

       -nnamelist      Specifies a namelist other than the default (/dev/kmem). The namelist specified must be a valid bootable operating system.

       -h              Prints the identifier of the current host in hexadecimal. This numeric value is unique across all Sun hosts.

       -d              The output includes the configuration of system peripherals formatted as a device tree.

       -D              For each system peripheral in the device tree, display the name of the device driver used to manage the peripheral.

EXAMPLES

       Example 1: Sample output format

       The following example displays the format of the sysdef -d output:

       example% sysdef -d
       Node 'SUNW,Ultra-5_10', unit #-1
           Node 'packages', unit #-1 (no driver)
               Node 'terminal-emulator', unit #-1 (no driver)
               Node 'deblocker', unit #-1 (no driver)
               Node 'obp-tftp', unit #-1 (no driver)
               Node 'disk-label', unit #-1 (no driver)
               Node 'SUNW,builtin-drivers', unit #-1 (no driver)
               Node 'sun-keyboard', unit #-1 (no driver)
               Node 'ufs-file-system', unit #-1 (no driver)
           Node 'chosen', unit #-1 (no driver)
           Node 'openprom', unit #-1 (no driver)
               Node 'client-services', unit #-1 (no driver)
           Node 'options', unit #0
           Node 'aliases', unit #-1 (no driver)
           Node 'memory', unit #-1 (no driver)
           Node 'virtual-memory', unit #-1 (no driver)
           Node 'pci', unit #0
               Node 'pci', unit #0
                   Node 'ebus', unit #0
                       Node 'auxio', unit #-1 (no driver)
                       Node 'power', unit #0
                       Node 'SUNW,pll', unit #-1 (no driver)
                       Node 'se', unit #0 (no driver)
                       Node 'su', unit #0
                       Node 'su', unit #1
                       Node 'ecpp', unit #-1 (no driver)
                       Node 'fdthree', unit #0
                       Node 'eeprom', unit #-1 (no driver)
                       Node 'flashprom', unit #-1 (no driver)
                       Node 'SUNW,CS4231', unit #0 (no driver)
                   Node 'network', unit #0
                   Node 'SUNW,m64B', unit #0
                   Node 'ide', unit #0
                       Node 'disk', unit #-1 (no driver)
                       Node 'cdrom', unit #-1 (no driver)
                       Node 'sd', unit #1
                       Node 'dad', unit #1
               Node 'pci', unit #-1 (no driver)
           Node 'SUNW,UltraSPARC-IIi', unit #-1 (no driver)
           Node 'pseudo', unit #0
       [output truncated]

FILES

       /dev/kmem       default operating system image

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

SEE ALSO

       hostid(1), prtconf(1M), nlist(3ELF), attributes(5)

SunOS 5.10                                                          4 Oct 2004                                                          sysdef(1M)
All times are GMT -4. The time now is 08:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy