e2fsck: Cannot continue, aborting












7















I got this output:



fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/ubuntu--vg-root is mounted.
e2fsck: Cannot continue, aborting.


after I used the fsck command. Any answers?










share|improve this question




















  • 3





    As it says, the device is mounted. You can't fsck a volume while it is mounted.

    – psusi
    Oct 14 '14 at 13:47











  • I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

    – Brian Knoblauch
    Apr 25 '18 at 18:16
















7















I got this output:



fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/ubuntu--vg-root is mounted.
e2fsck: Cannot continue, aborting.


after I used the fsck command. Any answers?










share|improve this question




















  • 3





    As it says, the device is mounted. You can't fsck a volume while it is mounted.

    – psusi
    Oct 14 '14 at 13:47











  • I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

    – Brian Knoblauch
    Apr 25 '18 at 18:16














7












7








7


1






I got this output:



fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/ubuntu--vg-root is mounted.
e2fsck: Cannot continue, aborting.


after I used the fsck command. Any answers?










share|improve this question
















I got this output:



fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/ubuntu--vg-root is mounted.
e2fsck: Cannot continue, aborting.


after I used the fsck command. Any answers?







fsck






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 14 '14 at 14:55









αғsнιη

24.3k2295156




24.3k2295156










asked Oct 14 '14 at 13:34









Shew Jia HaoShew Jia Hao

36112




36112








  • 3





    As it says, the device is mounted. You can't fsck a volume while it is mounted.

    – psusi
    Oct 14 '14 at 13:47











  • I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

    – Brian Knoblauch
    Apr 25 '18 at 18:16














  • 3





    As it says, the device is mounted. You can't fsck a volume while it is mounted.

    – psusi
    Oct 14 '14 at 13:47











  • I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

    – Brian Knoblauch
    Apr 25 '18 at 18:16








3




3





As it says, the device is mounted. You can't fsck a volume while it is mounted.

– psusi
Oct 14 '14 at 13:47





As it says, the device is mounted. You can't fsck a volume while it is mounted.

– psusi
Oct 14 '14 at 13:47













I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

– Brian Knoblauch
Apr 25 '18 at 18:16





I ran across the same thing. A little confusing. The line about it being mounted looks like a general statement rather than an error report. :-)

– Brian Knoblauch
Apr 25 '18 at 18:16










3 Answers
3






active

oldest

votes


















10














If you just use fsck to check the volume you can run



fsck -nf /dev/sda1



  • n -> dry-run: will not do any change (just checking)

  • f -> force : sometimes it says clean but you can force a new check


If you want to fix filesystem errors, first unmount your partition: umount /dev/sda1






