05:55:06 <gitomat> [illumos-gate] 16083 zinject: zpool_scrub_multiple_copies is failing -- Toomas Soome <tsoome⊙mc>
19:48:50 <Smithx10> Trying to get the Serial Number from a NVME device that was disconnected from fmadm https://gist.github.com/Smithx10/089b424c8a10d50ce4a09514134c97d6
19:48:58 <Smithx10> and ideas ? 
19:49:01 <Smithx10> any*
20:48:03 <jbk> fmdump -eV should list the individual events (that might explain what happened).. if you I think either repair or acquit, it should unretire the device so you can talk to it
20:50:47 <Smithx10> I tried acquit,  but it doesn't seem to come back
20:52:46 <Smithx10> Guessing I have to do something to bring it back into being a disk? 
20:57:35 <jbk> try repaired
20:57:47 <Smithx10> Did that too,  got nothing :( 
20:58:02 <jbk> w/ the uuid of the incident?
20:58:12 <Smithx10> fmadm repair da386b5f-e493-44ce-b8ad-f32939ef140e
20:58:21 <Smithx10> faulty comes up clean
20:59:22 <jbk> the man page is actually incredibly unclear here
21:00:32 <jbk> it talks about taking an fmri or 'label' as an argument
21:00:48 <jbk> but nowhere in there do i see it explain what 'label' is actually supposed to be
21:00:57 <jbk> nor is it something immediately obvious in the faulty output
21:01:12 <jbk> the one thing it doesn't appear to be is the event id
21:01:35 <richlowe> tsoome: did you once explain to me why `1 3 lshift .` doesn't output in ficl-sys?
21:02:06 <jbk> which i'm sure we just inherited from Sun, but we can (and should) do better here
21:10:21 <Smithx10> Would be nice if the Serial was in the fmadm output 
21:57:10 <tsoome> richlowe it is overwritten by prompt. add cr to the end.
21:58:30 <richlowe> thanks
21:59:36 <tsoome> probably bug, I guess....