Stealth
Jun 22, 2013, 10:01:02 AM6/22/13
to
Hello all,
I'm trying to put a new second dirve in my DNS 323 Alt-f RC3, but I see some very strange things
For beginning my HDD seem works perfectly I copied 1.1 TO without problem and fast
1) smartd seem doesn’t works good, all test fail
I'm trying to put a new second dirve in my DNS 323 Alt-f RC3, but I see some very strange things
For beginning my HDD seem works perfectly I copied 1.1 TO without problem and fast
1) smartd seem doesn’t works good, all test fail
# 1 Extended offline Completed: read failure 90% 86 126885792 # 2 Extended offline Aborted by host 90% 71 - # 3 Extended offline Completed: read failure 90% 48 126879080
2) When I restart my NAS I always receive two messages about the new HDD
host name: DNS-323 DNS domain: localnet NIS domain: (none) The following warning/error was logged by the smartd daemon: Device: /dev/sdb [SAT], 1456 Currently unreadable (pending) sectors
And
host name: DNS-323 DNS domain: localnet NIS domain: (none) The following warning/error was logged by the smartd daemon: Device: /dev/sdb [SAT], 1456 Offline uncorrectable sectors Device info: ST2000DM001-1CH164, S/N:Z1E4ADAE, WWN:5-000c50-050ab6e96, FW:CC27, 2.00 TB
Smart repport:
=== START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST2000DM001-1CH164 Serial Number: Z1E4ADAE LU WWN Device Id: 5 000c50 050ab6e96 Firmware Version: CC27 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm 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: 3.0 Gb/s) Local Time is: Sat Jun 22 15:51:50 2013 CEST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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 114 100 006 Pre-fail Always - 59249160 3 Spin_Up_Time 0x0003 098 096 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 408 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 578363 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 92 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 6 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 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 064 060 045 Old_age Always - 36 (Min/Max 1/40) 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 - 5 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 484 194 Temperature_Celsius 0x0022 036 040 000 Old_age Always - 36 (128 0 0 0 0) 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 1456 198 Offline_Uncorrectable 0x0010 092 092 000 Old_age Offline - 1456 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 34h+40m+35.445s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2151974200 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1075706 SMART Error Log Version: 1 No Errors Logged
It's like my disk is bad (why not, but it works good) or there is a problem about smart, this disk replace another maybe smartd
still with old HDD configuration ?
Thanks
João Cardoso
Jun 22, 2013, 3:43:18 PM6/22/13
to al...@googlegroups.com
On Saturday, June 22, 2013 2:58:44 PM UTC+1, Stealth wrote:
Hello all,
I'm trying to put a new second dirve in my DNS 323 Alt-f RC3, but I see some very strange things
For beginning my HDD seem works perfectly I copied 1.1 TO without problem and fast
1) smartd seem doesn’t works good, all test fail# 1 Extended offline Completed: read failure 90% 86 126885792 # 2 Extended offline Aborted by host 90% 71 - # 3 Extended offline Completed: read failure 90% 48 126879080
...
The following warning/error was logged by the smartd daemon: Device: /dev/sdb [SAT], 1456 Offline uncorrectable sectors Device info: ST2000DM001-1CH164, S/N:Z1E4ADAE, WWN:5-000c50-050ab6e96, FW:CC27, 2.00 TB
Smart repport:
=== START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST2000DM001-1CH164 Serial Number: Z1E4ADAE LU WWN Device Id: 5 000c50 050ab6e96 Firmware Version: CC27 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm 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: 3.0 Gb/s) Local Time is: Sat Jun 22 15:51:50 2013 CEST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en
Have you followed these links?
...
197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 1456 198 Offline_Uncorrectable 0x0010 092 092 000 Old_age Offline - 1456
At this time you might have already searched for that.
Your friend, the wikipedia http://en.wikipedia.org/wiki/S.M.A.R.T., tells you about those itens that 1456 sector read errors occured (1456 * 512 bytes = 750KB) and are waiting for an unsucesseful write for being remaped with good sectors (but you might not be able to read the files they referred to, if any).
1456 sectors is not that a big number, as the drive has a total of 3907029168 sectors... but keep an eye on that number (parameter 198) and if it continues growing return the drive.
Those bad sectors might or might not refer to actual files, I don't know if they are the result of the smart test itself or from a user trying to access files.
If they come from real files, to force a remap try reading all files from the box (do a dummy box backup, e.g.); if they are from the smart test itself, you can only force the remap filling the drive with data (I suspect that the read errors come from the smart test itself, so only when you, as a user, will try to use those sectors they will be remaped)
I don't know what is the typical values that manufactures reserve for remapping, search for that to know if you are still away from that limit; currently the drive as no reallocated sectors (see item 5 from the report, Reallocated_Sector_Ct)
...
Stealth
Jun 23, 2013, 2:53:39 PM6/23/13
to
It's a very recent release (04/2013) the firmware is CC27 I can't upgrade now
I tried with the disk umount (also no swap) without success, although the short test works
Seem sometimes the drive spindow without any reason, for example today when I 'm writing a file the HDD spindow a short moment ( with power sav disabled and 10 minutes to spindow, but need more test to be sure )
I think maybe I should try a long smart test with my computer, to be sure
João Cardoso
Jun 23, 2013, 6:22:52 PM6/23/13
to
On Sunday, June 23, 2013 9:54:12 AM UTC+1, Stealth wrote:
It's a very recent release (04/2013) the firmware is CC27 I can't upgrade now
I tried with the disk umount (also no swap) without success, although the short test works
SMART tests are performed internally to the drive, not by the operation system or any of its programs, so you can continue using the drive for normal data access (but other SMART commands issued to the drive can terminate the ones currently being executed).
Seem sometimes the drive spindow without any reason, for example today when I 'm writing a file the HDD spindow a short moment ( with power sav disabled and 10 minutes to spindow, but need more test to be sure )
Not related.
I think maybe I should try a long smart test with my computer, to be sure
Should make no difference, but you can try.
As I said above, SMART commands are sent to the drive, like normal data read or write commands, it is up to the drive to execute them and store the results internally -- you later see that stored results.
Regarding the initial issue: as the drive is new, it is "normal" for it to be still recording its bad sectors (although that should be done at the factory...)
You could exercise all its sectors by performing a 'dd if=/dev/sda of=/dev/null bs=10M' command, that tries to read *all* its sectors, even those not yet written (it will take ages, 40MB/s, and might fail for some sectors), then record the relevant SMART parameters and later, say a week, see if their values increases -- that would be bad.
Quoting:
S.M.A.R.T. (...) is a monitoring system for computer hard disk drives to detect and report on various indicators of reliability, in the hope of anticipating failures.
...
Each drive manufacturer defines a set of attributes, and sets threshold values beyond which attributes should not pass under normal operation. Each attribute has a raw value, whose meaning is entirely up to the drive manufacturer (but often corresponds to counts or a physical unit, such as degrees Celsius or seconds), a normalized value, which ranges from 1 to 253 (with 1 representing the worst case and 253 representing the best) and a worst value, which represents the lowest recorded normalized value. Depending on the manufacturer, a value of 100 or 200 will often be chosen as the initial normalized value.
...
 | Higher raw value is better |
