I think my problem is more basic than that - how do I even identify which
device is my USB caddy disk? So far I seem to have:
mjch at mawrth:~# zpool status
pool: rpool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
c8d0s0 ONLINE 0 0 0
errors: No known data errors
... although this is an internal SATA disk. dmesg did spit this out when I
added the disk:
Oct 24 08:22:28 mawrth usba: [ID 912658 kern.info] USB 2.0 device
(usb13fd,1840) operating at hi speed (USB 2.x) on USB 2.0 root hub: storage at
2, scsa2usb0 at bus address 3
Oct 24 08:22:28 mawrth usba: [ID 349649 kern.info] Generic External
355644304545594B20202020
Oct 24 08:22:28 mawrth genunix: [ID 936769 kern.info] scsa2usb0 is /pci at
0,0/pci1043,830f at 1d,7/storage at 2
Oct 24 08:22:28 mawrth genunix: [ID 408114 kern.info] /pci at 0,0/pci1043,830f
at 1d,7/storage at 2 (scsa2usb0) online
Oct 24 08:22:28 mawrth scsi: [ID 583861 kern.info] sd0 at scsa2usb0: target 0
lun 0
Oct 24 08:22:28 mawrth genunix: [ID 936769 kern.info] sd0 is /pci at
0,0/pci1043,830f at 1d,7/storage at 2/disk at 0,0
Oct 24 08:22:28 mawrth genunix: [ID 408114 kern.info] /pci at 0,0/pci1043,830f
at 1d,7/storage at 2/disk at 0,0 (sd0) online
... but I'm not sure how these device paths translate to something more useful
...
--
This message posted from opensolaris.org
