May 9, 201313 yr I recently dealt with a drive failure and decided to take advantage of a good price on 3TB drives at the same time and expand my system a bit. First, I removed the failed 1TB drive. Second, I added a new, pre-cleared 3TB drive. No issues. I let it rebuild parity and everything seems fine. Once that was done I tried to add my other 3TB drive (also pre-cleared). The system won't let me. I don't get any errors. It appears as though nothing happens at all. I can stop the array. Add the drive. Check the "yes I want to do this" box, click <Start>. The screen refreshes and I'm back at the "Stopped. Found 1 new disk(s)." status. Here is the smartctl info for the drive that I can't add: smartctl -a -d ata /dev/sdi (--) smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: TOSHIBA DT01ACA300 Serial Number: Z2U4VZWGS Firmware Version: MX6OABB0 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: Thu May 9 09:56:32 2013 CDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (22939) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 140 140 054 Pre-fail Offline - 69 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 338 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 6 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 1234 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 6 194 Temperature_Celsius 0x0002 157 157 000 Old_age Always - 38 (Min/Max 25/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1224 - 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. I'm attaching my syslog, a screen shot of MyMain showing the preclear status message of the drive that I can't add. I'm running unRAID Server Pro version: 5.0-rc8a. All of my system info is in my sig also. Any tips or things I should/could check would be appreciated. Thanks, Whip syslog-2013-05-08.zip
May 9, 201313 yr Author Attach a syslog. Isn't that what I attached? I mean, it's the file under /var/log/syslog - I just compressed it into a zip.
May 9, 201313 yr I recently dealt with a drive failure and decided to take advantage of a good price on 3TB drives at the same time and expand my system a bit. First, I removed the failed 1TB drive. Second, I added a new, pre-cleared 3TB drive. No issues. I let it rebuild parity and everything seems fine. Once that was done I tried to add my other 3TB drive. The system won't let me. I don't get any errors. It appears as though nothing happens at all. I can stop the array. Add the drive. Check the "yes I want to do this" box, click <Start>. The screen refreshes and I'm back at the "Stopped. Found 1 new disk(s)." status. Here is the smartctl info: smartctl -a -d ata /dev/sdi (--) smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: TOSHIBA DT01ACA300 Serial Number: Z2U4VZWGS Firmware Version: MX6OABB0 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: Thu May 9 09:56:32 2013 CDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (22939) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 140 140 054 Pre-fail Offline - 69 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 338 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 6 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 1234 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 6 194 Temperature_Celsius 0x0002 157 157 000 Old_age Always - 38 (Min/Max 25/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1224 - 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. I'm attaching my syslog, a screen shot of MyMain showing the preclear status message. I'm running unRAID Server Pro version: 5.0-rc8a. All of my system info is in my sig also. Any tips or things I should/could check would be appreciated. Thanks, Whip Is your other drive precleared? If not I've seen reports of a bug where 5.0RC's are not automatically clearing the drive when added to an array with a parity disk. The work around is to preclear the disk and then add it. This assumes that is even close to your problem of course. And yes I see that you said the first drive was precleared but I didn't read anything about the second.
May 9, 201313 yr Yes, sorry, the 2nd drive is also pre-cleared. I'll fix the original post. I'm out of ideas - sorry.
May 9, 201313 yr As noted, there's an issue with adding drives unless they're pre-cleared, but that's not the case here. You need to send a note to Tom about this, to be sure he's aware of the problem. However, the FIRST thing I'd do is update to RC12a. Do that; run a parity check; and THEN try to add your new Pre-cleared drive.
May 9, 201313 yr Author As noted, there's an issue with adding drives unless they're pre-cleared, but that's not the case here. You need to send a note to Tom about this, to be sure he's aware of the problem. However, the FIRST thing I'd do is update to RC12a. Do that; run a parity check; and THEN try to add your new Pre-cleared drive. I had considered updating, but thought I'd run it by here first. I'll update and try again. Thanks, Whip
May 10, 201313 yr As noted, there's an issue with adding drives unless they're pre-cleared, but that's not the case here. You need to send a note to Tom about this, to be sure he's aware of the problem. However, the FIRST thing I'd do is update to RC12a. Do that; run a parity check; and THEN try to add your new Pre-cleared drive. I had considered updating, but thought I'd run it by here first. I'll update and try again. Thanks, Whip Good plan. Two reasons to do the update: (a) It just may resolve the issue; and (b) if you sent Tom a note on this, the first thing he'd want you to do is update and try again [i agree with that -- no need to troubleshoot an issue until it's confirmed that it's a problem with the current release !]
May 11, 201313 yr Author Ok, updated to rc12. Precleared the drive again (just in case). Still can't add it. I'm attaching my syslog. How do I send Tom a note about this? Thanks, Whip syslog-2013-05-11.zip
May 11, 201313 yr How do I send Tom a note about this? Point to "Members" at the top of this page, then click on "Search for Members" Enter "Limetech" in the search box -- you'll get several matches, but the first one is what you want. Click on the username (limetech); then click on Send PM ... you don't need to fill in the "To" section; but do add a Subject and a brief description of your issue. I'd make it a very brief note, with a link to this thread.
May 11, 201313 yr Post a note back when it's resolved and let us know just what was wrong. ... always nice to know the details ==> you never know when someone else may have the same problem.
May 14, 201313 yr Thanks. Several other folks said the same thing; so that's clearly not the cause of the issue.
Archived
This topic is now archived and is closed to further replies.