In this case, only press the power to shut down, restart can start normally . why?
Env: * Windows 11 + ubuntu24 dual system
Linux servers 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
VMC
January 20, 2025, 4:07pm
2
Where did you get this message? Did you Ubuntu ever boot normally. How did you build your system: Windows, then Ubuntu, or visaversa.
Also, give us you hardware. Maybe someone else has then same system.
popey
January 20, 2025, 4:11pm
3
Given @tianyazi other posts , I suspect this is a Xiaomi Redmi notebook model: XMA1903-DA.
Timed out for waiting the udev queue being empty
The above may be a clue.
Do you have other devices attached e.g. usb storage, dongles etc?
Remove all peripheral devices and see if the PC boots cleanly.
If you see the (initramfs)
prompt again, type exit
Any messages?
2 Likes
Brand : Redmi Book 16 pro 2024,
Model :Y3519
Hardware :Intel(R) Core™ Ultra 5 125H, Intel® ARC™ Graphics
usb storage, usb mouse, modongles etc → All removal, it will happen, there is just no way of knowing when it will happen.
Windows 11 and ubuntu24.04 are physically installed, and the system starts with the ubuntu24.04 system by default.
VMC
January 22, 2025, 5:18pm
6
What does “systemd-analyze blame” show?
Note: When entering initramfs automatically, it is found that the display content is different, the solution is the same, shut down, and then boot up to enter the desktop system normally.
ubuntu@servers:~$ systemd-analyze blame
33.601s docker.service
3.845s NetworkManager-wait-online.service
3.022s apt-daily-upgrade.service
1.272s snapd.seeded.service
1.228s snapd.service
1.095s logrotate.service
923ms vboxdrv.service
776ms NetworkManager.service
328ms apport.service
292ms thermald.service
237ms containerd.service
219ms dev-nvme0n1p9.device
219ms postgresql.service
218ms udisks2.service
195ms accounts-daemon.service
176ms cups.service
166ms gnome-remote-desktop.service
163ms iio-sensor-proxy.service
158ms snapd.apparmor.service
155ms power-profiles-daemon.service
153ms polkit.service
144ms user@1000.service
141ms lightdm.service
140ms plymouth-quit-wait.service
138ms avahi-daemon.service
137ms bluetooth.service
131ms dbus.service
123ms dpkg-db-backup.service
121ms gpu-manager.service
114ms switcheroo-control.service
112ms dev-loop6.device
108ms dev-loop5.device
107ms dev-loop1.device
104ms dev-loop3.device
102ms dev-loop7.device
102ms dev-loop2.device
97ms dev-loop4.device
97ms ModemManager.service
93ms rsyslog.service
91ms grub-common.service
87ms lm-sensors.service
77ms bolt.service
71ms systemd-udev-trigger.service
68ms systemd-journal-flush.service
68ms dev-loop0.device
68ms slapd.service
63ms dev-loop12.device
62ms update-notifier-download.service
62ms dev-loop16.device
61ms dev-loop17.device
60ms dev-loop13.device
60ms upower.service
60ms dev-loop8.device
59ms dev-loop14.device
59ms dev-loop15.device
59ms dev-loop11.device
58ms dev-loop10.device
57ms dev-loop9.device
55ms apparmor.service
52ms systemd-logind.service
48ms systemd-resolved.service
44ms systemd-udevd.service
41ms systemd-random-seed.service
40ms plymouth-start.service
38ms systemd-sysctl.service
38ms grub-initrd-fallback.service
37ms colord.service
34ms systemd-tmpfiles-setup.service
32ms keyboard-setup.service
31ms snap-bare-5.mount
30ms e2scrub_reap.service
29ms snap-core22-1722.mount
28ms systemd-modules-load.service
27ms snap-core22-1748.mount
26ms systemd-fsck@dev-disk-by\x2duuid-3AE1\x2dF0FD.service
24ms systemd-journald.service
24ms systemd-timesyncd.service
24ms snap-firefox-5647.mount
23ms systemd-tmpfiles-clean.service
23ms snap-firefox-5701.mount
22ms snap-gnome\x2d42\x2d2204-176.mount
21ms ssh.service
21ms snap-gnome\x2d42\x2d2204-202.mount
20ms snap-gtk\x2dcommon\x2dthemes-1535.mount
19ms snap-snap\x2dstore-1173.mount
18ms docker.socket
18ms snap-snap\x2dstore-1218.mount
17ms systemd-remount-fs.service
16ms wpa_supplicant.service
16ms snap-snapd-23258.mount
15ms snap-snapd-23545.mount
14ms systemd-tmpfiles-setup-dev-early.service
14ms systemd-binfmt.service
14ms plymouth-read-write.service
13ms sysstat.service
13ms snap-snapd\x2ddesktop\x2dintegration-178.mount
13ms kerneloops.service
12ms dev-hugepages.mount
12ms snap-snapd\x2ddesktop\x2dintegration-253.mount
12ms dev-mqueue.mount
11ms sys-kernel-debug.mount
11ms snap-thunderbird-634.mount
10ms sys-kernel-tracing.mount
10ms alsa-restore.service
10ms rtkit-daemon.service
10ms systemd-rfkill.service
9ms snap-thunderbird-609.mount
8ms boot-efi.mount
7ms kmod-static-nodes.service
7ms modprobe@dm_mod.service
7ms modprobe@configfs.service
7ms snap-ubuntu\x2dbudgie\x2dwelcome-518.mount
7ms systemd-tmpfiles-setup-dev.service
7ms modprobe@efi_pstore.service
7ms snap-ubuntu\x2dbudgie\x2dwelcome-536.mount
6ms modprobe@drm.service
6ms vboxweb-service.service
6ms user-runtime-dir@1000.service
6ms vboxautostart-service.service
6ms modprobe@loop.service
6ms proc-sys-fs-binfmt_misc.mount
6ms console-setup.service
6ms vboxballoonctrl-service.service
5ms sysstat-collect.service
5ms systemd-update-utmp-runlevel.service
5ms modprobe@fuse.service
5ms swap.img.swap
5ms systemd-backlight@backlight:intel_backlight.service
5ms systemd-update-utmp.service
4ms sys-fs-fuse-connections.mount
4ms gdm3.service
4ms openvpn.service
4ms systemd-user-sessions.service
3ms setvtrgb.service
2ms sys-kernel-config.mount
2ms ufw.service
1ms snapd.socket
When you arrive at the (initramfs)
prompt, did you type exit
Any messages?