Jump to content
  • 0

Smart check not accessible - Proliant Gen8 Microserver


JosephKav

Question

So I just installed the Scanner after using Drivepool for about 15 days now, however, with both of my disks I get "The on-disk SMART check is not accessible on any of your disks". Also, this http://prntscr.com/7a7lgz. However, smartctl seems to give me SMART data. Any ideas on how to fix? I'm currently using a HP Proliant Gen8 Microserver.

I tried unsafe DirectIO but that did not seem to work. Any help would be much appreciated

Link to comment
Share on other sites

Recommended Posts

  • 0

Did you restart the service or server after applying the setting?

And to make sure:

http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings

It should be the "Unsafe" option under "DirectIo".

 

If that didn't work, download the utility from here:

http://community.covecube.com/index.php?/topic/36-how-to-contribute-test-data/

Select the drive in question. 

Look for "SMART Attributes" and make sure this is "lit up" (green checkbox next to it) in the WMI or DirectIO section.

If it is, click on the elipse button ("....") and make sure it lists contents.

 

If it doesn't, then check the "Unsafe DirectIo" box. This should refresh the contents. Check again, and see if it's grabbing the SMART attributes then.

 

 

Also, how is the drive connected? 

And in StableBit Scanner, could you click on the column header and select "By Controller"? This will group the drives by controller and list which controller you're connected to.

Could you let us know what controller the drive is connected to?

Link to comment
Share on other sites

  • 0

If that didn't work, download the utility from here:

http://community.cov...bute-test-data/

Done

 

Select the drive in question. 

Look for "SMART Attributes" and make sure this is "lit up" (green checkbox next to it) in the WMI or DirectIO section.

 

Its not lit up in either

 

SMARTdata.png

 

 

If it doesn't, then check the "Unsafe DirectIo" box. This should refresh the contents. Check again, and see if it's grabbing the SMART attributes then.

 

Still not lit up (See image above)

 

Also, how is the drive connected?

Disk is connected via SATA to B120i RAID Controller (Drive is set up as a single disk in a RAID0 Volume)

 

And in StableBit Scanner, could you click on the column header and select "By Controller"? This will group the drives by controller and list which controller you're connected to.

HP Dynamic Smart Array B120i SATA Raid Controller

 

Could you let us know what controller the drive is connected to?

The controller above

Link to comment
Share on other sites

  • 0

Ah, okay, thanks for the image. I missed it in the text of the previous..

 

 

Specifically, the drive is showing up as a "logical volume". That means that you've added it to a RAID array (or a JBOD array). And that's the problem....

 

You can use the "Specific method" option to check all of the method that we support, to see if any work. If they do, let us know ... but I'm pretty sure that none will work.

 

The Controller needs to pass the disk through, without adding it to a RAID or JBOD array for it to pass on the SMART data properly. Unfortunately, I think that the specific controller in question REQUIRES you to create an array to use the disk in the OS.  If that's the case, then there isn't a way to get SMART data.

 

However, if you use something like HDSentinel, does that get SMART data from these drives?

Link to comment
Share on other sites

  • 0

I get a similar issue with a USB drive, except it appears when the USB box is checked. Files attached.

What version of StableBit Scanner are you using?

 

And could you check the "Specific Method" option, select the ScsiPassthrough method, and then click on the ellipsis next to the "green" SMART attributes section and see if it's getting data there? If not, check the ScsiPassthrough48 option and see if that works. 

Link to comment
Share on other sites

  • 0

What version of StableBit Scanner are you using?

 

And could you check the "Specific Method" option, select the ScsiPassthrough method, and then click on the ellipsis next to the "green" SMART attributes section and see if it's getting data there? If not, check the ScsiPassthrough48 option and see if that works. 

 

v2.5.1.3062

 

Also, whoops, wrong drive. Accidentally tried to directio check the 07A8 drive when the 0748 drive is the one having problems. Oops. Oddly enough, both drives behave the same to DirectIO, but not scanner, with ScsiPassthrough and Scsipassthrough48 working on both, default options with nothing checked not working, and yet Scanner can read SMART from the 07A8. Strange. Attached screenshots.

post-1926-0-77531600-1444035180_thumb.png

post-1926-0-77796800-1444035181_thumb.png

