Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live Desktop on USB stick boots so slowly that I gave up #3090

Open
patogit opened this issue Apr 8, 2024 · 9 comments
Open

Live Desktop on USB stick boots so slowly that I gave up #3090

patogit opened this issue Apr 8, 2024 · 9 comments
Labels

Comments

@patogit
Copy link

patogit commented Apr 8, 2024

Clear Linux versions:

41180 and 41270, both behave the same

Steps to reproduce:

  • Read the documentation.
  • Download Clear Linux ISO.
  • Verify checksum of ISO file.
  • Use Popsicle USB Flasher in Pop OS to put the ISO on a 16 GB SanDisk Extreme USB 3 stick that I have used for countless other GNU/Linux installations.
  • Boot the Thinkpad T470 or T470s from the USB stick.
  • Watch text fly by for 6.8 seconds, and then wait about 30 seconds between all of subsequent messages.
    • [6.8] switch_root:
    • [6.8] failed to unlink mnt
    • [6.8] : Directory not empty
    • [37.6] systemd[1]: systemd 255 running in system mode (+PAM +AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 -IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK -PCRE2 +PWQUALITY +P11KIT -QRENCODE +TMP2 +BZIP2 -LZ4 -XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=hybrid)
    • [37.6] systemd[1]: Detected architecture x86-64.
    • [67.7] systemd[1]: Hostname set to .
    • [68.1] systemd-gpt-auto-generator[304]: EFI loader partition unknown, exiting.
    • [68.1] systemd-gpt-auto-generator[304]: (The boot loader did not set FEI variable LoaderDevicePartUUID.)
    • [98.5] systemd[1]: Queued start job for default target graphical.target.
    • [98.5] systemd[1]: Created slice system-getty.slice.
  • From there, the boot keeps moving along slowly. I'm copying this by hand, and none of the text looks important to copy here. The verbs are: created, started, set up, expecting, reached, listening, skipped, listening, mounting, starting. I had enough patience to get to [914.0] systemd[1]: starting systemd-journald.service...

Expected outcome:

Every other GNU/Linux distro I have booted from a USB stick during the past 15 years takes maybe 60 seconds to boot. The slow ones maybe 120 seconds. This is going more than 15 minutes and still has not finished booting.

@fenrus75
Copy link
Contributor

fenrus75 commented Apr 8, 2024 via email

@Aqua1ung
Copy link

Aqua1ung commented Apr 9, 2024

Switch to Ventoy. Works wonderfully. Fast and everything.

@patogit
Copy link
Author

patogit commented Apr 9, 2024

hmm please consider using the img not the iso

@fenrus75 , my USB stick is 16 GB (Popsicle says 14.9 GiB). The .img is 16.1 GB (Popsicle says 15.0 GiB), so that won't fit on my USB stick. That leaves me with the question, Why publish the ISO if it doesn't work? Why is this booting so slowly?

Switch to Ventoy. Works wonderfully. Fast and everything.

@Aqua1ung , my problem isn't about flashing the USB, it's about booting the operating system from the USB. I flashed the same USB stick with the same software two days ago with a Bluefin ISO, and it booted fine.

@Aqua1ung
Copy link

Aqua1ung commented Apr 9, 2024

my problem isn't about flashing the USB, it's about booting the operating system from the USB.

Yes, that is what Ventoy does.

@patogit
Copy link
Author

patogit commented Apr 10, 2024

@Aqua1ung as I mentioned, I have no problem making a USB from any other distro and booting it successfully. However, just to be complete and follow the suggestions here, I installed Ventoy on my USB, copied the version 41270 ISO to the USB, booted that, and got exactly the same result as before: an incredibly slow boot process.

I was really looking forward to using Clear Linux, but I can't get it to boot from USB or in a VM or in a Distrobox, so for now, I am leaving behind Clear Linux. I hope it works someday, as it seems like a very well designed distro.

@xanscale
Copy link

xanscale commented Apr 14, 2024

same problem here
thinkpad X395
v. 41530

any news?

EDIT: same USB stick on my desktop boot without problem, on thinkpad not

@c13-github
Copy link

I'm not yet an experienced CLOS user nor tinkerer but I saw this looking for helpful material on #2830 and #3146 on and was surprised. On Alma 8.1 using Gnome Boxes on a core i5-7300U with 5GB vRAM I boot CLOS well within expected timeframes. This was to the live desktop. An issue occurring for me was during live install minimum disk free (20GB) was not met.

I have seen what @patogit describes as excessive boot time with a Fedora based rolling spin (Nobara). Its community support thought that was likely due to a Gnome-boxes issue and didn't believe it affected flashed ISO media bootups into their live OS. Only that particular spin release was impacted and it falls in the the same kernel release timeframe (6.6-6.8).

Perhaps in PopOS, CL*OS desired release (iSO for sure if it exists, .img not sure) can be spun up in a Gnome Box to reevaluate?

If there's a performance increase seen on a T46, then booting of CLOS from duplicated CLOS ISO media (now supplied on a different cadence since release 41810 it appears) may have implications re. flash itself (durability+IOPS). If CL*OS has any basis in Fedora whatsoever (only mentioning this because of dnf and rpm usage alluded to in guides) that would an interesting find.

@karroziv
Copy link

I'm getting the same problem with my USB. At the same time, the same flash drive works well on my older laptop. Maybe something is wrong with my BIOS settings, I do not know.
Motherboard- MSI MAG B760 TOMAHAWK
laptop - GL83-75D
(When specified in the BIOS, booting from a USB flash leads to the same thing)

@minas1618033
Copy link

I try it on my 2 PC, use Ventoy to boot installation media.
Quickly mount and load to ready on A ( R5 5600 + MSI B350M MORTAR )
And getting the same problem on B ( i7 14700 + MSI MAG Z790 TOMAHAWK MAX ), the installer still not ready after loading over 3 hours.

Final I found the temp solution at #3141
After I edit boot parameter, the installer load normally. Maybe you can try.

@ephut ephut removed the new label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants