unRAID 6.3.5 has been working great for the last week. But today, while copying files onto the array, it suddenly froze.

 

I could still ping it from the command prompt, but I could no longer access the webGUI nor the SMB shares.

 

I had to do a hard reboot to get unRAID up and running again. Now it started a parity check on its own.

Attached is a screenshot that I took from the unRAID monitor and the logs. Anyone an idea what happened there?

nas-diagnostics-20171202-1613.zip

Edited December 2, 20178 yr by cholzer

anyone an idea where I can find the reason for the freeze in the log? i looked through the files but I am not sure why it happened.

The syslog starts over after evety reboot, so unfortunately it doesn't tell much of any previous issues.

13 hours ago, johnnie.black said:

The syslog starts over after evety reboot, so unfortunately it doesn't tell much of any previous issues.

Hey, thanks for your reply!

 

So what you are saying is that whenever unRAID is restarted we lose all logs, right?

 

Is there an (debug) option to prevent that? Otherwise how does someone find the cause of freezes, crashes and random reboots? :-/

Try the fix common problems plugin in troubleshooting mode.

The really critical errors are normally emitted to the console so it's always interesting to have a monitor connected. Logging to console will work even if the file system layer has broken in the Linux kernel.

2 hours ago, pwm said:

The really critical errors are normally emitted to the console so it's always interesting to have a monitor connected. Logging to console will work even if the file system layer has broken in the Linux kernel.

 

The screenshot I provided in the first post does not help to track down the cause of my unRAID freeze though. Or?

3 hours ago, johnnie.black said:

Try the fix common problems plugin in troubleshooting mode.

 

Just what I needed, thanks!

 

Quote

When running in this mode the syslog is continually captured to the flash drive, and a diagnostics dump is performed every 30 minutes

 

1 hour ago, cholzer said:

 

The screenshot I provided in the first post does not help to track down the cause of my unRAID freeze though. Or?

No, the screenshot is from the boot - a screenshot before the reboot might possibly have contained any critical errors.

5 minutes ago, pwm said:

No, the screenshot is from the boot - a screenshot before the reboot might possibly have contained any critical errors.

 

The screenshot was taken when unRAID was in the frozen state. It was *not* taken after the forced reboot.

OK. Then it never emitted any critical error when it locked up.

 

The only line it emitted after it had started up was the last part of the last line. After the login prompt, it emitted that it had stopped PID 7747. But that isn't an error message.

 

But it's fully possible for a machine to freeze without emitting error messages too - it's just a question if some part of the Linux code has time to spot any error or not.

29 minutes ago, pwm said:

OK. Then it never emitted any critical error when it locked up.

 

The only line it emitted after it had started up was the last part of the last line. After the login prompt, it emitted that it had stopped PID 7747. But that isn't an error message.

 

But it's fully possible for a machine to freeze without emitting error messages too - it's just a question if some part of the Linux code has time to spot any error or not.

 

Yeah it responded to a ping, but neither the webGUI nor SMB worked.

The console did not respond to the keyboard either.

A quick followup.

I have created a cron job to reboot the system one per week and since I done that I did not have a single freeze!