How to identify dying USB key for boot volume?

[diskdiddler]

I know which one it is, it's da1p2 not da1p0 but that really isn't particularly useful information. How can I know I replace the correct disk? Is it ok to just pull one and check

Bonus question, there's no data / information / what model or size the USB keys are, how do I tell?

 

[SweetAndLow]

Can't really tell unless you know the serial number of each usb. You can try removing one and see if it boots if it does you pulled the bad usb. If it didn't buy you pulled the good usb.

 

[Ericloewe]

how do I tell

Take them apart and undertake the herculean task of identifying the vendor with just the bare board.

Or check camcontrol for USB devices, which should yield some information.

 

[diskdiddler]

Ok what about simple volume size, is there any way I can tell that without physically touching the machine?

Also the USB stick isn't dead, it's just got a single bad block. I'd like to replace it. Can I just pull one and do a boot pool scrub and it'll tell me which one went missing?

 

[Ericloewe]

zpool list should give you a rough idea of the drives' nominal size.

 

[diskdiddler]

Thanks, my assumption was correct, it's a particular 16GB model that I just so happen to have 4 versions of the same key.
I've added now a third key to my machine and I'll replicate over to that.

Am I correct or incorrect in thinking the mirror / replication process for boot keys copies _the entire key, boot flag and all_ so that I can pull the bad key out and the machine will just continue to boot, no issues?

 

[Ericloewe]

Woah, don't replicate!

Just add it to the boot pool as a mirror. See 19.3.2 here: https://www.freebsd.org/doc/handbook/zfs-zpool.html

Then detach the failed drive, as per the same section.

 

[diskdiddler]

I shouldn't have replicated, I've already started it, holy crap this is bad.

pool: freenas-boot
state: ONLINE
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Wed Jul 20 10:50:50 2016
5.94M scanned out of 3.94G at 18.3K/s, 62h36m to go
5.94M resilvered, 0.15% done

EDIT: How do I cancel this or should I just pull out the replacement USB key or something?

 

[diskdiddler]

(Yet another box in FreeNAS where the UI could do with some simple changes to the wording to avoid threads like this one.) and the developers wonder why I'm frustrated FN10 has a whole new UI - it's the little tweaks to the user interface which make for ease of use, logic, consistency. Considering how many simple things are lacking now, I worry going back to the drawing board they are just going to miss a whole slew of important things.

 

[Ericloewe]

I shouldn't have replicated, I've already started it, holy crap this is bad.

Not bad, just wipe the drive.

 

[diskdiddler]

Ok I detached the replacement, did a quick wipe, I suspect FreeNAS was clever enough to cancel the reslivering. (the wording in that menu needs work......)

I'm trying to remember how to mirror it via the GUI, not the command line, I'm in the process of attaching it now.
EDIT1: Nope, "attaching" the disk just restarted the resliver process :/


EDIT2: aaaaaaaaaaaaaand now I can't even detach the disk, the option is gone

 

[diskdiddler]

I removed the 3rd key
I have now managed to identify which key is which of the 2 original ones (don't ask how)

I intend to shut the system down.
Remove the bad key.
Put the replacement key in
Boot up

How can I outright stop the system from trying to resliver as soon as it detects that 3'rd key?

config:

NAME STATE READ WRITE CKSUM
freenas-boot DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
gptid/93096e78-b686-11e4-b873-28924a2d5aca ONLINE 0 0 1
gptid/ad8cafcc-b687-11e4-ba56-28924a2d5aca ONLINE 0 0 0
16174118798259370471 REMOVED 0 0 0 was /dev/da2p2

I want the system to forget that key ever existed.

I really don't want to insert that key and have the system 'try and get clever' with it. I need it to be forgotten entirely.

 

[Jurgen Segaert]

Bonus question, there's no data / information / what model or size the USB keys are, how do I tell?

I check the serial numbers of all my devices (both HDD & USB sticks) at build time and label them, for occasions such as these.
If your USB sticks are not identical, or if you just want to get some information w/o touching the machine you can also use one of the following commands:

Code:

dmesg | grep ^da
geom disk list

 

[wblock]

(Yet another box in FreeNAS where the UI could do with some simple changes to the wording to avoid threads like this one.) and the developers wonder why I'm frustrated FN10 has a whole new UI - it's the little tweaks to the user interface which make for ease of use, logic, consistency. Considering how many simple things are lacking now, I worry going back to the drawing board they are just going to miss a whole slew of important things.

FreeNAS 9.10 is still being maintained, so consider entering bug reports for these things. It's logical to assume that 9.X and 10.X will be compared at some point by the 10.X developers, so having that feature in place might make certain it works at least as well in 10.X.

 

[diskdiddler]

Thanks for the replies guys, I do serial number my HDDs (and my machine is fairly easy to identify which port is which) but the USB keys, being identical models - without S/N on the side, makes it hard.

Like I said, I now know which drive I need to replace but I don't know how to stop FreeNAS trying to replicate / resliver to the 3'rd key? How does one ENTIRELY wipe the umm GPT thing or serial number from the FreeNAS database of a disk?
See 4 posts above.

 

[wreedps]

If you pull out the "good" USB key while Freenas is running, will it lockup?