OMV Reboots on Shutdown after upgrade from Sardaukar to Stone Burner

Hi all - I am a first time poster. I have my OMV NAS set up so that it turns itself on (via a BIOS setting) at 7 AM (EST US) every morning, and then I have a Scheduled Job set up under Power Management that shuts down the NAS at 10:00 AM (EST US). I recently upgraded to Stone Burner (2.1.19), and now the machine reboots instead of shutting down at 10:00 AM.I have to go in through the Web GUI to manually shut down the machine, and, even using that method, it takes 5 or 6 tries until the machine shuts down and remains off. It did not exhibit this behavior under the prior release.

In order to rule out a bad Power Supply Unit, I booted my OMV NAS to a "Live" version of Ubuntu several times, and confirmed that the shutdown in Ubuntu turns off the machine properly, and there is not unexpected reboot.

Any thoughts on what might cause this?

Thanks!

Thanks for the quick response! I'm a bit of a noob - I used putty.exe to SSH into my OMV, and tried to execute the lspci command, and it tells me that lspci is not found. Is there another method I should be using?

Also, I did confirm through the OMV GUI that WOL is disabled. Should it also be disabled in the BIOS?

Ok thanks - installed the PCI utilities and ran lspci -nn. Result:

02:00.0 Ethernet Controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)

It is indeed a Realtek (onboard) NIC.

Thanks - I verified that "PME Event Wakeup" is disabled in the BIOS, so that doesn't seem to be the problem. I was hoping to avoid swapping out the PSU, but I'm thinking that's the way to go at this point, to rule out that it's a bad PSU. I'll report back if that doesn't fix it.

Thanks!

I tried swapping out my PSU - the problem persists. I'm thinking a fresh install is in order - I'll probably wait for 3.x. Thanks

A final update - I tried disabling the Realtek NIC in the BIOS, and installing an old SMC fast ethernet NIC in one of the PCI slots. I reinstalled OMV, and, while it configured and used the SMC NIC, it made no difference with the rebooting on shutdown. I ultimately swapped out the motherboard for a motherboard with an onboard Broadcom AC131 fast Ethernet NIC. That solved the rebooting problem.

The bad news is I downgraded from gigabit Ethernet to fast Ethernet - the good news is OMV had no problem retaining all the existing data on my media drives through the reinstallation (3 SATA drives of various capacity configured in linear RAID) - I simply left the data drives disconnected during the OMV reinstall to my OS drive, reconnected them after the install, and remounted the shares.

I will probably pick up a new NIC to get back to gigabit speeds - ANY brand except Realtek.

I've successfully run Volker's version of FreeNAS and all prior versions of OpenMediaVault on a variety of processors, both Intel (Atom) and AMD (Sempron 140 Sargas and an Athlon X2 4850e),all on consumer grade motherboards. 2 out of 3 of those motherboards (including the Foxconn board that the Intel Atom is running on) have Realtek onboard NICs.

My OMV needs are modest, and have been served well by modest hardware, both in the Intel and AMD family. I am successfully up and running again on an ECS/AMD motherboard/processor combo - the lowly and inexpensive ECS board is over 6 years old, having been operated as a FreeNAS, a Windows desktop machine, and finally back in service as an OMV NAS to rectify the current NIC reboot issue - so my own experience leads me to believe that the AMD processor is not implicated in this case.

The OMV software is fantastic, as are the support forums. I suspect a number of OMV users are running onboard Realtek NICs, and potentially a subsequent release may fix my issue. I didn't find it a headache to swap motherboards, and certainly hope I didn't waste anyone's time - I received nearly instantaneous and excellent response, with forum members quickly identifying the Realtek NIC as the root cause - I would hope that relating my experience is viewed as building the knowledge base, not wasting anyone's time. Thanks all.