SOLVED Can't tell if one or two drives failed, or worse...

[Z300M]

Proper planning solves this problem. ;)

Neat! (literally). What case is that? But I see that you have the daX labels on each drive as well, which I have just been persuaded do not necessarily remain constant.

 

[Jailer]

Neat! (literally). What case is that? But I see that you have the daX labels on each drive as well, which I have just been persuaded do not necessarily remain constant.

Yup the drive labels were put on when I assembled it and didn't know better. Case is Antec 1200, it's very roomy if your looking for a non rack mount solution. Only downside is trying to find the drive modules, they seem to be made of unobtanium. The 900 drive modules fit but don't have a removable filter in them like the 1200 modules do which is a must in a home with a wood stove.

 

[Z300M]

Yup the drive labels were put on when I assembled it and didn't know better. Case is Antec 1200, it's very roomy if your looking for a non rack mount solution. Only downside is trying to find the drive modules, they seem to be made of unobtanium. The 900 drive modules fit but don't have a removable filter in them like the 1200 modules do which is a must in a home with a wood stove.

That's the same case I have, but I have my 20(!) drives mounted in 4 x iStarUSA BPU-350SATA-KL cages. So I still have my Antec drive cages, which are not being used, but I'm not sure I want to get rid of any of them.

 

[Jailer]

So I still have my Antec drive cages, which are not being used, but I'm not sure I want to get rid of any of them.

If you ever do hit me up, I'm one short of what I need. I've got one 900 cage with a makeshift filter on it that kinda works but would like to replace it if I could.

 

[mrichardson03]

If it helps somebody else, I've put the physical location of the drive in the enclosure in the description field of each drive in Storage -> View Disks. This persists correctly across reboots even if the OS changes the name of the drive.

 

[Bidule0hm]

Don't trust these fields, they are as good as the device label (/dev/adaX, /dev/daX, ...), only the GPTID and the S/N are ok to identify a drive in the long run ;)

 

[Stux]

Don't trust these fields, they are as good as the device label (/dev/adaX, /dev/daX, ...), only the GPTID and the S/N are ok to identify a drive in the long run ;)

How so? Are they not stored on the disk? Do they spontaneously disappear?

One issue is when the disk does die, you don't see the field...

 

[Bidule0hm]

No, they're stored in the database (you now the config file you can save? it's actually a dump of a SQLite DB) and they're mapped to the device label (hence why they aren't better).

But yeah, I recommend to map your drive info before you have a problem (a bit like you should backup your config before anything happens) so you don't have to go on a treasure hunt the day a drive die... I actually made a script for that, look at the useful scripts link in my signature if you're interested ;)

 

[mrichardson03]

No, they're stored in the database (you now the config file you can save? it's actually a dump of a SQLite DB) and they're mapped to the device label (hence why they aren't better).

But yeah, I recommend to map your drive info before you have a problem (a bit like you should backup your config before anything happens) so you don't have to go on a treasure hunt the day a drive die... I actually made a script for that, look at the useful scripts link in my signature if you're interested ;)

That's not exactly true.

Code:

[root@freenas] /data# sqlite3 freenas-v1.db
SQLite version 3.11.1 2016-03-03 16:17:53
Enter ".help" for usage hints.
sqlite> .schema storage_disk
CREATE TABLE "storage_disk" ("disk_acousticlevel" varchar(120) NOT NULL, "disk_hddstandby" varchar(120) NOT NULL, "disk_size" varchar(20) NOT NULL, "disk_serial" varchar(30) NOT NULL, "disk_multipath_name" varchar(30) NOT NULL, "disk_identifier" varchar(42) NOT NULL , "disk_togglesmart" bool NOT NULL, "disk_number" integer NOT NULL, "disk_advpowermgmt" varchar(120) NOT NULL, "disk_transfermode" varchar(120) NOT NULL, "disk_multipath_member" varchar(30) NOT NULL, "disk_description" varchar(120) NOT NULL, "disk_subsystem" varchar(10) NOT NULL, "disk_smartoptions" varchar(120) NOT NULL, "disk_enabled" bool NOT NULL, "disk_name" varchar(120) NOT NULL);
CREATE UNIQUE INDEX "storage_disk_disk_identifier" ON "storage_disk"("disk_identifier");
sqlite> select * from storage_disk;
Disabled|Always On|3000592982016|     WD-WCC4N0048718||{serial}     WD-WCC4N0048718|1|2|Disabled|Auto||Slot 2|da||1|da2
Disabled|Always On|3000592982016|     WD-WMC4N0F4VZUV||{serial}     WD-WMC4N0F4VZUV|1|0|Disabled|Auto||Slot 4|da||1|da0
Disabled|Always On|3000592982016|     WD-WCC4NDA2NCC9||{serial}     WD-WCC4NDA2NCC9|1|3|Disabled|Auto||Slot 1|da||1|da3
Disabled|Always On|3000592982016|     WD-WCC4N0299267||{serial}     WD-WCC4N0299267|1|5|Disabled|Auto||Slot 5|da||1|da5
Disabled|Always On|3000592982016|     WD-WMC1T0860631||{serial}     WD-WMC1T0860631|1|4|Disabled|Auto||Slot 6|da||1|da4
Disabled|Always On|3000592982016|     WD-WCC4N0215045||{serial}WD-WCC4N0215045|1|1|Disabled|Auto||Slot 3|da||1|da1
sqlite> 

Disk identifier is built on the serial, and the table is indexed on that.

 

[Bidule0hm]

Maybe but some time ago a member used the desc field in the disks tab and they where following the device label changes, no the S/N.

So you do what you want but my advice is to not use them to identify a disk across reboots ;)