English Community

Datacenter StorageLenovoEMC Storage
All Forum Topics
Options

5 Posts

04-01-2020

US

5 Signins

40 Page Views

  • Posts: 5
  • Registered: ‎04-01-2020
  • Location: US
  • Views: 40
  • Message 1 of 3

PX4, reading smart status, spin down or 24/7?

2020-08-17, 4:41 AM

I just bought a new PX4-400d, and I have a couple questions. Currently populated with 3x HGST refurb 4TB drives, non raid, showing 10.7TB free.

 

Is there a way to read the smart status codes, app or add on, or its already there and I haven't found it? I used a PC to format and test before installing in the NAS.

 

Calif has expensive power, 45 cents / kwhr during peak times, use in our home is likely burst of up/down and then nothing for maybe even a day or more. Should I spin down the drives after like an hour via the energy saving app?

Reply
Options

34 Posts

03-25-2019

GB

34 Signins

291 Page Views

  • Posts: 34
  • Registered: ‎03-25-2019
  • Location: GB
  • Views: 291
  • Message 2 of 3

Re:PX4, reading smart status, spin down or 24/7?

2020-08-17, 10:20 AM

For SMART data see https://forums.lenovo.com/t5/LenovoEMC-Storage/SMART-Hard-Drive-Monitor/m-p/3321828 

 

I've just tested it on my PX6, it takes a while but does what you need.  You'll need 7-zip or similar to unzip the .gz and .tar files.

 

David

Reply
Options

5 Posts

04-01-2020

US

5 Signins

40 Page Views

  • Posts: 5
  • Registered: ‎04-01-2020
  • Location: US
  • Views: 40
  • Message 3 of 3

Re:PX4, reading smart status, spin down or 24/7?

2020-08-17, 13:13 PM

Clipped from link above.

 

3. For NAS devices running firmware 3.3.4 and higher including 4.x.x.
a. Log in to the NAS user interface with an administrator account
b. Change the URL to https://<devicename or IP address>/manage/diagnostics.html.
c. From here you can click on “Support Files”.
d. Then click the “Create a dump file” link.

4. Allow the log file dump to complete. This could take several minutes.
5. A new file name will appear on the list. Click on the file to download it to your computer.

 

Thanks, worked, it is LONG. Inside the created dump in /disks/sdd.info it shows they use www.smartmontools.org tool, but maybe not updated in ages. Poking around that site is next on my agenda for more understanding.

 

So far reading the dump details, its going to be some time before I understand more than the line that says "passed". ;)

 

Part of my testing of the drives was using a USB/Sata adapter that would seem to work for a few minutes, then disconnect from the PC and show the what do you want to do with this new device dialog, or show errors during diagnostic testing or formatting, and I think that may have put some errors in the smart log. Example below (sorry for the long, better complete than not). BTW putting that in not to ask for help, but just as a reference.

 

SMART Error Log Version: 1

ATA Error Count: 22 (device log contains only the most recent five errors)

CR = Command Register [HEX]

FR = Features Register [HEX]

SC = Sector Count Register [HEX]

SN = Sector Number Register [HEX]

CL = Cylinder Low Register [HEX]

CH = Cylinder High Register [HEX]

DH = Device/Head Register [HEX]

DC = Device Command Register [HEX]

ER = Error register [HEX]

ST = Status register [HEX]

Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.

 

Error 22 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER ST SC SN CL CH DH  -- -- -- -- -- -- --  

84 51 29 d7 b3 14 00

Error: ICRC, ABRT at LBA = 0x0014b3d7 = 1356759

Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name  -- -- -- -- -- -- -- --  ----------------  --------------------

61 00 08 00 b4 14 40 00      00:09:51.849  WRITE FPDMA QUEUED

61 00 00 00 b0 14 40 00      00:09:51.849  WRITE FPDMA QUEUED

61 00 08 00 ac 14 40 00      00:09:51.842  WRITE FPDMA QUEUED

