How do I run CHKDSK on EFI System Partition?












1















I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP.



Link: bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/170316‌​7



Unfortunately, I do not find any clear resource explaining the same. Kindly explain me the appropriate procedure.










share|improve this question

























  • What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

    – SamAndrew81
    Jul 11 '17 at 14:41











  • @SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

    – Benedict Florance
    Jul 11 '17 at 14:45













  • I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

    – SamAndrew81
    Jul 11 '17 at 15:58











  • I already have Windows 10 pre-installed along with the lap.

    – Benedict Florance
    Jul 11 '17 at 16:09
















1















I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP.



Link: bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/170316‌​7



Unfortunately, I do not find any clear resource explaining the same. Kindly explain me the appropriate procedure.










share|improve this question

























  • What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

    – SamAndrew81
    Jul 11 '17 at 14:41











  • @SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

    – Benedict Florance
    Jul 11 '17 at 14:45













  • I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

    – SamAndrew81
    Jul 11 '17 at 15:58











  • I already have Windows 10 pre-installed along with the lap.

    – Benedict Florance
    Jul 11 '17 at 16:09














1












1








1








I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP.



Link: bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/170316‌​7



Unfortunately, I do not find any clear resource explaining the same. Kindly explain me the appropriate procedure.










share|improve this question
















I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP.



Link: bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/170316‌​7



Unfortunately, I do not find any clear resource explaining the same. Kindly explain me the appropriate procedure.







windows windows-10 partitioning chkdsk efi






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 11 '17 at 17:00







Benedict Florance

















asked Jul 11 '17 at 14:30









Benedict FloranceBenedict Florance

1616




1616













  • What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

    – SamAndrew81
    Jul 11 '17 at 14:41











  • @SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

    – Benedict Florance
    Jul 11 '17 at 14:45













  • I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

    – SamAndrew81
    Jul 11 '17 at 15:58











  • I already have Windows 10 pre-installed along with the lap.

    – Benedict Florance
    Jul 11 '17 at 16:09



















  • What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

    – SamAndrew81
    Jul 11 '17 at 14:41











  • @SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

    – Benedict Florance
    Jul 11 '17 at 14:45













  • I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

    – SamAndrew81
    Jul 11 '17 at 15:58











  • I already have Windows 10 pre-installed along with the lap.

    – Benedict Florance
    Jul 11 '17 at 16:09

















What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

– SamAndrew81
Jul 11 '17 at 14:41





What is the exact issue you are having, do you suspect the drive might be failing? If so, you would do better to use the HDD manufacturer's diagnostics tools (SeaTools for Seagate, Lifeguard Utility for WD, etc). Otherwise you can try CHKDSK /f /r and select y to schedule it to run at next boot.

– SamAndrew81
Jul 11 '17 at 14:41













@SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

– Benedict Florance
Jul 11 '17 at 14:45







@SamAndrew81 I tried dual booting Ubuntu with Windows 10 in my Dell laptop. An grub-install error appeared. Checking through the log files, a launchpad expert advised that my EFI sytem partition is corrupt and I need to run chkdsk on ESP. bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1703167

– Benedict Florance
Jul 11 '17 at 14:45















I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

– SamAndrew81
Jul 11 '17 at 15:58





I see. You will need to boot to Windows installer USB flash-drive or perhaps the recovery partition, then you can tell CHKDSK which volume/partition to run against: superuser.com/questions/518634/…

– SamAndrew81
Jul 11 '17 at 15:58













I already have Windows 10 pre-installed along with the lap.

– Benedict Florance
Jul 11 '17 at 16:09





I already have Windows 10 pre-installed along with the lap.

– Benedict Florance
Jul 11 '17 at 16:09










3 Answers
3






active

oldest

votes


















1














