Hard Drive error: bad/missing sense data
I recently tried to check the spin down time of my hard drive with the following command:
sudo hdparm -I /dev/sdb | grep level
and got the error:
SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this command on this drive without errors
What does this mean, and how can I resolve the issue?
hard-drive error-handling
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
|
show 5 more comments
I recently tried to check the spin down time of my hard drive with the following command:
sudo hdparm -I /dev/sdb | grep level
and got the error:
SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this command on this drive without errors
What does this mean, and how can I resolve the issue?
hard-drive error-handling
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
2
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
1
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04
|
show 5 more comments
I recently tried to check the spin down time of my hard drive with the following command:
sudo hdparm -I /dev/sdb | grep level
and got the error:
SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this command on this drive without errors
What does this mean, and how can I resolve the issue?
hard-drive error-handling
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
I recently tried to check the spin down time of my hard drive with the following command:
sudo hdparm -I /dev/sdb | grep level
and got the error:
SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this command on this drive without errors
What does this mean, and how can I resolve the issue?
hard-drive error-handling
hard-drive error-handling
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
edited Oct 25 '17 at 13:02
David Foerster
27.8k1364110
27.8k1364110
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
asked May 6 '16 at 9:05
Kalamalka KidKalamalka Kid
1,50892250
1,50892250
2
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
1
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04
|
show 5 more comments
2
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
1
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04
2
2
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
1
1
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04
|
show 5 more comments
2 Answers
2
active
oldest
votes
looks like your drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal. You don't say what model of drive or controller you are using so its hard to offer more advice here.
You could test this by plugging into another usb controller or using a different drive with the same controller or better still direct via SATA.
3TB drives can be too big for some usb2 era controllers so i would recommend getting a reputable usb3 sata bridge instead, it will be much faster as well.
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
add a comment |
This problem is usually caused by USB-SATA bridge implementation and should be visible only with USB connected disk enclosures.
In case of external USB disk, the system needs to talk to the SATA drive inside the enclosure using UAS (USB Attached SCSI) protocol over SAT (SCSI / ATA Translation) to send ATA commands over SCSI over USB. The reason this is so complex is due historical reasons.
Somewhere in the chain USB → UAS → SCSI → SAT → SATA some piece of hardware has incorrect implementation. Usually all of this is done by a single microchip inside the enclosure called USB-SATA bridge and some well known variants are ASM1051, ASM1053 and ASM1153. Of these, the ASM1051 is known to be buggy and UAS should be avoided with any hardware containing this chip. ASM1053 and ASM1153 may or may not work depending on actual firmware inside the chip (the manufacturer is allowed to customize the firmware, the reference implementation does work correctly). For example, many enclosures made by Seagate use ASM1153 with custom firmware and have problems with some ATA commands even if the same chip does work correctly with reference firmware. (For example, some enclosures by Seagate work as long as OS never sends any 12 or 16 bit commands. Linux usb_storage supports quirk t for this purpose.) The end user usually cannot replace the firmware so if you have a bad chip/firmware your only option is to complain to the manufacturer. In case of Seagate, they "fix" the problem by stating that they officially support Windows and OS X only. Seagate is nowdays officially working with Linux community so perhaps their products will actually work in the future.
The only real way to figure out the bridge chip is to dismantle the enclosure and inspect the markings in the actual microchips.
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f768373%2fhard-drive-error-bad-missing-sense-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
looks like your drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal. You don't say what model of drive or controller you are using so its hard to offer more advice here.
You could test this by plugging into another usb controller or using a different drive with the same controller or better still direct via SATA.
3TB drives can be too big for some usb2 era controllers so i would recommend getting a reputable usb3 sata bridge instead, it will be much faster as well.
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
add a comment |
looks like your drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal. You don't say what model of drive or controller you are using so its hard to offer more advice here.
You could test this by plugging into another usb controller or using a different drive with the same controller or better still direct via SATA.
3TB drives can be too big for some usb2 era controllers so i would recommend getting a reputable usb3 sata bridge instead, it will be much faster as well.
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
add a comment |
looks like your drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal. You don't say what model of drive or controller you are using so its hard to offer more advice here.
You could test this by plugging into another usb controller or using a different drive with the same controller or better still direct via SATA.
3TB drives can be too big for some usb2 era controllers so i would recommend getting a reputable usb3 sata bridge instead, it will be much faster as well.
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
looks like your drive controller doesn't support that method of enquiry, not all usb sata chipsets are created equal. You don't say what model of drive or controller you are using so its hard to offer more advice here.
You could test this by plugging into another usb controller or using a different drive with the same controller or better still direct via SATA.
3TB drives can be too big for some usb2 era controllers so i would recommend getting a reputable usb3 sata bridge instead, it will be much faster as well.
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
answered May 13 '16 at 10:46
AmiasAmias
4,1801228
4,1801228
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
add a comment |
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
hi, thanks for taking the tiem to reply, my machine has no available sata ports (theres only 1 on intel nuc).;
– Kalamalka Kid
May 15 '16 at 21:19
add a comment |
This problem is usually caused by USB-SATA bridge implementation and should be visible only with USB connected disk enclosures.
In case of external USB disk, the system needs to talk to the SATA drive inside the enclosure using UAS (USB Attached SCSI) protocol over SAT (SCSI / ATA Translation) to send ATA commands over SCSI over USB. The reason this is so complex is due historical reasons.
Somewhere in the chain USB → UAS → SCSI → SAT → SATA some piece of hardware has incorrect implementation. Usually all of this is done by a single microchip inside the enclosure called USB-SATA bridge and some well known variants are ASM1051, ASM1053 and ASM1153. Of these, the ASM1051 is known to be buggy and UAS should be avoided with any hardware containing this chip. ASM1053 and ASM1153 may or may not work depending on actual firmware inside the chip (the manufacturer is allowed to customize the firmware, the reference implementation does work correctly). For example, many enclosures made by Seagate use ASM1153 with custom firmware and have problems with some ATA commands even if the same chip does work correctly with reference firmware. (For example, some enclosures by Seagate work as long as OS never sends any 12 or 16 bit commands. Linux usb_storage supports quirk t for this purpose.) The end user usually cannot replace the firmware so if you have a bad chip/firmware your only option is to complain to the manufacturer. In case of Seagate, they "fix" the problem by stating that they officially support Windows and OS X only. Seagate is nowdays officially working with Linux community so perhaps their products will actually work in the future.
The only real way to figure out the bridge chip is to dismantle the enclosure and inspect the markings in the actual microchips.
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
add a comment |
This problem is usually caused by USB-SATA bridge implementation and should be visible only with USB connected disk enclosures.
In case of external USB disk, the system needs to talk to the SATA drive inside the enclosure using UAS (USB Attached SCSI) protocol over SAT (SCSI / ATA Translation) to send ATA commands over SCSI over USB. The reason this is so complex is due historical reasons.
Somewhere in the chain USB → UAS → SCSI → SAT → SATA some piece of hardware has incorrect implementation. Usually all of this is done by a single microchip inside the enclosure called USB-SATA bridge and some well known variants are ASM1051, ASM1053 and ASM1153. Of these, the ASM1051 is known to be buggy and UAS should be avoided with any hardware containing this chip. ASM1053 and ASM1153 may or may not work depending on actual firmware inside the chip (the manufacturer is allowed to customize the firmware, the reference implementation does work correctly). For example, many enclosures made by Seagate use ASM1153 with custom firmware and have problems with some ATA commands even if the same chip does work correctly with reference firmware. (For example, some enclosures by Seagate work as long as OS never sends any 12 or 16 bit commands. Linux usb_storage supports quirk t for this purpose.) The end user usually cannot replace the firmware so if you have a bad chip/firmware your only option is to complain to the manufacturer. In case of Seagate, they "fix" the problem by stating that they officially support Windows and OS X only. Seagate is nowdays officially working with Linux community so perhaps their products will actually work in the future.
The only real way to figure out the bridge chip is to dismantle the enclosure and inspect the markings in the actual microchips.
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
add a comment |
This problem is usually caused by USB-SATA bridge implementation and should be visible only with USB connected disk enclosures.
In case of external USB disk, the system needs to talk to the SATA drive inside the enclosure using UAS (USB Attached SCSI) protocol over SAT (SCSI / ATA Translation) to send ATA commands over SCSI over USB. The reason this is so complex is due historical reasons.
Somewhere in the chain USB → UAS → SCSI → SAT → SATA some piece of hardware has incorrect implementation. Usually all of this is done by a single microchip inside the enclosure called USB-SATA bridge and some well known variants are ASM1051, ASM1053 and ASM1153. Of these, the ASM1051 is known to be buggy and UAS should be avoided with any hardware containing this chip. ASM1053 and ASM1153 may or may not work depending on actual firmware inside the chip (the manufacturer is allowed to customize the firmware, the reference implementation does work correctly). For example, many enclosures made by Seagate use ASM1153 with custom firmware and have problems with some ATA commands even if the same chip does work correctly with reference firmware. (For example, some enclosures by Seagate work as long as OS never sends any 12 or 16 bit commands. Linux usb_storage supports quirk t for this purpose.) The end user usually cannot replace the firmware so if you have a bad chip/firmware your only option is to complain to the manufacturer. In case of Seagate, they "fix" the problem by stating that they officially support Windows and OS X only. Seagate is nowdays officially working with Linux community so perhaps their products will actually work in the future.
The only real way to figure out the bridge chip is to dismantle the enclosure and inspect the markings in the actual microchips.
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
This problem is usually caused by USB-SATA bridge implementation and should be visible only with USB connected disk enclosures.
In case of external USB disk, the system needs to talk to the SATA drive inside the enclosure using UAS (USB Attached SCSI) protocol over SAT (SCSI / ATA Translation) to send ATA commands over SCSI over USB. The reason this is so complex is due historical reasons.
Somewhere in the chain USB → UAS → SCSI → SAT → SATA some piece of hardware has incorrect implementation. Usually all of this is done by a single microchip inside the enclosure called USB-SATA bridge and some well known variants are ASM1051, ASM1053 and ASM1153. Of these, the ASM1051 is known to be buggy and UAS should be avoided with any hardware containing this chip. ASM1053 and ASM1153 may or may not work depending on actual firmware inside the chip (the manufacturer is allowed to customize the firmware, the reference implementation does work correctly). For example, many enclosures made by Seagate use ASM1153 with custom firmware and have problems with some ATA commands even if the same chip does work correctly with reference firmware. (For example, some enclosures by Seagate work as long as OS never sends any 12 or 16 bit commands. Linux usb_storage supports quirk t for this purpose.) The end user usually cannot replace the firmware so if you have a bad chip/firmware your only option is to complain to the manufacturer. In case of Seagate, they "fix" the problem by stating that they officially support Windows and OS X only. Seagate is nowdays officially working with Linux community so perhaps their products will actually work in the future.
The only real way to figure out the bridge chip is to dismantle the enclosure and inspect the markings in the actual microchips.
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
answered Jan 1 at 13:38
Mikko RantalainenMikko Rantalainen
536514
536514
add a comment |
add a comment |
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.
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f768373%2fhard-drive-error-bad-missing-sense-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
2
Hi, was your hdd connected through a USB port? In this case, you can take a look here and verify if a new scan (with the hdd attached to a sata port) gives the same error.
– PieCot
May 11 '16 at 8:28
1
yes through USB. 3 TB drive but it is not a sata drive. external usb
– Kalamalka Kid
May 11 '16 at 10:48
Has it others interface than USB? If so, you can try to use another interface to repeat the scan. However, probably the error is due to the USB connection and your drive could actually be ok.
– PieCot
May 11 '16 at 10:58
no it is USB only - external drive
– Kalamalka Kid
May 11 '16 at 11:02
The drive reads & writes data just fine and mounts on startup as well. I just simply cannot run this commandm on this drive without errors
– Kalamalka Kid
May 11 '16 at 11:04