Missing /dev/ufs/cf



  • An upgrade from 2.3.2 to 2.3.2 patch1 crashed and left one of my Netgate APU devices unbootable.  No problem… downloaded the 2.3.2 image from http://firmware.netgate.com/APU/amd64/ and used win32DiskImager to write the image to the SD card.  Replaced /conf/config.xml with my previously backed up config and it's back in business.

    Now when I try to upgrade to 2.3.2 patch1, I get an error and the upgrade fails

    …>>> 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.
    **** 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.

    Proceed with upgrade? (y/N) y
    tee: /cf/conf/upgrade_log.txt: Read-only file system
    Secondary partition (/dev/ufs/pfsense1), used for upgrade not found

    Output of the mount command shows no /cf file system mounted

    /dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
    devfs on /dev (devfs, local)
    /dev/md0 on /tmp (ufs, local)
    /dev/md1 on /var (ufs, local)
    devfs on /var/dhcpd/dev (devfs, local)

    During boot I see these errors which explains why there is /cf filesystem mounted.

    Can't stat /dev/ufs/cf: No such file or directory

    ls -al /dev/ufs

    total 1
    dr-xr-xr-x  2 root  wheel      512 Dec  2 14:07 .
    dr-xr-xr-x  22 root  wheel      512 Dec  2 14:07 ..
    crw-r–---  1 root  operator  0x61 Dec  2 14:07 pfsense0

    I have downloaded the 2.3.2 patch1 image from http://firmware.netgate.com/auto-update/APU/amd64/ and wrote that to SD card & I have the same problem.  How do I get that filesystem back so I can perform future upgrades?


  • Rebel Alliance Developer Netgate

    Those are update images not full installation images. You only have one slice, not a full NanoBSD setup.

    Take the opportunity to instead use the 64-bit serial memstick to put a full install on there, forget NanoBSD.