Bas Posted September 30, 2017 Share Posted September 30, 2017 Hi, I'm having some issues with getting smart data from a particular type of SAS drive. I'm running a crossflashed IBM M1015 (IT mode, LSI P20 Firmware). Other disks attached to this controller are reporting temperatures and SMART data just fine. StableBit scanner is not showing SMART data, temperatures or age. I am able to get some data with Powershell and smartctl. I've also run the Direct I/O test utility. Please see the attached files and quotes below. It would be very nice if we could get some of this data into Stablebit Scanner! Kind regards, Bas Get-PhysicalDisk -FriendlyName PhysicalDisk16 | select * Usage : Auto-Select OperationalStatus : OK HealthStatus : Healthy BusType : SAS CannotPoolReason : Insufficient Capacity SupportedUsages : {Auto-Select, Manual-Select, Hot Spare, Retired...} MediaType : HDD ObjectId : {1}\\************\root/Microsoft/Windows/Storage/Providers_v2\SPACES_PhysicalDisk.ObjectId="{541c1371-e10e-11e3-80b1-806e6f6e6963}:PD:{795efb42-67b7-c1bb-e544-be3e6b9828f2}" PassThroughClass : PassThroughIds : PassThroughNamespace : PassThroughServer : UniqueId : 5000C50057550C8F AllocatedSize : 1000204886016 CanPool : False Description : DeviceId : 16 EnclosureNumber : 0 FirmwareVersion : 0002 FriendlyName : PhysicalDisk16 IsIndicationEnabled : False IsPartial : True LogicalSectorSize : 512 Manufacturer : SEAGATE Model : ST1000NM0001 OtherCannotPoolReasonDescription : PartNumber : PhysicalLocation : SES Enclosure 5001E677BA337FFD : Slot 6 PhysicalSectorSize : 512 SerialNumber : ************ Size : 1000204886016 SlotNumber : 6 SoftwareVersion : SpindleSpeed : 4294967295 PSComputerName : CimClass : ROOT/Microsoft/Windows/Storage:MSFT_PhysicalDisk CimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...} CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties Get-PhysicalDisk -FriendlyName PhysicalDisk16 | Get-StorageReliabilityCounter ObjectId : {1}\\************\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageReliabilityCounter.ObjectId="{541c1371-e10e-11e3-80b1-806e6f6e6963}:RC:{795efb42-67b7-c1bb-e544-be3e6b9828f2}" PassThroughClass : PassThroughIds : PassThroughNamespace : PassThroughServer : UniqueId : {541c1371-e10e-11e3-80b1-806e6f6e6963}:RC:{795efb42-67b7-c1bb-e544-be3e6b9828f2} DeviceId : 16 FlushLatencyMax : 16 LoadUnloadCycleCount : 32 LoadUnloadCycleCountMax : 300000 ManufactureDate : Year: 2013 Week: 36 PowerOnHours : 19726 ReadErrorsCorrected : 11187725 ReadErrorsTotal : 0 ReadErrorsUncorrected : 0 ReadLatencyMax : 268 StartStopCycleCount : 32 StartStopCycleCountMax : 10000 Temperature : 37 TemperatureMax : 68 Wear : 0 WriteErrorsCorrected : 0 WriteErrorsTotal : 0 WriteErrorsUncorrected : 0 WriteLatencyMax : 71 PSComputerName : C:\Program Files\smartmontools\bin>smartctl smartctl 6.3 2014-07-26 r3976 [x86_64-w64-mingw32-2012r2] (sf-6.3-1) Copyright © 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST1000NM0001 Revision: 0002 Compliance: SPC-4 User Capacity: 1.000.204.886.016 bytes [1,00 TB] Logical block size: 512 bytes Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50057550c8f Serial number: *************** Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Sat Sep 30 15:06:07 2017 WEDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 37 C Drive Trip Temperature: 68 C Manufactured in week 36 of year 2013 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 32 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 32 Elements in grown defect list: 186 Vendor (Seagate) cache information Blocks sent to initiator = 22153071 Blocks received from initiator = 4057140 Blocks read from cache and sent to initiator = 1803700 Number of read and write commands whose size <= segment size = 17176 Number of read and write commands whose size > segment size = 12 Vendor (Seagate/Hitachi) factory information number of hours powered up = 19741,50 number of minutes until next internal SMART test = 46 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 39537776 0 0 39537776 0 11,342 0 write: 0 0 0 0 0 2,093 0 Non-medium error count: 0 [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] No self-tests have been logged Quote Link to comment Share on other sites More sharing options...
Christopher (Drashna) Posted October 1, 2017 Share Posted October 1, 2017 Just a clarification here: SAS drives do not use SMART. Period. End of story. They report data in a very different way. And smrtctrl does read the SAS information. However, StableBit Scanner doesn't read the SAS info, at this point. This is something that we would like to add, but it is something that may not be quick to add. Specifically, we need: SAS hardware (both the controller and drive). I personally have SAS controllers, but not drives (but that's an easy problem to solve). And I believe Alex has the same. So testing shouldn't be a problem. Documentation, aka, we need to read over it, and understand how it works first. Time, aka, time to implement it. We've been very busy "catching up". We want to get all the bugs ironed out of our products. Once that's done, we'll look at adding more features, such as this. That said, I am very much interested in adding SAS support to StableBit Scanner, as it would make it that much more useful (and SAS drives are that much better). Quote Link to comment Share on other sites More sharing options...
Bas Posted October 1, 2017 Author Share Posted October 1, 2017 Thank you for your reply! I will deploy something with Powershell/smartctl to monitor these drives for now. If I can supply any more information that could be useful, or test anything please let me know. I would love to help. Quote Link to comment Share on other sites More sharing options...
Christopher (Drashna) Posted October 2, 2017 Share Posted October 2, 2017 Nope, nothing needed. We just need to look at the SAS protocol documentation, read up on it, and figure out how to implement it. So it's a matter of time. Quote Link to comment Share on other sites More sharing options...
cuco Posted October 29, 2017 Share Posted October 29, 2017 Great News. Like to see that Feature too! Christopher (Drashna) 1 Quote Link to comment Share on other sites More sharing options...
Christopher (Drashna) Posted October 30, 2017 Share Posted October 30, 2017 So would I, actually. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.