SMART options for Samsung HD204UI

[Beaker1024]

I have 2 Samsung HD204UI that I am fairly sure that I did the firmware update when I installed them ~3 years ago. 

Without the firmware patch they had a bug that would corrupt data if it got a NCQ write while the S.M.A.R.T. data was being read from the drive.

 

Problem is the firmware patch did not change the firmware version so there's no real way of knowing if your drive is safe.

 

I have looked at all the options and advanced options regarding SMART data reading in the scanner plugin.

 

I'm not sure the "Do not use Direct I/O when querying SMART" option is exactly what I need or not.  Can you expand on what this options prevents in more detail?

 

For the time being I"m checking the "Do not query SMART" for each of these drives to be safe.

 

I'd like to be able to uncheck those boxes and get the Scanner to read SMART (even if only during working hours and infrequently).

 

Do you have any suggestions or details on what some of these options do?

 

Thank you for your time and assistance!

[Christopher (Drashna)]

Wow, that's a pretty scary bug!

 

As for the drives, then yes, on the "Disk settings" page, I would recommend check the "Do not query SMART" option for these drives.

 

However, if there is no important data on the disks, then I would say attempt to reflash the disks, just to be sure. Grab a permanent marker and write "flashed" or something similar on them, so you can be certain in the future.

 

 

 

However, we do have the option to only query SMART data during the "work window" for StableBit Scanner. If you open the Scanner Settings, click on the "SMART" tab. Check the "Only query during the work window or if scanning" option.

 

 

Additionally, could you get the BitFlock ID for the system? (open the "SMART details" for one of the disks, check the "submit to bitflock" option, and post the ID once it's generated it).

[Christopher (Drashna)]

Okay, just to clarify here (for you and the future)...

 

While this is absolutely terrifying (IMO), Alex (the developer) is already aware of the issue, and has code in StableBit Scanner to detect and "handle" these drives in a 100% safe manner. What I mean, is that we DO NOT sent the "identify" command to these drives, regardless of the firmware version. Since this is what cases the destabilization and data loss, it means that "we" can safely query the drive without compromising your data. 

 

So you can safely enable the SMART queries for the drive.

 

However, that means you may not have as much information in the disk details section (such as firmware version) for these drives. I'm sure you're 100% fine with that, though.

 

However, you can override the behavior, if you're so inclined. 

http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings

Add your model to the "GoodIdentifyOverride" setting.

[Beaker1024]

Christopher - Thanks for the detailed response.  I wasn't expecting responses over the Holidays (I just finally decided I needed your software and give it a try this week), Thanks again!

 

I noticed the drive details were a bit less on the Samsung than the WDs I have.  They didn't have the fancy SATA connector image and info on port, etc.... That's OK I'll live without that for the extra safety!

 

Especially when you can get me the SMART details safely for detecting drive failure (most important).  BTW I found digital pictures of the screen when I did the firmware updates saying successful.  Just have tried to always not do the event that causes the error just in case.  Really wish they changed the firmware #.

 

I should and likely will start two more threads.  I've almost worked through all my setup / concerns and this software set is amazing!

 

Have a great Holiday!  I'll be buying the full set of software from you soon + really like the new programs you have slated to develop!  Especially the one regarding UPS Power status (IIRC).

 

Can you post a quick step outline on how and what the BitFlok ID is/works?  I understand its general purpose just not the more detail view of it.

[Christopher (Drashna)]

Beaker,

 

You're very welcome. This was a topic that was very important to answer, IMO.

 

As for the Disk Details, that would be why. That information is populated by the "Identify" command. Since we avoid querying that data for these drives, you won't see it (unless you enable that "GoodIdentifyOverride" option).

 

And yeah, they should increment the firmware version number. That's the ENTIRE point of releasing a patch like this....

 

 

And I'm glad to hear it! 

As for the slated programs, I can't give ETAs, but we do want to get to them sooner, rather than later.

 

As for the BitFlock ID, both the stand-alone program and StableBit Scanner use BitFlock. The stand alone app lets you create a "nest" that lists your drives, and uploads information about them (such as the SMART data). You can access and share this data.

Additionally, both products store a number of "rules" on how to interpret the SMART data, as well as which drives to "ignore" for stuff like the "identify" command. It also includes a lot more information about the disks, and the controller's they're attached to, which we can use to "fix" problems, or even blacklist devices. It's a big part of StableBit Scanner.