July 25, 201114 yr Just finished my unRAID build on Thursday. Installed 5 x 2TB drives. Precleared them all with no errors that I could see. I set it up as mentioned here: http://www.mediasmartserver.net/2011/05/20/guide-unraid-server-part-3-configuring-and-using-unraid/ I haven't set the 5th drive as parity yet until I've copied most of my files over. Set up a share called Media/Movies and started adding movies. I added about 1TB worth all films begining with the letter 'A'. The server only used disk1 for the 1TB worth. I then started on 'B' and the server starting using disk2. For some reason after 8 films when it gets to 'Bad Boys 1995' it only copies some of it then I get an error on my MacBook Pro (error code -51) and it stops. If I check the server via the browser the temperature is reading 0 for disk2 and it has a lot of errors. Here is the syslog, apologies for the length, it crashed last night just before I went to sleep and I captured the log this morning: Thanks syslog.zip
July 25, 201114 yr Author Having browsing these forums today I did a SMART report on the problematic drive. There are some errors on there. Could someone confirm for me that it's the drive and what my next steps should be? Will everything on disk1 be OK (complete)? Install another disk2 and copy to the array everything that was on disk2? I've noticed a few people recommending having a parity disk assigned from the start (I was going to copy over 8TB before starting parity for speed reasons), should I? If I have to how do I go about moving disks 3 and 4 to disks 2 and 3? smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST32000542AS Serial Number: 5XW0MJ4Q Firmware Version: CC34 User Capacity: 2,000,398,934,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: Mon Jul 25 10:32:28 2011 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 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: ( 633) 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: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table 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 105 092 006 Pre-fail Always - 242659823 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2869 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 92 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 4297058382 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5796 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 35 183 Runtime_Bad_Block 0x0032 087 087 000 Old_age Always - 13 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 131 188 Command_Timeout 0x0032 093 093 000 Old_age Always - 55835623441 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 065 056 045 Old_age Always - 35 (Lifetime Min/Max 27/39) 194 Temperature_Celsius 0x0022 035 044 000 Old_age Always - 35 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 048 030 000 Old_age Always - 242659823 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 24245090389109 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2264107572 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 4039086743 SMART Error Log Version: 1 ATA Error Count: 132 (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 132 occurred at disk power-on lifetime: 5768 hours (240 days + 8 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 51 00 ff ff ff 0f 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 ff ff ff 4f 00 1d+11:06:59.855 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 1d+11:06:59.855 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+11:06:59.844 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+11:06:59.844 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+11:06:59.844 READ NATIVE MAX ADDRESS EXT Error 131 occurred at disk power-on lifetime: 5768 hours (240 days + 8 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 51 00 ff ff ff 0f 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 ff ff ff 4f 00 1d+11:06:55.913 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 1d+11:06:55.913 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 1d+11:06:55.913 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+11:06:55.902 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+11:06:55.902 SET FEATURES [set transfer mode] Error 130 occurred at disk power-on lifetime: 5768 hours (240 days + 8 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 51 00 ff ff ff 0f 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 00 ff ff ff 4f 00 1d+11:06:52.053 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 1d+11:06:52.052 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+11:06:52.042 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+11:06:52.041 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+11:06:52.041 READ NATIVE MAX ADDRESS EXT Error 129 occurred at disk power-on lifetime: 5768 hours (240 days + 8 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 51 00 ff ff ff 0f 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 00 ff ff ff 4f 00 1d+11:06:48.232 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 1d+11:06:48.232 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+11:06:48.221 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+11:06:48.221 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+11:06:48.221 READ NATIVE MAX ADDRESS EXT Error 128 occurred at disk power-on lifetime: 5768 hours (240 days + 8 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 51 00 ff ff ff 0f 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 00 ff ff ff 4f 00 1d+11:06:44.250 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 1d+11:06:44.250 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+11:06:44.239 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+11:06:44.239 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+11:06:44.239 READ NATIVE MAX ADDRESS EXT 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.
July 25, 201114 yr The smart report shows some issues with drive2. How many times did you preclear the drives. I recommend and do three preclears on all my drives. Your other data should be fine, though I would assign the parity drive from the start. I am a fan of the slower but safer method.
July 25, 201114 yr Author Thanks for the reply. I ran the preclear once on each drive. What is the advantage of doing it more than once, to stress test them? To get it right would you recommend starting again? I was in a rush to move all my data but after this issue I'm not. I might preclear two more times and assign the parity drive at the start.
July 25, 201114 yr Thanks for the reply. Not a problem I ran the preclear once on each drive. What is the advantage of doing it more than once, to stress test them? Yes, it will stress test the drive, and hopefully find out if a drive is going to fail prematurely. Drive 2 might have cleared fine but it appears that there are more issues with it even after one successful preclear. To get it right would you recommend starting again? I was in a rush to move all my data but after this issue I'm not. Probably would not hurt. As I said I preclear all my drives 3 times and any drive that is sold with the servers I build are preclear'ed 3 times. Then most drives go through 2-3 parity check/verify steps, and finally they have data written to them over the LAN to test that. Takes me almost 2 weeks to do all of that. Better safe than sorry I might preclear two more times and assign the parity drive at the start. I would preclear all drives at least 1 more time, probably 2, and then start from the beginning if you can.
July 25, 201114 yr Author Thanks I will start again tonight. Is it better to preclear one at a time (3 times) then move on or just set them all off preclearing and repeat. It took about 30+ hours to preclear 5 x 2TB drives once.
July 25, 201114 yr Thanks I will start again tonight. Is it better to preclear one at a time (3 times) then move on or just set them all off preclearing and repeat. It took about 30+ hours to preclear 5 x 2TB drives once. All at once should work just fine. I was recently preclearing 11ish drives at the same time on a system I am putting together right now. This is a system with 4GB of RAM so that may have allowed me to cleat that many at once.
July 25, 201114 yr Author I noticed before if I try to remove disk 2 and put 3 as 2 and 4 as 3 it just says they are all in the wrong place and the correct disk2 is missing. Will the server notice I have precleared again them and ignore their old assignments?
July 25, 201114 yr if you are running 4.7 you will have to run initconfig from the command line. If you are on 5.0bX there is a "button" called "New Config" that does the same thing. You will have to run either of those before assigning disks to the array when you restart your build.
Archived
This topic is now archived and is closed to further replies.