Where is SG_IO sense data stored?

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











up vote
0
down vote

favorite












I'm getting the following error message when running hdparm -S on my external USB hard drive:



SG_IO: bad/missing sense data


Where is this sense data stored on the hard drive? I never encountered this error before, so I'm assuming something on the drive went corrupt.







share|improve this question


















  • 1




    Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
    – galoget
    Jan 31 at 4:24










  • @galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
    – Geremia
    Jan 31 at 16:03














up vote
0
down vote

favorite












I'm getting the following error message when running hdparm -S on my external USB hard drive:



SG_IO: bad/missing sense data


Where is this sense data stored on the hard drive? I never encountered this error before, so I'm assuming something on the drive went corrupt.







share|improve this question


















  • 1




    Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
    – galoget
    Jan 31 at 4:24










  • @galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
    – Geremia
    Jan 31 at 16:03












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm getting the following error message when running hdparm -S on my external USB hard drive:



SG_IO: bad/missing sense data


Where is this sense data stored on the hard drive? I never encountered this error before, so I'm assuming something on the drive went corrupt.







share|improve this question














I'm getting the following error message when running hdparm -S on my external USB hard drive:



SG_IO: bad/missing sense data


Where is this sense data stored on the hard drive? I never encountered this error before, so I'm assuming something on the drive went corrupt.









share|improve this question













share|improve this question




share|improve this question








edited Jan 31 at 4:45









galoget

36319




36319










asked Jan 31 at 4:19









Geremia

509716




509716







  • 1




    Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
    – galoget
    Jan 31 at 4:24










  • @galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
    – Geremia
    Jan 31 at 16:03












  • 1




    Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
    – galoget
    Jan 31 at 4:24










  • @galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
    – Geremia
    Jan 31 at 16:03







1




1




Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
– galoget
Jan 31 at 4:24




Here is a good explanation of the issue you're having:Hard Drive error: bad/missing sense data
– galoget
Jan 31 at 4:24












@galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
– Geremia
Jan 31 at 16:03




@galoget That answer makes it seem it's a hardware issue ("drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal"). As I said in my question, hdparm -S worked before with the hard drive, but only now does it return the "SG_IO: bad/missing sense data". Did my hardware go bad?
– Geremia
Jan 31 at 16:03










2 Answers
2






active

oldest

votes

















up vote
1
down vote













hdparm is communicating with the driver controller firmware. It is requesting the sensor data from there. Here it might be that the controller/firmware does not support this command/operation or the tool is not the right for your controller/firmware.



If interested in more background information and details you may follow up at Linux SCSI Generic (sg) Driver, Python-SCSI or t10.org.






share|improve this answer




















  • I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
    – Geremia
    Jan 31 at 16:05


















up vote
0
down vote



accepted










The issue was that I needed to use:



sdparm -rs SCT=600 /dev/my_disk
sdparm -rC stop /dev/my_disk


instead of



hdparm -S 12 /dev/my_disk
hdparm -y /dev/my_disk


respectively.



(courtesy this table of sdparm's equivalents of hdparm commands)






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: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    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%2f420858%2fwhere-is-sg-io-sense-data-stored%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote













    hdparm is communicating with the driver controller firmware. It is requesting the sensor data from there. Here it might be that the controller/firmware does not support this command/operation or the tool is not the right for your controller/firmware.



    If interested in more background information and details you may follow up at Linux SCSI Generic (sg) Driver, Python-SCSI or t10.org.






    share|improve this answer




















    • I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
      – Geremia
      Jan 31 at 16:05















    up vote
    1
    down vote













    hdparm is communicating with the driver controller firmware. It is requesting the sensor data from there. Here it might be that the controller/firmware does not support this command/operation or the tool is not the right for your controller/firmware.



    If interested in more background information and details you may follow up at Linux SCSI Generic (sg) Driver, Python-SCSI or t10.org.






    share|improve this answer




















    • I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
      – Geremia
      Jan 31 at 16:05













    up vote
    1
    down vote










    up vote
    1
    down vote









    hdparm is communicating with the driver controller firmware. It is requesting the sensor data from there. Here it might be that the controller/firmware does not support this command/operation or the tool is not the right for your controller/firmware.



    If interested in more background information and details you may follow up at Linux SCSI Generic (sg) Driver, Python-SCSI or t10.org.






    share|improve this answer












    hdparm is communicating with the driver controller firmware. It is requesting the sensor data from there. Here it might be that the controller/firmware does not support this command/operation or the tool is not the right for your controller/firmware.



    If interested in more background information and details you may follow up at Linux SCSI Generic (sg) Driver, Python-SCSI or t10.org.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 31 at 6:41









    U880D

    401314




    401314











    • I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
      – Geremia
      Jan 31 at 16:05

















    • I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
      – Geremia
      Jan 31 at 16:05
















    I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
    – Geremia
    Jan 31 at 16:05





    I did encounter the issue after upgrading my Linux kernel (I think to 4.14.14 or 4.14.15), so maybe it is the sg driver that changed.
    – Geremia
    Jan 31 at 16:05













    up vote
    0
    down vote



    accepted










    The issue was that I needed to use:



    sdparm -rs SCT=600 /dev/my_disk
    sdparm -rC stop /dev/my_disk


    instead of



    hdparm -S 12 /dev/my_disk
    hdparm -y /dev/my_disk


    respectively.



    (courtesy this table of sdparm's equivalents of hdparm commands)






    share|improve this answer


























      up vote
      0
      down vote



      accepted










      The issue was that I needed to use:



      sdparm -rs SCT=600 /dev/my_disk
      sdparm -rC stop /dev/my_disk


      instead of



      hdparm -S 12 /dev/my_disk
      hdparm -y /dev/my_disk


      respectively.



      (courtesy this table of sdparm's equivalents of hdparm commands)






      share|improve this answer
























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        The issue was that I needed to use:



        sdparm -rs SCT=600 /dev/my_disk
        sdparm -rC stop /dev/my_disk


        instead of



        hdparm -S 12 /dev/my_disk
        hdparm -y /dev/my_disk


        respectively.



        (courtesy this table of sdparm's equivalents of hdparm commands)






        share|improve this answer














        The issue was that I needed to use:



        sdparm -rs SCT=600 /dev/my_disk
        sdparm -rC stop /dev/my_disk


        instead of



        hdparm -S 12 /dev/my_disk
        hdparm -y /dev/my_disk


        respectively.



        (courtesy this table of sdparm's equivalents of hdparm commands)







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 24 at 17:12

























        answered Mar 24 at 17:05









        Geremia

        509716




        509716






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f420858%2fwhere-is-sg-io-sense-data-stored%23new-answer', 'question_page');

            );

            Post as a guest













































































            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