Failed Rollback from 10.0.4 to 9.10, can't import volumes on 9.x

[wljohnson05]

Once we got the news that 10 was basically dead in the water, I tried rolling back my boot environment to 9.10. That failed and I couldn't get FreeNAS to boot back up. Eventually I got tired of it and I flashed a clean install of 9.10 on the usb and I can get it to boot up clean. Upon trying to restore my encrypted volumes with their keys and passphrases, I get the disks failed to attach error. I tried different variations of 9 with the same result. So I loaded back up 10 and restored my config and all and I can unlock them just fine, but anything on 9 will not let them attach. I didn't upgrade the volumes or anything.

Any clue why this is happening? Am I stuck with 10?

I copied off everything from some of the volumes to just a usb hard drive backup, so in reality if I had to blow them away and start over I could, but one volume has 13TB of data on it and I don't have any good way to move that around.

 

[Ericloewe]

I'd file a bug report. This stuff has seen little testing, so the devs will probably be interested.

Paste the link here, afterwards.

 

[Zofoor]

Probably you need to use the nightly version as Corral has added on the volume some flags that aren't supported by the latest stable version.

Sent from my Nexus 5 using Tapatalk

 

[Zofoor]

https://forums.freenas.org/index.php?resources/migrating-from-freenas-corral-to-freenas-9-10.33/

Sent from my Nexus 5 using Tapatalk

 

[Ericloewe]

Probably you need to use the nightly version as Corral has added on the volume some flags that aren't supported by the latest stable version.

Sent from my Nexus 5 using Tapatalk

No. If you read the guide you linked, you'll find that that's not the case.

 

[wljohnson05]

No. If you read the guide you linked, you'll find that that's not the case.

Agreed. I actually tried the nightly version as well.

 

[wljohnson05]

I'd file a bug report. This stuff has seen little testing, so the devs will probably be interested.

Paste the link here, afterwards.

https://bugs.freenas.org/issues/23444