>...please, try to answer the specific questions that i have asked and ONLY those questions.
Main Topics
Browse All Topicshi,
background: i'm running solaris 9 on a sunblade 100. i've got two internal hdds. my current solaris 9 os is on the primary master hdd. currently only user-defined file systems are mounted on the secondary internal hdd. i am investigating and preparing for possibly installing solaris 10 on a new boot enviroment that i MIGHT create on the secondary internal hdd.
i have spent the last 2 hours searching google and ee for answers to the following questions. please, does anybody here know the answers? (see below for details of what i DO know):
1. probe-ide reports my 2nd internal hdd as ""Device 2 ( Secondary Master )". what do i have to do to make show-disks list a device path for my 2nd internal hdd?
2. devalias reports aliases for 5 disks. am i correct in assuming that these are only "reserved" aliases and that they don't necessarily map to actual devices?
assuming the alias "disk1" and the device path "/pci@1f,0/ide@d/disk@1,0"
ok boot disk1
ok boot /pci@1f,0/ide@d/disk@1,0
3. but why does "ok .properties" on "/pci@1f,0/ide@d/disk@1,0"
4. what non-destructive command would prove that the alias "disk1" and the device path "/pci@1f,0/ide@d/disk@1,0"
thanks in advance for your help
NOTE: i don't have an os on the 2nd internal hdd YET. i am only preparing for when i do eventually install an os on that drive. so you would be wasting your time replying with answers like, "just try it and see". please, try to answer the specific questions that i have asked and ONLY those questions.
this is what i know:
ok probe-ide
Device 0 ( Primary Master )
ATA Model: ST320011A
Device 1 ( Primary Slave )
Removeable ATAPI Model: LTN486S
Device 2 ( Secondary Master )
ATA Model: Maxtor 6Y120P0
Device 3 ( Secondary Slave )
Not Present
==========================
ok show-disks
a) /pci@1f,0/ide@d/cdrom
b) /pci@1f,0/ide@d/disk
q) NO SELECTION
==========================
ok devalias
...
cdrom2 /pci@1f,0/ide@d/cdrom@2,0:
cdrom1 /pci@1f,0/ide@d/cdrom@1,0:
cdrom /pci@1f,0/ide@d/cdrom@1,0:
disk /pci@1f,0/ide@d/disk@0,0
disk3 /pci@1f,0/ide@d/disk@3,0
disk2 /pci@1f,0/ide@d/disk@2,0
disk1 /pci@1f,0/ide@d/disk@1,0
disk0 /pci@1f,0/ide@d/disk@0,0
ide /pci@1f,0/ide@d
...
==========================
ok dev /pci@1f,0/ide@d/disk@1,0
ok .properties
device_type block
name disk
compatible ide-disk
==========================
$ prtconf -v
System Configuration: Sun Microsystems sun4u
...
ide, instance #0
Driver properties:
name='target2-dcd-options'
value=000000a4
name='target1-dcd-options'
value=000000a2
name='target0-dcd-options'
value=000000a4
name='dcd_options' type=int items=1 dev=(135,0)
value=000000a5
name='scsi-selection-timeo
value=000000fa
name='scsi-options' type=int items=1 dev=(135,0)
value=00107ff8
name='scsi-watchdog-tick' type=int items=1 dev=(135,0)
value=0000000a
name='scsi-tag-age-limit' type=int items=1 dev=(135,0)
value=00000002
name='scsi-reset-delay' type=int items=1 dev=(135,0)
value=00000bb8
name='atapi' type=int items=1 dev=none
value=00000001
name='pm-components' type=string items=3 dev=none
value='NAME=ide-controller
disk (driver not attached)
cdrom (driver not attached)
dad, instance #0
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000000
name='class_prop' type=string items=1
value='ata'
name='type' type=string items=1
value='ata'
name='class' type=string items=1
value='dada'
Driver properties:
name='pm-components' type=string items=4 dev=none
value='NAME=ide-disk' + '0=standby' + '1=idle' + '2=active'
name='pm-hardware-state' type=string items=1 dev=none
value='needs-suspend-resum
name='ddi-kernel-ioctl' type=boolean dev=none
Hardware properties:
name='devid' type=string items=1
value='id1,dad@AST320011A=
dad, instance #1
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000002
name='class_prop' type=string items=1
value='ata'
name='type' type=string items=1
value='ata'
name='class' type=string items=1
value='dada'
Driver properties:
name='pm-components' type=string items=4 dev=none
value='NAME=ide-disk' + '0=standby' + '1=idle' + '2=active'
name='pm-hardware-state' type=string items=1 dev=none
value='needs-suspend-resum
name='ddi-kernel-ioctl' type=boolean dev=none
Hardware properties:
name='devid' type=string items=1
value='id1,dad@AMaxtor_6Y1
...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Since the OBP seeting can be change by anyone (redefined the values etc).
To verify the device name is correct or not, you can do it the the Solaris commandline.
type in:
prtconf –vp | grep -i disk1
then compare with the out put:
ls -al /dev/dsk/c0t2d0s0
PS: you can use format to find out the device name for your 2nd HD
replace c0t2d0 with the real device you have.
eg, here's the out put off my Sun Blade 100:
# prtconf -vp | grep disk
disk-write-fix:
name: 'disk-label'
bootpath: '/pci@1f,0/ide@d/disk@0,0:
diag-device: 'disk net'
boot-device: 'disk:a disk:b net'
disk: '/pci@1f,0/ide@d/disk@0,0'
disk3: '/pci@1f,0/ide@d/disk@3,0'
disk2: '/pci@1f,0/ide@d/disk@2,0'
disk1: '/pci@1f,0/ide@d/disk@1,0'
disk0: '/pci@1f,0/ide@d/disk@0,0'
name: 'disk'
compatible: 'ide-disk'
ls -al /dev/dsk/c0t2d0s0
lrwxrwxrwx 1 root root 38 May 15 2002 /dev/dsk/c0t2d0s0 -> ../../devices/pci@1f,0/ide
my disk c0t2d0 is disk2 in my OBP.
Note: the OBP device pathname format is:
driver-name@unit-address:d
and the device alias can set by anyone has access to the OBP.
1. good question, but not relevant. Use the info that Yuzh provided to figure it out.
2. Yes
3. disk and disk1 are normally, but not always set to the same disk. If someone else has palyed with the system, they could be set to anything, including invalid settings.
4. boot disk (if it boots then it is point at your disk with the os otherwise it is the other disk)
boot disk1 (if it boots then it is point at your disk with the os otherwise it is the other disk)
boot disk2 (if it boots then it is point at your disk with the os otherwise it is the other disk)
Business Accounts
Answer for Membership
by: yuzhPosted on 2007-04-29 at 18:38:35ID: 18999106
For OBP, device setting details please read the Sun blade 100 manuals: s-n-soluti ons/hardwa re/docs/ Wo rkstation_ Products/W orkstation s/Sun_Blad e_Workstat ions/ Sun_B lade_100/i ndex.html
http://www.sun.com/product
To install a different version of OS in your 2nd Hd, you can simply, boot uo from CDROM or boot server, select the 2nd DH to install.
When you want to boot from the 2nd HD, at OPB, tupe in:
boot disk1