March 19, 201511 yr So, my 9 month old was standing next to my server, and then I noticed he was pulling on of the the taps from my Norco SS-500. Well, he took the hard drive out. I went ahead and stopped the array, turned the server off, and re-inserted the drive. I turned on the server again, and the WebGui shows all the drives with green balls. Well, today, I noticed that my drive # 3 has a red ball DISK_DSBL. I've tried to run a smart report, but I get the following error: Smart Long Test of /dev/sdd could take several hours or more. You must disable disk spin-down during this test, otherwise it will abort when the disk is spun down. smartctl -t long -d ata /dev/sdd 2>&1 smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org SMART Disabled. Use option -s with argument 'on' to enable it. (override with '-T permissive' option) I've checked the power cables and the data cable, and they were both connected fine. I want to run a smart report, but I am not sure what the above comment means? Thanks for any assistance. syslog-2015-03-18.txt
March 19, 201511 yr So, my 9 month old was standing next to my server, and then I noticed he was pulling on of the the taps from my Norco SS-500. Well, he took the hard drive out. I went ahead and stopped the array, turned the server off, and re-inserted the drive. I turned on the server again, and the WebGui shows all the drives with green balls. Well, today, I noticed that my drive # 3 has a red ball DISK_DSBL. I've tried to run a smart report, but I get the following error: Smart Long Test of /dev/sdd could take several hours or more. You must disable disk spin-down during this test, otherwise it will abort when the disk is spun down. smartctl -t long -d ata /dev/sdd 2>&1 smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org SMART Disabled. Use option -s with argument 'on' to enable it. (override with '-T permissive' option) I've checked the power cables and the data cable, and they were both connected fine. I want to run a smart report, but I am not sure what the above comment means? Thanks for any assistance. Remove the "-d ata" from the command and use "-A" instead. If you are doing this from unMenu then just type the command on the command line but use "-A" instead of "-d ata". You would type "smartctl -t long -A /dev/sdd 2>&1" based on what you posted (without the double quotes). Sounds like you have a controller that doesn't like "-d ata" like my M1015s. For MyMain there is a configuration parameter for each drive that will allow it to work correctly with smartctl but not sure where you tried to get the smart report from so the same parameter may not work for you if you are not using MyMain in unMenu to get your smart reports.
March 19, 201511 yr Try "smartctl -s on /dev/sdd" then "smartctl -a /dev/sdd" If still no response then power cycle.
March 20, 201511 yr Author So, my 9 month old was standing next to my server, and then I noticed he was pulling on of the the taps from my Norco SS-500. Well, he took the hard drive out. I went ahead and stopped the array, turned the server off, and re-inserted the drive. I turned on the server again, and the WebGui shows all the drives with green balls. Well, today, I noticed that my drive # 3 has a red ball DISK_DSBL. I've tried to run a smart report, but I get the following error: Smart Long Test of /dev/sdd could take several hours or more. You must disable disk spin-down during this test, otherwise it will abort when the disk is spun down. smartctl -t long -d ata /dev/sdd 2>&1 smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org SMART Disabled. Use option -s with argument 'on' to enable it. (override with '-T permissive' option) I've checked the power cables and the data cable, and they were both connected fine. I want to run a smart report, but I am not sure what the above comment means? Thanks for any assistance. Remove the "-d ata" from the command and use "-A" instead. If you are doing this from unMenu then just type the command on the command line but use "-A" instead of "-d ata". You would type "smartctl -t long -A /dev/sdd 2>&1" based on what you posted (without the double quotes). Sounds like you have a controller that doesn't like "-d ata" like my M1015s. For MyMain there is a configuration parameter for each drive that will allow it to work correctly with smartctl but not sure where you tried to get the smart report from so the same parameter may not work for you if you are not using MyMain in unMenu to get your smart reports. I was using MyMain and Disk management option, and both gave me the same result.
March 20, 201511 yr Author Try "smartctl -s on /dev/sdd" then "smartctl -a /dev/sdd" If still no response then power cycle. I used PuTTy with those lines of code, and it worked. This is what I've got. Tower login: root Linux 3.9.11p-unRAID. root@Tower:~# smartctl -s on /dev/sdd smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enabled. root@Tower:~# smartctl -a /dev/sdd smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF) Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA7632469 LU WWN Device Id: 5 0014ee 2b092aa04 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Thu Mar 19 21:33:50 2015 PDT 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: (0x82) Offline data collection activity was completed without error. 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: (39300) 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: ( 379) 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 197 197 051 Pre-fail Always - 6880 3 Spin_Up_Time 0x0027 244 169 021 Pre-fail Always - 2775 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1596 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 12131 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 528 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 52 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 16523 194 Temperature_Celsius 0x0022 114 103 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 18 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 4 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 198 198 000 Old_age Offline - 640 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@Tower:~#
March 20, 201511 yr Stop the array; unassign the failed disk; Start the array so it's shown on "missing"; then Stop the array and re-assign it; then Start the array and it should do a rebuild onto the same disk. If that doesn't work, then you likely have an actual failure on the disk ... but the SMART report doesn't shown any issues, so I suspect it will rebuild just fine.
March 20, 201511 yr If that doesn't work, then you likely have an actual failure on the disk ... but the SMART report doesn't shown any issues, so I suspect it will rebuild just fine. Not quite true - the report shows a non-zero value for Pending sectors and Offline uncorrectable errors. It is possible a rebuild will clear these, but if not then the drive should probably not be used with unRAID.
March 20, 201511 yr I missed that, since the value is offset to the next line. Howver, the "value" is a perfect 200 for that parameter, so it may be an anomaly that was caused by the "yanking" of the drive at an inopportune time. I'd try the rebuild and see how it goes -- and then do a SMART report afterwards if all goes well to see if these have been cleared.
March 20, 201511 yr Author I've ordered another drive. I'm hoping it will be here tomorrow. I'll preclear and replace that drive with the new 3TB drive. Thereafter, I'll preclear and do a smart report on the questionable drive. If it's good after that then I'll added to the array. Would that be the safest option?
March 20, 201511 yr Yes, definitely the safest option. That lets you rebuild the failed drive on a new drive while still retaining the current state of the old drive, so if anything goes awry you can always try to recover data from that drive (assuming you don't have good backups).
March 21, 201511 yr Author Now the question is what are the steps to rebuilt they new drive? Do I just remove the old drive and add the new drive in the same spot?
March 21, 201511 yr Stop the array; Unassign the bad disk; Start the array so it shows the disk is "missing"; Stop the array and assign the new drive in its place; Start the array and let it do the rebuild.
March 21, 201511 yr Author Stop the array; Unassign the bad disk; Start the array so it shows the disk is "missing"; Stop the array and assign the new drive in its place; Start the array and let it do the rebuild. Thanks.
April 1, 201511 yr Author I just finished pre-clearing my new WD 3TB HDD to replace the bad 2TB one. However, I wanted to confirm that these are the steps to follow to replace it! backup 'config/super.dat' and 'config/disk.cfg' files to workstation Stop the array Power down Replace harddrive with new drive. Turn on Replaced drive appears with blue dot Tick the "I'm sure" checkbox, and press "Start will bring the array on-line, start Data-Rebuild, and then expand the file system." Hefty disk activity and main page will show lots of reading on "the other" disks and writing on new disk as data is being rebuilt. End
April 1, 201511 yr You need to unassign the old drive first, and Start the array so it shows as "Missing". Then Stop the array; assign the new drive; and then Start it and let it do the rebuild.
April 1, 201511 yr You need to unassign the old drive first, and Start the array so it shows as "Missing". Then Stop the array; assign the new drive; and then Start it and let it do the rebuild. I must admit I am not quite sure if that step is actually necessary if replacing a drive, or only when you want to force a drive to rebuild onto itself. However it will not do any harm to include that step and it may be good thing to do from the perspective of standardising the process. A comment on the proposal to back up the config (which is not strictly speaking necessary but is good idea in case things go wrong), is that it should be done with the array in a stopped state - not before stopping the array as the OP suggested.
April 1, 201511 yr Author Well, I stopped the array, turned it off. Took the old hdd out and placed the new on in the same as the old one. Started everything up, added the new drive and started the rebuild. Now, I'm doing a parity check. Thanks for all the help guys!
Archived
This topic is now archived and is closed to further replies.