badblocks: Resource busy while trying to determine device size

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












I am trying to run bad blocks on macOS High Sierra 10.13.6. I installed bad blocks using macports. I keep encountering errors when attempting to run it and I am not sure how to even get bad blocks running



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0s2


This keeps returning the error



badblocks: Resource busy while trying to determine device size



If I try



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0


I get the error



badblocks: Value too large to be stored in data type invalid end block (7813820416): must be 32-bit value










share|improve this question

















This question has an open bounty worth +50
reputation from mcbeav ending ending at 2018-12-10 08:58:50Z">in 2 hours.


This question has not received enough attention.















  • Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
    – Haxiel
    Dec 3 at 9:27










  • Does your filesystem contain an NFS Mount?
    – eyoung100
    4 hours ago














up vote
-1
down vote

favorite












I am trying to run bad blocks on macOS High Sierra 10.13.6. I installed bad blocks using macports. I keep encountering errors when attempting to run it and I am not sure how to even get bad blocks running



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0s2


This keeps returning the error



badblocks: Resource busy while trying to determine device size



If I try



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0


I get the error



badblocks: Value too large to be stored in data type invalid end block (7813820416): must be 32-bit value










share|improve this question

















This question has an open bounty worth +50
reputation from mcbeav ending ending at 2018-12-10 08:58:50Z">in 2 hours.


This question has not received enough attention.















  • Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
    – Haxiel
    Dec 3 at 9:27










  • Does your filesystem contain an NFS Mount?
    – eyoung100
    4 hours ago












up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I am trying to run bad blocks on macOS High Sierra 10.13.6. I installed bad blocks using macports. I keep encountering errors when attempting to run it and I am not sure how to even get bad blocks running



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0s2


This keeps returning the error



badblocks: Resource busy while trying to determine device size



If I try



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0


I get the error



badblocks: Value too large to be stored in data type invalid end block (7813820416): must be 32-bit value










share|improve this question















I am trying to run bad blocks on macOS High Sierra 10.13.6. I installed bad blocks using macports. I keep encountering errors when attempting to run it and I am not sure how to even get bad blocks running



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0s2


This keeps returning the error



badblocks: Resource busy while trying to determine device size



If I try



sudo badblocks -c 4096 -s -w -o /Users/mcbeav/Desktop/blocks.txt /dev/disk0


I get the error



badblocks: Value too large to be stored in data type invalid end block (7813820416): must be 32-bit value







terminal badblocks






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 1 at 7:37









Rui F Ribeiro

38.5k1479128




38.5k1479128










asked Dec 1 at 6:36









mcbeav

523




523






This question has an open bounty worth +50
reputation from mcbeav ending ending at 2018-12-10 08:58:50Z">in 2 hours.


This question has not received enough attention.








This question has an open bounty worth +50
reputation from mcbeav ending ending at 2018-12-10 08:58:50Z">in 2 hours.


This question has not received enough attention.













  • Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
    – Haxiel
    Dec 3 at 9:27










  • Does your filesystem contain an NFS Mount?
    – eyoung100
    4 hours ago
















  • Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
    – Haxiel
    Dec 3 at 9:27










  • Does your filesystem contain an NFS Mount?
    – eyoung100
    4 hours ago















Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
– Haxiel
Dec 3 at 9:27




Are you sure about using the -w parameter? The badblocks man page advises not to use it on an existing file system.
– Haxiel
Dec 3 at 9:27












Does your filesystem contain an NFS Mount?
– eyoung100
4 hours ago




Does your filesystem contain an NFS Mount?
– eyoung100
4 hours ago










1 Answer
1






active

oldest

votes

















up vote
0
down vote













You should try using dumpe2fs. Or use a Linux live CD/USB, with persistence and use badblocks on the unmounted drive. As using badblocks on a mounted drive is not going to work properly.



dumpe2fs -b /dev/sda


Note remember to use the path to your drive, as it may differ from my example.






share|improve this answer




















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f485307%2fbadblocks-resource-busy-while-trying-to-determine-device-size%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    You should try using dumpe2fs. Or use a Linux live CD/USB, with persistence and use badblocks on the unmounted drive. As using badblocks on a mounted drive is not going to work properly.



    dumpe2fs -b /dev/sda


    Note remember to use the path to your drive, as it may differ from my example.






    share|improve this answer
























      up vote
      0
      down vote













      You should try using dumpe2fs. Or use a Linux live CD/USB, with persistence and use badblocks on the unmounted drive. As using badblocks on a mounted drive is not going to work properly.



      dumpe2fs -b /dev/sda


      Note remember to use the path to your drive, as it may differ from my example.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        You should try using dumpe2fs. Or use a Linux live CD/USB, with persistence and use badblocks on the unmounted drive. As using badblocks on a mounted drive is not going to work properly.



        dumpe2fs -b /dev/sda


        Note remember to use the path to your drive, as it may differ from my example.






        share|improve this answer












        You should try using dumpe2fs. Or use a Linux live CD/USB, with persistence and use badblocks on the unmounted drive. As using badblocks on a mounted drive is not going to work properly.



        dumpe2fs -b /dev/sda


        Note remember to use the path to your drive, as it may differ from my example.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 3 hours ago









        Michael Prokopec

        85416




        85416



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2funix.stackexchange.com%2fquestions%2f485307%2fbadblocks-resource-busy-while-trying-to-determine-device-size%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

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay