{"id":1401,"date":"2013-10-18T19:18:29","date_gmt":"2013-10-18T11:18:29","guid":{"rendered":"http:\/\/www.computersolutions.cn\/blog\/?p=1401"},"modified":"2013-10-18T19:22:34","modified_gmt":"2013-10-18T11:22:34","slug":"ubuntu-13-diskby-id-name-changes-zfs","status":"publish","type":"post","link":"https:\/\/www.computersolutions.cn\/blog\/2013\/10\/ubuntu-13-diskby-id-name-changes-zfs\/","title":{"rendered":"Ubuntu 13 disk\/by-id name changes (zfs)"},"content":{"rendered":"

Looks like Ubuntu 13 has changed the dev id’s for disks!
\nIf you use ZFS, like us, then you may be caught by this subtle naughty change.<\/p>\n

Previously, disk-id’s were something like this:
\nscsi-SATA_ST4000DM000-1CD_Z3000WGF<\/p>\n

In Ubuntu 13 this changed:
\nata-ST4000DM000-1CD168_Z3000WGF<\/p>\n

According to the FAQ in ZFS on Linux, this *isn’t* supposed to change.<\/p>\n

http:\/\/zfsonlinux.org\/faq.html#WhatDevNamesShouldIUseWhenCreatingMyPool<\/a><\/p>\n

\/dev\/disk\/by-id\/: Best for small pools (less than 10 disks)
\nSummary: This directory contains disk identifiers with more human readable names. The disk identifier usually consists of the interface type, vendor name, model number, device serial number, and partition number. This approach is more user friendly because it simplifies identifying a specific disk.
\nBenefits: Nice for small systems with a single disk controller. Because the names are persistent and guaranteed not to change<\/strong>, it doesn't matter how the disks are attached to the system. You can take them all out, randomly mixed them up on the desk, put them back anywhere in the system and your pool will still be automatically imported correctly.<\/code><\/p>\n

So… on a reboot after upgrading a clients NAS, all the data was missing, with the nefarious pool error.
\nSee below:<\/p>\n


\nroot@hpnas:# zpool status
\npool: nas
\nstate: UNAVAIL
\nstatus: One or more devices could not be used because the label is missing
\nor invalid. There are insufficient replicas for the pool to continue
\nfunctioning.
\naction: Destroy and re-create the pool from
\na backup source.
\nsee: http:\/\/zfsonlinux.org\/msg\/ZFS-8000-5E
\nscan: none requested
\nconfig:<\/p>\n

NAME STATE READ WRITE CKSUM
\nnas UNAVAIL 0 0 0 insufficient replicas
\nraidz1-0 UNAVAIL 0 0 0 insufficient replicas
\nscsi-SATA_ST4000DM000-1CD_Z3000WGF UNAVAIL 0 0 0
\nscsi-SATA_ST4000DX000-1CL_Z1Z036ST UNAVAIL 0 0 0
\nscsi-SATA_ST4000DX000-1CL_Z1Z04QDM UNAVAIL 0 0 0
\nscsi-SATA_ST4000DX000-1CL_Z1Z05B9Y UNAVAIL 0 0 0
\n<\/code><\/p>\n

Don’t worry, the data’s still there. Ubuntu has just changed the disk names, so ZFS assumes the disks are broken.<\/p>\n

Simple way to fix it is to export the pool, then reimport with the new names.
\nOur pool is named “nas” in the example below:<\/p>\n

root@hpnas:# zpool export nas
\nroot@hpnas:# zpool import -d \/dev\/disk\/by-id nas -f
\n<\/code><\/p>\n

As you can see, our pool is now a happy chappy, and our data should be back<\/p>\n


\nroot@hpnas:# zfs list
\nNAME USED AVAIL REFER MOUNTPOINT
\nnas 5.25T 5.12T 209K \/nas
\nnas\/storage 5.25T 5.12T 5.25T \/nas\/storage
\nroot@hpnas:\/dev\/disk\/by-id# zfs list
\nNAME USED AVAIL REFER MOUNTPOINT
\nnas 5.25T 5.12T 209K \/nas
\nnas\/storage 5.25T 5.12T 5.25T \/nas\/storage
\nroot@hpnas:\/dev\/disk\/by-id# zpool status
\npool: nas
\nstate: ONLINE
\nscan: none requested
\nconfig:<\/p>\n

NAME STATE READ WRITE CKSUM
\nnas ONLINE 0 0 0
\nraidz1-0 ONLINE 0 0 0
\nata-ST4000DM000-1CD168_Z3000WGF ONLINE 0 0 0
\nata-ST4000DX000-1CL160_Z1Z036ST ONLINE 0 0 0
\nata-ST4000DX000-1CL160_Z1Z04QDM ONLINE 0 0 0
\nata-ST4000DX000-1CL160_Z1Z05B9Y ONLINE 0 0 0<\/p>\n

errors: No known data errors
\n<\/code><\/p>\n

Bit naughty of Ubuntu to do that imho…<\/p>\n","protected":false},"excerpt":{"rendered":"

Looks like Ubuntu 13 has changed the dev id’s for disks! If you use ZFS, like us, then you may be caught by this subtle naughty change. Previously, disk-id’s were something like this: scsi-SATA_ST4000DM000-1CD_Z3000WGF In Ubuntu 13 this changed: ata-ST4000DM000-1CD168_Z3000WGF According to the FAQ in ZFS on Linux, this *isn’t* supposed to change. http:\/\/zfsonlinux.org\/faq.html#WhatDevNamesShouldIUseWhenCreatingMyPool \/dev\/disk\/by-id\/: […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[25,4],"tags":[],"class_list":["post-1401","post","type-post","status-publish","format-standard","hentry","category-technical-mumbo-jumbo","category-useful-info"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/1401","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/comments?post=1401"}],"version-history":[{"count":3,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/1401\/revisions"}],"predecessor-version":[{"id":1404,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/1401\/revisions\/1404"}],"wp:attachment":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/media?parent=1401"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/categories?post=1401"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/tags?post=1401"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}