July 23, 20187 yr Over the time period I've had unRaid on my box, I've had instability issues that I couldn't figure out. This time around it's my parity drive. It goes disabled randomly and I cant figure it out... Can anyone help me out here? Attached is my diagnostics. Thanks everyone! henraid-diagnostics-20180723-1725.zip
July 24, 20187 yr Author @trurl So right now, my parity is disabled, just making sure, you want me to power down, check the connection on the sata and power on the parity drive and boot back up? Its already disabled so did you want me to rebuild? Edited July 24, 20187 yr by henkim21
July 24, 20187 yr Community Expert Power down, check connections power and SATA on parity disk. The diagnostics you posted don't have any SMART for parity probably because it is disconnected in some way. After fixing connections, hopefully new diagnostics will have SMART for parity and we can decide if the disk is OK for rebuilding.
July 24, 20187 yr Author @trurl Okay here are the new diagnostics... I ran the short smart test and it completed, I'm running an extended smart test but its been at 10% forever... henraid-diagnostics-20180723-2246.zip
July 24, 20187 yr Community Expert SMART looks fine, you're using a SAS2LP, these are known to drop disks without reason for some users.
July 24, 20187 yr Author Thanks for your help everyone! I stopped the system, unassigned the parity drive, started the system, stopped the system and was right about to reassign the parity for a rebuild when.... it went nuts..the drive was seen by unassigned devices but was not coming up in the dropdown menu to reassign parity...so I rebooted. After the reboot, the system saw the parity drive but not my first data disk... I tried another reboot and eventually got the parity drive and data drive back assigned in its proper place...started the rebuild and then the parity drive immediately had write errors and was disabled... Are the reported SAS2LP instabilities this bad? Do I have another issue on my hands? Is an LSI controller the recommended buy currently?
July 24, 20187 yr Author also one thing I dont remember doing is checking the FW version of the sas2lp and donwgrading/disabling INT13...is this info from 2011 still valid? or maybe I should just go with an LSI? I know I need an HBA because most if not all of my sata ports on my board are Marvell...motherboard is an ASRock - Z77 Pro3... Im not opposed to taking this opportunity to upgrade my whole system... https://www.reddit.com/r/JDM_WAAAT/comments/8zgkfj/server_build_nas_killer_v_20_the_terminator_dual/ this build is interesting...its got an LSI controller built in... Any thoughts/opinions? Is the INT13 something that will definitely cause issues? If so I will take the time to downgrade fw if necessary and disable INT13. If no, I may just swap to an LSI controller...
July 24, 20187 yr Community Expert AFAIK INT13 doesn't cause dropped drives, it might be related to data corruption, .i.e, parity sync errors, when it happens, the best way to solve the dropped disks issue is to replace it with an LSI.
July 30, 20187 yr Author Bad news, I bought the h310, flashed it to IT mode, installed the card, rebuilt my array, and did a parity check... all looked good for about a day until I saw my parity drive is disabled again this afternoon... attached are my logs... can anyone take a look? My next idea is my power supply... there was one time in the past where I wasnt able to rebuild my parity after a failure and was finally able to after I used a molex splitter to power my 8tb red i am using for parity... maybe I should look into another psu that is a more trusted brand than xigmatek? I thought itd be okay since its at least 80 plus bronze and single 12v raail rated for 36A...what am i missing? henraid-diagnostics-20180729-1859.zip Edited July 30, 20187 yr by henkim21
July 31, 20187 yr Author I replaced the psu with the seasonic and am rebuilding parity now... hopefully itll take care of the instability...thanks for everyone who took the time to take a look at my logs.
Archived
This topic is now archived and is closed to further replies.