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

    After HDD crash and reboot with spare disk, openVPN not working

    Scheduled Pinned Locked Moved Hardware
    3 Posts 2 Posters 182 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.
    • B
      big_blue
      last edited by

      Hi.
      After a HDD crash and boot with the valid drive all the openVPN connection are not working any more. I ve got a certificate validation error while open the tunnel and pfSense was not able to validate the user.

      After reload a backup of the config everything was fine again.

      Background:
      During installation i created a ZFS mirror drive. So the two devices will be written in parallel. In my mind a failure of one disk is not a problem.

      After changing the SATA connection of the valid disk i was able to boot pfSeense from this disk and all the config looks good.

      After a while i getting a call, the VPN is not able to work any more. I do some tests and got the certificate validation error. I created a manual backup a few hours ago, and after reload the config from that backup everything was fine.

      Now i am a little bit confused about the ZFS mirror while installation process. I expect both of the disk are the same and there is no difference which one of the HDDs i am using to boot and start the pfsense.

      Is there something more i have to prepare to get a full backup lf the config on both HDDs?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, that's odd. Were you able to see the cert being passed? Why it was failing?

        The drive mirror should have identical configs. I can only see that sort of error happening if it somehow pulled in some older config from somewhere. That would have been logged at boot if it had though.

        1 Reply Last reply Reply Quote 0
        • B
          big_blue
          last edited by

          That was my expectation too. I didn't notice anything during the boot process. I was in a hurry, so I didn't look carefully at the logs.

          At the moment it is not a problem, the backup was only a few hours old. I just wanted to make sure that I didn't do anything wrong at the initial setup.

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