TQ

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?

syslog from today syslog.01.08.2016.zip

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.

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

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?

So attempt to re-seat controller then see what the parity drive shows?

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

So it looks like my USB drive also had some errors on it thus preventing the above method from working as it was mounted as read-only. I've rectified that issue, and unassigned, started, stopped, reassigned, and restarted again. Data rebuild is currently at 0.4%. Hopefully this will complete today. Thank you @trurl.

So here's the issue(s). Bad disk. Couldn't even SMART it. Array offline for several weeks while I finally got time to work on it. Replaced bad disk. Booted up array, and like the FAQ says...I unassigned the bad disk. Then went in and added the new disk to Slot 5. Upon starting the array, it was rebuilding the drive, just like it's supposed to. Then, I had a power failure that powered off my UNRAID box. From then on, the configuration is valid but the disk is disabled. I'm confident that the data did NOT get back on there. So, I decided to pre-clear the drive once more and try again. Unfortunately there isn't an option to re-build the drive a second time. I do not have a syslog from before or during most of this drama, but I do have some from the pre-clear to now. Syslog is attached. SMART of the new "disabled" disk: :~# smartctl -a -A /dev/sdd 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 === Device Model: ST2000VN000-1H3164 Firmware Version: SC42 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Dec 1 20:06:43 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 107) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 260) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x10bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 111 099 006 Pre-fail Always - 40285912 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1503 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 5499085 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3971 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 24 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 082 082 000 Old_age Always - 18 190 Airflow_Temperature_Cel 0x0022 074 061 045 Old_age Always - 26 (Min/Max 21/39) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 23 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1503 194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (0 20 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 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 Short offline Completed without error 00% 2516 - # 2 Short offline Completed without error 00% 2516 - 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. Unraid-syslog.txt

I have the same thing today. Nervous about array being online but "unprotected".

The management page never responded after trying to start the array. I could never get into the web mgmt page after that. It just kept "loading". So I was finally able to try the smart test as described above. Here is the result: smartctl -t short /dev/sdf Wait at least 5 mins... smartctl -a -d ata /dev/sdf >/boot/smart-sdf.txt This produces the following output in the file: root@QuizzleUNRAID:~# cat /boot/smart-sdf.txt |more 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 Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options. root@QuizzleUNRAID:~# cat /boot/smart-sdf.txt |more 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 Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Selftest: root@QuizzleUNRAID:~# smartctl -l selftest /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 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% 48079 - # 2 Extended offline Aborted by host 90% 29912 - # 3 Short offline Completed without error 00% 9424 - # 4 Extended offline Completed without error 00% 9215 - Not sure what to do next.

Thanks for the replies. I've rebooted and tried to start in Maintenance Mode, but the managment interface just keeps trying to load like it never actually entered Maintenance Mode properly. In the mean time, I was able to run a check on another disk (to be sure what to expect) and it passed the reiserfsck --check. ########### reiserfsck --check started at Mon Sep 7 13:13:59 2015 ########### Replaying journal: Trans replayed: mountid 56, transid 503347, desc 6708, len 1, commit 6710, next trans offset 6693 Trans replayed: mountid 56, transid 503348, desc 6711, len 1, commit 6713, next trans offset 6696 Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 2 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 429447 Internal nodes 2710 Directories 5382 Other files 12238 Data block pointers 432666611 (6988730 of them are zero) Safe links 0 Once I attempted to run the check on Disk 5, it just stalled out. QuizzleUNRAID:/dev# reiserfsck --check /dev/md5 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes And that's where it's sat for a while. A new syslog is attached but I'm unsure if it will glean any new info. syslog-09.07.2015.2.zip

This all started when my system seemed to not be serving up files anymore. I then tried viewing the df -h command and noticing that the tmpfs /var/log was full. I cleaned up some logs but the system remained unresponsive. Decided I would reboot. Solves everything, right? So, after powering off and back on...my array wont start. I let it sit for over an hour, and the GUI just tells me it's "mounting disks..." Is something terribly wrong with my system now? Syslog attached as zip. syslog-09.07.2015.zip

My thought was hardware related too, but I just wanted to cover all my bases by attaching a syslog in hopes that the community might notice something that I didn't. Seems like the thoughts on hardware were correct; tonight I noticed a small, un-obvious cable lodged into my CPU fan causing it not to spin. That explains why after so many minutes, the server would just shut itself off. Re-routed those cables tonight and powered unRAID back on. Currently running Parity check and has been up for several hours. I guess that was it. Thanks to the few of you for responses, the unRAID community is such a wonderful community and I'm happy to belong to this group.

Starting last night, my unRAID server just powered off. I powered it back on and it was online for about 45 mins then shutdown again. Prior to this, it had been running fine for some time. Today I powered it up and didnt start the array but starting tailing the syslog. I still cannot figure out what it going on but its still happening. I just keep seeing this over, and over, and over.... Mar 23 18:45:01 unRAID kernel: md: unRAID driver removed Mar 23 18:45:01 unRAID kernel: md: unRAID driver 2.2.0 installed Mar 23 18:45:01 unRAID emhttp: Device inventory: Mar 23 18:45:01 unRAID emhttp: OCZ-VERTEX_7B36ED6572C5W05PX8BD (sdb) 3126 Mar 23 18:45:01 unRAID emhttp: ST2000VN000-1H3164_W1H39E52 (sdc) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD5L8LF (sdd) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_6YD162D8 (sde) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2SB3K (sdf) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2WYC6 (sdg) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2WYD4 (sdh) 19535145 Mar 23 18:45:01 unRAID emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2706097 (sdi) Mar 23 18:45:01 unRAID emhttp: shcmd (9464): /usr/local/sbin/emhttp_event Mar 23 18:45:01 unRAID emhttp_event: driver_loaded Mar 23 18:45:01 unRAID kernel: mdcmd (1): import 0 8,128 2930266532 WDC_W Mar 23 18:45:01 unRAID kernel: md: import disk0: [8,128] (sdi) WDC_WD30EZ Mar 23 18:45:01 unRAID kernel: mdcmd (2): import 1 8,80 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk1: [8,80] (sdf) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (3): import 2 8,96 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk2: [8,96] (sdg) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (4): import 3 8,112 1953514552 ST200 Mar 23 18:45:01 unRAID kernel: md: import disk3: [8,112] (sdh) ST2000DL00 Mar 23 18:45:01 unRAID kernel: mdcmd (5): import 4 8,64 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk4: [8,64] (sde) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (6): import 5 8,48 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk5: [8,48] (sdd) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (7): import 6 8,32 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk6: [8,32] (sdc) ST2000VN000 Mar 23 18:45:01 unRAID kernel: mdcmd (: import 7 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (9): import 8 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (10): import 9 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (11): import 10 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (12): import 11 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (13): import 12 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (14): import 13 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (15): import 14 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (16): import 15 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (17): import 16 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (18): import 17 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (19): import 18 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (20): import 19 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (21): import 20 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (22): import 21 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (23): import 22 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (24): import 23 0,0 Mar 23 18:45:02 unRAID emhttp: shcmd (9465): rmmod md-mod |& logger Mar 23 18:45:02 unRAID emhttp: shcmd (9466): modprobe md-mod super=/boot/ Mar 23 18:45:02 unRAID emhttp: shcmd (9467): udevadm settle unRAID-syslog.txt.gz