Correction: zpool import -d /dev/disk/by-partuuid big
Its bed time here a while ago, and I am keen to take a fresh backup of some critical things tomorrow before I try it.
I am not super familiar with most zpool commands so will investigate what you and @dan have mentioned, but this ‘should’ be a low risk activity for the data in the pool I believe?
Thanks so much for the help so far, it is very much appreciated.
Correct.
Thanks!
Correction: zpool import -R /mnt -d /dev/disk/by-partuuid big
Correction:
zpool import -R /mnt -d /dev/disk/by-partuuid big
Not necessary if you export again and then finally import from the UI ![]()
Not necessary if you export again and then finally import from the UI
Correction: No correction needed.
How did you create that pool?
This is how Core pools look in Scale.
This is how Core pools look in Scale.
Wouldn’t you consider that a bug in the upgrade process?
Wouldn’t you consider that a bug in the upgrade process?
I would myself! This is a pretty significant issue that I think I got lucky on not having an issue earlier, or more significantly.
Is it possible to raise this as a bug or something, at minimum some documentation and a link on the core → scale migration page to the documentation to fix this.
You can export the pool and reimport it using the partuuid’s instead.
I believe you just add the-d /dev/disk/by-partuuid/to the import command, but someone else here can probably chime in on that.
- export the pool from the UI
zpool import -d /dev/disk/by-id bigzpool export big- import the pool from the UI
Correction:
zpool import -d /dev/disk/by-partuuid big
Correction:
zpool import -R /mnt -d /dev/disk/by-partuuid big
You guys are absolute legends!
I backed up overnight and in the morning was able to perform the steps that pmh put forward with the correction from dan.
To anyone that finds this page in their desperation in a search.
- I had to stop the SMB service before it let me export the pool in the UI.
- On the dialog box for the export pool, untick “Delete saved configurations from TrueNAS?” to preserve config of the pool
- Perform the steps as per pmh with step 2 as per dans notes
- Enjoy a setup that should not break anymore if your hardware changes a bit or drive order etc
Just as a btw to those following on, i got the second WD drive booting on its own fine too, but it was not possible to recover the pool when both drives plugged in still.
So I exported the small pool and was able to boot with both drives then, I did the same UUID fix as above and imported the 2 disks into a new pool and I am back up and running fully now!
It stored only cctv recordings, so no loss, I store important events elsewhere.
I can not thank everyone enough that chimed in to help, much appreciated!
Cheers!
Wouldn’t you consider that a bug in the upgrade process?
Yes. Which would be why I reported it as a bug ![]()
It was closed.
Sorry, cant log into the bug tracker right now to look it up.