post-1926-0-77590700-1444035182_thumb.png

post-1926-0-67904700-1444035183_thumb.png

Link to comment
Share on other sites

  • 0

Either way, could you click on the ellipse ("...") button next to the SMART attributes and see what it shows?

If it's not showing anything, try the other method. If it does, let me know.

 

Here's what it says:

  Smart attributes for device:   6
  Version:   16
  Offline data collection status:   NeverStartted
  Self-test execution status:   PreviousCompletedNoErorrOrNoTestRun
  Self-test percent remaining:   0
  To complete off-line data collection:   03:05:00
  Off-line data collection capability:   ExecuteOffLineImmediate, Vendor1, OffLineReadScanning, SelfTest, ConveyanceSelfTest, SelectiveSelfTest
  SMART capability:   SmartAutoSaveOnPowerModeSwitch, SmartEnableDisableAndAttributeAutosaveSupported
  Error logging capability:   True
  Short self-test polling time:   00:02:00
  Extended self-test polling time:   02:02:00
  Conveyance self-test polling time:   00:05:00

  Attributes:   17
    1:   200 [0x000000000000]
    3:   179 [0x0000000007E9]
    4:   96 [0x0000000012FD]
    5:   200 [0x000000000000]
    7:   200 [0x000000000000]
    9:   71 [0x000000005393]
    10:   100 [0x000000000000]
    11:   100 [0x000000000000]
    12:   100 [0x000000000058]
    192:   185 [0x000000002E2C]
    193:   85 [0x000000054E15]
    194:   115 [0x000000000020]
    196:   200 [0x000000000000]
    197:   200 [0x000000000000]
    198:   100 [0x000000000000]
    199:   200 [0x000000000000]
    200:   100 [0x000000000000]
  Checksum valid:   True

Link to comment
Share on other sites

  • 0

Okay, that's definitely getting SMART data then. 

 

Could you see if the public beta build fixes this issue for you, then?

http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.2.3103_BETA.exe

 

Nope, still not getting smart data from that drive in Scanner.

 

Edit: And I had to downgrade to the official release because the Beta decided all my drives had random bad sectors. Not good.

Link to comment
Share on other sites

  • 0

Okay, I've flagged this for Alex (the developer) and he'll take a look into it.

 

In the meanwhile, could you open the SMART Details page on a drive that does work and check the "Submit to BitFlock" option. Post the ID here.

 

https://stablebit.com/Admin/IssueAnalysis/20816

 

 

Also, was the bad sector issue for all the disks, or just specific ones (eg, on specific controllers)?

 

https://stablebit.com/Admin/IssueAnalysis/20808

Link to comment
Share on other sites

  • 0

Okay, I've flagged this for Alex (the developer) and he'll take a look into it.

 

In the meanwhile, could you open the SMART Details page on a drive that does work and check the "Submit to BitFlock" option. Post the ID here.

 

https://stablebit.com/Admin/IssueAnalysis/20816

 

 

Also, was the bad sector issue for all the disks, or just specific ones (eg, on specific controllers)?

 

https://stablebit.com/Admin/IssueAnalysis/20808

ID: USRYRN9X

 

Also, bad sectors popped up on all disk scans while on the Beta you linked.

Link to comment
Share on other sites

  • 0
 

Could you upgrade to the latest beta build?


 

Additionally, you'll need to enable an Advanced setting to get this working properly. 

 

Click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option.

Click on Settings, and select the new Advanced Settings and information option. Open the Configuration Properties tab. You will find a list of all the settings here, organized into section. Find the "DirectIO" section, and check the "DoNotCorrectSize" option.  You'll need to reboot the system after doing this (or restart the service).  
Link to comment
Share on other sites

  • 0

 

 
Could you upgrade to the latest beta build?
 
Additionally, you'll need to enable an Advanced setting to get this working properly. 
 
Click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option.
Click on Settings, and select the new Advanced Settings and information option. Open the Configuration Properties tab. You will find a list of all the settings here, organized into section. Find the "DirectIO" section, and check the "DoNotCorrectSize" option.  You'll need to reboot the system after doing this (or restart the service).  

 

No more false damaged disk warnings.

post-1926-0-10608500-1446248443_thumb.png

Link to comment
Share on other sites

  • 0

