Custom Query (1542 matches)

Dear Seagate Team,

We are using ST4000NM0035-1V4 drives and we are noticing that these drives are not in the smartmontool database, we checked in latest drivedb.h(6.4 trunk Path)file but their is also no entry for these drives.

Due to this "power ON hours" for these are listing to some garbage values. Kindly add these drive model in your database.

Below is the drive specifications:-

Model - ST4000NM0035-1V4
Capacity - 4TB(usable capacity - 3725.5GB)
RPM - 7200
Firmware - TNC3
speed - 6 Gb/s
cache - 128MB

​https://www.cnet.com/products/seagate-enterprise-capacity-3-5-hdd-4tb-512n-sata/specs/

Attaching the short and full smartmontool report for the reference.

Sent a mail too for the reference

Thanks & Regards,

Abhishek Bathole American MegaTrends India Pvt. Ltd

I would like to prepare a patch to implement '--json' cmd option, as mentioned in ticket #766. I'm new to this project and would appreciate your help.

1. Is it okay if I use C++11 features, even if it as little as "auto"?

2. What's your opinion about using a JSON library? (specifically this one - ​JSON for Modern C++)

3. I wish to create a data structure to hold the smart data, and print it when it's completely populated.

Do you have insights about how the data structure should look like, considering hierarchy, data order, and which containers to use?

When looking at the first chunks of output for SATA I was wondering how to represent the data, so it would be easy to traverse and print. The general idea is to have a container to represent each section, for example:

struct smart_data {

map<string, string> info_section; map<string, string> smart_data_section; vector<map<string,string>> vendor_specific_attr; more containers go here

};

Is there a certain format you prefer it to be represented?

4. Is there a way to mock output from devices I don't have (such as SAS)? I wish to test this output but I don't have all of the supported disks out there...

Many thanks!

Most smartctl commands have a default timeout of 20 seconds. This is sufficiently long for pretty much any disk to spin up from standby. However, many large JBODs implement staggered spinup, where they limit the number of drives that can simultaneously spin up. On such systems, it may take considerably longer for all drives to spin up. For example, I have a 96-drive JBOD where spinning up all drives takes nearly 45 seconds. The attached patch fixes smartctl for me.