Jump to content

[SOLVED] Issues setting up parity drive


Recommended Posts

Posted (edited)

Hi, this is my first time diving into setting up a server so I am hoping I am just missing something obvious. I have been trying for a week to get a parity drive set up but it keeps failing and setting itself as disabled. I have searched the forums and have tried a few things I have found but I can't seem to figure it out. Hoping someone with more experience could shed some light.

 

Setup:

2 brand new Western Digital 8tb drives taken from Easystore externals

Running unraid 6.8.3

 

Things I have tried:

- Formatting drives

- Stop array, de-select parity drive, start array, stop array, re-select parity drive.

- Run full diagnostics on both drives - both pass with no errors.

- Check cables/connections.

 

One thing to note: The drives originally wouldn't spin up. After searching I found out that these drives in particular go into an error state if 3.3v is supplied via the power supply cable. I have cut and taped off that wire. They spin up fine now and I have had no issues with them going offline that I can tell.

 

I have tried the parity check 3 times (each about 12 hours). I am kinda frustrated and exhausted. I feel like it shouldn't be this hard. I have attached the sys log but please let me know if there is any other info that would be helpful. Also, I have not put anything on the drives yet so there is no worry about data loss if that helps with suggesting something such as formatting again. I just wanted to get it setup before I use them just in case I screw it up.

 

edinburgh-diagnostics-20200530-1731.zip

Edited by itsmepetey
Issue was solved
Posted

Lots of call traces, including in the Unraid driver, this could point to some hardware issue, run memtest, also look for a BIOS update.

 

There is also constant log spam like this:

 

May 30 12:46:30 EDINBURGH kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:01.3
May 30 12:46:30 EDINBURGH kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
May 30 12:46:30 EDINBURGH kernel: pcieport 0000:00:01.3:   device [1022:1483] error status/mask=00000040/00006000
May 30 12:46:30 EDINBURGH kernel: pcieport 0000:00:01.3:    [ 6] BadTLP                
May 30 12:46:48 EDINBURGH kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:01.3
May 30 12:46:48 EDINBURGH kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
May 30 12:46:48 EDINBURGH kernel: pcieport 0000:00:01.3:   device [1022:1483] error status/mask=00000040/00006000
May 30 12:46:48 EDINBURGH kernel: pcieport 0000:00:01.3:    [ 6] BadTLP    

See if this helps.

Posted

I took your advice. I updated the BIOS and then ran a memtest over night. No errors showed up so I went ahead and gave the parity sync another go. That fixed it and it completed without errors. Thanks for taking a look!

  • JorgeB changed the title to [SOLVED] Issues setting up parity drive

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...