share|improve this answer

































    2














    I encountered similar issue especially when you are still accessing the mount point. It can below any one of below two reasons.



    You cannot run on the root FS
    Say you can in directory "/mnt" and you have unmounted the volume mounted on "/mnt". You will encounter same error. Make use that you are not in same directory.



    Before :



    root@ip-172-31-28-38 /mnt# fsck -f /dev/xvdh
    fsck from util-linux 2.23.2
    e2fsck 1.42.12 (29-Aug-2014)
    /dev/xvdh is in use.
    e2fsck: Cannot continue, aborting.


    root@ip-172-31-28-38 /mnt#
    root@ip-172-31-28-38 /mnt# cd /


    After :



    root@ip-172-31-28-38 /# fsck -f /dev/xvdh
    fsck from util-linux 2.23.2
    e2fsck 1.42.12 (29-Aug-2014)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/xvdh: 12/524288 files (0.0% non-contiguous), 70287/2097152 blocks
    root@ip-172-31-28-38 /#





    share|improve this answer































      0














      I don't know why, but I had to service udev stop (on debian based system).



      After stopping udev the e2fsck -f /dev/sda1-command worked and didn't print the e2fsck: Cannot continue, aborting-Message anymore.



      I dont't know, if it has something to do with http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html - but this page gave me the hint to try it.






      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%2f536955%2fe2fsck-cannot-continue-aborting%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









        10














        If you just use fsck to check the volume you can run



        fsck -nf /dev/sda1



        • n -> dry-run: will not do any change (just checking)

        • f -> force : sometimes it says clean but you can force a new check


        If you want to fix filesystem errors, first unmount your partition: umount /dev/sda1






        share|improve this answer






























          10














          If you just use fsck to check the volume you can run



          fsck -nf /dev/sda1



          • n -> dry-run: will not do any change (just checking)

          • f -> force : sometimes it says clean but you can force a new check


          If you want to fix filesystem errors, first unmount your partition: umount /dev/sda1






          share|improve this answer




























            10












            10








            10







            If you just use fsck to check the volume you can run



            fsck -nf /dev/sda1



            • n -> dry-run: will not do any change (just checking)

            • f -> force : sometimes it says clean but you can force a new check


            If you want to fix filesystem errors, first unmount your partition: umount /dev/sda1






            share|improve this answer















            If you just use fsck to check the volume you can run



            fsck -nf /dev/sda1



            • n -> dry-run: will not do any change (just checking)

            • f -> force : sometimes it says clean but you can force a new check


            If you want to fix filesystem errors, first unmount your partition: umount /dev/sda1







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 2 '15 at 16:22









            Cees Timmerman

            235116




            235116










            answered Nov 17 '14 at 20:44









            BoopBoop

            20115




            20115

























                2














                I encountered similar issue especially when you are still accessing the mount point. It can below any one of below two reasons.



                You cannot run on the root FS
                Say you can in directory "/mnt" and you have unmounted the volume mounted on "/mnt". You will encounter same error. Make use that you are not in same directory.



                Before :



                root@ip-172-31-28-38 /mnt# fsck -f /dev/xvdh
                fsck from util-linux 2.23.2
                e2fsck 1.42.12 (29-Aug-2014)
                /dev/xvdh is in use.
                e2fsck: Cannot continue, aborting.


                root@ip-172-31-28-38 /mnt#
                root@ip-172-31-28-38 /mnt# cd /


                After :



                root@ip-172-31-28-38 /# fsck -f /dev/xvdh
                fsck from util-linux 2.23.2
                e2fsck 1.42.12 (29-Aug-2014)
                Pass 1: Checking inodes, blocks, and sizes
                Pass 2: Checking directory structure
                Pass 3: Checking directory connectivity
                Pass 4: Checking reference counts
                Pass 5: Checking group summary information
                /dev/xvdh: 12/524288 files (0.0% non-contiguous), 70287/2097152 blocks
                root@ip-172-31-28-38 /#





                share|improve this answer




























                  2














                  I encountered similar issue especially when you are still accessing the mount point. It can below any one of below two reasons.



                  You cannot run on the root FS
                  Say you can in directory "/mnt" and you have unmounted the volume mounted on "/mnt". You will encounter same error. Make use that you are not in same directory.



                  Before :



                  root@ip-172-31-28-38 /mnt# fsck -f /dev/xvdh
                  fsck from util-linux 2.23.2
                  e2fsck 1.42.12 (29-Aug-2014)
                  /dev/xvdh is in use.
                  e2fsck: Cannot continue, aborting.


                  root@ip-172-31-28-38 /mnt#
                  root@ip-172-31-28-38 /mnt# cd /


                  After :



                  root@ip-172-31-28-38 /# fsck -f /dev/xvdh
                  fsck from util-linux 2.23.2
                  e2fsck 1.42.12 (29-Aug-2014)
                  Pass 1: Checking inodes, blocks, and sizes
                  Pass 2: Checking directory structure
                  Pass 3: Checking directory connectivity
                  Pass 4: Checking reference counts
                  Pass 5: Checking group summary information
                  /dev/xvdh: 12/524288 files (0.0% non-contiguous), 70287/2097152 blocks
                  root@ip-172-31-28-38 /#





                  share|improve this answer


























                    2












                    2








                    2







                    I encountered similar issue especially when you are still accessing the mount point. It can below any one of below two reasons.



                    You cannot run on the root FS
                    Say you can in directory "/mnt" and you have unmounted the volume mounted on "/mnt". You will encounter same error. Make use that you are not in same directory.



                    Before :



                    root@ip-172-31-28-38 /mnt# fsck -f /dev/xvdh
                    fsck from util-linux 2.23.2
                    e2fsck 1.42.12 (29-Aug-2014)
                    /dev/xvdh is in use.
                    e2fsck: Cannot continue, aborting.


                    root@ip-172-31-28-38 /mnt#
                    root@ip-172-31-28-38 /mnt# cd /


                    After :



                    root@ip-172-31-28-38 /# fsck -f /dev/xvdh
                    fsck from util-linux 2.23.2
                    e2fsck 1.42.12 (29-Aug-2014)
                    Pass 1: Checking inodes, blocks, and sizes
                    Pass 2: Checking directory structure
                    Pass 3: Checking directory connectivity
                    Pass 4: Checking reference counts
                    Pass 5: Checking group summary information
                    /dev/xvdh: 12/524288 files (0.0% non-contiguous), 70287/2097152 blocks
                    root@ip-172-31-28-38 /#





                    share|improve this answer













                    I encountered similar issue especially when you are still accessing the mount point. It can below any one of below two reasons.



                    You cannot run on the root FS
                    Say you can in directory "/mnt" and you have unmounted the volume mounted on "/mnt". You will encounter same error. Make use that you are not in same directory.



                    Before :



                    root@ip-172-31-28-38 /mnt# fsck -f /dev/xvdh
                    fsck from util-linux 2.23.2
                    e2fsck 1.42.12 (29-Aug-2014)
                    /dev/xvdh is in use.
                    e2fsck: Cannot continue, aborting.


                    root@ip-172-31-28-38 /mnt#
                    root@ip-172-31-28-38 /mnt# cd /


                    After :



                    root@ip-172-31-28-38 /# fsck -f /dev/xvdh
                    fsck from util-linux 2.23.2
                    e2fsck 1.42.12 (29-Aug-2014)
                    Pass 1: Checking inodes, blocks, and sizes
                    Pass 2: Checking directory structure
                    Pass 3: Checking directory connectivity
                    Pass 4: Checking reference counts
                    Pass 5: Checking group summary information
                    /dev/xvdh: 12/524288 files (0.0% non-contiguous), 70287/2097152 blocks
                    root@ip-172-31-28-38 /#






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Apr 26 '17 at 14:16









                    Sachin AngadiSachin Angadi

                    212




                    212























                        0














                        I don't know why, but I had to service udev stop (on debian based system).



                        After stopping udev the e2fsck -f /dev/sda1-command worked and didn't print the e2fsck: Cannot continue, aborting-Message anymore.



                        I dont't know, if it has something to do with http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html - but this page gave me the hint to try it.






                        share|improve this answer




























                          0














                          I don't know why, but I had to service udev stop (on debian based system).



                          After stopping udev the e2fsck -f /dev/sda1-command worked and didn't print the e2fsck: Cannot continue, aborting-Message anymore.



                          I dont't know, if it has something to do with http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html - but this page gave me the hint to try it.






                          share|improve this answer


























                            0












                            0








                            0







                            I don't know why, but I had to service udev stop (on debian based system).



                            After stopping udev the e2fsck -f /dev/sda1-command worked and didn't print the e2fsck: Cannot continue, aborting-Message anymore.



                            I dont't know, if it has something to do with http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html - but this page gave me the hint to try it.






                            share|improve this answer













                            I don't know why, but I had to service udev stop (on debian based system).



                            After stopping udev the e2fsck -f /dev/sda1-command worked and didn't print the e2fsck: Cannot continue, aborting-Message anymore.



                            I dont't know, if it has something to do with http://dev.bizo.com/2012/07/mdadm-device-or-resource-busy.html - but this page gave me the hint to try it.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Jan 1 at 19:36









                            elieli

                            1314




                            1314






























                                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%2f536955%2fe2fsck-cannot-continue-aborting%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

                                Ellipse (mathématiques)

                                Quarter-circle Tiles

                                Mont Emei