Jump to content

Seagate NAS ST4000VN000 64MB 4TB


pjakesson

Recommended Posts

How is the disk attached?

Is it connected to an Add-on controller card?

 

Also, could you try this config file:

https://www.dropbox.com/s/0krodbweqz1rrc4/Scanner.Service.exe.config

Some times editing the file yourself.... doesn't seem to work. And I'm not exactly sure why, but this file is taken from my server and should work. Most everyone has reported that it does.

 

 

Alternatively, you can try this:

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

Try it with UnsafeDirectIo unchecked. If the "SMART Attributes" in WMI *and* DirectIO don't work, check the "UnsafeDirectIo" box. If that does get a green check for either one of those, look at the bottom and report the "Methods:" used.

 

But the drive itself should be supported.

Link to comment
Share on other sites

How is the disk attached?

Is it connected to an Add-on controller card?

 

 

 

I have the disk in an external SSI SI-1359RUS3 5 bay chassi which have a JMicron JMB539/JMB393 controller

and I have it connected through USB3..

 

I will try your suggestions and get back with results.

 

Per

 

Alternatively, you can try this:

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

Try it with UnsafeDirectIo unchecked. If the "SMART Attributes" in WMI *and* DirectIO don't work, check the "UnsafeDirectIo" box. If that does get a green check for either one of those, look at the bottom and report the "Methods:" used.

 

But the drive itself should be supported.

 

Your config file did not make any difference, unfortunately.

 

 

I have attached a screenshot of the DirectIoTest-1_0_5016_597.exe  output.

 

I looks as I could get SMART data, or?

 

Per

post-31-0-91235400-1387637849_thumb.png

Link to comment
Share on other sites

  • 7 months later...

 

 

Well, bringing up an old thread with my problems.

 

I resigned and accepted that my Seagate 4TB was not offering S.M.A.R.T data through the controller.

 

But yesterday I ripped a Seagate 2TB Expansion disk from it casing and put into my USB 3 cabinet

and Stablebit Scanner is pulling S.M.A.R.T data  from that disk with no problem.

 

It is the 2 bottom disk in attached screenshot:

 

vmuhdj.png

 

 

Why can't Stablebit Scanner get  S.M.A.R.T data from the 4 TB disk?

 

Thanks in advance

 

Per

 

Link to comment
Share on other sites

To make sure, this is the same USB controller, and it's not getting the SMART data from the 4TB drive?

 

If that is the case, it may be the USB controller that is the issue.

 

 

However, could you doublecheck with the DirectIoTest app again? Instead of checking the "UnsafeDirectIo" option, could you check the "USB" option.

If it gets the SMART data, could you report what the Hardware ID is that it lists, as well as the methods used? (Or just grab a screenshot again)

Link to comment
Share on other sites

Yes it is the same USB controller (since it is the same cabinet/case?)

 

So you think the controller doesn't work with disks > 2TB, well perhaps.

 

Anyway here is a screenshot of the DirectIoTest app with USB option checked.

 

2zej9zd.png

 

It seems that it is receiving S.M.A.R.T data OK?

 

thanks for looking into this.

 

BTW querying the 2TB disk in the same case, I get identical output except for S.M.A.R.T Error log is supported.

 

Per

Link to comment
Share on other sites

Further information:

 

When I retrieve the S.M.A.R.T Attributes list I get the following output:

 

  Smart attributes for device:   9
  Version:   0
  Offline data collection status:   NeverStartted
  Self-test execution status:   PreviousCompletedNoErorrOrNoTestRun
  Self-test percent remaining:   0
  To complete off-line data collection:   00:00:00
  Off-line data collection capability:   0
  SMART capability:   0
  Error logging capability:   False
  Short self-test polling time:   00:00:00
  Extended self-test polling time:   00:00:00
  Conveyance self-test polling time:   00:00:00
 
  Attributes:   0
  Checksum valid:   True
 

 

Doesn't look that promising?

 

Per

Link to comment
Share on other sites

If that's the case, then it looks like it's passing on the SMART information but it's truncating the actual attributes.

 

You see the two methods it lists at the bottom? Could you enable the "Specific Method" option, and check both of these to see if it shows the SMART attributes?

 

Also, normally, it should show the hardware ID for the USB controller here.

However, you can use Device Manager to find that out:

  1. Run "devmgmt.msc"
  2. select "Devices by connection" in the "View" menu.
  3. Find the disk in question, and then right click on the USB mass storage device that the disk is "connected" to.
  4. Go to the properties page, and get the Hardware ID from there.
Link to comment
Share on other sites

 

If that's the case, then it looks like it's passing on the SMART information but it's truncating the actual attributes.

 

You see the two methods it lists at the bottom? Could you enable the "Specific Method" option, and check both of these to see if it shows the SMART attributes?

 

Same result for both methods,ScsiPassthrough and ScasiPassthrough48, empty S.M.A.R.T Attributes list.

 

Couldn't really find the disk with your method. I get the following view from "devmgmt.msc":

 

11264qa.png

 

 

But if I select the disk from the default view, and select properties I get these hardware Id's;

 

20fp8hj.png

 

Are they the ones you are asking for?

 

Per

Link to comment
Share on other sites

Reading through your answer again I realized you wanted the hardware Id for the controller,

and by looking on the disk's parent, as in:

 

2qbfzvo.png

 

I think I identified the correct USB Mass Storage Device as in:

 

2rptegg.png

 

Is that what you wanted me to find out?

 

Per

Link to comment
Share on other sites

Yes, it is. Thank you.

 

I've flagged the issue for Alex.

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

 

 

However, I'm not sure if there is anything we can do here.

It looks like the enclosure is not reporting the full SMART information from the disk. If it's not reporting it, we can't grab it. 

You may want to try the other specific methods and see if one works. Or see if moving the disk to a different slot helps.

 

Also, it may be that the chipset for the enclosure doesn't like the 4TB disks and is having issues with them.

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
Reply to this topic...

×   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...