Date: Mon, 14 Oct 2019 13:19:26 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Garrett Wollman <wollman@hergotha.csail.mit.edu> Cc: slw@zxy.spb.ru, freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <9D676F55-EFEC-4647-BE28-C2C7B9807614@dons.net.au> In-Reply-To: <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> <201909201706.x8KH6Tov048682@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 21 Sep 2019, at 02:36, Garrett Wollman = <wollman@hergotha.csail.mit.edu> wrote: >=20 > In article <20190920155304.GN3953@zxy.spb.ru>, slw@zxy.spb.ru writes: >=20 >> 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 <=3D> daXY mapping = and >> turn ON led by sas2ircu. >=20 > sesutil does this for you! >=20 > # sesutil locate daXY on > # sesutil locate daXY off >=20 > So long as your enclosure supports SES (all the modern ones I've seen > do) and is enumerable by ses(4). FWIW I find it doesn't work on the Supermicro chassis (SYS-5019S-MR) we = use with SATA disks. [chumphon 2:42] ~> sudo sesutil locate ada0 on sesutil: Count not find the SES id of device 'ada0' (Also I just noticed a spelling error in the above, "Count" should be = "Could") [chumphon 2:42] ~> sudo sesutil map ses0: Enclosure Name: AHCI SGPIO Enclosure Enclosure ID: 0 Element 0, Type: Array Device Slot Status: Unsupported (0x00 0x00 0x00 0x00) Element 1, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 000 Element 2, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 001 Element 3, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 002 Element 4, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 003 Element 5, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 004 Element 6, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 005 Element 7, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 006 Element 8, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 007 Using led(4) works: echo 1 | sudo tee /dev/led/ahci0.X.fault=20 (The X lines up with the "ahcich4" part of dmesg for adaX) although I find you can only turn the LED on and not off which limits = it's usefulness somewhat.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D676F55-EFEC-4647-BE28-C2C7B9807614>