January 28, 201511 yr My unraid box has been running for a few years now without any major problems. About 4 months back I had an issue with the parity drive and I did a parity recheck on it and then life was good. Well, I was copying a movie to the unraid box this evening and it just kind of locked up. It just stopped responding and I couldn't do anything, so I had to press the power button and power it down. Now it has some what come back up, but I am having some major issues with it. I can't access the unmenu. I can telnet into it, but I am not an expert without any guidance on using any commands under the root menu. I have done some preclear_disk using the telnet but that is about it. So, if I go to the ip address of the unraid box, it takes a long time to navigate from tab to tab, but on the "main" tab, the three drives "parity" and "disk1" and disk2" all are green. The parity drive is up to at 9,385 errors and going up, with 1,446 writes. Below the command area it says "starting". So, before I go messing something up anyone have any advice on what todo? Did my parity drive fail? I have another 2 TB parity drive on order, but it won't be here till Friday. Should I wait till Friday and just power down the box, and replace the parity drive and let it do a parity rebuild? Is there anything I can try in the mean time through the telnet under the root menu? Do I need to let it finish error on the parity drive, then I can stop and unmount the parity drive? Any help or advice would be super appreciated. Thanks.... The parity drive is a "WDC_WD20EARS" green drive, so maybe my luck of not having a red drive caught up to me. :-( I was copying a movie over to my unraid box, and it just kind of locked up. [/img]
January 28, 201511 yr Author Syslog report it attached in zip file. Smart Report: 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-00S8B1 Serial Number: WD-WCAVY6068687 Firmware Version: 80.00A80 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 Jan 28 09:05:02 2015 CST 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: (39600) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. 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 199 199 051 Pre-fail Always - 19995 3 Spin_Up_Time 0x0027 164 140 021 Pre-fail Always - 8758 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 831 5 Reallocated_Sector_Ct 0x0033 161 161 140 Pre-fail Always - 846 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 054 054 000 Old_age Always - 34231 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 - 129 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 110 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4983 194 Temperature_Celsius 0x0022 125 112 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 334 197 Current_Pending_Sector 0x0032 199 197 000 Old_age Always - 420 198 Offline_Uncorrectable 0x0030 200 198 000 Old_age Offline - 139 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x0008 200 187 000 Old_age Offline - 178 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: read failure 10% 31105 3814136784 # 2 Short offline Completed without error 00% 30929 - # 3 Short offline Completed without error 00% 26552 - # 4 Short offline Completed without error 00% 26552 - # 5 Extended offline Aborted by host 90% 26552 - # 6 Short offline Completed without error 00% 26324 - # 7 Short offline Completed without error 00% 20955 - 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. syslog.zip
January 28, 201511 yr The smart report does not look good. Not sure where you got that syslog because it has Feb 5 timestamps and includes disks that are not in your screenshot.
January 28, 201511 yr Author Sorry about that, I grabbed the wrong zip file. Here is the latest syslog... syslog-2015-01-28.zip
January 28, 201511 yr Author Thanks.... Was this the corruption in the last syslog "FAT: Filesystem error (dev sdd1) Jan 28 09:17:03 UNRAID kernel: invalid access to FAT (entry 0x2e09f239)" The "sdd1" was the flash drive? I didn't know what that was. Attached is syslog after I did a checkdisk on the flash drive and it fixed a few issues. Do you still think sda drive (parity) drive is bad and I should replace it when I get my replacement drive in? syslog-2015-01-28AfterChkDsk.txt
January 28, 201511 yr Thanks.... Was this the corruption in the last syslog "FAT: Filesystem error (dev sdd1) Jan 28 09:17:03 UNRAID kernel: invalid access to FAT (entry 0x2e09f239)" The "sdd1" was the flash drive? I didn't know what that was. YES Attached is syslog after I did a checkdisk on the flash drive and it fixed a few issues. Do you still think sda drive (parity) drive is bad and I should replace it when I get my replacement drive in? Yes. You have several SMART values that are worrisome. See here
Archived
This topic is now archived and is closed to further replies.