Hi!

 

I've done my best to find a solution to this, both specifically on this forum and on the Internet in general, and although I've found some ideas and suggestions I don't really want to try something until I've asked specifically here for some more guidance.

 

Earlier this week I had a power outage that caused the server to shut down. When the power came back I checked to see if the server started as it should and as far as I could tell, the array was healthy and all my apps started as they should. After a couple of hours the entire server became unresponsive though, not even the console via keyboard and monitor worked, and my only option was a hard reset.

 

After this I ran a read check of all disks. Unfortunately I managed to bump the USB stick for the UnRaid OS which caused it to dismount, forcing me to reboot the server after only a couple of hours of the read check. When I restarted the check UnRaid reported that it had found 394 errors, but after the second check completed, everything was ok and it had found 0 errors.

 

The array is healthy and parity is valid, but despite this I can't enable my parity disk. I've rebooted the server after the successful parity check, still no dice.

 

 

This is the disk log information for the parity disk, which I interpret as the disk itself being just fine.

 

Apr  9 18:17:36 NAS kernel: ata18: SATA max UDMA/133 abar m8192@0xdf280000 port 0xdf280680 irq 127
Apr  9 18:17:36 NAS kernel: ata18: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr  9 18:17:36 NAS kernel: ata18.00: ATA-10: WDC WD60EFZX-68B3FN0, 81.00A81, max UDMA/133
Apr  9 18:17:36 NAS kernel: ata18.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Apr  9 18:17:36 NAS kernel: ata18.00: configured for UDMA/133
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] 4096-byte physical blocks
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] Write Protect is off
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] Mode Sense: 00 3a 00 00
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] Preferred minimum I/O size 4096 bytes
Apr  9 18:17:36 NAS kernel: sdk: sdk1
Apr  9 18:17:36 NAS kernel: sd 18:0:0:0: [sdk] Attached SCSI disk
Apr  9 18:17:49 NAS  emhttpd: WDC_WD60EFZX-68B3FN0_WD-CA1K55ZK (sdk) 512 11721045168
Apr  9 18:17:49 NAS kernel: mdcmd (1): import 0 sdk 64 5860522532 0 WDC_WD60EFZX-68B3FN0_WD-CA1K55ZK
Apr  9 18:17:49 NAS kernel: md: import disk0: (sdk) WDC_WD60EFZX-68B3FN0_WD-CA1K55ZK size: 5860522532 
Apr  9 18:17:50 NAS  emhttpd: read SMART /dev/sdk
Apr  9 18:30:09 NAS  emhttpd: spinning down /dev/sdk
Apr  9 18:30:16 NAS  emhttpd: spinning up /dev/sdk
Apr  9 18:30:19 NAS  emhttpd: read SMART /dev/sdk

 

Before I start over with a new config, or remove and add back my parity disk, or other more or less intrusive operations, is there something else I should test or try?

 

Thanks!

To clear the disabled state you need to rebuild the parity drive as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

 

Thanks, that wasn't as drastic as I had feared, and I didn't realize that you could rebuild the disk onto itself.

 

I appreciate the quick response.