Nope, not even with DirectIO Unsafe checked, either.

 

Okay, and to double check, the ScsiPassthrough and ScsiPassthrough48 methods in the Direct IO Test both returned correct information (eg, what you've posted above)?

 

And for both of the external disks?

 

 

And could you try one more thing, just in case.  In the Advanced config, enable the "NoWMI" option in the "SMART" section, and reboot.

 

 

 

The reason I'm asking, is that the specific model you have listed above shows that it should be using ScsiPassthrough for the SMART Query method. But that clearly isn't happening. 

Link to comment
Share on other sites

  • 0

Okay, and to double check, the ScsiPassthrough and ScsiPassthrough48 methods in the Direct IO Test both returned correct information (eg, what you've posted above)?

 

And for both of the external disks?

 

 

And could you try one more thing, just in case.  In the Advanced config, enable the "NoWMI" option in the "SMART" section, and reboot.

 

 

 

The reason I'm asking, is that the specific model you have listed above shows that it should be using ScsiPassthrough for the SMART Query method. But that clearly isn't happening. 

Still nothing on the 0748, even with NoWMI checked, NoWMI and Unsafe checked, and only Unsafe checked. DirectIO test program unsafe returns SMART values on the 0748 though.

  Smart attributes for device:   8
  Version:   16
  Offline data collection status:   NeverStartted
  Self-test execution status:   PreviousCompletedNoErorrOrNoTestRun
  Self-test percent remaining:   0
  To complete off-line data collection:   03:05:00
  Off-line data collection capability:   ExecuteOffLineImmediate, Vendor1, OffLineReadScanning, SelfTest, ConveyanceSelfTest, SelectiveSelfTest
  SMART capability:   SmartAutoSaveOnPowerModeSwitch, SmartEnableDisableAndAttributeAutosaveSupported
  Error logging capability:   True
  Short self-test polling time:   00:02:00
  Extended self-test polling time:   02:02:00
  Conveyance self-test polling time:   00:05:00

  Attributes:   17
    1:   200 [0x000000000000]
    3:   179 [0x000000000802]
    4:   96 [0x000000001320]
    5:   200 [0x000000000000]
    7:   100 [0x000000000000]
    9:   70 [0x00000000561A]
    10:   100 [0x000000000000]
    11:   100 [0x000000000000]
    12:   100 [0x000000000061]
    192:   183 [0x000000003229]
    193:   78 [0x00000005999C]
    194:   116 [0x00000000001F]
    196:   200 [0x000000000000]
    197:   200 [0x000000000000]
    198:   100 [0x000000000000]
    199:   200 [0x000000000000]
    200:   100 [0x000000000000]
  Checksum valid:   True
Summary of \\.\PHYSICALDRIVE8:
  SATA compliance: 
Sata
  SATA spec: 
SATA Rev 3.0
  SATA speed: 
3.0 Gbps of 3.0 Gbps Max
  PATA speed: 

  DMA mode: 
Multiword DMA Mode 0
  UDMA mode: 
Ultra DMA Mode 6
  Multiword DMA mode: 
Multiword DMA Mode 2
  Major version: 
ATA8-ACS
  Sector count: 
976,773,168.00
  TRIM Support: 
CoveNativeSafe.Info.AtapiIdentify+

Identification of \\.\PHYSICALDRIVE8:
  Model: 
WDC WD5000BMVW-11S5XS0 (0x57, 0x44, 0x43, 0x20, 0x57, 0x44, 0x35, 0x30, 0x30, 0x30, 0x42, 0x4D, 0x56, 0x57, 0x2D, 0x31, 0x31, 0x53, 0x35, 0x58, 0x53, 0x30)
  Firmware: 
01.01A01
  Serial number: 
WD-WXF1E32UHYX3
  ATAPI major version: 
ATA_1, ATA_2, ATA_3, ATA_ATAPI_4, ATA_ATAPI_5, ATA_ATAPI_6, ATA_ATAPI_7, ATA8_ACS
  ATAPI minor version: 
0

Logical cylinders: 
	16383
Logical heads: 
	16
Logical sectors per track: 
	63
Commands supported 1: 
	Smart, SecurityMode, MandatoryPowerManagement, WriteCache, LookAhead, HostProtectedArea, WriteBuffer, ReadBuffer, Nop
Commands supported 2: 
	DownloadMicrocode, AdvancedPowerManagement, SetMaxSecurityExtension, _48BitAddress, DeviceConfigurationOverlay, MandatoryFlushCache, FlushCacheExt, AlwaysPresent
Commands supported 3: 
	SmartErrorLogging, SmartSelfTest, GeneralPurposeLoggingFeature, _64BitWorldWideName, IdleImmediateWithUnload, AlwaysPresent

Commands supported 4: 
	ReadWriteDmaExtGplOptional, SegmentForDownloadMicrocode, AlwaysPresent

Commands enabled 1: 
	Smart, MandatoryPowerManagement, WriteCache, LookAhead, HostProtectedArea, WriteBuffer, ReadBuffer, Nop
Commands enabled 2: 
	DownloadMicrocode, AdvancedPowerManagement, _48BitAddress, DeviceConfigurationOverlay, MandatoryFlushCache, FlushCacheExt, CommandSet4Valid
Commands enabled 3: 
	SmartErrorLogging, SmartSelfTest, GeneralPurposeLoggingFeature, _64BitWorldWideName, IdleImmediateWithUnload, AlwaysPresent

Commands enabled 4: 
	ReadWriteDmaExtGplOptional, SegmentForDownloadMicrocode, AlwaysPresent

Capabilities 1: 
	DmaSupported, LbaSupported, IordyMayBeDisabled, IordySupported, StandbyTimerValuesSupported

  Capabilities 2: 
	VendorSpecificStandbyTimerValueMinumum, AlwaysPresent

Trusted computing: 
	0

Maximum logical sectors: 
	268,435,455.00

  Additional supported: 
	0

Queue depth: 
	32

  SATA capabilities: 
	SataGen1SignalingSpeed_1_5_Gbs, SataGen2SignalingSpeed_3_0_Gbs, Ncq, ReceiptOfHostInitiatedPowerManagement, SataPhyEventCountersLog, UnloadWhileNcqCommandsOutstanding, NcqPriorityInformation

  SATA features supported: 
	DmaSetupAutoActivation, InitiatingPowerManagement, SoftwareSettingsPreservation

  SATA features enabled: 
	SoftwareSettingsPreservation

  Multiword DMA: 
	MultiwordDma0Supported, MultiwordDma1Supported, MultiwordDma2Supported, MultiwordDmaMode0Selected

UltraDMA: 
	UdmaMode0Supported, UdmaMode1Supported, UdmaMode2Supported, UdmaMode3Supported, UdmaMode4Supported, UdmaMode5Supported, UdmaMode6Supported

Advanced power management: 	MinimumPowerConsumptionWithoutStandby (80)

Automatic acoustic management: 
	[CURRENT] VendorSpecific (00)
	[DEFAULT] VendorSpecific (00)

Sector count (LBA): 	976,773,168.00

Logical sectors / physical: 	8 (Flags: 0x6000)

World wide name: 	0x50014EE6AD26ADAD (Authority=0x5, Organization=0x14EE, Vendor=0x6AD26ADAD
	Organization name: Western Digital Technologies, Inc.
	Organization address:
20511 Lake Forest Dr.
Lake Forest Ca 92630
UNITED STATES

Words per logical sector: 	0.00

Security: 	SecuritySupported, EnhancedSecurityEraseSupported

  Device nominal form factor: 
NotReported

Current media serial: 	

The 07A8 requires Unsafe IO in the test program as well, but shows up normally in Scanner, while the 0748 only returns SMART info from the test program. Odd, that.

Link to comment
Share on other sites

  • 0

If I could interject here, I have an HP Gen8 Server (ML310e) running the same B120i controller and it is possible to run that controller in straight ACHI mode.  It allows all the SMART metrics to pass through with the default settings in Stablebit Scanner.    I have 4 Drives plugged in right now and they all report back without issues.  If OP is running a single drive RAID volume, maybe it's worth it to just switch to ACHI.

 

I also had similar issues with getting SMART data from a USB enclosure.  I just assumed it was a limitation of the USB.  What's weird is that I can plug the same enclosure via eSATA and I can get SMART data coming back with that...   I'm going to read through this thread a little closer and see if I can get SMART via USB again.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...