Hi,
my OMV NAS crashes and I hope it's known issue.
BUG: Unable to handle kernel NULL dereference at 000000000XX
Any ideas how to start troubleshooting? Should I try a different kernel at boot?
Hi,
my OMV NAS crashes and I hope it's known issue.
BUG: Unable to handle kernel NULL dereference at 000000000XX
Any ideas how to start troubleshooting? Should I try a different kernel at boot?
What motherboard? Have you updated the bios?
What motherboard? Have you updated the bios?
AsRock H370M-ITX/ac
I had the problem before and exchanged the motherboard, because I thought it was the reason. The new one would offer me a BIOS update, but the old one was running on the new BIOS and had the same issue. I just exchanged the RAM module, because I had another one lying around... Maybe that helps.
Any other ideas?
Any other ideas?
If you can get it to boot with an older kernel, I would use omv-extras to install the proxmox kernel. If you want to test ahead of time, just boot an Ubuntu 18.04 iso. This is the same kernel for the most part.
If you can get it to boot with an older kernel, I would use omv-extras to install the proxmox kernel. If you want to test ahead of time, just boot an Ubuntu 18.04 iso. This is the same kernel for the most part.
The NAS was not crashing the last 3 days, but I noticed some error messages in the syslog this morning. Any idea what exactly they could mean?
Also the rrdcached process has/had a problem starting up, when I restarted the NAS today. I can also provide the syslog if that helps.
The NAS was not crashing the last 3 days, but I noticed some error messages in the syslog this morning. Any idea what exactly they could mean?
OMV's engine is segfaulting. Not good. Your system keeps running because monit restarts the engine. Have you ran memtest on this system? A php app typically should not segfault.
Also the rrdcached process has/had a problem starting up, when I restarted the NAS today. I can also provide the syslog if that helps.
I'm guessing it is related to the engine segfaulting. Sounds like bad memory or something kernel related.
Seems like it was the virtualbox plugin. I deactivated it and syslog looks much better now... Maybe a reinstall will help
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!