should show-disks list device path for "Device 2 ( Secondary Master )"?

i have spent the last 2 hours searching google and these forums for answers to the following questions. please, does anybody here know the answers? (see below for details of what iDO 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" do actually map to "Device 2 ( Secondary Master )"; i expect that either one or the other of the following commands would result in booting from "Device 2 ( Secondary Master )":

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" report the name as "disk" instead of "disk1" (see below)?

4. what non-destructive command would prove that the alias "disk1" and the device path "/pci@1f,0/ide@d/disk@1,0" actually maps to "Device 2 ( Secondary Master )"?

thanks in advance for your help

NOTE: i don't have an os on the 2nd internal hddYET. 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".

btw, the 2nd internal hdd works fine. i have been using it with no problem for the past 2 years. it is formatted as one big soft partition with 5 or 6 user-defined file systems; each on its own slice. but it does not have an os on it yet.

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:f

cdrom1/pci@1f,0/ide@d/cdrom@1,0:f

cdrom/pci@1f,0/ide@d/cdrom@1,0:f

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_typeblock

namedisk

compatibleide-disk

=============================

$ prtconf -v

System Configuration: Sun Microsystems sun4u

...

ide, instance #0

Driver properties:

name='target2-dcd-options' type=int items=1 dev=none

value=000000a4

name='target1-dcd-options' type=int items=1 dev=none

value=000000a2

name='target0-dcd-options' type=int items=1 dev=none

value=000000a4

name='dcd_options' type=int items=1 dev=(135,0)

value=000000a5

name='scsi-selection-timeout' type=int items=1 dev=(135,0)

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' +'0=Device D3 State' +'3=Device D0 State'

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-resume'

name='ddi-kernel-ioctl' type=boolean dev=none

Hardware properties:

name='devid' type=string items=1

value='id1,dad@AST320011A=3HT23B31'

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-resume'

name='ddi-kernel-ioctl' type=boolean dev=none

Hardware properties:

name='devid' type=string items=1

value='id1,dad@AMaxtor_6Y120P0=Y35BVHTE'

...

[7327 byte] By [sun-certifieda] at [2007-11-27 2:45:34]
# 1

> 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?

Right, it's just name mapping. The existence of a name does not mean that a device with thame name exists.

> assuming the alias "disk1" and the device path

> "/pci@1f,0/ide@d/disk@1,0" do actually map to

> "Device 2 ( Secondary Master )";

Why there? I believe it maps to "Device 1"

> i expect

> that either one or the other of the following

> commands would result in booting from "Device 2 (

> Secondary Master )":

> >ok boot disk1

> ok boot /pci@1f,0/ide@d/disk@1,0

>

If you want to boot from Device 2, then 'boot disk2'.

> 3. but why does "ok .properties" on

> "/pci@1f,0/ide@d/disk@1,0" report the name as

> "disk" instead of "disk1" (see below)?

Because 'disk1' is just an alias. Any name or names may be created as aliases to the path, but the properties of the path will not change.

> 4. what non-destructive command would prove that

> the alias "disk1" and the device path

> "/pci@1f,0/ide@d/disk@1,0" actually maps to

> "Device 2 ( Secondary Master )"?

I'm not sure. But I do hope that it's not true, and that 'disk 2' -> Device 2.

From the 'probe-ide' list, it appears that Device 1 is a CDrom, while 0 and 2 are disks.

I would boot an OS and compare that to 'iostat -En' output, which should show a CD on 'd1'.

> btw, the 2nd internal hdd works fine. i have been

> using it with no problem for the past 2 years. it is

> formatted as one big soft partition with 5 or 6

> user-defined file systems; each on its own slice. but

> it does not have an os on it yet.

What is the OS path to that disk?

--

Darren

Darren_Dunhama at 2007-7-12 3:13:15 > top of Java-index,General,Talk to the Sysop...
# 2

thanks darren!

you have really cleared it up for me. i have added duke dollars to this thread as an extra thanks for addressing each of my specific questions separately!

Why there? I believe it maps to "Device 1"

partly, because a "curt" reply from a poster called, "rukbat" confused me into thinking that device 1 -> disk0; device 2 disk1:

http://forum.java.sun.com/thread.jspa?threadID=5166538 (3rd reply from the bottom)

<rukbat>If you hope to have one OS on one drive and another on the next drive,

then configure it to always power-on and stop at the OK prompt.

Then after they're installed, you'd simply type...

boot disk0 to launch the first OS.

boot disk1 to launch the other OS.</rukbat>

What is the OS path to that disk?

"/dev/dsk/c0t2d0s0". and from that i've worked out what i believe is the obp device path to that disk:

sun-certified$ ls -al /dev/dsk/c0t2d0s0

lrwxrwxrwx1 rootroot 38 Apr 22 2005 /dev/dsk/c0t2d0s0 -> ../../devices/pci@1f,0/ide@d/dad@2,0:a

I would boot an OS and compare that to 'iostat -En' output, which should show a CD on 'd1'.

if by "d1" you mean "t1" (as in "c0t1d0"), then you're absolutely right!

sun-certified$ iostat -En

c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0

Model: ST320011ARevision: 3.10Serial No: 3HT23B31

Size: 20.02GB <20019879936 bytes>

Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0

Illegal Request: 0

c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0

Model: Maxtor 6Y120P0Revision: YAR41BW0 Serial No: Y35BVHTE

Size: 122.94GB <122939473920 bytes>

Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0

Illegal Request: 0

c0t1d0 Soft Errors: 8 Hard Errors: 0 Transport Errors: 0

Vendor: LITEONProduct: CD-ROM LTN486SRevision: Y3S2 Serial No:

Size: 0.56GB <558039040 bytes>

Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0

Illegal Request: 8 Predictive Failure Analysis: 0

this is just a side note; not important: i came across the syntax definition of "c0t1d0" in some sun manual a while back. if i recall correctly, doesn't it break down to something like this:

c = controller

t = target

d = disk

s = slice

please, correct me if i'm wrong.

thanks again, darren. the whole device path thing is a lot clearer now.

sun-certifieda at 2007-7-12 3:13:15 > top of Java-index,General,Talk to the Sysop...
# 3

> this is just a side note; not important: i came

> across the syntax definition of "c0t1d0" in some sun

> manual a while back. if i recall correctly, doesn't

> it break down to something like this:

>

>c = controller

> t = target

>d = disk

> s = slice

>

> please, correct me if i'm wrong.

Correct, but the mappings aren't necessarily static.

The mapping from a physical hardware path to a controller is made when the OS first detects it. You can see that mapping in /dev/cfg. It means that two machines with the same hardware may see the disks at different controller numbers.

The device driver controls the 'target' and 'disk' numbers. For the simple IDE bus, the mapping is static. 0-3 -> Device 0 - Device 3 -> PM,PS,SM,SS.

For things like Fiber-channel Fabric devices, the mapping is much more complex (and may not be small integers).

--

Darren

Darren_Dunhama at 2007-7-12 3:13:15 > top of Java-index,General,Talk to the Sysop...