|---|---|
 | Lower raw value is better |
| Critical: pink colored row | Potential indicators of imminent electromechanical failure |
| 05 | 0x05 | Reallocated Sectors Count | | Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as "reallocated" and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called "remaps". The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[2] While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. If sequential access speed is critical, the remapped sectors can be manually marked as bad blocks in the file system in order to prevent their use. |
| 197 | 0xC5 | Current Pending Sector Count | | Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, this value is decreased and the sector is not remapped. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written.[27] However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors. |
| 198 | 0xC6 | Uncorrectable Sector Countor Offline Uncorrectableor Off-Line Scan Uncorrectable Sector Count[21] | | The total count of uncorrectable errors when reading/writing a sector. A rise in the value of this attribute indicates defects of the disk surface and/or problems in the mechanical subsystem. |
Stealth
Jun 24, 2013, 3:20:10 AM6/24/13
to al...@googlegroups.com
Thanks for your help, and very good explanations, I'm trying DD now
How can we explain that I receive this mail only at each reboot ? Never also ?
How can we explain that I receive this mail only at each reboot ? Never also ?
Stealth
Jun 24, 2013, 4:36:50 AM6/24/13
to
While the DD I have a some
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 09:53:03 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: EH complete
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000003, dev error, EDMA self-disable
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: cmd 60/00:00:50:1f:90/01:00:07:00:00/40 tag 0 ncq 131072 in
Jun 24 09:53:03 DNS-323 user.err kernel: res 41/40:00:a0:1f:90/00:01:07:00:00/00 Emask 0x409 (media error) <F>
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 09:53:03 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Unhandled sense code
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Jun 24 09:53:03 DNS-323 user.warn kernel: Descriptor sense data with sense descriptors (in hex):
Jun 24 09:53:03 DNS-323 user.info kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jun 24 09:53:03 DNS-323 user.info kernel: 07 90 1f a0
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 07 90 1f
Seem close, here http://comments.gmane.org/gmane.linux.utilities.smartmontools/6821
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 09:53:03 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: EH complete
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000003, dev error, EDMA self-disable
Jun 24 09:53:03 DNS-323 user.err kernel: ata2.00: cmd 60/00:00:50:1f:90/01:00:07:00:00/40 tag 0 ncq 131072 in
Jun 24 09:53:03 DNS-323 user.err kernel: res 41/40:00:a0:1f:90/00:01:07:00:00/00 Emask 0x409 (media error) <F>
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 09:53:03 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 09:53:03 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Unhandled sense code
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Jun 24 09:53:03 DNS-323 user.warn kernel: Descriptor sense data with sense descriptors (in hex):
Jun 24 09:53:03 DNS-323 user.info kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jun 24 09:53:03 DNS-323 user.info kernel: 07 90 1f a0
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
Jun 24 09:53:03 DNS-323 user.info kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 07 90 1f
Seem close, here http://comments.gmane.org/gmane.linux.utilities.smartmontools/6821
Stealth
Jun 24, 2013, 6:18:24 AM6/24/13
to
I retried
Jun 24 11:51:30 DNS-323 daemon.info sysctrl: temp=41.5 fan=0
Jun 24 11:52:00 DNS-323 daemon.info sysctrl: temp=41.8 fan=0
Jun 24 11:52:31 DNS-323 daemon.info sysctrl: temp=42.1 fan=0
Jun 24 11:53:01 DNS-323 daemon.info sysctrl: temp=42.8 fan=0
Jun 24 11:53:31 DNS-323 daemon.info sysctrl: temp=43.4 fan=0
Jun 24 11:54:01 DNS-323 daemon.info sysctrl: temp=44.0 fan=0
Jun 24 11:54:31 DNS-323 daemon.info sysctrl: temp=44.5 fan=400
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:08 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:08 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:09 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:09 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:09 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:12 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:12 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:13 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:13 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:13 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:16 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:16 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:17 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:17 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:17 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:20 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:20 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:21 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:21 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:21 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:25 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:25 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:25 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:25 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
There are some links about this kind of messages, like
Jun 24 11:51:30 DNS-323 daemon.info sysctrl: temp=41.5 fan=0
Jun 24 11:52:00 DNS-323 daemon.info sysctrl: temp=41.8 fan=0
Jun 24 11:52:31 DNS-323 daemon.info sysctrl: temp=42.1 fan=0
Jun 24 11:53:01 DNS-323 daemon.info sysctrl: temp=42.8 fan=0
Jun 24 11:53:31 DNS-323 daemon.info sysctrl: temp=43.4 fan=0
Jun 24 11:54:01 DNS-323 daemon.info sysctrl: temp=44.0 fan=0
Jun 24 11:54:31 DNS-323 daemon.info sysctrl: temp=44.5 fan=400
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:08 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:08 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:08 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:09 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:09 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:09 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:12 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:12 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:12 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:13 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:13 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:13 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:16 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:16 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:16 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:17 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:17 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:17 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:20 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:20 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:20 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:21 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:21 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
Jun 24 11:55:21 DNS-323 user.info kernel: ata2: EH complete
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jun 24 11:55:25 DNS-323 user.err kernel: ata2.00: cmd c8/00:00:c8:6d:90/00:00:00:00:00/e7 tag 0 dma 131072 in
Jun 24 11:55:25 DNS-323 user.err kernel: res 51/40:00:48:6e:90/00:00:00:00:00/07 Emask 0x9 (media error)
Jun 24 11:55:25 DNS-323 user.info kernel: ata2: hard resetting link
Jun 24 11:55:25 DNS-323 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 24 11:55:25 DNS-323 user.info kernel: ata2.00: configured for UDMA/133
There are some links about this kind of messages, like
I was able to completely eliminate this issue by 1. disabling NCQ -> (Fred) I tried without success 2. limiting the speed of SATA to 1.5GB I have done so by modifying my /boot/grub/grub.conf and adding libata.force=noncq,1.5G
How I can try that with alt-f ?
João Cardoso
Jun 24, 2013, 11:12:44 AM6/24/13
to al...@googlegroups.com
You can't.
While on a PC the linux kernel is started by the grub or lilo bootloaders, that reside on disk and thus have adjustable parameters that can be supplied to the kernel command line (the 'libata.force=noncq,1.5G'), in our box the kernel is started by the u-boot bootloader, that resides on flash and has no adjustable parameter.
Our only hypothesis is to change that after power on, as in
echo 1 > /sys/block/sda/device/queue_depthreplace sda with the correct device name. https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Disabling NCQ might have performance impact.
The post you mention above refers to a possible firmware issue that might be solved by a disk firmware upgrade (on a PC, not on the box); the smart program already reported something similar.
Other posts reports possible conflicts with the drive going to spin-down, try disabling spindown also (one at a time, or you wouldn't know which one is the culprit, if any)
Does the 05/197/198 attribute values of the smart report show any change after the 'dd' test? Please verify it.
FredB
Jun 24, 2013, 11:54:44 AM6/24/13
to
>
> Our only hypothesis is to change that after power on, as in
>
>
> echo 1 > /sys/ block / sda / device / queue_depth
> replace sda with the correct device name.
> https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
>
> Does that solves the issue? If it does one can try to perform that
> automatically using the 'boot user script'
>
>
> Disabling NCQ might have performance impact.
> The post you mention above refers to a possible firmware issue that
> might be solved by a disk firmware upgrade (on a PC, not on the
> box); the smart program already reported something similar.
>
> Other posts reports possible conflicts with the drive going to
> spin-down, try disabling spindown also (one at a time, or you
> wouldn't know which one is the culprit, if any)
>
>
> Does the 05/197/198 attribute values of the smart report show any
> change after the 'dd' test? Please verify it.
>
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
197 Current_Pending_Sector 0x0012 088 088 000 Old_age Always - 2080 -> goes to 2088 but seem slowly reduce now ...
198 Offline_Uncorrectable 0x0010 088 088 000 Old_age Offline - 2080
Today I synchronised 500 Go, between sda (read) and sdb (write - the "bad" disk -), without problem and no error log, but the reboot email error still present without any exception, each time for 5 reboots
fsck.ext4 with bad block report nothing, I will try smartd tonight with a computer, I saw what you wrote before and I agree but it's just to check sata hardware and maybe a problem with kernel version.
The test should be fast because DNS 323 return directly - Completed: read failure.
Thank again
EDIT:
Now
Device: /dev/sdb [SAT], 2072 Offline uncorrectable sectors
Stealth
Jun 24, 2013, 11:47:02 AM6/24/13
to al...@googlegroups.com
Only while the DD, nothing with rsync
Stealth
Jun 24, 2013, 2:50:50 PM6/24/13
to
With Ubuntu I cleared the HDD and recreated partitions, the values seem better now
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
197 Current_Pending_Sector 0x0012 100 080 000 Old_age Always - 128
198 Offline_Uncorrectable 0x0010 100 080 000 Old_age Offline - 128
And I can make a long test I'm waiting the result now
1 Extended offline Self-test routine in progress 90% 143 -
I found something, the HDD need to be mounted for the smartcl test
Tomorrow I will retry with the DNS 323
I'm a little worried it seem very unstable ...
-------------------------------------------------
hdparm on ubuntu (to compare with dns 323 tomorrow)
/dev/sdb:
ATA device, with non-removable media
Model Number: ST2000DM001-1CH164
Serial Number: ZXXXXX
Firmware Revision: CC27
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x001f)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 3907029168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 1907729 MBytes
device size with M = 1000*1000: 2000398 MBytes (2000 GB)
cache/buffer size = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 254
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* unknown 76[15]
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
214min for SECURITY ERASE UNIT. 214min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c50050ab6e96
NAA : 5
IEEE OUI : 000c50
Unique ID : 050ab6e96
Checksum: correct
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
198 Offline_Uncorrectable 0x0010 100 080 000 Old_age Offline - 128
And I can make a long test I'm waiting the result now
1 Extended offline Self-test routine in progress 90% 143 -
I found something, the HDD need to be mounted for the smartcl test
Tomorrow I will retry with the DNS 323
I'm a little worried it seem very unstable ...
-------------------------------------------------
hdparm on ubuntu (to compare with dns 323 tomorrow)
/dev/sdb:
ATA device, with non-removable media
Model Number: ST2000DM001-1CH164
Serial Number: ZXXXXX
Firmware Revision: CC27
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x001f)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 3907029168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 1907729 MBytes
device size with M = 1000*1000: 2000398 MBytes (2000 GB)
cache/buffer size = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 254
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* unknown 76[15]
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
214min for SECURITY ERASE UNIT. 214min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c50050ab6e96
NAA : 5
IEEE OUI : 000c50
Unique ID : 050ab6e96
Checksum: correct
Stealth
Jun 25, 2013, 6:13:01 AM6/25/13
to al...@googlegroups.com
The values changes, sometime more, sometime less
I can't trust, I will replace
Thank for your help
I can't trust, I will replace
Thank for your help
Reply all
Reply to author
Forward
0 new messages