The root cause of this is most likely the Windows Fast Startup and Hibernate features. See here and here for information on how to disable these features in Windows. As background, these features turn a shutdown operation into a suspend-to-disk operation. This has the desired effect of reducing subsequent startup times. Unfortunately, the undesirable consequence is that it becomes unsafe to share partitions between OSes, since they'll be in an inconsistent state when the non-Windows OS boots; and then when Windows boots, it won't know how to handle any changes made by the non-Windows OS. Thus, file corruption can result. This can affect the EFI System Partition (ESP), where both Windows and Ubuntu boot loaders are stored. In your case, I'm speculating that these features were active (as they are by default), which resulted in what looks to Ubuntu like filesystem damage.



The solution, if I'm right, is to disable those features. You might need to reboot back into Windows for the change to take effect. Thereafter, you should be able to safely read and write the ESP.



If the partition still shows damage after disabling these features, there is a native Linux tool for repairing FAT filesystems, dosfsck. You can use that instead of CHKDSK in Windows, but you need to either pass it the -a option, as in sudo dosfsck /dev/sda1 to check /dev/sda1; or use more advanced options to approve individual changes. That said, if you're seeing filesystem damage, you might want to back up the partition first. Using a file-level backup tool (cp, tar, or zip, for instance) should be sufficient. A backup will provide you with a fallback position should a filesystem repair operation make matters worse. (This assumes that all the files are successfully read and backed up, of course!) In that case, you can create a fresh filesystem and restore all the files.



I've never tried using CHKDSK on an ESP in Windows. My suspicion is that it could be done as follows:




  1. Open an Administrator Command Prompt window.

  2. Type mountvol E: /S to mount the ESP as E: in that window. (Change E: to whatever you like.)

  3. Type CHKDSK E: to run the check.


As I said, I've not tried this, so I can't promise it would work. If I'm right about the cause of your problem, this procedure alone will be useless, even if there's filesystem damage; you'll still need to disable Fast Startup and Hibernate to make the system safe for use in a multi-boot environment.






share|improve this answer
























  • Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

    – Benedict Florance
    Jul 13 '17 at 19:40





















1














On Windows, I used DISKPART to assign the EFI System partition a letter. Fired up DISKPART, and typed LIST DISK to find the disk, followed by SELECT DISK <N> (where is the drive number). Followed the same steps to find the proper partition (i.e. LIST PARTITION followed by SELECT PARTITION <N>), and then simply typed ASSIGN LETTER = X to have Windows mount the partition to letter X.



Then opened CMD with administrative access. Ran CHKDSK X: /f /r



Then, I tried installing Ubuntu once again, and it installed successfully!






