Custom Query (1417 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (325 - 327 of 1417)

Ticket Resolution Summary Owner Reporter
#341 worksforme smartd tries to send Email even though it was not configured to do so. a_user
Description

Hi

I am using smartmontools/smartd 6.2 on Fedora 20. My smartd.conf file looks like this (all other lines are just empty or comments):

DEFAULT -H -s S/../../1/20 -p -f -l error -l xerror -n standby,q /dev/sda -i 197 -i 198 -W 5,32,38 -s L/../01/./21 DEVICESCAN -W 10,37,42

smartd itself is started by systemd with this command line:

/usr/sbin/smartd -n -q never

I have 4 different disks attached to this computer (/dev/sda, /dev/sdb, /dev/sdc, /dev/sdd). At the time /dev/sdb and /dev/sdc got hotter than 37 degree Celsius smartd tried to start /usr/bin/esmtp to send an email. I didn't configure smartd to send any email (not using the -m or -M options). Am I missing something or does smartd behave wrong?

Additional info: although /dev/sdd has some uncorrectable sectors it is only logged to syslog, not to mail (as expected/configured). Seems like just the last line is incorrectly interpreted.

#342 fixed Add Apple 512Mb SSD Christian Franke Alex Samorukov
Description

Cant find any specification and attributes seems to be very non-standard. E.g. 174 and 175 according to my tests are read/write in Mb.

M-PRG-00963913:smart asamorukov$ /usr/local/sbin/smartctl /dev/disk1  -v 174,raw48,Mb_Read -v175,raw48,Mb_Write -A -i
smartctl 6.2 2013-07-26 r3841 [x86_64-apple-darwin13.2.0] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     APPLE SSD SM0512F
Firmware Version: UXM2JA1Q
User Capacity:    500,277,790,720 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Jul 18 13:02:18 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 40
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x001a   200   200   000    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0033   100   100   000    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       69
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       179
169 Unknown_Attribute       0x0013   253   253   010    Pre-fail  Always       -       3651410075136
173 Unknown_Attribute       0x0032   200   200   100    Old_age   Always       -       4296474628
174 Mb_Read                 0x0022   099   099   000    Old_age   Always       -       1839891
175 Mb_Write                0x0022   099   099   000    Old_age   Always       -       1862708
192 Power-Off_Retract_Count 0x0012   099   099   000    Old_age   Always       -       16
194 Temperature_Celsius     0x0022   054   054   000    Old_age   Always       -       46 (Min/Max 17/75)
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age   Always       -       0
240 Unknown_SSD_Attribute   0x0022   100   100   000    Old_age   Always       -       0


#343 fixed Read Defect Data commands for SSD Doug Gilbert Kimito
Description

The Read Defect Data command on most SAS SSD is going to return CHECK CONDITION for request of LBA, CHS, BFI format. Usually for KCQ=01/1C/02 "defect list not found".

This is because the retired NAND media does not fit any of those convictions. Most SAS SSD vendors will support and return a vendor unique format which depending on the vendor may not give you the format definition. Then this command becomes useful only to the vendor. Fortunately, most vendors provide other means to look at bad blocks.

My issue is that I use smartctl a lot and every time I run it during a long test run, it generates a bunch of CHECK CONDITIONS in my outputs that I have to filter out.

Could smartctl omit the Read Defect Data command if the device is an SSD? or provide a switch so that I can disable checking for defect through Read Defect Data?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.