Bug #8537
closed
Update from 2.3.5_1 to 2.3.5_2 on nanobsd failed
0%
Description
Update process from GUI failed due to Duplicate slice missing.
See below detailled informations from GUI textare
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Unlocking package pfSense-kernel-pfSense_wrap... done.
- WARNING **
Duplicate slice required!!
Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happen
After installation a reboot will be required to switch partition.
Secondary partition (/dev/ufs/pfsense1), used for upgrade not found
Locking package pfSense-kernel-pfSense_wrap... failed.
Locking package pfSense-kernel-pfSense_wrap... failed.
Locking package pfSense-kernel-pfSense_wrap... failed.
Locking package pfSense-kernel-pfSense_wrap... failed.
Locking package pfSense-kernel-pfSense_wrap... failed.
.
.
.... So many same sentence...
__RC=1 __REBOOT_AFTER=10
Updated by Jim Pingle over 6 years ago
- Status changed from New to Not a Bug
- Priority changed from High to Normal
- Target version deleted (
2.3.6)
"Secondary partition (/dev/ufs/pfsense1), used for upgrade not found" reads like you didn't write a full NanoBSD image to the disk, just an upgrade slice. Or perhaps something wrong with the disk itself (hardware issue).
Not enough detail here for a proper bug report, and NanoBSD is dead anyhow. Upgrades work fine on systems we have tested before 2.3.5-p2 release.
If you want to dig into the problem, please use a discussion platform such as the forum (when it comes back online today), or the pfSense subreddit.
Updated by Laurent BONNIN over 6 years ago
Jim Pingle wrote:
"Secondary partition (/dev/ufs/pfsense1), used for upgrade not found" reads like you didn't write a full NanoBSD image to the disk, just an upgrade slice. Or perhaps something wrong with the disk itself (hardware issue).
Not enough detail here for a proper bug report, and NanoBSD is dead anyhow. Upgrades work fine on systems we have tested before 2.3.5-p2 release.
If you want to dig into the problem, please use a discussion platform such as the forum (when it comes back online today), or the pfSense subreddit.
Dear,
Thanks for replying so quickly :)
The card was made using the IMG from web site...
And I already did an update from GUI and it worked like a charme.
I will check the disk (a CF).
Regards,
Laurent
Updated by Chris Palmer over 6 years ago
I cannot confirm this.
Update from 2.3.5_1 to 2.3.5_2 on nanobsd successful here.