December 31, 20169 yr I have a 10x6TB unraid server running 5.0.5 (1 parity + 9 data) I was writing a file to disk9 and it was failing. I have been having some issues with my local network, so i tried deleting the failed file and unraid told me the file system was read only. I rebooted unraid through the web interface, and now it is telling me that a new parity disk has been installed. On the device status screen, there is a blue ball next to the parity drive. All the other drives are green. Relevant lines from syslog: Dec 31 03:37:29 Tower2 kernel: mdcmd (1): import 0 8,80 5860522532 WDC_WD60EFRX-68MYMN0_WD-WX21D1406561 Dec 31 03:37:29 Tower2 kernel: md: import disk0: [8,80] (sdf) WDC_WD60EFRX-68MYMN0_WD-WX21D1406561 size: 5860522532 Dec 31 03:37:29 Tower2 kernel: md: disk0 replaced I haven't added or removed any drives, so I am unsure what to do next. I don't want to corrupt my existing data. How do I go about resolving this? The full syslog is attached. syslog_tower2.txt
December 31, 20169 yr Author How can I get SMART reports without starting the array and mounting the disks?
December 31, 20169 yr No need to start the array: http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report
December 31, 20169 yr Running diagnostics (see Tools), creates a SMART report of all disks present in the system regardless of the array state.
December 31, 20169 yr Author Smart report from parity drive (/dev/sdf) smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 198 194 021 Pre-fail Always - 9066 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 461 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 087 087 000 Old_age Always - 10174 10 Spin_Retry_Count 0x0032 100 100 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 - 44 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1133 194 Temperature_Celsius 0x0022 119 110 000 Old_age Always - 33 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
December 31, 20169 yr Running diagnostics (see Tools), creates a SMART report of all disks present in the system regardless of the array state. He's still on v5
December 31, 20169 yr Running diagnostics (see Tools), creates a SMART report of all disks present in the system regardless of the array state. He's still on v5 Ay ay, didn't pay enough attention, would recommend to upgrade to v6 though
December 31, 20169 yr SMART looks fine, syslog is not very useful because it's after rebooting, assuming all other disks are fine, you have to options: 1) Start the array to begin a parity sync (you'll be unprotected until it finishes) 2) Assume parity is mostly valid and: Take a screenshot of all array assignments Go to Utils and click New Config Reassign all disks, double check parity is in the parity slot Before starting the array check the box "Parity is already valid" Run a parity check ETA: when done also recommend upgrading to v6
December 31, 20169 yr Author The smart reports for the other drives look very similar, no real errors that i can see. Sounds like the best thing to do here is to run another parity sync. Out of interest, what could have caused unraid to think my parity drive has changed? Some configuration file getting corrupted somehow?
December 31, 20169 yr Difficult to guess, if it was a disk error it should get disable (red ball), next time grab the syslog before rebooting.
December 31, 20169 yr The smart reports for the other drives look very similar, no real errors that i can see. Sounds like the best thing to do here is to run another parity sync. Out of interest, what could have caused unraid to think my parity drive has changed? Some configuration file getting corrupted somehow? You may want to compare super.dat and super.old files, they should be the same unless some corruption. super.dat keeps track of current disk assignments and a new disk (blue) isn't referenced in this file yet.
December 31, 20169 yr ... Sounds like the best thing to do here is to run another parity sync. If you're going to do a New Config and new parity sync anyway, I'd go ahead and upgrade to v6 before doing it. You're going to be running "at risk" anyway, and no longer have the ability to rebuild any of the other drives ... so you may as well move to the newest version while you're doing it.
Archived
This topic is now archived and is closed to further replies.