very slow restart 9 minutes or longer

1st Official Post

    So OMV takes roughly 9 minutes to restart.

    i have a x64 computer built with intel i5 ans 16gb ram.

    OMV is on a kingston thumbdrive.

    it' a fresh install, well fresh in deceber.

    i have docker setup with 10 apps.

    i ran

    Code
    systemd-analyze blame

    here's the output


    Any ideas on how to sort this out?

    Post instead, after a reboot, the output of:


    systemd-analyze critical-chain


    As for what it's shown on your post, you can disable several services, if you don't use them:


    openmediavault-issue.service This is just to show the initial message on the CLI with the IP, etc


    wpa_supplicant.service Not needed if you don't use WiFi network.


    This will reduce some bits on the boot.

    so i ran

    Code
    apt remove --purge wpasupplicant -y

    big mistake as it appears, docker was removed, plugins removed.

    rebooted and now waiting.

    looks like i'm going to start from scratch. reinstall OMV

    Quote from HackitZ

    so i ran

    Why?

    I Said "disable services".

    Never said to uninstall any thing.

    Even less "to purge"

    That command just removed everything and purged the config of all the apps:

    This is a simulated output of what you did:



    You can try to reinstall OMV by running the install script but the config will probably empty.

    here is what it did.

    I've run this still working on it.

    Code
    apt update && apt install --reinstall openmediavault -y

omv-confdbadm populate

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

    I'll see what it looks like when it's down and i reinstall the plugins i had.

    ok i'm backup.

    i ran

    Code
    systemd-analyze critical-chain

    i disabled wpa_supplicant

    with

    Code
     systemctl disable --now wpa_supplicant.service
then
 systemctl status wpa_supplicant.service

    I know this will only save seconds.

    Just rebooted and i'm at 5:52 seconds from hitting ok on restart to the login page.

    Is that standard in omv 7?

    before my system crashed last spring i kinda remewber a restart taking at most 2 minutes.

    am i wasting my time here worrying aboutn this?

    this is what started to me to think i should go back to an ssd drive.


    it's is better though, heres the output of

    Code
    systemd-analyze blame

    comparted to before it seems much better, not sure system-analyze blame is thre best command for this kind of issue.

    Only 2x services are taking up time:

    Quote from HackitZ

    openmediavault-issue.service @1min 19.920s +17.699s

    +17secs

    Quote from HackitZ

    systemd-networkd-wait-online.service @12.454s +1min 7.444s

    +1min 7secs


    You can disable issue services with:

    systemctl disable openmediavault-issue.service

    systemctl stop openmediavault-issue.service


    As for wait-online service, which hardware are you on?

    Thanks Soma for taking the time.

    It's a computer i built, intel, i5, 16gb ram, asus board. i bought the hardware in the summer.

    i'lll try those to steps.

    Thanks again

    rebooted

    new time, 5:12


    is this roughly the same for you? am i being unrealistic?

    suppose if it's working i should just leave well enough alone.

    Never timed it, and never gave much thought to it.


    The systemd-analyze critical-chain gives me a bit less than 2min so, it's enough for me.


    The GUI takes some more time after that to come up but I don't have any rush.

  • HackitZ

    Added the Label resolved
    • Official Post
    Quote from HackitZ

    apt remove --purge wpasupplicant -y

    You should never use the -y option. With that you have no chance to check what is going to happen and stop the execution.

    Without it, you will be asked if you want to continue. Before that you can read which packages are going to be removed if you press "y".

    Quote from zakk87

    Kingston is the problem

    Care to develop?

    I also use Kingston thumb drives and see no issues with them.

    Namely datatraveller modelo with RW 200/60MB/s

    DataTraveler Kyson USB Flash Drive – 64GB - 512GB - Kingston Technology
    DataTraveler Kyson is a high-performance USB flash drive with extremely fast transfer speeds of up to 512GB of storage with stylish metal casing and capless…
    www.kingston.com


    More than enough for a OS drive that runs on RAM.

    The author did not write what model it is. Most kingston memory is 100MB/s ro / 5MB/s rw and they cause problems. I am happy that you are an informed user of high end Kingston but the author may have an exodia g2/M where the read/write drops 80% and doesn't like small files.

    I think we need the hdparm test and, above all, the model name.

    [CoolerMaster ELITE 110] [J1900I-C] [4GB RAM] [Samsung 2xHD103UJ + Hitachi 5K3000 2TB + 2xToshiba P300 HDWD130 3TB]

    Quote from HackitZ

    so i ran

    Code
    apt remove --purge wpasupplicant -y

    big mistake as it appears, docker was removed, plugins removed.

    rebooted and now waiting.

    looks like i'm going to start from scratch. reinstall OMV

    As you have found out, using the -y option is what hosed you.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Like 1

Participate now!

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

Register Yourself Login