61 00 00 00 a8 14 40 00      00:09:51.842  WRITE FPDMA QUEUED

61 00 08 00 a4 14 40 00      00:09:51.836  WRITE FPDMA QUEUED

 

Error 21 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)

When the command that caused the error occurred, the device was active or idle.  

After command completion occurred, registers were:

ER ST SC SN CL CH DH  -- -- -- -- -- -- --

84 51 0d f3 51 12 00  Error: ICRC, ABRT at LBA = 0x001251f3 = 1200627

Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name  -- -- -- -- -- -- -- --  ----------------  --------------------

61 00 00 00 50 12 40 00      00:09:36.741  WRITE FPDMA QUEUED  

61 00 08 00 4c 12 40 00      00:09:36.739  WRITE FPDMA QUEUED

61 00 00 00 48 12 40 00      00:09:36.738  WRITE FPDMA QUEUED

61 00 08 00 44 12 40 00      00:09:36.737  WRITE FPDMA QUEUED

61 00 00 00 40 12 40 00      00:09:36.735  WRITE FPDMA QUEUED

 

Error 20 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER ST SC SN CL CH DH  -- -- -- -- -- -- --

84 51 55 ab 0e 12 00  Error: ICRC, ABRT at LBA = 0x00120eab = 1183403

Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name  -- -- -- -- -- -- -- --  ----------------  --------------------

61 00 08 00 0c 12 40 00      00:09:34.701  WRITE FPDMA QUEUED

61 00 00 00 08 12 40 00      00:09:34.701  WRITE FPDMA QUEUED

61 00 08 00 04 12 40 00      00:09:34.696  WRITE FPDMA QUEUED

61 00 00 00 00 12 40 00      00:09:34.696  WRITE FPDMA QUEUED

61 00 08 00 fc 11 40 00      00:09:34.690  WRITE FPDMA QUEUED

 

Error 19 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)  

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER ST SC SN CL CH DH  -- -- -- -- -- -- --

84 51 33 cd b1 0b 00  Error: ICRC, ABRT at LBA = 0x000bb1cd = 766413

Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name  -- -- -- -- -- -- -- --  ----------------  --------------------  

61 00 08 00 b4 0b 40 00      00:09:18.333  WRITE FPDMA QUEUED

61 00 00 00 b0 0b 40 00      00:09:18.333  WRITE FPDMA QUEUED

61 00 08 00 ac 0b 40 00      00:09:18.326  WRITE FPDMA QUEUED

61 00 00 00 a8 0b 40 00      00:09:18.326  WRITE FPDMA QUEUED

61 00 08 00 a4 0b 40 00      00:09:18.319  WRITE FPDMA QUEUED

 

Error 18 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)  

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER ST SC SN CL CH DH  -- -- -- -- -- -- --

84 51 3f c1 1c 08 00  Error: ICRC, ABRT at LBA = 0x00081cc1 = 531649

Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name  -- -- -- -- -- -- -- --  ----------------  --------------------

61 00 08 00 1c 08 40 00      00:09:15.741  WRITE FPDMA QUEUED

61 00 00 00 18 08 40 00      00:09:15.741  WRITE FPDMA QUEUED

61 00 08 00 14 08 40 00      00:09:15.736  WRITE FPDMA QUEUED

61 00 00 00 10 08 40 00      00:09:15.736  WRITE FPDMA QUEUED

61 00 08 00 0c 08 40 00      00:09:15.729  WRITE FPDMA QUEUED

 

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline       Completed without error       00%         0         -

# 2  Vendor (0xb0)       Completed without error       00%     38134         -

# 3  Vendor (0x71)       Completed without error       00%     38134         -

 

SMART Selective self-test log data structure revision number 1

SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

   1        0        0  Not_testing

   2        0        0  Not_testing

   3        0        0  Not_testing

   4        0        0  Not_testing

   5        0        0  Not_testing

 

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

 

 

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete