• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    could not mount /dev/nvme0n1p3 (/bin/fog.upload->beginUpload). The disk contains an unclean file system

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    4
    6
    199
    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.
    • D
      davidsontiago
      last edited by

      Olá pessoal boa tarde!

      Me deparei com esse erro no Fog.

      Alguém já passou por isso e poderia orientar?

      Erro Fog.jpeg

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @davidsontiago
        last edited by

        @davidsontiago Have you tried booting the machine and running checkdisk?

        Similarly, you should turn off fast booting by opening command prompt and running powercfg /hibernate off then try to capture the image.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        D 2 Replies Last reply Reply Quote 0
        • D
          davidsontiago @Tom Elliott
          last edited by

          @Tom-Elliott Olá bom dia!

          Obrigado por responder.

          Não rodei o checkdisk, a máquina é nova.

          Montamos a imagem recente, e rodamos o sysprep.

          Já queria aproveitar o sysprep, neste caso, terei que subir o SO novamente para então rodar o powercfg ;

          Vou testar aqui.

          1 Reply Last reply Reply Quote 0
          • D
            davidsontiago @Tom Elliott
            last edited by

            @Tom-Elliott Olá, obrigado por responder.

            Então, essa máquina é nova, preparamos a imagem e rodamos o sysprep.
            pra eu rodar o comando no Windows, terei que carregar o Windows novamente e rodar o sysprep de novo

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @davidsontiago
              last edited by

              @davidsontiago If you are using sysprep, include the command line option to tell sysprep to power off the computer. You have this message because when you pick shutdown from the menu, windows doesn’t actually shutdown the computer but put it into a sleep state leaving some files open that FOG sees. Sysprep will power off the computer correctly for cloning or use the following command “shutdown -s -t 0” to properly power off the source computer and close all open files.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 0
              • I
                IrishMLK
                last edited by

                This can sometimes happen after you have sysprepped an machine and missed the boot menu prompt, entering the Out-of-box-experience. Trying to shutdown the device will leave the dirty bit resulting in the unclean error.

                To avoid having to sysprep again, allow the device to enter OOBE again and hit shift+F10 and enter “oobe\bypassnro” at the resulting command prompt. Once you hit enter, the system will perform a clean reboot, clearing the dirty bit and allowing Fog to capture the filesystem correctly.

                Hopes this helps someone else as some Dell machines are notorious for failing to get an IP from IPV4 PXE boot.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post

                207

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project