January 8, 201610 yr A few weeks ago I was recovering from an unclean shutdown and the array obviously wanted a parity sync on the next boot. I let that go for several hours... Upon checking in on it many hours later, I noticed I had a ton of read errors from multiple data disks and the parity sync seemed to have finished before the supposed time. At this time, all of my data shares were read-only! Copied syslog to usb stick, shut it down and went out of town for holiday. Today, I booted back up and it shows parity disk is a "new disk, not in array". Haven't started the array yet. Any ideas on what I should do? Syslogs.zip
January 8, 201610 yr Since multiple drives all went down at the same time, I would be inclined to think that the controller card is slightly loose in the PCIe slot or you've got power delivery problems to those drives (splitter problems, etc)
January 8, 201610 yr So attempt to re-seat controller then see what the parity drive shows? Yes. I think that you should assume that the parity is not necessarily good since you got errors last time, so rebuilding it will be the way to go. If it WAS good then you should simply be writing the same contents as was previously there so that would not do any damage. The only time there would be an issue is if one of the data disks is also reporting issues, and in that case you should probably check back here saying exactly what the situation is to get guidance on the best way forward.
January 8, 201610 yr Author Powered off and checked the controller card and all sas/sata connections. Everything looks good. Powered back on and I'm in the same state with the "New Parity" disk: "new disk, not in array" Should I replace the Parity drive and start a sync again? Should I leave the old one in there and start a sync?
January 8, 201610 yr Should I replace the Parity drive and start a sync again? Should I leave the old one in there and start a sync? I would get the SMART attributes and as long as that shows no causes for concern simply sync to the old drive.
January 8, 201610 yr Author SMART looks good on Parity Drive: root@QuizzleUNRAID:~# smartctl -a -A /dev/sdk 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 INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00MMMB0 LU WWN Device Id: 5 0014ee 207345654 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Jan 8 10:51:46 2016 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: (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: (50760) 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: ( 488) 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 195 118 051 Pre-fail Always - 188460 3 Spin_Up_Time 0x0027 148 144 021 Pre-fail Always - 9591 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4421 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 069 069 000 Old_age Always - 22695 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 - 209 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 200 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 655167 194 Temperature_Celsius 0x0022 123 109 000 Old_age Always - 29 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 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 Short offline Completed without error 00% 5262 - # 2 Short offline Completed without error 00% 1574 - I'll start it up and see what happens. Thanks
January 8, 201610 yr Author Appears to have stopped, but far short of completing. Also, nice little orange notification error...Parity disk has invalid data And...the array apparently has stopped itself.
January 9, 201610 yr I was hoping for a syslog prior to a restart of the server showing the failed state and hopefully why it failed. As it stands, the log covers ~15 minutes and appears clean.
January 9, 201610 yr Author Not sure what else to do. I've started the array again and again it starts a parity check, but the array stops a little while later. Warning: Parity disk has invalid data What should I do? Should I pre-clear parity drive and start it again to allow to re-build?
January 9, 201610 yr Not sure what else to do. I've started the array again and again it starts a parity check, but the array stops a little while later. Warning: Parity disk has invalid data What should I do? Should I pre-clear parity drive and start it again to allow to re-build? Pre-clearing a parity disk has no effect other than to a confidence check. When you did the parity check was it a correcting or non-correcting check? It may be necessary to do a correcting check to get parity back in sync with the data drives.
January 9, 201610 yr Author Pre-clearing a parity disk has no effect other than to a confidence check. When you did the parity check was it a correcting or non-correcting check? It may be necessary to do a correcting check to get parity back in sync with the data drives. Not sure, as I only see this: Start will bring the array on-line and start Parity-Sync. next to the start button for the array. I'm starting to wonder if during the party-sync the system is rebooting. I just noticed that the system shows online for only 2+ hours. I started the array/sync before then.
Archived
This topic is now archived and is closed to further replies.