iocage pool "disappears" on reboot (11.2-BETA3)

[sami]

Hi,

Sure this strange issue is on a beta release, none the less I would like to learn why.
I do not have any errors to post really so, please, help me out to which errors to look for.

I have 3 pools connected to my test machine.

freenas-boot (ada1 - freenas)
tank (all media)
iocage (ada0 - iocage jails - SSD)

The iocage gets activated by iocage when running a fetch. My normal approach is to create a machine, do some things, set template=yes, create machine off of that template.
Once said and done, the pool still looks great on zpool status since this has happened before I tried to do a zpool scrub iocage which reveals no problems.

Here's where the problems come in. Once I issue a reboot, ada1 is no longer detected by FreeNAS during boot. dmesg | grep ada0 gives me nothing.
Running iocage list now activates tank as iocage pool instead.

I am fairly limited in my knowledge about ZFS and looking to learn as I go. If I'm missing something basic here to look into, please feel free to teach me.

As a side note, I'm counting the hours to RC1 so I can see if the issue is still there.

 

[sretalla]

I see your problem.

The iocage dataset which is created with iocage activate needs to get mounted as /mnt/iocage.

If you have a pool called iocage also trying to mount there, I think you're in trouble (like you are noticing).

Rename your jails pool and see if it goes better.

 

[sami]

I see your problem.

The iocage dataset which is created with iocage activate needs to get mounted as /mnt/iocage.

If you have a pool called iocage also trying to mount there, I think you're in trouble (like you are noticing).

Rename your jails pool and see if it goes better.

I'll keep that in mind for future testing.
However, the actual drive is "lost" and not showing up on boot when first reboot is issued. That may be a HW issue, not sure.

 

[sretalla]

Have a look at zfs get mountpoint /mnt/iocage.

Don't forget that disk assignment isn't permanent, so ada1 or whatever isn't always the same disk.

Also have a look at zpool import and see if you have something there...

I agree that if your disk is broken, you have another problem to worry about.

 

[8-bit Yoda]

Yeah, you'll have to rename your pool.
https://forums.freenas.org/index.ph...me-with-data-already-in-it.13061/#post-303693