Dietpi - hanging on restart

General Discussion
1

when I was testing my application to run on rasp-pi-4 8gb, via hp -usb drive
everything was working good i.e
quick boot,
plymouth animated splash screens,
and when I did reboot, it showed splash screen too for some time

but now my hands are on rasp-pi-4 1gb, via same ht -usb drive
but
boot is lagging and showing mmc1: Controller never released inhibit bit(s) for quite a while and
after that, it just shows one image from the animated splash screen for like 10s
and then it starts my application
also when i reboot, splash screen is fully gone

and surprisingly my entire boot process is taking 3-4 mins

1 Like
2

What do these report?

systemd-analyze blame
systemd-analyze critical-chain
3

systemd-analyze blame

returns this:

~# systemd-analyze blame
1min 23.810s ifup@eth0.service
1min 12.263s plymouth-quit-wait.service
     27.438s ssh.service
     21.268s plymouth-quit.service
     14.638s ifup@wlan0.service
      7.184s systemd-user-sessions.service
      4.153s dev-sda2.device
      3.642s ifupdown-pre.service
      1.579s rpi-eeprom-update.service
       823ms plymouth-start.service
       753ms boot.mount
       714ms systemd-sysusers.service
       710ms systemd-random-seed.service
       672ms systemd-udev-trigger.service
       635ms keyboard-setup.service
       634ms networking.service
       625ms systemd-fsck-root.service
       617ms user@0.service
       617ms systemd-logind.service
       598ms dbus.service
       593ms dietpi-ramlog.service
       408ms fake-hwclock.service
       305ms modprobe@drm.service
       270ms dietpi-preboot.service
       263ms systemd-udevd.service
       252ms systemd-journald.service
       232ms systemd-fsck@dev-disk-by\x2dpartuuid-e87e153f\x2d01.service
       216ms systemd-sysctl.service
       210ms dev-mqueue.mount
       207ms sys-kernel-debug.mount
       205ms sys-kernel-tracing.mount
       200ms systemd-modules-load.service
       150ms systemd-remount-fs.service
       145ms modprobe@fuse.service
       145ms systemd-timesyncd.service
       130ms kmod-static-nodes.service
       130ms modprobe@configfs.service
       100ms user-runtime-dir@0.service
        82ms var-swap.swap
        79ms systemd-tmpfiles-setup.service
        72ms systemd-rfkill.service
        68ms systemd-update-utmp-runlevel.service
        64ms systemd-tmpfiles-setup-dev.service
        64ms systemd-binfmt.service
        34ms console-setup.service
        33ms systemd-journal-flush.service
        32ms alsa-restore.service
        29ms systemd-update-utmp.service
        28ms proc-sys-fs-binfmt_misc.mount
        23ms plymouth-read-write.service
        16ms modprobe@dm_mod.service
        14ms modprobe@efi_pstore.service
        12ms modprobe@loop.service
        11ms tmp.mount
         9ms sys-fs-fuse-connections.mount
         9ms sys-kernel-config.mount
         8ms var-log.mount

and systemd-analyze critical-chain returns:

:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2min 58.798s
└─multi-user.target @2min 58.798s
  └─getty.target @2min 58.798s
    └─getty@tty1.service @2min 58.796s
      └─plymouth-quit-wait.service @1min 46.509s +1min 12.263s
        └─systemd-user-sessions.service @1min 38.479s +7.184s
          └─network.target @1min 32.286s
            └─ifup@eth0.service @8.228s +1min 23.810s
              └─network-pre.target @8.184s
                └─dietpi-preboot.service @7.912s +270ms
                  └─dietpi-ramlog.service @7.282s +593ms
                    └─basic.target @7.231s
                      └─sockets.target @7.230s
                        └─dbus.socket @7.230s
                          └─sysinit.target @7.222s
                            └─systemd-timesyncd.service @7.076s +145ms
                              └─systemd-tmpfiles-setup.service @6.975s +79ms
                                └─local-fs.target @6.922s
                                  └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @6.984s
                                    └─local-fs-pre.target @3.025s
                                      └─systemd-tmpfiles-setup-dev.service @2.960s +64ms
                                        └─systemd-sysusers.service @2.229s +714ms
                                          └─systemd-remount-fs.service @2.068s +150ms
                                            └─systemd-fsck-root.service @1.407s +625ms
                                              └─systemd-journald.socket @1.290s
                                                └─-.mount @1.252s
                                                  └─-.slice @1.252s

and I don’t want it to wait for any internet, just start plymouth animation i have setup correctly and that is it.

4

Did you tried setting STATIC IP instead of DHCP

5

Yes, if you have setup the network interface to negotiate with DHCP, but there is no DHCP server available, the network will delay until it times out.
The other option is to disable the network waiting during boot. From dietpi-config option 8, switch off boot wait for network.
However there is a caveat if some service doesn’t find any interface IP available it may not bind to any and eventually not start.

6

so I tried using static IP yesterday
and things broke

cz it is not my server that is running on rasp-pi
it is actual product running on pi

and i save a network with a specific name and credentials and give my user to set as their hotspot cred and then when they are in proximity of pi, the sync-engine within the application start to fetch updates from the main server

so on boot, i don’t want it to wait for network, but it should connect to that specific wifi credentials when its admin is near it.

7

Then go for the second option not to wait for network during boot.