Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Duplicate Slice from Command Line

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    2 Posts 2 Posters 797 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      joe91
      last edited by

      I am trying to follow https://doc.pfsense.org/index.php/Upgrading_64-bit_NanoBSD_2.3_to_2.4 to upgrade my pfSense appliance (currently on 2.3.4-RELEASE-p1 (amd64)), which came pre installed with NanoBSD 64-bit, to 2.4.0.

      Bootup slice is currently da0s2, so I am clicking the Duplicate da0s2 -> da0s1 button as instructed, however, at this point the GUI just hangs indefinitely, tried twice, second time leaving it overnight for approx 7.5 hours. all the the System Log say is:

      nginx: 2017/11/01 23:34:10 [error] 23269#100103: *132 upstream timed out (60: Operation timed out) while reading upstream, client: [IPRemoved], server: , request: "POST /diag_nanobsd.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "[HostnameRemoved]", referrer: "https://[HostnameRemoved]/diag_nanobsd.php"

      So it may have suceeded in the background, but I'd rather be sure, therefore, I would like to SSH onto the appliance and do the duplication via the command line (where I can see the result/any errors), however, cannot seem to find the command documented anywhere.

      Does anyone know what the command to duplicate da0s2 to da0s1 is? Is it as simple as using dd?

      1 Reply Last reply Reply Quote 0
      • S
        simianpirate
        last edited by

        I am also having this issue following along with the conversion guide. I click the button and wait, finally I just get a blank web ui view.

        Update:

        I did an ls on /dev after pressing the button and saw that it created an new sa1

        Went ahead and ran the script, updated, and let it reboot.

        It did take longer than normal to boot but I believe it was doing a filesystem check. Don't know for sure, as I don't have a console cable available.

        Just did the update to 2.4.1 from the web ui and everything rebooted again just fine.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.