Hello,

 

I am having issues with creating a parity drive on my new unraid server.  I am new to UnRaid so this is a bit foreign to me (still at the trial version).  Attached is a copy of the error I am getting under the notification corner.  Just to give you an idea of what's under the hood (if it helps), the following is my set up:

 

-SuperMicro X9DRi-LN4F+ mobo

-8x 4GB DDR3 ECC REG RDIMM Ram

-2x E5-2650 v1 CPU

-8x Hitachi UltraStar 3TB 7200RPM HUA723030ALA641 SATA HDD

-6x Arctic 120mm PWM case fans

-2x Cooler Master Hyper 212 heatsink CPU fan

-SanDisk 16GB low profile USB thumb drive (this is what's running unraid)

-650W psu

-Silicon Power 512GB SSD

-Silicon Power 128GB SSD

-Case Phanteks Enthroo Pro Black Steel case.

Here's the SMART result of the parity drive.  I took it off the array and ran the test.

serverhoss-smart-20180526-2007.zip

Hitachi_HUA723030ALA641_YVGXTPVA-20180526-2007.txt

Please post your diagnostics: Tools -> Diagnostics after the error and before rebooting.

I tried to do this before rebooting but the server was being unresponsive (another issue that I am having at points - I will have great connection speed when I start up the server, but after a few hours the connection speed gradually degrades to the point that loading up a page on the server takes almost a minute).  I had to reboot to get it going, and then I downloaded the diagnostic report (attached).

serverhoss-diagnostics-20180527-1342.zip

i'm redoing the parity drive along with formatting another drive to have as my main drive in the array so i've left it alone for about 8 hours - having my 128gb ssd as a cache. i've come back and clicked the "dashboard" tab at the top of the gui and i have no connection to the server - my browser says it cannot connect to it. i check my router and it states that the server is connected to the router. i disabled the default router firewall and still not able to connect. i don't want to force shutdown the server rig in order to "refresh" the network connection to it (and cause perhaps corrupt the format and parity). so this is a problem.

8 minutes ago, dreminemike said:

i'm redoing the parity drive along with formatting another drive to have as my main drive in the array so i've left it alone for about 8 hours - having my 128gb ssd as a cache. i've come back and clicked the "dashboard" tab at the top of the gui and i have no connection to the server - my browser says it cannot connect to it. i check my router and it states that the server is connected to the router. i disabled the default router firewall and still not able to connect. i don't want to force shutdown the server rig in order to "refresh" the network connection to it (and cause perhaps corrupt the format and parity). so this is a problem.

 

I am by no means an expert here, however I had the same issue, are you connecting via //tower/ or the IP address?

Try whichever one you're not using, there is also a thread on these issues which fixed it for me, I will have a browse and see if I can find it.

12 hours ago, dreminemike said:

I had to reboot to get it going, and then I downloaded the diagnostic report (attached).

Unfortunately diags are not very helpful after a reboot, try to get them on the command line next time, by typing diagnostics on the console.

the server pc wouldn't even register me typing on the keyboard.  i tried accessing the terminal or any page via another pc and it wouldn't load the page.  i just had to force-reboot the server.  this is getting a bit frustrating on my end.  i was redoing a parity drive since yesterday afternoon and it seems like all that was for nothing.

Edited May 28, 20188 yr by dreminemike

11 hours ago, GoudaK said:

 

I am by no means an expert here, however I had the same issue, are you connecting via //tower/ or the IP address?

Try whichever one you're not using, there is also a thread on these issues which fixed it for me, I will have a browse and see if I can find it.

tried both. still nothing.  had to force-reboot the server because it was unresponsive on both the pc accessing it and the server pc itself.  this is starting to get very frustrating.