Hello there

 

I have been using unRAID Pro for about a year now.  A bit of quick background..  I was on 4.5.x for the longest time.  Last week, I started noticing errors accumulating in the ERRORS column beside the parity drive.  So I tried doing the PARITY CHECK via the main screen.  Somewhere in between it completing 5% and 10% of the parity check, suddenly the server would be completely unresponsive.  No longer accessible via the web, nor via the keyboard attached to the PC.  Hard lockup.

 

So I upgraded my unRAID version to the newest 5.0 beta to see if things would change or help, and again, it got to about 5% of the parity check and now the server is completely crashed and unresponsive again.

 

How am I supposed to fix this if I can't even get at the log files because the server is locked up?  What the hell is going on?  How am I supposed to rescue or replace this parity drive if it can't even complete the checking process without freezing up?

 

This is extremely annoying and I am losing faith in this unRAID product, mostly because it's so unhelpful when troubleshooting an issue like this..  Should I just try replacing the drive even though it can't even complete a parity check on the old one?  What is my plan to troubleshoot this matter?

 

It's starting to get very irritating so any help would be greatly appreciated.

 

Thanks in advance.

 

 

 

PS:  the signup process to this forum is way annoying.  whats with the password restrictions and minimum sizes?  You really think people care about hacking your account on a support forum for unRAID?  Sheesh

Hello there

 

I have been using unRAID Pro for about a year now.  A bit of quick background..  I was on 4.5.x for the longest time.  Last week, I started noticing errors accumulating in the ERRORS column beside the parity drive.  So I tried doing the PARITY CHECK via the main screen.  Somewhere in between it completing 5% and 10% of the parity check, suddenly the server would be completely unresponsive.  No longer accessible via the web, nor via the keyboard attached to the PC.  Hard lockup.

 

So I upgraded my unRAID version to the newest 5.0 beta to see if things would change or help, and again, it got to about 5% of the parity check and now the server is completely crashed and unresponsive again.

Sorry to hear you are just now starting to have problems with your server.

 

The issues you are having sound like a hard drive problem and not something that unRAID can "fix"; only replacing a drive, cable, or power supply connection can fix that kind of issue.

 

How am I supposed to fix this if I can't even get at the log files because the server is locked up?  What the hell is going on?  How am I supposed to rescue or replace this parity drive if it can't even complete the checking process without freezing up?

There is a sticky thread, right above the one you posted that tells you what you might need to do when something is going wrong.  If the server is locking up when you are doing a parity check... you think that maybe doing a parity check should be avoided for right now.

 

This is extremely annoying and I am losing faith in this unRAID product, mostly because it's so unhelpful when troubleshooting an issue like this..  Should I just try replacing the drive even though it can't even complete a parity check on the old one?  What is my plan to troubleshoot this matter?

Like I mentioned above, we need more info.  There are a couple sticky threads that will tell you what we need to better help.

 

It's starting to get very irritating so any help would be greatly appreciated.

Usually any question asked we can help with.

 

PS:  the signup process to this forum is way annoying.  whats with the password restrictions and minimum sizes?  You really think people care about hacking your account on a support forum for unRAID?  Sheesh

You would be surprised.  The forum has had problems with spam and any measure taken to stop that is more than welcome to most members and especially us mods.

Hi, thanks for the reply so far

 

So if the server hard locks and I can't access it via http nor via the keyboard/server side itself to check the log files, is the previous log with errors stored anywhere after I reboot the system?  Because clicking 'Log' in the top right corner of the web interface only shows the log starting at the current system boot, it has no history of previous messages to try and troubleshoot this

 

What should I do?

 

Should I just try and pull that erroring parity drive out and replace it with this brand new 2TB drive I bought?  I haven't done anything yet because I thought trying to repair parity was the first step

 

Let me know, thanks again

 

cheers

Hi, thanks for the reply so far

 

So if the server hard locks and I can't access it via http nor via the keyboard/server side itself to check the log files, is the previous log with errors stored anywhere after I reboot the system?  Because clicking 'Log' in the top right corner of the web interface only shows the log starting at the current system boot, it has no history of previous messages to try and troubleshoot this

 

What should I do?

 

Should I just try and pull that erroring parity drive out and replace it with this brand new 2TB drive I bought?  I haven't done anything yet because I thought trying to repair parity was the first step

 

Let me know, thanks again

 

cheers

 

This does sounds like a drive problem but without a syslog, even the startup log will help, we can't give much advice.

 

Look here for instructions on how to capture a syslog as the machine is running.  The "tail" command is one that you need to run and then start the parity check.  Watch it run as the parity check approaches the point were it seems to fail.