March 25, 201313 yr Hi, I just added a new 3TB Seagate HDD to my 9TB existing unraid system. After a week, I upgraded to RC12a on Saturday evening to try fix and "transport endpoint error". This morning I noticed that the new HDD was booted out of the unraid system. I did two preclears on the new HDD got during thanksgiving sale of 2012. The first was a 4 pass and the second was a 2 pass (see below) and didn't show up any errors. I saw a bunch of disk write errors (have about 250 GB of data currently on the disk), log copied below. What I am not sure is whether this is the HDD problem or something unrelated .. RC12, SATA cables, connectors, etc? I have a replacement 3TB WDCRed that is going through preclear .. Had to stop preclear multiple times due to "transport endpoint error". If I stopped the preclear after few cycles, is there a way for me to check the partial preclear reports? I have the array stopped to reduce any load cycles until I fix this issue. Thanks for the help and suggestions! Output from preclear: =============== ============================================================================ == == S.M.A.R.T Final Report for /dev/sdc == Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN168 Serial Number: Z1F0Y3XY Firmware Version: CC4B User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Wed Jan 2 03:06:22 2013 EST 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 General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. 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 117 099 006 Pre-fail Always - 161655800 3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 251738 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 108 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 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 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 072 045 Old_age Always - 27 (Min/Max 19/28) 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 - 3 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 22 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 19 0 0) 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 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 200312979718251 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 982338821226 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 595721622793 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. == ============================================================================ =============== Error from Syslog this morning after adding it to the unraid: ====== > pwd /var/log > grep disk8 syslog.1 Mar 24 12:57:51 Tower kernel: md: import disk8: [8,80] (sdf) ST3000DM001-9YN168_Z1F0Y3XY size: 2930266532 Mar 24 12:57:57 Tower emhttp: shcmd (48): mkdir /mnt/disk8 Mar 24 12:57:57 Tower emhttp: shcmd (49): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md8 /mnt/disk8 |& logger Mar 24 12:57:57 Tower emhttp: shcmd (50): chmod 777 '/mnt/disk8' Mar 24 12:57:57 Tower emhttp: shcmd (51): chown nobody:users '/mnt/disk8' Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321032 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321040 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321048 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321056 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321064 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321072 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321080 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321088 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321096 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321104 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321112 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321120 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321128 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321136 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321144 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321152 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321160 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321168 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321176 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321184 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321192 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321200 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321208 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321216 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321224 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321232 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321240 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321248 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321256 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321264 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321272 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321280 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321288 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321296 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321304 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321312 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321320 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321328 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321336 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321344 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321352 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321360 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321368 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321376 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321384 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321392 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321400 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321408 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321416 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321424 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321432 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321440 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321448 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321456 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321464 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321472 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321480 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321488 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321496 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321504 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321512 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321520 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321528 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321536 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321544 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321552 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321560 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321568 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321576 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321584 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321592 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321600 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321608 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321616 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321624 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321632 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321640 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321648 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321656 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321664 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321672 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321680 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321688 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321696 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321704 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321712 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321720 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321728 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321736 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321744 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321752 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321760 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321768 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321776 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321784 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321792 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321800 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321808 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321816 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321824 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321832 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321840 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321848 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321856 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321864 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321872 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321880 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321888 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321896 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321904 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321912 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321920 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321928 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321936 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321944 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321952 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321960 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321968 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321976 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321984 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=321992 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322000 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322008 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322016 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322024 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322032 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322040 Mar 25 03:42:52 Tower kernel: md: disk8 write error, sector=322048 ===========
March 25, 201313 yr We have no idea either... You did not attach a syslog showing the failure, (an excerpt is usually not enough and since you only included lines with disk8 in their content, most of the information needed is completely missing.) You included a SMART report from before the failure, and no current SMART report. It could be as simple as a loose cable, or it might be a defective disk, or a bad power supply splitter, or a bad drive tray. Your next step should be to get a current smart report and attach a full (possibly zipped) syslog. Joe L.
March 25, 201313 yr Author Joe - Thanks. The smart report is from the unmenu "run long test"? Did you want me to attach the entire syslog? There are two files, syslog and syslog.1. Is there a specific section you are looking for so that I can remove the details which point to personal details on the server? P.S. Is there a way I can get the preclear reports from the completed cycles? For eg if the first 3 preclear cycles are done and I had to interrupt the 4th, the report from 3 cycles should still be there ..
March 25, 201313 yr Did you want me to attach the entire syslog? There are two files, syslog and syslog.1. Is there a specific section you are looking for so that I can remove the details which point to personal details on the server? CTRL+H and regex. P.S. Is there a way I can get the preclear reports from the completed cycles? For eg if the first 3 preclear cycles are done and I had to interrupt the 4th, the report from 3 cycles should still be there .. /tmp/smart_.*
March 26, 201313 yr There is no way of knowing which part of the syslog is relevant. Aside from file names listed by the mover, the log should not contain any personal info. None of the contents can be used to exploit your system. The GUID key is useless without the physical USB device. The MAC address is not useful and the IP address is from the same pool of private addresses that everyone else in the world is using. If your using a public address then you are already being attacked and I hope you've secured the system. What personal info concerns you?
March 26, 201313 yr There is no way of knowing which part of the syslog is relevant. Aside from file names listed by the mover, the log should not contain any personal info. None of the contents can be used to exploit your system. The GUID key is useless without the physical USB device. The MAC address is not useful and the IP address is from the same pool of private addresses that everyone else in the world is using. If your using a public address then you are already being attacked and I hope you've secured the system. What personal info concerns you? Transmission just loves to dump unimportant bullshit to the system log, mainly including all your torrents every 5 minutes, which, may or may not be private. I believe Sab likes to do the same when a download fails, etc...
Archived
This topic is now archived and is closed to further replies.