Date: Fri, 20 Sep 2019 17:06:42 -0000 From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: slw@zxy.spb.ru Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <201909201706.x8KH6Tov048682@hergotha.csail.mit.edu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> <CAOjFWZ6O4H9atcV-C-ZV0xye24P%2B69frgaVez98ZiGytzweOuw@mail.gmail.com> <20190920155304.GN3953@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20190920155304.GN3953@zxy.spb.ru>, slw@zxy.spb.ru writes: >Location of device in multi-chassis storage system is different story. >I am don't know how to field engineer insert disks in chassis. >For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and >turn ON led by sas2ircu. sesutil does this for you! # sesutil locate daXY on # sesutil locate daXY off So long as your enclosure supports SES (all the modern ones I've seen do) and is enumerable by ses(4). -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201909201706.x8KH6Tov048682>