Error when switching boot slices

Xypherious

Hello all,

I recieve the following error when executing the script /etc/rc.nanobsd_switch_boot_slice

gpart: No such geom: mmc.
Boot slice  : mmcs2 (pfsense1)
Active slice: mmcs

Switching active slice...gpart: No such geom: mmc.
gpart: arg0 'mmc': Invalid argument
boot0cfg: Unable to get providername for /dev/mmc

Done.

gpart: No such geom: mmc.
Boot slice  : mmcs2 (pfsense1)
Active slice: mmcs

These are my current slices:

=>      63  15724481  mmcsd0  MBR  (7.5G)
        63   3844449       1  freebsd  (1.8G)
   3844512        63          - free -  (32K)
   3844575   3844449       2  freebsd  [active]  (1.8G)
   7689024    102816       3  freebsd  (50M)
   7791840   7932704          - free -  (3.8G)

=>      0  3844449  mmcsd0s2  BSD  (1.8G)
        0       16            - free -  (8.0K)
       16  3844433         1  !0  (1.8G)

=>      0  3844449  mmcsd0s1  BSD  (1.8G)
        0       16            - free -  (8.0K)
       16  3844433         1  !0  (1.8G)

I need to switch to another slice in orde to upgrade to 2.4.0

Thanks in advance

jimp

That looks like it's having trouble parsing out the disk name and slice numbers from your setup. Though I don't think we've ever tried NanoBSD on an mmcsdX disk.

Your best bet is likely to not use NanoBSD there, run a full install instead. Activate the option to put /tmp and /var in RAM.

NanoBSD is dead, it is no longer in 2.4 and 2.3.x is in security/errata maintenance only for the next year. It's unlikely any development time would be dedicated to fixing such a rare issue with NanoBSD.

Xypherious

I will need to find out if my system is capable of running a full install. Could you please explain what you mean by Activate the option to put /tmp and /var in RAM.?

Thanks for helping me out :)

jimp

If it can run NanoBSD, it can probably run a full install. As long as it's 64-bit hardware and can boot from USB to run the installer.

As for the /tmp and /var bit, if you look at System > Advanced on the Miscellaneous tab there you will find the option to place /tmp and /var in RAM disks. The vast majority of the writes on pfSense are in /tmp and /var to temporary volatile status files or logs, and placing those in RAM disks will prevent those writes from wearing out your drives.