Menu
▾
▴
smartmontools-support — (old) mailing list for discussion, bug reports, support requests, and feature requests (2002-10-11 until 2017-07-30)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(50) |
Nov
(161) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(84) |
Feb
(103) |
Mar
(54) |
Apr
(63) |
May
(44) |
Jun
(45) |
Jul
(44) |
Aug
(55) |
Sep
(15) |
Oct
(99) |
Nov
(101) |
Dec
(104) |
| 2004 |
Jan
(76) |
Feb
(98) |
Mar
(99) |
Apr
(130) |
May
(107) |
Jun
(79) |
Jul
(94) |
Aug
(164) |
Sep
(115) |
Oct
(125) |
Nov
(160) |
Dec
(84) |
| 2005 |
Jan
(72) |
Feb
(85) |
Mar
(55) |
Apr
(109) |
May
(64) |
Jun
(33) |
Jul
(71) |
Aug
(77) |
Sep
(84) |
Oct
(102) |
Nov
(106) |
Dec
(51) |
| 2006 |
Jan
(47) |
Feb
(58) |
Mar
(60) |
Apr
(106) |
May
(73) |
Jun
(65) |
Jul
(109) |
Aug
(103) |
Sep
(73) |
Oct
(57) |
Nov
(94) |
Dec
(62) |
| 2007 |
Jan
(61) |
Feb
(67) |
Mar
(90) |
Apr
(90) |
May
(77) |
Jun
(82) |
Jul
(75) |
Aug
(74) |
Sep
(63) |
Oct
(70) |
Nov
(60) |
Dec
(59) |
| 2008 |
Jan
(68) |
Feb
(113) |
Mar
(128) |
Apr
(89) |
May
(57) |
Jun
(88) |
Jul
(74) |
Aug
(43) |
Sep
(77) |
Oct
(106) |
Nov
(99) |
Dec
(82) |
| 2009 |
Jan
(126) |
Feb
(49) |
Mar
(47) |
Apr
(26) |
May
(38) |
Jun
(75) |
Jul
(61) |
Aug
(45) |
Sep
(105) |
Oct
(77) |
Nov
(46) |
Dec
(47) |
| 2010 |
Jan
(58) |
Feb
(88) |
Mar
(54) |
Apr
(78) |
May
(30) |
Jun
(40) |
Jul
(46) |
Aug
(36) |
Sep
(30) |
Oct
(29) |
Nov
(80) |
Dec
(52) |
| 2011 |
Jan
(30) |
Feb
(27) |
Mar
(25) |
Apr
(77) |
May
(24) |
Jun
(45) |
Jul
(34) |
Aug
(24) |
Sep
(65) |
Oct
(55) |
Nov
(72) |
Dec
(19) |
| 2012 |
Jan
(58) |
Feb
(44) |
Mar
(90) |
Apr
(11) |
May
(27) |
Jun
(32) |
Jul
(61) |
Aug
(32) |
Sep
(39) |
Oct
(45) |
Nov
(50) |
Dec
(21) |
| 2013 |
Jan
(44) |
Feb
(26) |
Mar
(37) |
Apr
(46) |
May
(24) |
Jun
(44) |
Jul
(15) |
Aug
(16) |
Sep
(20) |
Oct
(36) |
Nov
(36) |
Dec
(41) |
| 2014 |
Jan
(21) |
Feb
(9) |
Mar
(14) |
Apr
(16) |
May
(32) |
Jun
(50) |
Jul
(71) |
Aug
(47) |
Sep
(17) |
Oct
(9) |
Nov
(40) |
Dec
(42) |
| 2015 |
Jan
(11) |
Feb
(25) |
Mar
(22) |
Apr
(21) |
May
(6) |
Jun
(3) |
Jul
(7) |
Aug
(42) |
Sep
(28) |
Oct
(33) |
Nov
(5) |
Dec
(7) |
| 2016 |
Jan
(12) |
Feb
(18) |
Mar
(19) |
Apr
(31) |
May
(27) |
Jun
(23) |
Jul
(12) |
Aug
(33) |
Sep
(5) |
Oct
(28) |
Nov
(19) |
Dec
(8) |
| 2017 |
Jan
(52) |
Feb
(36) |
Mar
(12) |
Apr
(17) |
May
(8) |
Jun
(12) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dan L. <da...@ob...> - 2021-03-13 22:41:35
|
>> On 11.3.2021 13:44, Budi Janto wrote: >>> Mar 11 18:45:42 BEC-STG-P1 kernel: (ada2:ahcich5:0:0:0): >>> READ_FPDMA_QUEUED. ACB: 60 20 28 1f 90 40 b8 01 00 00 00 00 I should correct myself. The string above is printed by (FreeBSD, sys/cam/ata/ata_all.c, ata_cmd_sbuf() ): > sbuf_printf(sb, "%02x %02x %02x %02x " > "%02x %02x %02x %02x %02x %02x %02x %02x", > cmd->command, cmd->features, > cmd->lba_low, cmd->lba_mid, cmd->lba_high, cmd->device, > cmd->lba_low_exp, cmd->lba_mid_exp, cmd->lba_high_exp, > cmd->features_exp, cmd->sector_count, cmd->sector_count_exp); Address of sector is 0x01B8901F28 not 0x01B840901F as I misclaimed previously. Dan |
|
From: Christian F. <Chr...@t-...> - 2018-08-13 09:48:44
|
Alex Regan wrote: > I have a Seagate 5TB disk that was given to me because the original > owner was having trouble with it and thought it was defective (it > probably is). It's also listed as a "component" by Seagate so not > covered under warranty. > > Before tossing it, I thought I would run some tests. I ran badblocks > across the majority of the disk and it completed at least one pass > without error. > > I also ran a smartctl long test and it appeared to complete > successfully, but doesn't display the normal self-test log report at > the end. > > Here is the results of a "smartctl -a" on the device. Can someone tell > me the significance of the errors below? > ... > % smartctl -a /dev/sda > smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.32-std522-amd64] > (local build) > Copyright (C) 2002-17, Bruce Allen, Christian Franke, > www.smartmontools.org > > === START OF INFORMATION SECTION === > Model Family: Seagate Desktop HDD.15 > Device Model: ST5000DM000-1FK178 > ... > Firmware Version: ZZZZ BTW: Interesting FW Version :-) > ... > > Read SMART Self-test Log failed: scsi error unsupported field in scsi > command > > Read SMART Selective Self-test Log failed: scsi error unsupported > field in scsi command This usually does not indicate disk problems. Either these logs are not supported or this is a limitation of some software layer (e.g. SCSI ATA Translation) between smartctl and disk. Did you connect this drive via USB? If yes, which USB Id? Note that "smartctl -a" does not print newer ATA logs . Try "smartctl -x". Thanks, Christian |
|
From: Alex R. <mys...@gm...> - 2018-08-11 20:42:16
|
Hi, I have a Seagate 5TB disk that was given to me because the original owner was having trouble with it and thought it was defective (it probably is). It's also listed as a "component" by Seagate so not covered under warranty. Before tossing it, I thought I would run some tests. I ran badblocks across the majority of the disk and it completed at least one pass without error. I also ran a smartctl long test and it appeared to complete successfully, but doesn't display the normal self-test log report at the end. Here is the results of a "smartctl -a" on the device. Can someone tell me the significance of the errors below? I've pasted the results here, but also pastebinned them in case this info isn't legible https://pastebin.com/Ce3NYmCq % smartctl -a /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.32-std522-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST5000DM000-1FK178 Serial Number: W4J0TRCE LU WWN Device Id: 5 000c50 08ab777ea Firmware Version: ZZZZ User Capacity: 5,000,981,078,016 bytes [5.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Aug 11 14:09:58 2018 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED ... SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 086 006 Pre-fail Always - 34760 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1128 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 071 070 030 Pre-fail Always - 25859650096 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 279 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 10 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 659 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 067 053 045 Old_age Always - 33 (Min/Max 24/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 194 Temperature_Celsius 0x0022 033 047 000 Old_age Always - 33 (0 24 0 0 0) 195 Hardware_ECC_Recovered 0x001a 115 108 000 Old_age Always - 34760 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 661 (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 661 occurred at disk power-on lifetime: 229 hours (9 days + 13 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 -- -- -- -- -- -- -- 40 53 00 a0 27 76 09 Error: UNC at LBA = 0x097627a0 = 158738336 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 a0 27 76 49 00 20:49:02.670 READ FPDMA QUEUED 60 00 08 98 27 76 49 00 20:49:02.499 READ FPDMA QUEUED 60 00 08 90 27 76 49 00 20:49:02.218 READ FPDMA QUEUED 60 00 08 88 27 76 49 00 20:49:02.078 READ FPDMA QUEUED 60 00 08 80 27 76 49 00 20:49:01.928 READ FPDMA QUEUED Error 660 occurred at disk power-on lifetime: 229 hours (9 days + 13 hours) When the command that caused the error occurred, the device was active or idle. Read SMART Self-test Log failed: scsi error unsupported field in scsi command Read SMART Selective Self-test Log failed: scsi error unsupported field in scsi command |
|
From: Phil R. <phi...@in...> - 2018-03-01 17:10:08
|
Is it possible to get the list of new messages less often. Maybe twice each month? Thanks. Phil. |
|
From: Gabriele P. <gp...@sm...> - 2017-07-30 11:49:20
|
Dear smartmontools users, due to recent changes at sourceforge https://sourceforge.net/blog/sourceforge-project-e-mail-policy-update/ we decided to move the mailing lists to another host[1]. Please subscribe to the new lists here: Announcement mailing list https://listi.jpberlin.de/mailman/listinfo/smartmontools-announce Support, discussion, bug report and suggestion mailing list https://listi.jpberlin.de/mailman/listinfo/smartmontools-support List for contributions of info about drives that are not yet in smartmontools drive db https://listi.jpberlin.de/mailman/listinfo/smartmontools-database Unfortunately it is not possible for us to export and move the old mailing list archives to the new location due to the restricted admin privileges at sourceforge. Sourceforge support told us that they also cannot hand over a copy "as it would be a violation of the laws we made these changes to comply with to release any subscriber information." So you have to search on two places for a while until the old messages can be classified as outdated. Find links to our archives on the web in the wiki: https://www.smartmontools.org/wiki/Help#Mailinglist So far the info and see you on the new lists! Cheers, Gabriele [1] Many thanks to jpberlin (https://www.jpberlin.de/) who offer free service, complete list administration access and mailing list archives for our Free Software Project :-) -- Smartmontools developer team https://www.smartmontools.org/wiki/Team |
|
From: Jared D. <jrd...@gm...> - 2017-07-27 23:30:52
|
Greetings, Sorry if this isn't sent to the right place, but you make it really hard to tell who on earth to contact on your website, and there's no IRC channel that I could find either. I'm trying to submit a new ticket to your Trac system for a device not in the device list, but Trac never sends out the verification email for me to verify me email so that I can post the new ticket. Not sure if that's a known issue or not, but I'm sure it's not on my end, I've waited at least half an hour. Thanks, Jared D. |
|
From: Alexander S. <ash...@gm...> - 2017-07-21 10:24:20
|
Hello everyone, I just released GSmartControl 1.0.2 (a GUI for smartctl), you may find it at http://gsmartcontrol.sourceforge.net . Changes include: Fixed incomplete capturing of smartctl output under Windows. Added missing icons under Windows. Fixed being able to turn on AODC even if unsupported. Thanks, Alexander |
|
From: Crip P. <kna...@gm...> - 2017-06-27 06:10:23
|
Hello, I tried to use smartctl to find SMART attribute which'd tell me what is the current wear out level of my SSD. But I didn't find anything remotely similar among available attributes. Could you help me with that? smartctl -a output is attached to the email Kind regards, Krzysiek |
|
From: Alexander S. <ash...@gm...> - 2017-06-19 15:33:23
|
Hello all, I just released GSmartControl 1.0.1 (a GUI for smartctl), you may find it at http://gsmartcontrol.sourceforge.net . Changes include: Fixed compilation under Fedora Rawhide. Fixed compilation under macOS. Fixed optimization flags for architectures other than x86 and x86-64. Any help with testing is really appreciated. Thanks, Alexander |
|
From: David K. <kos...@gm...> - 2017-06-19 13:50:27
|
Hello, attribute 202 which is now called Percent_Lifetime_Used is supposed to be percent lifetime remaining, according to spec PDF attached (on page 21). Version details also attached, but I updated database today. |
|
From: Kees v. d. W. <ke...@to...> - 2017-06-18 12:04:31
|
Hello, It has been a little while since I posted my question on the smartmontools support forum. Thanks for the primary answer I got from Robert S. To my own disgrace, I must now admit that I have been wrong by saying that the device about which I got this health warning did not exist on my system. It DOES exist!! However, a complete health scan was never performed before, as I discovered. I then let it run once and I haven't seen a warning since then. Therefore, I suppose that this post can be closed. Should the messages about this drive appear again, I can post a new question if necessary. Thanks anyway for your attention. Kees van der Wiel |
|
From: Alexander S. <ash...@gm...> - 2017-06-16 16:58:03
|
Hello all, I just released GSmartControl 1.0.0 (a GUI for smartctl), you may find it at http://gsmartcontrol.sourceforge.net . Changes include: Ported the interface to GTK+ 3. Tweaked the user interface a bit. Added 64-bit packages for Windows. Dropped support for Windows XP, 2000 and 2003 (they are no longer supported by GTK+). Fixed detection of newer system-installed smartmontools under Windows. Any help with testing is really appreciated. Thanks, Alexander |
|
From: Franc Z. <fz...@in...> - 2017-06-15 20:50:43
|
Normal SATA SMART Attribute Behavior (Seagate): http://t1.daumcdn.net/brunch/service/user/axm/file/Vw3RJSZllYbDc86ssL6bofiL4r0.pdf |
|
From: Franc Z. <fz...@in...> - 2017-06-15 20:39:05
|
Sorry if this spec is already in the support docs ... Seagate SMART Attribute Specification: http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf |
|
From: mathog <ma...@ca...> - 2017-06-12 16:17:56
|
On 05-Jun-2017 16:20, mathog wrote: > Read Device Identity failed: megasas_cmd result: 0.0 = 0/45 > > ./smartctl --scan > /dev/sda -d scsi # /dev/sda, SCSI device > /dev/bus/0 -d megaraid,0 # /dev/bus/0 [megaraid_disk_00], SCSI device > /dev/bus/0 -d megaraid,1 # /dev/bus/0 [megaraid_disk_01], SCSI device > /dev/bus/0 -d megaraid,2 # /dev/bus/0 [megaraid_disk_02], SCSI device > /dev/bus/0 -d megaraid,3 # /dev/bus/0 [megaraid_disk_03], SCSI device > /dev/bus/0 -d megaraid,4 # /dev/bus/0 [megaraid_disk_04], SCSI device > /dev/bus/0 -d megaraid,5 # /dev/bus/0 [megaraid_disk_05], SCSI device > /dev/bus/0 -d megaraid,6 # /dev/bus/0 [megaraid_disk_06], SCSI device > /dev/bus/0 -d megaraid,7 # /dev/bus/0 [megaraid_disk_07], SCSI device Figured it out, the syntax needed is: smartctl -a /dev/sda -d megaraid,0 the other machines have a "sat+" immediately before the megaraid. These don't, probably because the disks are SAS. Regards, David Mathog ma...@ca... Manager, Sequence Analysis Facility, Biology Division, Caltech |
|
From: Carlos E. R. <rob...@te...> - 2017-06-11 20:20:26
|
On 2017-06-10 20:05, scar wrote: > I'm trying to repair a disk with a bad sector that is waiting to be > re-written. I've run the extended offline test and it reports a bad LBA > at 1872148287. this is the same sector that libata reports in the > system log: ... > I was thinking i would just try "hdparm --write-sector 1872148287 > /dev/sde" instead but wanted to check here first Just a wild guess of mine: run a badblocks read test of the entire disk. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) |
|
From: scar <sc...@dr...> - 2017-06-10 18:25:20
|
I'm trying to repair a disk with a bad sector that is waiting to be
re-written. I've run the extended offline test and it reports a bad LBA
at 1872148287. this is the same sector that libata reports in the
system log:
end_request: I/O error, dev sde, sector 1872148287
At the same time, the system log also reports some I/O errors on logical
blocks:
Buffer I/O error on device sde, logical block 234018535
Buffer I/O error on device sde, logical block 234018536
Buffer I/O error on device sde, logical block 234018537
Buffer I/O error on device sde, logical block 234018538
Buffer I/O error on device sde, logical block 234018539
The errors happen when i start the bitcoin client, so i think it's
related to the large dataset for the blockchain. However i tried
following the BadBlockHowto and the block number i came up with using
the formula was 234018279 for example. However this might not be
significant because all of these blocks are in the same inode anyways,
18095158. When i use "ncheck 18095158" with debugfs on the decrypted
filesystem (/dev/mapper/sde1_crypt) it tells me the file occupying this
inode (and it is not related to bitcoin).
I'm able to copy and calculate the md5sum of this file just fine, and
there aren't any errors in the syslog when i do this. So I guess there
is something different to figure out when the underlying partition is
encrypted. More details:
# fdisk -lu /dev/sde
Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005fd19
Device Boot Start End Blocks Id System
/dev/sde1 2048 1953525167 976761560 83 Linux
#
/dev/sde1 is decrypted to /dev/mapper/sde1_crypt:
# tune2fs -l /dev/mapper/sde1_crypt | grep Block
Block count: 244189878
Block size: 4096
Blocks per group: 32768
#
I was thinking i would just try "hdparm --write-sector 1872148287
/dev/sde" instead but wanted to check here first
Thanks
|
|
From: mathog <ma...@ca...> - 2017-06-05 23:58:31
|
Hi,
smartctl talks happily to disks on several machines with PERC adapaters
here, but one it does not like. megacli says that the adapter on this
Centos 6.9 machine is:
Product Name : PERC H730 Adapter
Serial No : 54N00BK
FW Package Build: 25.2.2-0004
Mfg. Data
================
Mfg. Date : 04/24/15
Rework Date : 04/24/15
Revision No : A01
Battery FRU : N/A
Image Versions in Flash:
================
BIOS Version : 6.18.03.0_4.16.07.00_0x06070400
Ctrl-R Version : 5.03-0010
FW Version : 4.241.00-4163
NVDATA Version : 3.1310.00-0084
Boot Block Version : 3.02.00.00-0000
Pending Images in Flash
================
None
PCI Info
================
Controller Id : 0000
Vendor Id : 1000
Device Id : 005d
SubVendorId : 1028
SubDeviceId : 1f43
Host Interface : PCIE
ChipRevision : C0
Link Speed : 3
Number of Frontend Port: 0
Device Interface : PCIE
Number of Backend Port: 8
However the smartctl which comes with Centos 6.9 will not talk to it:
smartctl -i /dev/sda -d sat+megaraid,0
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-573.22.1.el6.x86_64]
(local build)
Copyright (C) 2002-12 by Bruce Allen,
http://smartmontools.sourceforge.net
Smartctl: Device Read Identity Failed: megasas_cmd result: 0.0 = 0/45
smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
and neither will one just built from scratch:
./smartctl -i /dev/sda -d sat+megaraid,0
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-2.6.32-573.22.1.el6.x86_64]
(local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org
Read Device Identity failed: megasas_cmd result: 0.0 = 0/45
./smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/bus/0 -d megaraid,0 # /dev/bus/0 [megaraid_disk_00], SCSI device
/dev/bus/0 -d megaraid,1 # /dev/bus/0 [megaraid_disk_01], SCSI device
/dev/bus/0 -d megaraid,2 # /dev/bus/0 [megaraid_disk_02], SCSI device
/dev/bus/0 -d megaraid,3 # /dev/bus/0 [megaraid_disk_03], SCSI device
/dev/bus/0 -d megaraid,4 # /dev/bus/0 [megaraid_disk_04], SCSI device
/dev/bus/0 -d megaraid,5 # /dev/bus/0 [megaraid_disk_05], SCSI device
/dev/bus/0 -d megaraid,6 # /dev/bus/0 [megaraid_disk_06], SCSI device
/dev/bus/0 -d megaraid,7 # /dev/bus/0 [megaraid_disk_07], SCSI device
Suggestions?
Thanks,
David Mathog
ma...@ca...
Manager, Sequence Analysis Facility, Biology Division, Caltech
|
|
From: Kees v. d. W. <ke...@to...> - 2017-06-01 13:50:15
|
Hello, On your support-website I found your reaction to my original question, which was handled on https://sourceforge.net/p/smartmontools/mailman/message/35864140/ . Robert S. asked me to send the config file of smartd. Since I'm not sure which file is meant exactly, I found three files that could be involved. I compressed them as txt-files in the attached tar.bz-file. Hope this wil be an efficient reaction for Robert, in order to be able to provide the answer to my problem. I hope I used the right reply-method now, so that my message will be recieved in good order. Greetings, Kees |
|
From: Jeremy Z. <Jer...@va...> - 2017-05-31 17:27:03
|
Hello, I discovered a typo in the smartctl(8) man page from smartmontools-6.5-1.dmg (from https://sourceforge.net/projects/smartmontools/files/smartmontools/6.5/). smartctl(8) man page package version: smartmontools-6.5 2016-05-07 r4318 $Id: smartctl.8.in 4311 2016-04-27 21:03:01Z chrfranke $ Subsection(s): OPTIONS => RUN-TIME BEHAVIOUR OPTIONS: => -d TYPE, --device=TYPE Line(s): "test - prints the guessed type, then opens the device and prints the (possibly changed) TYPE name and then exists without performing any further commands." Issue: The word "exists" should be "exits". Thanks for the detailed documentation, Jeremy Zaretski IT Technician Varsteel Ltd. |
|
From: Robert S <ro...@sp...> - 2017-05-29 04:03:40
|
Since it's smartd issuing the warnings, perhaps posting your config file would help. On 5/27/2017 8:06 AM, Kees van der Wiel wrote: > Hello, > > On my linux-system, s.m.a.r.t. is installed. Since quite a while, I'm > getting a disk-health warning. However, this warning concerns a hdd > that does not exist in my system. I could not find a method for > peventing s.m.a.r.t. to look for this device, in order to stop these > messages. Completely removing and re-installing s.m.a.r.t. did not > solve this "problem" either. Could you please tell me what I can do to > stop these messages from being produced? > Here is the message that I keep recieving: > May 27 14:44:55 kees-MS-7721 smartd[981]: Device: /dev/sdc [SAT], > open() failed: No such device > May 27 14:44:55 kees-MS-7721 smartd[981]: Sending warning via > /usr/share/smartmontools/smartd-runner to root ... > May 27 14:44:55 kees-MS-7721 smartd[981]: Warning via > /usr/share/smartmontools/smartd-runner to root produced unexpected > output (183 bytes) to STDOUT/STDERR: > May 27 14:44:55 kees-MS-7721 smartd[981]: /etc/smartmontools/run.d/10mail: > May 27 14:44:55 kees-MS-7721 smartd[981]: Your system does not have > /usr/bin/mail. Install the mailx or mailutils package > May 27 14:44:55 kees-MS-7721 smartd[981]: run-parts: > /etc/smartmontools/run.d/10mail exited with return code 1 > May 27 14:44:55 kees-MS-7721 smartd[981]: Warning via > /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit > exit status: 256/1) > > Hope to read your reaction, > Kees > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support |
|
From: Kees v. d. W. <ke...@to...> - 2017-05-27 13:24:34
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
On my linux-system, s.m.a.r.t. is installed. Since quite a while,
I'm getting a disk-health warning. However, this warning concerns a
hdd that does not exist in my system. I could not find a method for
peventing s.m.a.r.t. to look for this device, in order to stop these
messages. Completely removing and re-installing s.m.a.r.t. did not
solve this "problem" either. Could you please tell me what I can do
to stop these messages from being produced?<br>
Here is the message that I keep recieving:<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: Device: /dev/sdc [SAT],
open() failed: No such device<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: Sending warning via
/usr/share/smartmontools/smartd-runner to root ...<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: Warning via
/usr/share/smartmontools/smartd-runner to root produced unexpected
output (183 bytes) to STDOUT/STDERR:<br>
May 27 14:44:55 kees-MS-7721 smartd[981]:
/etc/smartmontools/run.d/10mail:<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: Your system does not have
/usr/bin/mail. Install the mailx or mailutils package<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: run-parts:
/etc/smartmontools/run.d/10mail exited with return code 1<br>
May 27 14:44:55 kees-MS-7721 smartd[981]: Warning via
/usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit
exit status: 256/1)<br>
<br>
Hope to read your reaction,<br>
Kees<br>
</body>
</html>
|
|
From: Christian F. <Chr...@t-...> - 2017-05-14 16:07:26
|
Alexander Shaduri wrote: > Sorry for the mistake, the home URL should be: > http://gsmartcontrol.sourceforge.net I added a News entry to smartmontools homepage. Thanks, Christian |
|
From: Alexander S. <ash...@gm...> - 2017-05-11 11:43:49
|
Hi Orsiris, Thanks for testing it, I'm glad you like it. The NVME drive seems to be treated like an SCSI drive by smartctl (that is, the output is somewhat free-form, unlike (S)ATA drives, where the output is "standardized"). Unfortunately, GSmartControl doesn't support such drives (yet), so it doesn't make much sense to detect them. Thanks, Alexander On Thu, 11 May 2017 11:54:04 +0200 Orsiris de Jong wrote: > Hello Alexander, > > > > Congratulations for the new version of your tool, really looks > steamlined :) > > I just ran it on my Win10 x64 with an nvme and an ssd disk. > > > > The NVME disk is detected, but output is limited: > > smartctl 6.5 2016-05-07 r4318 [i686-w64-mingw32-win10(64)] (sf-6.5-1) > > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > > > === START OF INFORMATION SECTION === > Vendor: NVMe > Product: Samsung SSD 950 > Revision: 2B0Q > Compliance: SPC-4 > LU is resource provisioned, LBPRZ=1 > Rotation Rate: Solid State Device > Logical Unit id: YYYYYYYYYYYYYYYYYYYYY 2B0Q > Serial number: XXXXXXXXXXXXXXXXXXX > Device type: disk > Local Time is: Thu May 11 11:34:15 2017 PM > SMART support is: Available - device has SMART capability. > SMART support is: Disabled > Temperature Warning: Disabled or Not Supported > > === START OF READ SMART DATA SECTION === > Request Sense failed, [Input/output error] > Current Drive Temperature: 51 C > Drive Trip Temperature: 80 C > > Error Counter logging not supported > > > [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S > on'] Device does not support Self Test logging > > ------------------------------ > Doing the same with smartctl -a /dev/nvme0 > C:\Program Files\smartmontools\bin>smartctl -a /dev/nvme0 > smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-win10] (sf-6.5-1) > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > === START OF INFORMATION SECTION === > Model Number: Samsung SSD 950 PRO 256GB > Serial Number: XXXXXXXXXXXXXXXXXXX > Firmware Version: 2B0QBXX7 > PCI Vendor/Subsystem ID: 0x144d > IEEE OUI Identifier: 0x002538 > Controller ID: 1 > Number of Namespaces: 1 > Namespace 1 Size/Capacity: 256 060 514 304 [256 GB] > Namespace 1 Utilization: 153 960 095 744 [153 GB] > Namespace 1 Formatted LBA Size: 512 > Local Time is: Thu May 11 11:35:11 2017 PM > Firmware Updates (0x06): 3 Slots > Optional Admin Commands (0x0007): Security Format Frmw_DL > Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero > Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages > > Supported Power States > St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat > 0 + 6.50W - - 0 0 0 0 5 5 > 1 + 5.80W - - 1 1 1 1 30 30 > 2 + 3.60W - - 2 2 2 2 100 100 > 3 - 0.0700W - - 3 3 3 3 500 5000 > 4 - 0.0050W - - 4 4 4 4 2000 22000 > > 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, NSID 0xffffffff) > Critical Warning: 0x00 > Temperature: 51 Celsius > Available Spare: 100% > Available Spare Threshold: 10% > Percentage Used: 0% > Data Units Read: 8 802 764 [4,50 TB] > Data Units Written: 8 100 637 [4,14 TB] > Host Read Commands: 163 470 567 > Host Write Commands: 207 549 906 > Controller Busy Time: 879 > Power Cycles: 1 846 > Power On Hours: 3 551 > Unsafe Shutdowns: 210 > Media and Data Integrity Errors: 0 > Error Information Log Entries: 97 > > Error Information (NVMe Log 0x01, max 64 entries) > Num ErrCount SQId CmdId Status PELoc LBA NSID VS > 0 97 0 0x001d 0x4004 0x000 0 0 - > 1 96 0 0x001c 0x4004 0x000 0 0 - > 2 95 0 0x001d 0x4004 0x000 0 0 - > 3 94 0 0x001c 0x4004 0x000 0 0 - > 4 93 0 0x001d 0x4004 0x000 0 0 - > 5 92 0 0x001c 0x4004 0x000 0 0 - > 6 91 0 0x001f 0x4004 0x000 0 0 - > 7 90 0 0x001e 0x4004 0x000 0 0 - > 8 89 0 0x001f 0x4004 0x000 0 0 - > 9 88 0 0x001e 0x4004 0x000 0 0 - > 10 87 0 0x001d 0x4004 0x000 0 0 - > 11 86 0 0x001c 0x4004 0x000 0 0 - > 12 85 0 0x001d 0x4004 0x000 0 0 - > 13 84 0 0x001c 0x4004 0x000 0 0 - > 14 83 0 0x001d 0x4004 0x000 0 0 - > 15 82 0 0x001c 0x4004 0x000 0 0 - > ... (48 entries not shown) > I've seen that smartctl --scan can't really find nvme devices as of > v6.5. > > Is there a chance to run a pseudo code loop like > > > > for i in {0..15}; do > > smartctl -a /dev/nvme$i > > if [$! == 0]; then device_exists+=$i; fi > > done > > > > This would allow to detect those devices and get nvme output. > > > > Btw, the berlios.de link didn't work for me, had to go to sourceforge. > > > > Best regards, > > > > Orsiris de Jong > > oz...@ne... - http://www.netpower.fr <http://www.netpower.fr> > > Tel: 06 75 40 48 41 |
|
From: Alexander S. <ash...@gm...> - 2017-05-11 11:35:37
|
Sorry for the mistake, the home URL should be: http://gsmartcontrol.sourceforge.net Cheers, Alexander On Thu, 11 May 2017 13:26:18 +0400 Alexander Shaduri wrote: > Hello all, > > It's been a long while since the last release, but here it is: > I just released GSmartControl 0.9.0 (a GUI for smartctl), you may find > it at http://gsmartcontrol.berlios.de . > > Changes include: > > Implemented (untested) support for Linux-based Areca controllers with > enclosures. > Implemented (untested) support for Windows-based Areca controllers > (thanks to Richard Kagerer). > Implemented (untested) support for Linux-based HP controllers with cciss > and hpsa/hpahcisr drivers (thanks to Fabrice Bacchella). > Changes in Preferences no longer fail silently until rescan/restart. > Better drive detection under Windows after removable drives are > detached. Windows version is no longer marked as "dpi aware" since it's > not supported that well. > Drive attribute descriptions have been updated (including clarifications > for SSDs). > Added support for SSD-only and HDD-only vendor attributes. > Devices having only basic info can be displayed now in the info window. > Fixed BDRW drive detection (it was detected as a HDD). > Other minor improvements. > A number of issues have been fixed (including a crash). > > Any help with testing is really appreciated. > > Thanks, > Alexander |
58 messages has been excluded from this view by a project administrator.
