Custom Query (1470 matches)

MediaSonic PROBOX K32-SU3 3.5-inch USB 3.0 (mediasonic.ca) smartctl reports: "Unknown USB bridge [0x2109:0x0711 (0x114)]"

0x4971:0x8017 (0x8104) Works with -d sat and with -d sat,12 It's a Rosewill Armer RX307-PU3-35B. It supports USB3 and UASP, and it appears so far to be stable. $25 at Newegg.

So, it seems that I finally bought a supported device that also supports USB3 and UASP, and that has already outlasted the others I've tried:

MediaSonic ProBox K32-SU3 Purex Technology

I just bought a Seagate SAS-3 HDD ST8000NM0075. I notice it wasn't producing SMART data although SMART was enabled, and eventually discovered the GLTSD bit, which apparently comes preset to "on", disabling SMART attribute storage (I think - a bit hazy about this!). I've just disabled it and hoping that helps.

The point being, this restriction wasn't obvious in the smartctl output at all. It's true that if I read every line of smartctl -x, there's a mention buried somewhere round line 300 about "GLSTD" being "off", but the term doesn't mean anything to most people who own or use a hard drive, and most won't dig into such output and question every line.

So this is a request, if there is a reason why smartctl thinks it might be impaired in its drive interrogation, due to SMART being disabled, SMART data or log storage being disabled, expected log pages not being found, etc, can that be stated in a clear prominent way, at the top of the output, so it's not easily missed?

It doesn't have to take much room. Just stating "Diagnostic output may be incomplete, due to disabled or inaccessible features on this device: <brief list>." would be enough.

Thanks!