SMART data from USB drives

[Tom Del Rosso]

It seems Everest can't get the SMART data from USB drives. Can anything do
it? Thanks.

 

[Rod Speed]

It seems Everest can't get the SMART data from USB drives.

It isnt as absolute as that, but certainly it cant get the smart data from all drives that other
stuff can.

Can anything do it?

try smartctl

 

[Arno Wagner]

It seems Everest can't get the SMART data from USB drives. Can anything do
it? Thanks.

No. Fundamentally impossible. Remove the drive from the enclosure
and connect it directly via (S)ATA.

Arno

 

[Folkert Rienstra]

No. Fundamentally impossible.
Wotanidjut.

Remove the drive from the enclosure
and connect it directly via (S)ATA.

Arno

 

[Tom Del Rosso]

It isnt as absolute as that, but certainly it cant get the smart data
from all drives that other stuff can.


try smartctl

Thanks. It looks powerful, but after playing with the options for a while I
can't get it to see the USB device.

 

[Arno Wagner]

Thanks. It looks powerful, but after playing with the options for a while I
can't get it to see the USB device.

That is as expected. Despite of what some pople here claim, SMART does not
work over USB. You need to remove the drive and connect it via ATA or
SATA, depending on the drive interface.

Arno

 

[Rod Speed]

Thanks. It looks powerful, but after playing with the
options for a while I can't get it to see the USB device.

Yeah, its much harder with USB. Not impossible tho, Arno has never had a clue.

 

[Folkert Rienstra]

That is as expected. Despite of what some pople here claim,

SMART does not work over USB.

Wotanidjut.
It depends on what USB bridge and what USB driver.
All kinds of data/commands can be sent over USB.
The problem is the program interface in the host and the firmware
interface in the devices to get the necessary commands to the drive
and data from the drive. If these aren't in place then you're ****ed.

You need to remove the drive and connect it via ATA or SATA,
depending on the drive interface.

No, really?

 

[Tom Del Rosso]

That is as expected. Despite of what some pople here claim, SMART
does not work over USB. You need to remove the drive and connect it
via ATA or SATA, depending on the drive interface.

I would take this simple route, but the case is designed not to be opened.

 

[Tom Del Rosso]

Yeah, its much harder with USB. Not impossible tho, Arno has never
had a clue.

Do you treat it like a SCSI?

 

[Arno Wagner]

I would take this simple route, but the case is designed not to be opened.

Well, then you will not get SMART values. The only other option that
works to some degree is to read the complete disk and measure the
time. If it increases, chances are the drive has problems. Far less
reliable, but about the only thing you can do. I used to do this in an
automated fashion before Linux had SMART support.

Arno

 

[Arno Wagner]

Do you treat it like a SCSI?

USB uses the SCSI storage command set. It does not use the SCSI
SMART command set and it does not do ATA-to-SCSI SMART attribute
tanslation, at least not in any standardized way. Some vendors
may actually have non-stanrdadized passthrough extensions, but
they would only be usable with software from the USB device vendor.

Rod is making the idea of generic SMART support on USB up to
appear knowledgeable. It does not exist. So far he has not even
demonstrated a single case of non-standardized vendor specific
support.

Arno

 

[Rod Speed]

I would take this simple route, but the case is designed not to be opened.

Bet it is, its just not obvious how to open it.

 

[Rod Speed]

Do you treat it like a SCSI?

Nope, you need a driver that can do it with the bridge in the case.

And thats a theoretical possibility, bet ****nert cant actually list one that does.

 

[zappo]

USB uses the SCSI storage command set.

No it doesnt.

It does not use the SCSI SMART command set and it does not
do ATA-to-SCSI SMART attribute tanslation, at least not in any
standardized way. Some vendors may actually have non-stanrdadized
passthrough extensions, but they would only be usable with software
from the USB device vendor.

Rod is making the idea of generic SMART
support on USB up to appear knowledgeable.

I never ever said a word about generic SMART support on USB.

And I have said repeatedly that I prefer external drives that support
eSATA as well as USB, because that makes SMART report trivial.

It does not exist.

Never ever said it did.

So far he has not even demonstrated a single case
of non-standardized vendor specific support.

Never ever said that is available either.

 

[Fred]

No it doesnt.

I never ever said a word about generic SMART support on USB.

You did imply it when you said :
"it cant get the smart data from all drives that other stuff can".

And I have said repeatedly that I prefer external drives that support
eSATA as well as USB, because that makes SMART report trivial.

It's what you implied when you said :
"it cant get the smart data from all drives that other stuff can".

Never ever said it did.
Weasel.


Never ever said that is available either.

It's what you implied when you said :
" it cant get the smart data from all drives that other stuff can".

 

[Folkert Rienstra]

Well, then you will not get SMART values. The only other option that
works to some degree is to read the complete disk and measure the
time. If it increases, chances are the drive has problems. Far less
reliable, but about the only thing you can do.

I used to do this in an automated fashion before Linux had SMART support.

Yep, you are indeed an idjut.

 

[Folkert Rienstra]

USB uses the SCSI storage command set.

USB doesn't. USB mass storage devices do. And that is just one layer.

It does not use the SCSI SMART command set

Idjut. Obviously beause there isn't any.

and it does not do ATA-to-SCSI SMART attribute tanslation,

Which is what a bridge device would have to do and has nothing
whatsoever to do with USB and whatever protocol it uses.

at least not in any standardized way.

And why bother if you can wrap the ATA commands in USB packets
and just pass them through to the ATA device.

Some vendors may actually have non-stanrdadized passthrough extensions,
but they would only be usable with software from the USB device vendor.

So much for that "Fundamentally impossible".

Rod is making the idea of generic SMART support on USB up to
appear knowledgeable.

And you do exactly the same for the opposite.
Neither of you babblebots own the truth.

It does not exist. So far he has not even demonstrated a single case of
non-standardized vendor specific support.

Like you can prove that they don't exist.

 

[Fred]

Nope, you need a driver that can do it with the bridge in the case.

That's not what you said before.

And thats a theoretical possibility,

Right, it depends on the bridge supporting it too.

bet ****nert cant actually list one that does.

He doesn't have to, he didn't make that foolish claim, you did.
And now you are weaseling out again, trying to blame him for it.

 

[Rod Speed]

You did imply it when you said :
"it cant get the smart data from all drives that other stuff can".

Like hell I did. That wasnt even about generic SMART support on USB,
it was JUST a comment that Everest can fail to show the SMART data
with some INTERNAL drives, nothing to do with USB at all.

It's what you implied when you said :
"it cant get the smart data from all drives that other stuff can".

Like hell I did. That wasnt even about generic SMART support on USB,
it was JUST a comment that Everest can fail to show the SMART data
with some INTERNAL drives, nothing to do with USB at all.

Weasel.

Silly little ****wit pseudokraut.

It's what you implied when you said :
" it cant get the smart data from all drives that other stuff can".

Like hell I did. That wasnt even about generic SMART support on USB,
it was JUST a comment that Everest can fail to show the SMART data
with some INTERNAL drives, nothing to do with USB at all.