share|improve this answer































    -1














    I had a similar problem recently while installing Ubuntu 18.04 alongside Windows 10. Linux syslog indicated a problem with creating directory /boot/efi/EFI/ubuntu. So, I ran the chkdsk in windows which found the ESP to be corrupted. It fixed the problem with the Ubuntu entry in the partition by deleting it. I then reinstalled Ubuntu from the live disk and it went through.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1228831%2fhow-do-i-run-chkdsk-on-efi-system-partition%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      The root cause of this is most likely the Windows Fast Startup and Hibernate features. See here and here for information on how to disable these features in Windows. As background, these features turn a shutdown operation into a suspend-to-disk operation. This has the desired effect of reducing subsequent startup times. Unfortunately, the undesirable consequence is that it becomes unsafe to share partitions between OSes, since they'll be in an inconsistent state when the non-Windows OS boots; and then when Windows boots, it won't know how to handle any changes made by the non-Windows OS. Thus, file corruption can result. This can affect the EFI System Partition (ESP), where both Windows and Ubuntu boot loaders are stored. In your case, I'm speculating that these features were active (as they are by default), which resulted in what looks to Ubuntu like filesystem damage.



      The solution, if I'm right, is to disable those features. You might need to reboot back into Windows for the change to take effect. Thereafter, you should be able to safely read and write the ESP.



      If the partition still shows damage after disabling these features, there is a native Linux tool for repairing FAT filesystems, dosfsck. You can use that instead of CHKDSK in Windows, but you need to either pass it the -a option, as in sudo dosfsck /dev/sda1 to check /dev/sda1; or use more advanced options to approve individual changes. That said, if you're seeing filesystem damage, you might want to back up the partition first. Using a file-level backup tool (cp, tar, or zip, for instance) should be sufficient. A backup will provide you with a fallback position should a filesystem repair operation make matters worse. (This assumes that all the files are successfully read and backed up, of course!) In that case, you can create a fresh filesystem and restore all the files.



      I've never tried using CHKDSK on an ESP in Windows. My suspicion is that it could be done as follows:




      1. Open an Administrator Command Prompt window.

      2. Type mountvol E: /S to mount the ESP as E: in that window. (Change E: to whatever you like.)

      3. Type CHKDSK E: to run the check.


      As I said, I've not tried this, so I can't promise it would work. If I'm right about the cause of your problem, this procedure alone will be useless, even if there's filesystem damage; you'll still need to disable Fast Startup and Hibernate to make the system safe for use in a multi-boot environment.






      share|improve this answer
























      • Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

        – Benedict Florance
        Jul 13 '17 at 19:40


















      1














      The root cause of this is most likely the Windows Fast Startup and Hibernate features. See here and here for information on how to disable these features in Windows. As background, these features turn a shutdown operation into a suspend-to-disk operation. This has the desired effect of reducing subsequent startup times. Unfortunately, the undesirable consequence is that it becomes unsafe to share partitions between OSes, since they'll be in an inconsistent state when the non-Windows OS boots; and then when Windows boots, it won't know how to handle any changes made by the non-Windows OS. Thus, file corruption can result. This can affect the EFI System Partition (ESP), where both Windows and Ubuntu boot loaders are stored. In your case, I'm speculating that these features were active (as they are by default), which resulted in what looks to Ubuntu like filesystem damage.



      The solution, if I'm right, is to disable those features. You might need to reboot back into Windows for the change to take effect. Thereafter, you should be able to safely read and write the ESP.



      If the partition still shows damage after disabling these features, there is a native Linux tool for repairing FAT filesystems, dosfsck. You can use that instead of CHKDSK in Windows, but you need to either pass it the -a option, as in sudo dosfsck /dev/sda1 to check /dev/sda1; or use more advanced options to approve individual changes. That said, if you're seeing filesystem damage, you might want to back up the partition first. Using a file-level backup tool (cp, tar, or zip, for instance) should be sufficient. A backup will provide you with a fallback position should a filesystem repair operation make matters worse. (This assumes that all the files are successfully read and backed up, of course!) In that case, you can create a fresh filesystem and restore all the files.



      I've never tried using CHKDSK on an ESP in Windows. My suspicion is that it could be done as follows:




      1. Open an Administrator Command Prompt window.

      2. Type mountvol E: /S to mount the ESP as E: in that window. (Change E: to whatever you like.)

      3. Type CHKDSK E: to run the check.


      As I said, I've not tried this, so I can't promise it would work. If I'm right about the cause of your problem, this procedure alone will be useless, even if there's filesystem damage; you'll still need to disable Fast Startup and Hibernate to make the system safe for use in a multi-boot environment.






      share|improve this answer
























      • Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

        – Benedict Florance
        Jul 13 '17 at 19:40
















      1












      1








      1







      The root cause of this is most likely the Windows Fast Startup and Hibernate features. See here and here for information on how to disable these features in Windows. As background, these features turn a shutdown operation into a suspend-to-disk operation. This has the desired effect of reducing subsequent startup times. Unfortunately, the undesirable consequence is that it becomes unsafe to share partitions between OSes, since they'll be in an inconsistent state when the non-Windows OS boots; and then when Windows boots, it won't know how to handle any changes made by the non-Windows OS. Thus, file corruption can result. This can affect the EFI System Partition (ESP), where both Windows and Ubuntu boot loaders are stored. In your case, I'm speculating that these features were active (as they are by default), which resulted in what looks to Ubuntu like filesystem damage.



      The solution, if I'm right, is to disable those features. You might need to reboot back into Windows for the change to take effect. Thereafter, you should be able to safely read and write the ESP.



      If the partition still shows damage after disabling these features, there is a native Linux tool for repairing FAT filesystems, dosfsck. You can use that instead of CHKDSK in Windows, but you need to either pass it the -a option, as in sudo dosfsck /dev/sda1 to check /dev/sda1; or use more advanced options to approve individual changes. That said, if you're seeing filesystem damage, you might want to back up the partition first. Using a file-level backup tool (cp, tar, or zip, for instance) should be sufficient. A backup will provide you with a fallback position should a filesystem repair operation make matters worse. (This assumes that all the files are successfully read and backed up, of course!) In that case, you can create a fresh filesystem and restore all the files.



      I've never tried using CHKDSK on an ESP in Windows. My suspicion is that it could be done as follows:




      1. Open an Administrator Command Prompt window.

      2. Type mountvol E: /S to mount the ESP as E: in that window. (Change E: to whatever you like.)

      3. Type CHKDSK E: to run the check.


      As I said, I've not tried this, so I can't promise it would work. If I'm right about the cause of your problem, this procedure alone will be useless, even if there's filesystem damage; you'll still need to disable Fast Startup and Hibernate to make the system safe for use in a multi-boot environment.






      share|improve this answer













      The root cause of this is most likely the Windows Fast Startup and Hibernate features. See here and here for information on how to disable these features in Windows. As background, these features turn a shutdown operation into a suspend-to-disk operation. This has the desired effect of reducing subsequent startup times. Unfortunately, the undesirable consequence is that it becomes unsafe to share partitions between OSes, since they'll be in an inconsistent state when the non-Windows OS boots; and then when Windows boots, it won't know how to handle any changes made by the non-Windows OS. Thus, file corruption can result. This can affect the EFI System Partition (ESP), where both Windows and Ubuntu boot loaders are stored. In your case, I'm speculating that these features were active (as they are by default), which resulted in what looks to Ubuntu like filesystem damage.



      The solution, if I'm right, is to disable those features. You might need to reboot back into Windows for the change to take effect. Thereafter, you should be able to safely read and write the ESP.



      If the partition still shows damage after disabling these features, there is a native Linux tool for repairing FAT filesystems, dosfsck. You can use that instead of CHKDSK in Windows, but you need to either pass it the -a option, as in sudo dosfsck /dev/sda1 to check /dev/sda1; or use more advanced options to approve individual changes. That said, if you're seeing filesystem damage, you might want to back up the partition first. Using a file-level backup tool (cp, tar, or zip, for instance) should be sufficient. A backup will provide you with a fallback position should a filesystem repair operation make matters worse. (This assumes that all the files are successfully read and backed up, of course!) In that case, you can create a fresh filesystem and restore all the files.



      I've never tried using CHKDSK on an ESP in Windows. My suspicion is that it could be done as follows:




      1. Open an Administrator Command Prompt window.

      2. Type mountvol E: /S to mount the ESP as E: in that window. (Change E: to whatever you like.)

      3. Type CHKDSK E: to run the check.


      As I said, I've not tried this, so I can't promise it would work. If I'm right about the cause of your problem, this procedure alone will be useless, even if there's filesystem damage; you'll still need to disable Fast Startup and Hibernate to make the system safe for use in a multi-boot environment.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jul 13 '17 at 17:05









      Rod SmithRod Smith

      17.1k22042




      17.1k22042













      • Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

        – Benedict Florance
        Jul 13 '17 at 19:40





















      • Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

        – Benedict Florance
        Jul 13 '17 at 19:40



















      Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

      – Benedict Florance
      Jul 13 '17 at 19:40







      Thanks! I did CHKDSK on EFI and it resolved the error. Check the answer :)

      – Benedict Florance
      Jul 13 '17 at 19:40















      1














      On Windows, I used DISKPART to assign the EFI System partition a letter. Fired up DISKPART, and typed LIST DISK to find the disk, followed by SELECT DISK <N> (where is the drive number). Followed the same steps to find the proper partition (i.e. LIST PARTITION followed by SELECT PARTITION <N>), and then simply typed ASSIGN LETTER = X to have Windows mount the partition to letter X.



      Then opened CMD with administrative access. Ran CHKDSK X: /f /r



      Then, I tried installing Ubuntu once again, and it installed successfully!






      share|improve this answer




























        1














        On Windows, I used DISKPART to assign the EFI System partition a letter. Fired up DISKPART, and typed LIST DISK to find the disk, followed by SELECT DISK <N> (where is the drive number). Followed the same steps to find the proper partition (i.e. LIST PARTITION followed by SELECT PARTITION <N>), and then simply typed ASSIGN LETTER = X to have Windows mount the partition to letter X.



        Then opened CMD with administrative access. Ran CHKDSK X: /f /r



        Then, I tried installing Ubuntu once again, and it installed successfully!






        share|improve this answer


























          1












          1








          1







          On Windows, I used DISKPART to assign the EFI System partition a letter. Fired up DISKPART, and typed LIST DISK to find the disk, followed by SELECT DISK <N> (where is the drive number). Followed the same steps to find the proper partition (i.e. LIST PARTITION followed by SELECT PARTITION <N>), and then simply typed ASSIGN LETTER = X to have Windows mount the partition to letter X.



          Then opened CMD with administrative access. Ran CHKDSK X: /f /r



          Then, I tried installing Ubuntu once again, and it installed successfully!






          share|improve this answer













          On Windows, I used DISKPART to assign the EFI System partition a letter. Fired up DISKPART, and typed LIST DISK to find the disk, followed by SELECT DISK <N> (where is the drive number). Followed the same steps to find the proper partition (i.e. LIST PARTITION followed by SELECT PARTITION <N>), and then simply typed ASSIGN LETTER = X to have Windows mount the partition to letter X.



          Then opened CMD with administrative access. Ran CHKDSK X: /f /r



          Then, I tried installing Ubuntu once again, and it installed successfully!







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 13 '17 at 19:41









          Benedict FloranceBenedict Florance

          1616




          1616























              -1














              I had a similar problem recently while installing Ubuntu 18.04 alongside Windows 10. Linux syslog indicated a problem with creating directory /boot/efi/EFI/ubuntu. So, I ran the chkdsk in windows which found the ESP to be corrupted. It fixed the problem with the Ubuntu entry in the partition by deleting it. I then reinstalled Ubuntu from the live disk and it went through.






              share|improve this answer




























                -1














                I had a similar problem recently while installing Ubuntu 18.04 alongside Windows 10. Linux syslog indicated a problem with creating directory /boot/efi/EFI/ubuntu. So, I ran the chkdsk in windows which found the ESP to be corrupted. It fixed the problem with the Ubuntu entry in the partition by deleting it. I then reinstalled Ubuntu from the live disk and it went through.






                share|improve this answer


























                  -1












                  -1








                  -1







                  I had a similar problem recently while installing Ubuntu 18.04 alongside Windows 10. Linux syslog indicated a problem with creating directory /boot/efi/EFI/ubuntu. So, I ran the chkdsk in windows which found the ESP to be corrupted. It fixed the problem with the Ubuntu entry in the partition by deleting it. I then reinstalled Ubuntu from the live disk and it went through.






                  share|improve this answer













                  I had a similar problem recently while installing Ubuntu 18.04 alongside Windows 10. Linux syslog indicated a problem with creating directory /boot/efi/EFI/ubuntu. So, I ran the chkdsk in windows which found the ESP to be corrupted. It fixed the problem with the Ubuntu entry in the partition by deleting it. I then reinstalled Ubuntu from the live disk and it went through.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 12 at 17:14









                  Spark MSpark M

                  1




                  1






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1228831%2fhow-do-i-run-chkdsk-on-efi-system-partition%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Probability when a professor distributes a quiz and homework assignment to a class of n students.

                      Aardman Animations

                      Are they similar matrix