July 25, 20169 yr My server shows my Parity is invalid and it has disabled the drive. I plugged the parity drive into my windows 10 rig and checked it out and it shows good health and no bad sectors. Should I just format the parity drive or do I need to do something else to get it reset? I did some searching around but did not find an answer for my issue. Any help is greatly appreciated. Greg
July 25, 20169 yr Author OK, so after doing another search, I think this is what I should do: Take a screenshot of your current array assignments, or make good notes of them Stop the array (if it is started) Go to <Tools> and click <New config> Reassign all disks using your notes or screen shot Double check that your Parity disk is assigned correctly! Click the check box "Parity is already valid" (make sure it is checked) Start the array Done! It is strongly recommended to do a parity check now, to make sure parity is fine Sound right?
July 25, 20169 yr there must be a reason why the parity is showing as invalid and drive was disabled. A check in windows wont really tell you what you need. read here https://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F
July 25, 20169 yr Community Expert If you think the parity disk is OK there's no need to do a new config, just unassign the parity disk, start array, stop array, assign it again and start array to begin parity sync.
July 25, 20169 yr If you think the parity disk is OK there's no need to do a new config, just unassign the parity disk, start array, stop array, assign it again and start array to begin parity sync. I agree with johnnie as it's the safest bet. If you're 100% sure that nothing has been written to the array, then you can do a new config and select that parity is already valid. If you've written to the array since the parity disk went offline, then the parity data is no longer valid and will have to be rebuilt. Even if there is a tiny bit of doubt, you're better off rebuilding parity.
July 26, 20169 yr Author So I am trying to rebuild my parity drive, but when I do a tools>new config and try to assign the parity drive, I can see it and select it, but then it disappears from the selection box. Any thoughts? Should I just pull the drive and wipe it in windows, then reinstall it into the array?
July 26, 20169 yr Sorry, Kind of a newb. How do I obtain the diagnostics? Tools Tab - Diagnostics Button
July 26, 20169 yr Author Darn, I just found it and tried to get back and post that I figured that out. I'll post when I get home tonight.
July 27, 20169 yr Author Alright, here is the diag file. I have no idea how to read this but here it is for the experts. tower-diagnostics-20160726-1928.zip
July 27, 20169 yr Community Expert The SMART report for the parity disk is incomplete, but the disk doesn't look healthy: Error 822 occurred at disk power-on lifetime: 23636 hours (984 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 80 ff ff ff ef 00 1d+03:42:35.109 READ DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.109 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.108 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.108 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.107 WRITE DMA EXT Error 821 occurred at disk power-on lifetime: 23636 hours (984 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 80 ff ff ff ef 00 1d+03:42:35.109 READ DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.109 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.108 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.108 WRITE DMA EXT 35 00 08 ff ff ff ef 00 1d+03:42:35.107 WRITE DMA EXT Error 820 occurred at disk power-on lifetime: 23636 hours (984 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 1d+03:42:09.957 READ DMA EXT ec 00 00 00 00 00 a0 00 1d+03:42:09.953 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 1d+03:42:09.750 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 1d+03:42:09.722 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 1d+03:42:03.563 READ DMA EXT Error 819 occurred at disk power-on lifetime: 23636 hours (984 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 1d+03:42:09.957 READ DMA EXT ec 00 00 00 00 00 a0 00 1d+03:42:09.953 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 1d+03:42:09.750 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 1d+03:42:09.722 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 1d+03:42:03.563 READ DMA EXT Error 818 occurred at disk power-on lifetime: 23636 hours (984 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 1d+03:42:03.563 READ DMA EXT ca 00 08 a0 c1 00 e0 00 1d+03:42:03.562 WRITE DMA ca 00 20 a8 c1 00 e0 00 1d+03:42:03.561 WRITE DMA 35 00 08 ff ff ff ef 00 1d+03:42:03.561 WRITE DMA EXT ca 00 40 30 2e 0e e2 00 1d+03:42:03.560 WRITE DMA
July 27, 20169 yr Author I think I am going to wipe the drive and see what the SMART report says. Guess I should look into a new drive for the Parity drive
July 27, 20169 yr I think I am going to wipe the drive and see what the SMART report says. Guess I should look into a new drive for the Parity drive I dont think wiping the drive will help. If money permits I would replace that drive if i was you.
Archived
This topic is now archived and is closed to further replies.