Labelling best practices?

[hendry]

I did find https://forums.freenas.org/index.php?resources/identify-your-drives-by-serial-number.64/ & https://doc.freenas.org/11/storage.html#replacing-a-failed-drive but I haven't found a proactive guide to labelling my disks.

https://www.youtube.com/watch?v=SwSY3Lccv8U

Can I take one out my running system or is that a no no?

Thanks in advance,

 

[kdragon75]

You ca map the gptid to a serial number with the following commands:
glable status
camcontrol devlist
From there, shutdown, pull drives, and label with serial numbers. You should have no issues mapping from a gptid in your zpool to a physical drive now. You may also be able to use sesutil to blink/turn on fault lights if your system supports it.

 

[hendry]

View disks on the Web console
https://s.natalian.org/2018-10-30/1540910526_2558x1406.png


Prints more info than:

Code:

[hendry@freenas ~]$ glabel status
									  Name  Status  Components
gptid/3d6ac889-5f14-11e8-b724-b05ada874af8	 N/A  da0p1
gptid/d29b9c19-5ed3-11e8-8715-b05ada874af8	 N/A  ada0p2
gptid/d3740634-5ed3-11e8-8715-b05ada874af8	 N/A  ada1p2
[hendry@freenas ~]$ sudo sesutil status
sesutil: No SES devices found
[hendry@freenas ~]$ sudo camcontrol devlist
<WDC WD40EFRX-68N32N0 82.00A82>	at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD40EFRX-68N32N0 82.00A82>	at scbus3 target 0 lun 0 (pass1,ada1)
<SanDisk Ultra Fit 1.00>		   at scbus7 target 0 lun 0 (pass2,da0)

I wish it could just simply say what HD is which bay. Really don't want to shut down just to label my drives!

 

[kdragon75]

The GUI doesn't show the gptid of the drives. Alo did you look into using sesutil ? If you hardware supports it, you can use it to map your drives.

 

[kdragon75]

Oh I just saw

[hendry@freenas ~]$ sudo sesutil status sesutil: No SES devices found

kinda just tucked in there...

Really don't want to shut down just to label my drives!

No ses and no doing it ahead of time can bite.

 

[hendry]

Why do I need to note the gptid of the drives @kdragon75? Sorry, I don't understand.

I've worked out that WD-WCC7K1EKE8K2 is my far left drive and WD-WCC7K6RFEFT6 is far right. Same serials as I can see in Storage -> View disks.

https://youtu.be/z0HZd3dpsdo

Another think I don't understand. Why isn't there a tool to enumerate my bays and tell me my drives like so:

1. WD-WCC7K1EKE8K2
2
3.
4. WD-WCC7K6RFEFT6

 

[kdragon75]

You server doesn't seem to support ses. I'm sure some proprietary hp drivers can identify them based on factor specs. FreeNAS does not use proprietary or closed-source drivers and has no idea how the cabling is physically setup as that's what ses does. You could also use dd if=/dev/ada1 of=/dev/null bs=4096 count=5000 to read lots of data from the drive causing the led to blink more than the others. That's less reliable thought.

 

[kdragon75]

As for the gptid, if you ever need to look at you pool from the console using the zpool commands, you will need to know the gptid as that's how there identified in FreeNAS as ada1 and ada2 etc, could potentially switch.

 

[hendry]

So there is no automatic mapping between View disks and zpool status ??

https://gist.github.com/kaihendry/cfc20813632fbd57d797b2357142633a


I have to work it out?

 

[kdragon75]

Well, ZFS (zpool status -v) is going to show the block devices as they were added. FreeNAS will sort of hold your hand but ZFS will not. Besides it should only take a few moments unless you have 20+ disks.

 

[bkvamme]

Have a look at the drive info script here.

https://forums.freenas.org/index.ph...d-identification-and-backup-the-config.27365/

Added my version just now, and the CSV version can output a file where you can mark with drive bay and slot.
https://forums.freenas.org/index.ph...ation-and-backup-the-config.27365/post-496062