Custom Query (1095 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (49 - 51 of 1095)

Ticket Resolution Summary Owner Reporter
#1383 duplicate IronWolf Pro 125 floatinglettersllc
Description

I was referred to you by Synology. We have 5 new Seagate IronWolf? Pro 125 SSD NAS drives. They have a critical error because of an issue Unknown Attribute failure. Are you able to resolve this issue by adding the attributes to your DB? My understanding is that Synology pulls that data.

#246 Unkown_Attribute failed. Error in this S.M.A.R.T attribute usually indicates that severe electronic or physical damages have occurred to the drive, and that the error cannot be suppressed manually. We highly recommend backing up your data and replacing the drive immediately.

#1382 invalid SAMSUNG MZVLQ512HALU-00000 glennkissinger
Description
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-51-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZVLQ512HALU-00000
Serial Number:                      S4Y4NF0N246246
Firmware Version:                   FXV7000Q
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 512,110,190,592 [512 GB]
Unallocated NVM Capacity:           0
Controller ID:                      5
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512,110,190,592 [512 GB]
Namespace 1 Utilization:            63,678,894,080 [63.6 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 a201b8954d
Local Time is:                      Sun Oct 18 20:57:57 2020 MDT
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     4.83W       -        -    0  0  0  0        0       0
 1 +     3.54W       -        -    1  1  1  1        0       0
 2 +     3.04W       -        -    2  2  2  2        0     500
 3 -   0.0500W       -        -    3  3  3  3      210    1200
 4 -   0.0050W       -        -    4  4  4  4     1000    9000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        14 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    1,384,917 [709 GB]
Data Units Written:                 997,639 [510 GB]
Host Read Commands:                 14,918,554
Host Write Commands:                10,334,899
Controller Busy Time:               142
Power Cycles:                       169
Power On Hours:                     74
Unsafe Shutdowns:                   35
Media and Data Integrity Errors:    0
Error Information Log Entries:      383
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               14 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged

Non-Volatile memory controller product: Samsung Electronics Co Ltd

#1381 fixed --nocheck standby is ignored if device does not support power check which causes spin up Christian Franke Marc Gutt
Description

I connected an HDD through USB. The USB controller blocks some hdparm/ATA commands and by that the following:

smartctl -n standby -A /dev/sdg

returns:

CHECK POWER MODE: incomplete response, ATA output registers missing
CHECK POWER MODE not implemented, ignoring -n option

I would prefer that it does not ignore the -n option in such a case to avoid HDD spin up (the reason why -n was used).

This caused a small bug in Unraid: https://forums.unraid.net/bug-reports/stable-releases/683-usb-hdds-randomly-spin-up-but-status-stays-unchanged-r1091/

But I was able to solve it by changing the command to the "-i" option:

smartctl -n standby -i /dev/sdg

It returns the same "not implemented" error, but it does luckily not spin up the HDD.

Note: See TracQuery for help on using queries.