The attempt to mount a file system with type vfat in SSI1(0,0,0),partition#1(sda)at/boot/efi failed












3















I'm trying to install Ubuntu 14.04 and it pops up a message saying:



The attempt to mount a file system with type vfat in SSI1(0,0,0),partition#1(sda)at/boot/efi failed


Can someone help please?










share|improve this question




















  • 1





    Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

    – David Foerster
    Mar 25 '17 at 11:03






  • 1





    Possible duplicate of Problem installing 12.04 in efi mode

    – karel
    Mar 26 '17 at 12:04
















3















I'm trying to install Ubuntu 14.04 and it pops up a message saying:



The attempt to mount a file system with type vfat in SSI1(0,0,0),partition#1(sda)at/boot/efi failed


Can someone help please?










share|improve this question




















  • 1





    Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

    – David Foerster
    Mar 25 '17 at 11:03






  • 1





    Possible duplicate of Problem installing 12.04 in efi mode

    – karel
    Mar 26 '17 at 12:04














3












3








3


1






I'm trying to install Ubuntu 14.04 and it pops up a message saying:



The attempt to mount a file system with type vfat in SSI1(0,0,0),partition#1(sda)at/boot/efi failed


Can someone help please?










share|improve this question
















I'm trying to install Ubuntu 14.04 and it pops up a message saying:



The attempt to mount a file system with type vfat in SSI1(0,0,0),partition#1(sda)at/boot/efi failed


Can someone help please?







mount uefi partitions






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 17 '17 at 22:01









Zanna

50.4k13133241




50.4k13133241










asked Jul 25 '14 at 0:06









carlos carlos

1612




1612








  • 1





    Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

    – David Foerster
    Mar 25 '17 at 11:03






  • 1





    Possible duplicate of Problem installing 12.04 in efi mode

    – karel
    Mar 26 '17 at 12:04














  • 1





    Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

    – David Foerster
    Mar 25 '17 at 11:03






  • 1





    Possible duplicate of Problem installing 12.04 in efi mode

    – karel
    Mar 26 '17 at 12:04








1




1





Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

– David Foerster
Mar 25 '17 at 11:03





Possible duplicate of Installing Ubuntu Alongside a Pre-Installed Windows with UEFI

– David Foerster
Mar 25 '17 at 11:03




1




1





Possible duplicate of Problem installing 12.04 in efi mode

– karel
Mar 26 '17 at 12:04





Possible duplicate of Problem installing 12.04 in efi mode

– karel
Mar 26 '17 at 12:04










5 Answers
5






active

oldest

votes


















3














I had exactly the same problem today while installing Ubuntu Server on a UEFI machine. I received the following message:



The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #2 (sda) at /boot/efi failed.


I created an EFI partition and a normal linux partition on a USB disk with the gdisk command. fdisk -l gave the following result for the disk:



Device       Start     End Sectors  Size Type
/dev/sdc1 2048 1050623 1048576 512M EFI System
/dev/sdc2 1050624 7831518 6780895 3.2G Linux filesystem


I then tried to mount the EFI partition with mount /dev/sdc1 /test/, but got the following response:



mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.


I also tried mount -t vfat /dev/sdc1 /test/, but received the same response. I then formatted the EFI partition with mkfs.vfat /dev/sdc1. I then tried to mount the EFI partition again with mount /dev/sdc1 /test/. It worked perfectly.



My conclusion is therefore that the Ubuntu Server installer needs the EFI partition to be formatted when it tries to mount it to /boot/efi.






share|improve this answer


























  • Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

    – Donn Lee
    Sep 27 '18 at 0:45



















2














It's quite possible that you're seeing the effects of the Windows "Fast Startup" feature. This feature turns shutdowns into suspend-to-disk operations, which means that filesystems Windows has mounted (potentially including the EFI System Partition (ESP), which Ubuntu mounts at /boot/efi) may appear to be damaged in Ubuntu, and may not mount correctly. The solution is to disable Fast Startup in Windows. Note that the Windows Fast Startup feature is entirely separate from a feature that probably has a similar name in the firmware. The firmware feature is much less dangerous, although it will sometimes interfere with the computer's ability to boot from a USB flash drive, so it may need to be disabled to get the installer to boot.






share|improve this answer































    0














    it sounds like you are getting a read error on either the hard disk or the cd, if you are confident the hard drive is fine then you can try burning another dvd and if that does not work it means you probably have a bad hard disk. If you can rule out either of those please report the bug on launchpad






    share|improve this answer































      0














      I reformatted my main partition as ext4.



      Went into terminal with ctrl alt f1



      Then formatted the partition



      sudo mkfs -t ext4 /dev/sda2





      share|improve this answer

































        0














        I had my first partition intended for the UEFI partition, and it was 100MB and type ext4. I got this error you got too, and I have secure boot and fast boot enabled in my BIOS/UEFI settings. My fix was to simply use gparted to delete that 100 MB partition and then when I did the Ubuntu 18 install I chose "Something else" and at that point dedicated the 100 MB partition for the UEFI boot stuff. It then formatted it for me and it worked!



        Summary for me: don't have it pre-formatted as ext4. Instead, leave the empty 100 MB or so there for the UEFI boot partition, but let the Ubuntu installer partition and format it.



        For all other partitions it was ok to have manually done them before-hand via gparted, and I did not have to turn off fast boot or secure boot in the BIOS/UEFI settings. Note, however, that I do NOT have Windows installed on this machine: it is Ubuntu 18 only.






        share|improve this answer

























          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          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%2faskubuntu.com%2fquestions%2f502307%2fthe-attempt-to-mount-a-file-system-with-type-vfat-in-ssi10-0-0-partition1sda%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          I had exactly the same problem today while installing Ubuntu Server on a UEFI machine. I received the following message:



          The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #2 (sda) at /boot/efi failed.


          I created an EFI partition and a normal linux partition on a USB disk with the gdisk command. fdisk -l gave the following result for the disk:



          Device       Start     End Sectors  Size Type
          /dev/sdc1 2048 1050623 1048576 512M EFI System
          /dev/sdc2 1050624 7831518 6780895 3.2G Linux filesystem


          I then tried to mount the EFI partition with mount /dev/sdc1 /test/, but got the following response:



          mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
          missing codepage or helper program, or other error

          In some cases useful info is found in syslog - try
          dmesg | tail or so.


          I also tried mount -t vfat /dev/sdc1 /test/, but received the same response. I then formatted the EFI partition with mkfs.vfat /dev/sdc1. I then tried to mount the EFI partition again with mount /dev/sdc1 /test/. It worked perfectly.



          My conclusion is therefore that the Ubuntu Server installer needs the EFI partition to be formatted when it tries to mount it to /boot/efi.






          share|improve this answer


























          • Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

            – Donn Lee
            Sep 27 '18 at 0:45
















          3














          I had exactly the same problem today while installing Ubuntu Server on a UEFI machine. I received the following message:



          The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #2 (sda) at /boot/efi failed.


          I created an EFI partition and a normal linux partition on a USB disk with the gdisk command. fdisk -l gave the following result for the disk:



          Device       Start     End Sectors  Size Type
          /dev/sdc1 2048 1050623 1048576 512M EFI System
          /dev/sdc2 1050624 7831518 6780895 3.2G Linux filesystem


          I then tried to mount the EFI partition with mount /dev/sdc1 /test/, but got the following response:



          mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
          missing codepage or helper program, or other error

          In some cases useful info is found in syslog - try
          dmesg | tail or so.


          I also tried mount -t vfat /dev/sdc1 /test/, but received the same response. I then formatted the EFI partition with mkfs.vfat /dev/sdc1. I then tried to mount the EFI partition again with mount /dev/sdc1 /test/. It worked perfectly.



          My conclusion is therefore that the Ubuntu Server installer needs the EFI partition to be formatted when it tries to mount it to /boot/efi.






          share|improve this answer


























          • Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

            – Donn Lee
            Sep 27 '18 at 0:45














          3












          3








          3







          I had exactly the same problem today while installing Ubuntu Server on a UEFI machine. I received the following message:



          The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #2 (sda) at /boot/efi failed.


          I created an EFI partition and a normal linux partition on a USB disk with the gdisk command. fdisk -l gave the following result for the disk:



          Device       Start     End Sectors  Size Type
          /dev/sdc1 2048 1050623 1048576 512M EFI System
          /dev/sdc2 1050624 7831518 6780895 3.2G Linux filesystem


          I then tried to mount the EFI partition with mount /dev/sdc1 /test/, but got the following response:



          mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
          missing codepage or helper program, or other error

          In some cases useful info is found in syslog - try
          dmesg | tail or so.


          I also tried mount -t vfat /dev/sdc1 /test/, but received the same response. I then formatted the EFI partition with mkfs.vfat /dev/sdc1. I then tried to mount the EFI partition again with mount /dev/sdc1 /test/. It worked perfectly.



          My conclusion is therefore that the Ubuntu Server installer needs the EFI partition to be formatted when it tries to mount it to /boot/efi.






          share|improve this answer















          I had exactly the same problem today while installing Ubuntu Server on a UEFI machine. I received the following message:



          The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #2 (sda) at /boot/efi failed.


          I created an EFI partition and a normal linux partition on a USB disk with the gdisk command. fdisk -l gave the following result for the disk:



          Device       Start     End Sectors  Size Type
          /dev/sdc1 2048 1050623 1048576 512M EFI System
          /dev/sdc2 1050624 7831518 6780895 3.2G Linux filesystem


          I then tried to mount the EFI partition with mount /dev/sdc1 /test/, but got the following response:



          mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
          missing codepage or helper program, or other error

          In some cases useful info is found in syslog - try
          dmesg | tail or so.


          I also tried mount -t vfat /dev/sdc1 /test/, but received the same response. I then formatted the EFI partition with mkfs.vfat /dev/sdc1. I then tried to mount the EFI partition again with mount /dev/sdc1 /test/. It worked perfectly.



          My conclusion is therefore that the Ubuntu Server installer needs the EFI partition to be formatted when it tries to mount it to /boot/efi.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 17 '17 at 21:59









          Zanna

          50.4k13133241




          50.4k13133241










          answered Sep 16 '17 at 19:27









          johzijohzi

          312




          312













          • Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

            – Donn Lee
            Sep 27 '18 at 0:45



















          • Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

            – Donn Lee
            Sep 27 '18 at 0:45

















          Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

          – Donn Lee
          Sep 27 '18 at 0:45





          Yep, encountered on ubuntu Server installer. Had to do mkfs.vfat -F 32 /dev/sdX1 (where "X" is my drive letter) before running installer again. Used a clonezilla usb flash disk to run mkfs.vfat, parted, etc

          – Donn Lee
          Sep 27 '18 at 0:45













          2














          It's quite possible that you're seeing the effects of the Windows "Fast Startup" feature. This feature turns shutdowns into suspend-to-disk operations, which means that filesystems Windows has mounted (potentially including the EFI System Partition (ESP), which Ubuntu mounts at /boot/efi) may appear to be damaged in Ubuntu, and may not mount correctly. The solution is to disable Fast Startup in Windows. Note that the Windows Fast Startup feature is entirely separate from a feature that probably has a similar name in the firmware. The firmware feature is much less dangerous, although it will sometimes interfere with the computer's ability to boot from a USB flash drive, so it may need to be disabled to get the installer to boot.






          share|improve this answer




























            2














            It's quite possible that you're seeing the effects of the Windows "Fast Startup" feature. This feature turns shutdowns into suspend-to-disk operations, which means that filesystems Windows has mounted (potentially including the EFI System Partition (ESP), which Ubuntu mounts at /boot/efi) may appear to be damaged in Ubuntu, and may not mount correctly. The solution is to disable Fast Startup in Windows. Note that the Windows Fast Startup feature is entirely separate from a feature that probably has a similar name in the firmware. The firmware feature is much less dangerous, although it will sometimes interfere with the computer's ability to boot from a USB flash drive, so it may need to be disabled to get the installer to boot.






            share|improve this answer


























              2












              2








              2







              It's quite possible that you're seeing the effects of the Windows "Fast Startup" feature. This feature turns shutdowns into suspend-to-disk operations, which means that filesystems Windows has mounted (potentially including the EFI System Partition (ESP), which Ubuntu mounts at /boot/efi) may appear to be damaged in Ubuntu, and may not mount correctly. The solution is to disable Fast Startup in Windows. Note that the Windows Fast Startup feature is entirely separate from a feature that probably has a similar name in the firmware. The firmware feature is much less dangerous, although it will sometimes interfere with the computer's ability to boot from a USB flash drive, so it may need to be disabled to get the installer to boot.






              share|improve this answer













              It's quite possible that you're seeing the effects of the Windows "Fast Startup" feature. This feature turns shutdowns into suspend-to-disk operations, which means that filesystems Windows has mounted (potentially including the EFI System Partition (ESP), which Ubuntu mounts at /boot/efi) may appear to be damaged in Ubuntu, and may not mount correctly. The solution is to disable Fast Startup in Windows. Note that the Windows Fast Startup feature is entirely separate from a feature that probably has a similar name in the firmware. The firmware feature is much less dangerous, although it will sometimes interfere with the computer's ability to boot from a USB flash drive, so it may need to be disabled to get the installer to boot.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jul 25 '14 at 0:51









              Rod SmithRod Smith

              35.2k43870




              35.2k43870























                  0














                  it sounds like you are getting a read error on either the hard disk or the cd, if you are confident the hard drive is fine then you can try burning another dvd and if that does not work it means you probably have a bad hard disk. If you can rule out either of those please report the bug on launchpad






                  share|improve this answer




























                    0














                    it sounds like you are getting a read error on either the hard disk or the cd, if you are confident the hard drive is fine then you can try burning another dvd and if that does not work it means you probably have a bad hard disk. If you can rule out either of those please report the bug on launchpad






                    share|improve this answer


























                      0












                      0








                      0







                      it sounds like you are getting a read error on either the hard disk or the cd, if you are confident the hard drive is fine then you can try burning another dvd and if that does not work it means you probably have a bad hard disk. If you can rule out either of those please report the bug on launchpad






                      share|improve this answer













                      it sounds like you are getting a read error on either the hard disk or the cd, if you are confident the hard drive is fine then you can try burning another dvd and if that does not work it means you probably have a bad hard disk. If you can rule out either of those please report the bug on launchpad







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jul 25 '14 at 0:17









                      sbergeronsbergeron

                      1,99852240




                      1,99852240























                          0














                          I reformatted my main partition as ext4.



                          Went into terminal with ctrl alt f1



                          Then formatted the partition



                          sudo mkfs -t ext4 /dev/sda2





                          share|improve this answer






























                            0














                            I reformatted my main partition as ext4.



                            Went into terminal with ctrl alt f1



                            Then formatted the partition



                            sudo mkfs -t ext4 /dev/sda2





                            share|improve this answer




























                              0












                              0








                              0







                              I reformatted my main partition as ext4.



                              Went into terminal with ctrl alt f1



                              Then formatted the partition



                              sudo mkfs -t ext4 /dev/sda2





                              share|improve this answer















                              I reformatted my main partition as ext4.



                              Went into terminal with ctrl alt f1



                              Then formatted the partition



                              sudo mkfs -t ext4 /dev/sda2






                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Sep 17 '17 at 22:03









                              Zanna

                              50.4k13133241




                              50.4k13133241










                              answered Feb 6 '16 at 18:47









                              FinkAvenueFinkAvenue

                              1113




                              1113























                                  0














                                  I had my first partition intended for the UEFI partition, and it was 100MB and type ext4. I got this error you got too, and I have secure boot and fast boot enabled in my BIOS/UEFI settings. My fix was to simply use gparted to delete that 100 MB partition and then when I did the Ubuntu 18 install I chose "Something else" and at that point dedicated the 100 MB partition for the UEFI boot stuff. It then formatted it for me and it worked!



                                  Summary for me: don't have it pre-formatted as ext4. Instead, leave the empty 100 MB or so there for the UEFI boot partition, but let the Ubuntu installer partition and format it.



                                  For all other partitions it was ok to have manually done them before-hand via gparted, and I did not have to turn off fast boot or secure boot in the BIOS/UEFI settings. Note, however, that I do NOT have Windows installed on this machine: it is Ubuntu 18 only.






                                  share|improve this answer






























                                    0














                                    I had my first partition intended for the UEFI partition, and it was 100MB and type ext4. I got this error you got too, and I have secure boot and fast boot enabled in my BIOS/UEFI settings. My fix was to simply use gparted to delete that 100 MB partition and then when I did the Ubuntu 18 install I chose "Something else" and at that point dedicated the 100 MB partition for the UEFI boot stuff. It then formatted it for me and it worked!



                                    Summary for me: don't have it pre-formatted as ext4. Instead, leave the empty 100 MB or so there for the UEFI boot partition, but let the Ubuntu installer partition and format it.



                                    For all other partitions it was ok to have manually done them before-hand via gparted, and I did not have to turn off fast boot or secure boot in the BIOS/UEFI settings. Note, however, that I do NOT have Windows installed on this machine: it is Ubuntu 18 only.






                                    share|improve this answer




























                                      0












                                      0








                                      0







                                      I had my first partition intended for the UEFI partition, and it was 100MB and type ext4. I got this error you got too, and I have secure boot and fast boot enabled in my BIOS/UEFI settings. My fix was to simply use gparted to delete that 100 MB partition and then when I did the Ubuntu 18 install I chose "Something else" and at that point dedicated the 100 MB partition for the UEFI boot stuff. It then formatted it for me and it worked!



                                      Summary for me: don't have it pre-formatted as ext4. Instead, leave the empty 100 MB or so there for the UEFI boot partition, but let the Ubuntu installer partition and format it.



                                      For all other partitions it was ok to have manually done them before-hand via gparted, and I did not have to turn off fast boot or secure boot in the BIOS/UEFI settings. Note, however, that I do NOT have Windows installed on this machine: it is Ubuntu 18 only.






                                      share|improve this answer















                                      I had my first partition intended for the UEFI partition, and it was 100MB and type ext4. I got this error you got too, and I have secure boot and fast boot enabled in my BIOS/UEFI settings. My fix was to simply use gparted to delete that 100 MB partition and then when I did the Ubuntu 18 install I chose "Something else" and at that point dedicated the 100 MB partition for the UEFI boot stuff. It then formatted it for me and it worked!



                                      Summary for me: don't have it pre-formatted as ext4. Instead, leave the empty 100 MB or so there for the UEFI boot partition, but let the Ubuntu installer partition and format it.



                                      For all other partitions it was ok to have manually done them before-hand via gparted, and I did not have to turn off fast boot or secure boot in the BIOS/UEFI settings. Note, however, that I do NOT have Windows installed on this machine: it is Ubuntu 18 only.







                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Dec 25 '18 at 9:22

























                                      answered Dec 25 '18 at 9:07









                                      Gabriel StaplesGabriel Staples

                                      661721




                                      661721






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Ask Ubuntu!


                                          • 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%2faskubuntu.com%2fquestions%2f502307%2fthe-attempt-to-mount-a-file-system-with-type-vfat-in-ssi10-0-0-partition1sda%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

                                          Quarter-circle Tiles

                                          build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

                                          Mont Emei