Installed on new HW - no shutdown anymore

1st Official Post
    • New

    Hi everyone.


    I had OMV installed for a long time on a sff 1 liter acer n4630g and all worked well but i wanted a new setup do be able to do hw encode in jellyfin.

    So i installed latest stable omv on a MSI B250 mobo with a I3 7100.

    I have the bios updated to the latest version.


    What is weird is that on this new system shutdown does not work correctly anymore.

    On selecting shutdown from the webui, it stops spinning the hdd but fans, leds, etc stay on.

    In this state, if i long press the power button it turns completely off and after 2-3 sec it turns back on again ...

    I have to unplug from the mains tot turn it off.


    Short pressing the power button while the unit is on does nothing ....


    Mobo info:

    # dmidecode 3.4

    Getting SMBIOS data from sysfs.

    SMBIOS 3.0 present.


    Handle 0x0002, DMI type 2, 15 bytes

    Base Board Information

    Manufacturer: MSI

    Product Name: B250M PRO-VDH (MS-7A70)

    Version: 2.0

    Serial Number: H516321385

    Asset Tag: Default string

    Features:

    Board is a hosting board

    Board is replaceable

    Location In Chassis: Default string

    Chassis Handle: 0x0003

    Type: Motherboard

    Contained Object Handles: 0


    Doing a shutdown -h now from local terminal does shutdown correctly the system.

    Can anyone help me figure this out ?


    Thanks.

    • New
    Quote

    Doing a shutdown -h now from local terminal does shutdown correctly the system.

    Tried shutdown -h now from WeTTY.

    It did not shut down completely ...

    • New
    Quote from Jon_Doe

    shutdown -h now

    Why the -h flag on the command?

    There's only -H that leaves the system halted.


    Use only the now instruction or a timed value and see how it works

    • New
    • Official Post
    Quote from Soma

    Why the -h flag on the command?

    -h means --poweroff. I always use shutdown -h now when shutting down a system. OMV uses systemctl poweroff when you use the shutdown in the web interface.

    omv 7.7.5-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.2 | compose 7.4.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1
    • New

    Also tried on local tty systemctl poweroff and the system did not shut down completely.

    Is there something, some tool, i can try to debug this ?

    • New
    • Official Post

    Almost has to be a setting in your bios. Watching a monitor plugged into the system when shutting down is the easiest way to maybe get more info. Otherwise, look into your bios settings.

    omv 7.7.5-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.2 | compose 7.4.5 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    I've searched the bios and only thing i found in relation with power management was ERP which has no effect on the issue if it's enabled or disabled.

    • New
    • Official Post

    Search the log for error messages related to power settings. It might help if you find anything. Look at the part where the system boots up.

    • New

    I have looked at dmesg and there are no errors or warnings.

    Same for journalctl --list-boots and journalctl -b -1

    There are no errors or warnings for ACPI ....


    journalctl -b -1 says at the end it reached target shutdown, all is off, all is fine.

    Except it's not completely off.


    So if it's a bios issue there are no settings to toggle ...

    The only infuriating thing is that Windows worked (of course) perfectly.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login