December 15, 201015 yr Hi, I'm starting to think that there is a bug in 4.6 for upgrading a disk. I want to upgrade a disc (from 1 Tb -> 2Tb), and both times something seems wrong. Just before rebuilding, the new disk has a blu dot, while rebuilding, the disk has a red dot? The wiki says it should be a yellow dot. The first time I wanted to replace the disk, I used the same controller/port as the original 1Tb disk (samsung HD103UI) . The disk was rebuild, and after rebuilding I still got a red dot. OK, bad disk/controller port, this can happen (I did preclear this drive though), so I bought a new disc, a new sata cable and a new controller (old controller = promise SATA300 TX4, new controller = SIL 3132). But now the same thing is happening! A blu dot just before the rebuild (so the disk is recognized by unraid), but immediatly after it starts rebuilding it gets red? Strange thing is, unraid does not give write errors (see attachment). This drive is, like I said, new, but I didn't preclear it (I know, I know...). Its a WD EARS that is jumpered (Previous 'bad' drive was also a jumpered EARS). Do I have 2 bad disks, or is this an unraid bug? Some help please PS: here is the smartctl for the 'bad' drive that is being reconstructed (reonstructiong is still going): root@Media_Tower:~# smartctl --all /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA2469282 Firmware Version: 51.0AB51 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: Exact ATA specification draft version not indicated Local Time is: Wed Dec 15 07:58:48 2010 CET 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. 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: (36960) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1291 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 14 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 22 194 Temperature_Celsius 0x0022 129 119 000 Old_age Always - 21 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 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. root@Media_Tower:~#
December 15, 201015 yr Author here is the syslog... sdm is the 1Tb drive I want to upgrade. Still has all its data sda is another new 2Tb drive on the new SIL controller (thatswhy it has no valid partition table) Both drives are outside the array (for now). The plan was to preclear and add them to the array when the upgrade of the disk is complete. syslog.txt
December 15, 201015 yr I'd say it might be a error in the wiki. I'd expect a "red" indicator as a drive is being re-constructed. (been a long time since I tried, but I've never seen a "yellow" indicator.) Edit: I did a search in the emhttp program for "yellow" and there is a yellow indicator image. (I just did not remember seeing it) Joe L.
December 17, 201015 yr Author An update, It was a bad HD with my first attempt, now everything is OK. I was able to add the second drive to the array.
Archived
This topic is now archived and is closed to further replies.