/dev/sdc should be checked for errors












1















Can anyone help me troubleshoot this? I tried looking online but for some reason not a lot is coming up, as if it's a big secret or something.



Every time I connect to it I see "/dev/sdc should be checked for errors" and below that (not sure if this is related) it says ***** System restart required *****



I did not set this server up but what I do know is /dev/sdc is an iSCSI connection to a RAID volume on a Promise VessRAID 1840i.



Are there ways to test the volume w/out unmounting the filesystem or effecting user's access to the data on it? If so please explain what needs to be done.



Thanks!










share|improve this question























  • askubuntu.com/questions/14928/…

    – Hannu
    Oct 17 '14 at 17:17











  • That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

    – ppetraki
    Oct 17 '14 at 18:17
















1















Can anyone help me troubleshoot this? I tried looking online but for some reason not a lot is coming up, as if it's a big secret or something.



Every time I connect to it I see "/dev/sdc should be checked for errors" and below that (not sure if this is related) it says ***** System restart required *****



I did not set this server up but what I do know is /dev/sdc is an iSCSI connection to a RAID volume on a Promise VessRAID 1840i.



Are there ways to test the volume w/out unmounting the filesystem or effecting user's access to the data on it? If so please explain what needs to be done.



Thanks!










share|improve this question























  • askubuntu.com/questions/14928/…

    – Hannu
    Oct 17 '14 at 17:17











  • That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

    – ppetraki
    Oct 17 '14 at 18:17














1












1








1








Can anyone help me troubleshoot this? I tried looking online but for some reason not a lot is coming up, as if it's a big secret or something.



Every time I connect to it I see "/dev/sdc should be checked for errors" and below that (not sure if this is related) it says ***** System restart required *****



I did not set this server up but what I do know is /dev/sdc is an iSCSI connection to a RAID volume on a Promise VessRAID 1840i.



Are there ways to test the volume w/out unmounting the filesystem or effecting user's access to the data on it? If so please explain what needs to be done.



Thanks!










share|improve this question














Can anyone help me troubleshoot this? I tried looking online but for some reason not a lot is coming up, as if it's a big secret or something.



Every time I connect to it I see "/dev/sdc should be checked for errors" and below that (not sure if this is related) it says ***** System restart required *****



I did not set this server up but what I do know is /dev/sdc is an iSCSI connection to a RAID volume on a Promise VessRAID 1840i.



Are there ways to test the volume w/out unmounting the filesystem or effecting user's access to the data on it? If so please explain what needs to be done.



Thanks!







fsck






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 17 '14 at 16:36









00fruX00fruX

54611127




54611127













  • askubuntu.com/questions/14928/…

    – Hannu
    Oct 17 '14 at 17:17











  • That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

    – ppetraki
    Oct 17 '14 at 18:17



















  • askubuntu.com/questions/14928/…

    – Hannu
    Oct 17 '14 at 17:17











  • That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

    – ppetraki
    Oct 17 '14 at 18:17

















askubuntu.com/questions/14928/…

– Hannu
Oct 17 '14 at 17:17





askubuntu.com/questions/14928/…

– Hannu
Oct 17 '14 at 17:17













That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

– ppetraki
Oct 17 '14 at 18:17





That sounds like it's coming from fsck so you should probably unmount it and check it out. tune2fs is your friend.

– ppetraki
Oct 17 '14 at 18:17










1 Answer
1






active

oldest

votes


















0














You'll need to unmount the drive to check the file system for errors. You can't do it while the filesystem is live.




  • Ensure FSCKFIX=yes is present in /etc/default/rcS (it's no by default).

  • Run touch /forcefsck, and reboot the system.

  • Revert your changes to rcS once fsck is complete.






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%2f538275%2fdev-sdc-should-be-checked-for-errors%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









    0














    You'll need to unmount the drive to check the file system for errors. You can't do it while the filesystem is live.




    • Ensure FSCKFIX=yes is present in /etc/default/rcS (it's no by default).

    • Run touch /forcefsck, and reboot the system.

    • Revert your changes to rcS once fsck is complete.






    share|improve this answer




























      0














      You'll need to unmount the drive to check the file system for errors. You can't do it while the filesystem is live.




      • Ensure FSCKFIX=yes is present in /etc/default/rcS (it's no by default).

      • Run touch /forcefsck, and reboot the system.

      • Revert your changes to rcS once fsck is complete.






      share|improve this answer


























        0












        0








        0







        You'll need to unmount the drive to check the file system for errors. You can't do it while the filesystem is live.




        • Ensure FSCKFIX=yes is present in /etc/default/rcS (it's no by default).

        • Run touch /forcefsck, and reboot the system.

        • Revert your changes to rcS once fsck is complete.






        share|improve this answer













        You'll need to unmount the drive to check the file system for errors. You can't do it while the filesystem is live.




        • Ensure FSCKFIX=yes is present in /etc/default/rcS (it's no by default).

        • Run touch /forcefsck, and reboot the system.

        • Revert your changes to rcS once fsck is complete.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jul 17 '15 at 0:43









        BoinstBoinst

        1213




        1213






























            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%2f538275%2fdev-sdc-should-be-checked-for-errors%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

            數位音樂下載

            When can things happen in Etherscan, such as the picture below?

            格利澤436b