Hello Everyone,

 

I am attempting to set up my first unRAID server and I am having problems starting my array. Here are a list of my specs:

Motherboard:

• Asus Z10PE-D16 WS 

CPU:

• 2x Intel Xeon E-2697 SR1XF

RAM:

• 4x32 Crucial DDR4 Dual Ranked ECC Memory

Storage:

• 1x 1TB Samsung 970 Evo m.2 nvme
• 4x Western Digital 1 TB WD Blue SN570 NVMe SSD

GPU:

• Asus GT 710

 

I have tried to attach my diagnostics file and it fails to upload. Here is a link to it:
https://drive.google.com/file/d/1aC6jYiKiO8zB2QTKcIMxEQSx3Ere9abs/view?usp=sharing

 

When I go to the web console I set my parity drive as the Samsung NVMe and I set the disks to the four WD NVMe's. I then hit start array and a timer appears at the top and the unRAID logo begins to move on screen.
 

If I open another tab and attempt to navigate to the url the server has disconnected from the network and it is unreachable. I am directly attached to the server via gpu/keyboard and it shows a blinking cursor but I cannot type into it. As such I leave the tab with the unRAID logo running in hopes that it will reconnect after. I cannot see any progress at all and my current attempt has been running for over 26 hours. 

 

The last time I tried it ran for 18 hours and I stopped it to restart my machine because I read somewhere that it should not be disconnected from the network and I should be able to see a completion bar of some kind. 

 

I am at a loss for what to do. Should I continue to let it run? Did I do something wrong? Any help would be greatly appreciated.

1 hour ago, ehosinski said:

a timer appears

What are you talking about a timer?  Post a screenshot...

 

1 hour ago, ehosinski said:

over 26 hours. 

Generally speaking (but not always the case), if the spinner appears and doesn't disappear within 120 seconds it will never disappear

1 hour ago, ehosinski said:

I have tried to attach my diagnostics file and it fails to upload. Here is a link to it:
https://drive.google.com/file/d/1aC6jYiKiO8zB2QTKcIMxEQSx3Ere9abs/view?usp=sharing

You should be able to upload it to the forum - not sure why it fails for you.   I cannot download from the link you provided so cannot help.

@itimpi It is letting me post it in this comment luckily but here it is.

@Squid I just realized it was the uptime timer, I am assuming it is kept client side which is why it worked. 

I will say I just attempted to run this from the unRAID OS gui and it actually freezes when I start the array and forced me to shut down which is why it goes offline. Which makes a lot more sense but I still don't understand why.

krakenhaus-diagnostics-19991231-1634.zip

Dec 31 16:30:44 Krakenhaus emhttpd: stale configuration

 

Try this: https://forums.unraid.net/topic/110030-solved-cannot-resolve-stale-configuration-error/?tab=comments#comment-1006155

I could not see any attempt to assign the disks in the posted diagnostics  

Maybe taking some diagnostics after doing the assignments but before starting the array might give a clue.

 

it might also be worth configuring the syslog server to see if that captures any additional information after attempting to start the array.

I had looked at that link, I actually just removed the USB and fresh installed unRAID with the media creation tool and it seems to be better already. Here is hoping

@itimpi Thank you! I will try to capture some diagnostics after this fresh install and see if the issue persists. I really appreciate the help.

So now I started the array and it didn't immediately take the server offline. However it told me that the disks were unmountable. I checked the box to enable formatting and clicked format (I probably should have waited until parity synced) but now the page is taking too long to respond again. I can still see the server on the network this time so it hasn't shut down. But I am again unable to visit the web console as intended. Should I give it a few hours to see if the parity works this time?

The keyboard/monitor is also unresponsive again so I can't even run diagnostics. (blinking cursor but accepts no input)

3 minutes ago, ehosinski said:

However it told me that the disks were unmountable

This is expected if the drives have not previously been formatted by Unraid.

 

4 minutes ago, ehosinski said:

I checked the box to enable formatting and clicked format (I probably should have waited until parity synced) but now the page is taking too long to respond again.

This could take quite a long time to complete if you are simultaneously building parity.   If not done at the same time it is normally quite quick.

 

As the server is still operational you may find that if you close the browser and then connect s second time then you get something useful.   If not then wait until parity is built.

@itimpi here is the diagnostics I ran after they were assigned but before starting the array

kraken-diagnostics-20220205-0918.zip

 

27 minutes ago, itimpi said:

This is expected if the drives have not previously been formatted by Unraid.

 

This could take quite a long time to complete if you are simultaneously building parity.   If not done at the same time it is normally quite quick.

 

As the server is still operational you may find that if you close the browser and then connect s second time then you get something useful.   If not then wait until parity is built.

It's not offline again. I think it likely froze again but I have no real way of knowing. I just have the web console up but if I were to refresh or anything it would just lead to a timeout.

It is worth seeing if you can make a ssh connection.

22 minutes ago, itimpi said:

It is worth seeing if you can make a ssh connection.

No reply from host unfortunately

Did you manage to get the syslog server set up?

2 hours ago, itimpi said:

Did you manage to get the syslog server set up?

I did not, I swapped in a HDD for the parity drive but now I am being told that the build will take 37 days 4 hours and 30 minutes?

I have attached the diagnostics again

krakenhaus-diagnostics-20220205-1632.zip

Those diagnostics are before parity build started. Can you get new ones?

Just now, trurl said:

Those diagnostics are before parity build started. Can you get new ones?

I would love to the problem is as soon as it starts to build parity the entire system is unresponsive.

You could try opening up the syslog in a window before starting the array?

 

at the moment the symptoms feel very like they must be hardware related in some way.

 

Are you sure that the power supply is OK for the hardware.   Building parity is a time when the system will be most demanding.

 

Have you tried running memtest (one of the options on the boot menu) to check out the RAM?   What speed are you clocking the RAM at?  Make sure it is within the rating for your motherboard/CPU combination.  Overclocking RAM is a not infrequent cause of crashes.