Quote from
Mario on March 13, 2018, 3:25 pm
For the update to 0.5.0.. We use the swap (temp) partition as a temporary place to store the new image when doing the upgrade. So basically we need to create the swap again so it is found by the script.
Please run:
lsblk
You should have an output like this:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 1 465.8G 0 disk
├─sdb2 8:18 1 449.6G 0 part
└─sdb1 8:17 1 16.1G 0 part [SWAP]
sda 8:0 1 465.8G 0 disk
├─sda4 8:4 1 449.6G 0 part
├─sda2 8:2 1 128M 0 part /boot
├─sda3 8:3 1 16G 0 part /
└─sda1 8:1 1 2M 0 part
Just look for the one with 16.1G, in this case /dev/sdb1. Then rebuild the swap:
mkswap /dev/sdb1
swapon /dev/sdb1
Bare in mind that if you have an hdd add on, your swap must be /dev/sdd1
Lets also check the zpools
zpool list
If 'antlets' is not listed, run
zpool import antlets
This may return a warning or error but if you re-run 'zpool list' we should see the 'antlets' zpool in the list.
Now you can start the update again
You can keep the new password simple since it is only used once for the second ssh session to complete the update. When the update is complete the root password will be your original password.
For the update to 0.5.0.. We use the swap (temp) partition as a temporary place to store the new image when doing the upgrade. So basically we need to create the swap again so it is found by the script.
Please run:
lsblk
You should have an output like this:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 1 465.8G 0 disk
├─sdb2 8:18 1 449.6G 0 part
└─sdb1 8:17 1 16.1G 0 part [SWAP]
sda 8:0 1 465.8G 0 disk
├─sda4 8:4 1 449.6G 0 part
├─sda2 8:2 1 128M 0 part /boot
├─sda3 8:3 1 16G 0 part /
└─sda1 8:1 1 2M 0 part
Just look for the one with 16.1G, in this case /dev/sdb1. Then rebuild the swap:
mkswap /dev/sdb1
swapon /dev/sdb1
Bare in mind that if you have an hdd add on, your swap must be /dev/sdd1
Lets also check the zpools
zpool list
If 'antlets' is not listed, run
zpool import antlets
This may return a warning or error but if you re-run 'zpool list' we should see the 'antlets' zpool in the list.
Now you can start the update again
You can keep the new password simple since it is only used once for the second ssh session to complete the update. When the update is complete the root password will be your original password.