Score:0

ZFS - New pool doesn't survive reboot

in flag

I'm in the process of "replacing" my mdadm raid5 array with a raidz2 array with ZFS on my Ubuntu 20.04 home server. But for some reason, after each reboot my zpool and datasets can't be detected or mounted.

Here are the command I used to create my pool :

zpool create epicpool raidz2 /dev/disk/by-id/ata-ST2000DM001-1ER164_Z4Z4MDDA /dev/disk/by-id/ata-ST2000DM006-2DM164_Z4Z8WEGZ /dev/disk/by-id/ata-ST2000DM008-2FR102_ZFL1MGYW     /dev/disk/by-id/ata-ST2000DM008-2FR102_ZFL47RPN /dev/disk/by-id/ata-ST32000542AS_6XW11TZ8
zfs create epicpool/storage
zfs set mountpoint=/share/storage epicpool/storage
zfs set compression=lz4 epicpool
zfs set atime=off epicpool

So far, I don't see what I do wrong. If I list my ZFS data, my storage is there :

$ zpool list
NAME       SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
epicpool  9.09T  1.30M  9.09T        -         -     0%     0%  1.00x    ONLINE  -
$ sudo zfs list
NAME               USED  AVAIL     REFER  MOUNTPOINT
epicpool           916K  5.21T      170K  /epicpool
epicpool/storage   170K  5.21T      170K  /epicpool/storage

But each time, after I reboot, nothing is detected :

$ zfs list
no datasets available
$ zpool list
no pools available

And if I try to import my pool (as we do on a brand new system for as far as I know), it keep saying that there is no pool available :

$ sudo zpool import -a
no pools available to import

Note that I also tried with the -d parameter and specifing my vdev as I'v done in my create command.

What is really weird is, if I do the ZDB command, I see all the correc information from my "zpool create" before my reboot, and if I list my partitions with fdisk, I see that the zfs partition are still there :

$sudo fdisk -l 
Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM001-1ER1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D387D033-B98F-A041-AE77-EA44D444D159

Device          Start        End    Sectors  Size Type
/dev/sda1        2048 3907012607 3907010560  1.8T Solaris /usr & Apple ZFS
/dev/sda9  3907012608 3907028991      16384    8M Solaris reserved 1


Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM008-2FR1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BA2BA653-2B9A-864D-A1A8-08FA8804F7B6

Device          Start        End    Sectors  Size Type
/dev/sdb1        2048 3907012607 3907010560  1.8T Solaris /usr & Apple ZFS
/dev/sdb9  3907012608 3907028991      16384    8M Solaris reserved 1


Disk /dev/sdc: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM006-2DM1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FBC930CA-BCFB-E848-8C67-9685AE3964E4

Device          Start        End    Sectors  Size Type
/dev/sdc1        2048 3907012607 3907010560  1.8T Solaris /usr & Apple ZFS
/dev/sdc9  3907012608 3907028991      16384    8M Solaris reserved 1

****[Another external drive]****  

Disk /dev/sde: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM008-2FR1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 028359F1-E2C9-8544-9A24-DA9D53614429

Device          Start        End    Sectors  Size Type
/dev/sde1        2048 3907012607 3907010560  1.8T Solaris /usr & Apple ZFS
/dev/sde9  3907012608 3907028991      16384    8M Solaris reserved 1


Disk /dev/sdg: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST32000542AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 42E11F66-8A66-704E-BE10-FB63FAB4ECE2

Device          Start        End    Sectors  Size Type
/dev/sdg1        2048 3907012607 3907010560  1.8T Solaris /usr & Apple ZFS
/dev/sdg9  3907012608 3907028991      16384    8M Solaris reserved 1

Since I'm a new ZFS user, I'm at a complete lost of what I should do next. Any help would be appreciated, I'm quite nervous to have all my data on a small external drive!

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.