Upgrade to 2.0 from 1.2.3 (nanobsd)



  • Hi there,

    can this be done at the moment? Or won't the update succeed? Will the config file be converted correctly?

    Cheers,
    James



  • maybe, maybe, and maybe.  ;D The first two I have no idea, haven't tried that. Most of what we're working on is full installs at the moment as that's all the company that's funding most 2.0 development uses. The last, that depends on what you're using, most things are converted properly, some are not.



  • On my system I can upgrade fine from 1.2.3 to 2.0, but I've heard of some having issues.  My CF card has the 1.2.3 release 512mb image as its base and I've upgraded from 1.2.3 to 2.0 several times because I do that instead of upgrading from 2.0 to 2.0 when updating to newer snapshots.  Basic configuration seems to carry over fine, but I don't know anything beyond that.  Months ago when I started using 2.0, I reset to defaults and recreated my configuration from scratch.

    I would definitely recommend backing up your 1.2.3 configuration before attempting to upgrade, so you can go back to 1.2.3 if needed.  To go back to 1.2.3, go to Diagnostics: NanoBSD and set your 1.2.3 slice as the active slice, replace /conf/config.xml with your backup, delete /tmp/config.cache, and reboot.  1.2.3 may not function well enough to restore your old config if you do not do this.  After booting into 1.2.3, you should restore your configuration to take care of anything 2.0 may have changed before rebooting.



  • I know the 512 MB has issues, it'll run out of space I believe and fail (though just reboot back into what you already have). As for the other sizes, some have reported success, some failures. There are at least 2 nanobsd upgrade related tickets right now.



  • Thanks for your replies guys. I guess I'll wait a little longer, at least for a RC. I am running the 4GB version btw…



  • @cmb:

    I know the 512 MB has issues, it'll run out of space I believe and fail (though just reboot back into what you already have). As for the other sizes, some have reported success, some failures. There are at least 2 nanobsd upgrade related tickets right now.

    I am using the 512 MB images.  I can upgrade from 1.2.3, but upgrades from 2.0 do say it ran out of space and fail.  From what I can tell, the difference seems to be that when receiving the image file 1.2.3 saves it to the disk, but 2.0 saves it to the RAM disk.  I'm guessing some who haven't been able to upgrade to 2.0 from 1.2.3 may have a package installed that is using up enough disk space that it runs out when trying to save the upgrade image (for those having an issue of running out of space when upgrading from 1.2.3).



  • I am using NanoBSD 4GB images.  2.0 x to 2.0 y doesn't work reliably (but it does sometimes). I haven't tried from 1.2, but I wouldn't count on NanoBSD upgrades being that reliable right now.

    Apparently those issues are known and will be taken care of at the right time.


Log in to reply