I mostly go by 'iostat -En' and match up serials with names. Not very efficient. But it 'works TM'.
Regards Jorge On 2016-03-05 19:38, Reginald Beardsley via illumos-discuss wrote:
How does one track from the BIOS level disk identification through to the OS presentation? SunOS 4.1 I knew everything, but Solaris changed that and I've never found a good guide to decoding the new device tree. What would happen if a pair of disk drive cables got swapped on a 3 disk RAIDZ1? With a 3 way mirror? That might have happened when I was cleaning out the dust. There were no issues booting or using the system until I started the scrub. Would installing the disks in a OI151a8 system straighten out the vdevs? I'm considering zpool import -f -R /a ID zpool scrub ID zpool export ID My thinking is that ZFS is using the information in the label and that the following happened: booted with cables swapped system detected error on the disk in the mirror that booted and updated the ZFS label this resulted in 2 disks marked c1d1s0 zpool scrub gets confused and hangs At that point anything that tried to get system information hangs and I had to force the power off. But the system seemed normal up until I did the scrub. "zpool status" worked fine. Thus since a "zpool import -f" from another system is going to ignore the ondisk drive identification (???) It seems to me it has to if the pool was not exported and that the export operation marks the vdev as exported so that there will not be conflicts if it is imported into another system. Hmmm. I think I'll build a bare install and see how it behaves if I abuse it. Reg
------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
