> Hi all! > > I've been working with Linux for many years, but > decided to start sniffing a bit at OpenSolaris as > well. > I've installed VirtualBox on my Linux machine to > check out OpenSolaris. I created a config with 2 IDE > & 4 SATA virtual drives (so that I can check out ZFS > and its raidz as well), but I am now having trouble > figuring which drive is which. When I do: > * ls /dev/dsk/ > > I get: > > c4d0p0 c4d0s13 c4d0s9 c4d1s12 c4d1s8 > c5t0d0s11 c5t0d0s7 c6t0d0s10 c6t0d0s6 > c6t1d0s1 c6t1d0s5 c6t2d0s0 c6t2d0s4 > c6t3d0p4 c6t3d0s3 > 0p1 c4d0s14 c4d1p0 c4d1s13 c4d1s9 [...] > > Quite the list... From > > zpool status > I know that c4d0s0 is most likely my primary IDE > drive. But which device is my secondary IDE? And > which are my 4 SATA's? > > > egards, > Evert
The usual /dev names for disks on Solaris are /dev/dsk/c#t#d#s# or /dev/dsk/c#t#d#p#, where c is controller number (one-up as discovered since installation, typically), t is target (from SCSI originally; maybe just a 0 or 1 for IDE, not sure); d is a SCSI LUN, p is an FDISK partition, and s is a Solaris slice (which on SPARC is a top-level partition, but on x86 exists within the Solaris FDISK partition on the boot disk; conventionally, s2 covers the entire disk or FDISK partition). Most of the contents of /dev are symlinks to device files under /devices, which more closely model the hardware device tree (but have more radically varying names). So you can probably get a hint as to which controller number corresponds to what device type by doing something like: cd /dev/dsk ls -l *p0 *s2 The link targets would include driver names for the controller and target device, so it shouldn't be too hard to sort out what's what. This message posted from opensolaris.org
