Ubuntu Desktop 23.04 and 25.04: installation: animated progress bar, but no progress – systemd-journald crashes

grahamperrin · May 11, 2025, 9:54am

Ubuntu Version

25.04

Problem

Is it ever normal to have the blankness pictured below (the third photograph), after starting installation and then clicking the mystery icon above the progress bar, to the right?

If so: how long should I wait for something to appear?

The progress bar is animated.

I see occasional signs of activity at the USB memory stick from which I’m installing. It has an LED.

A backtrace appears before the desktop environment appears (first photo). I’m inclined to treat this as negligible, splash-related.

Given the crash of systemd-journald (second photo), should I assume that any number of things might fail as a consequence?

System information

HP Pavilion 15-ab252ne:

Core™ i7-6500U (2.5 GHz, 4 MB cache, 2 cores)
12 GB memory
1.8 T disk
Intel Skylake GT2 (HD Graphics 520) and NVIDIA GM108M (GeForce 940M)
HP Pavilion Notebook - 15-ab252ne (ENERGY STAR) Product Specifications | HP® Support

Photographs

Troubleshooting

Tried:

two different USB memory sticks
three different ports.

tea-for-one · May 11, 2025, 1:12pm

No, not normal

Yes, I would assume that the installation has thrown a wobbly

Which utility did you use to make your bootable installation USB?
When installing, did you choose anything other than default e.g. filesystem, partitions, encryption etc?

grahamperrin · May 11, 2025, 3:57pm

For both drives:

dd if=ubuntu-25.04-desktop-amd64.iso of=/dev/da4 bs=1M conv=sync status=progress

Both created on FreeBSD-CURRENT:

grahamperrin@mowa219-gjp4-zbook-freebsd ~> pkg which /bin/dd
/bin/dd was installed by package FreeBSD-runtime-15.snap20250509233319
grahamperrin@mowa219-gjp4-zbook-freebsd ~> uname -mvKU
FreeBSD 15.0-CURRENT main-n277198-8c7d193e3cbe GENERIC-NODEBUG amd64 1500042 1500042
grahamperrin@mowa219-gjp4-zbook-freebsd ~>

Earlier runs included:

attempted connections to Wi-Fi, at least one of which failed
the combination of LUKS + ZFS, just one of these attempts got no further than the passphrase dialogue (IIRC the response to clicking Next was as if I had left both fields blank).

The most recent run (pictured above) was simpler. IIRC my only variation from defaults was offline inclusion of third party software for NVIDIA etc…

From numerous attempts to install: there is a sense of randomness, so it’s possible that both memory sticks are comparably faulty, but my gut tells me that the causes of the problem lie elsewhere.

The photograph below was of attempted reproduction of the failure to proceed beyond the passphrase dialogue. Not reproducible at the time (and the pictured phrase was a one-off for test purposes).

grahamperrin · May 11, 2025, 4:07pm

Sorry, I forgot to mention a key point:

the pictured black/blankness is in response to me clicking the nondescript (non-labelled) command prompt icon below the area that’s blank.

In the absence of a description: I assume that clicking the icon is intended to reveal a console-like view of messages.

When I refrain from clicking the icon, I get:

the progress bar, animated
no progress beyond … splash texts and images, which, I guess, cycle endlessly.

Clicking the icon does toggle between the splashes and the blankness.

Maybe worth mentioning: all attempts include erasure of the entire disk (ignoring the presence of Windows).

Next up: I’ll use gdisk to clear the partition table before retrying an installation of the OS.

eeickmeyer · May 11, 2025, 4:37pm

Just an FYI, the progress bar doesn’t show actual progress. It’s merely meant to show that there is activity.

The official way of burning to a USB is via the following links:

I don’t see dd in any of those tutorials, so I’m thinking you might benefit from doing it using one of the officially-documented methods I linked above. Anything other than what I linked above is either third-party or outdated. I’m not sure we can support burning it via FreeBSD.

If systemd-journald is crashing, the most likely cause is a bad write-to-media or bad media.

grahamperrin · May 11, 2025, 4:42pm

dd is the norm on FreeBSD. It’s the recommended method for writing ISOs and other types of image to memory sticks – not for FreeBSD images alone. See for example https://www.freebsd.org/releases/14.2R/announce/.

dd(1)

eeickmeyer · May 11, 2025, 4:43pm

Not my point. My point is we cannot support burn methods from FreeBSD, even if it’s supported by them. The only ways we can support are shown in my links. That’s only because we only support Ubuntu here.

grahamperrin · May 11, 2025, 4:43pm

I’m not seeking support for the burn method, but thanks.

tea-for-one · May 11, 2025, 5:01pm

When you have successfully booted to a live session, you can use gparted to create a GPT (partition table) on your target disk.

Also, please heed the valuable advice from @eeickmeyer , there are many examples of failed installations due to the way the installation medium was created.

Anyway, fingers crossed and let’s see what happens

grahamperrin · May 11, 2025, 5:17pm

Thanks,

Quicker for me to use gdisk with what’s currently booted, but first, I’ll try installation without the table (already zapped).

I can try a third memory stick but trust me – please – about dd.

grahamperrin · May 11, 2025, 7:34pm

I tried ubuntu-25.04-desktop-amd64.iso with two more drives.

After problems with the fourth, I reused the first with an older image:

ubuntu-23.04-desktop-amd64.iso

After problems with that, I tried the 23.04 image with a fifth drive:

systemd-journald crashed before the installer appeared.

It’s possible that all five drives are faulty/marginal.

Maybe a problem with the notebook. I don’t suspect an issue with the HDD.

I’ll not have the notebook for long (background: https://redd.it/1kjs8qv). If anyone makes the issue reproducible with comparable hardware: please report a bug.

Thanks

For reference only:

a record of the two most recent writes to USB drives

root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # date 
Sun May 11 19:28:14 BST 2025
root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # geom disk list /dev/da4
Geom name: da4
Providers:
1. Name: da4
   Mediasize: 15518924800 (14G)
   Sectorsize: 512
   Mode: r0w0e0
   descr: Kingston DataTraveler 3.0
   ident: 08606E6D402DBF10471501BC
   rotationrate: unknown
   fwsectors: 63
   fwheads: 255

root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # dd if=./ubuntu-23.04-desktop-amd64.iso of=/dev/da4 bs=1M conv=sync status=progress
  4923064320 bytes (4923 MB, 4695 MiB) transferred 309.058s, 16 MB/s
4704+0 records in
4704+0 records out
4932501504 bytes transferred in 310.230638 secs (15899466 bytes/sec)
root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # cd
root@mowa219-gjp4-zbook-freebsd:~ # lsblk /dev/da4
DEVICE         MAJ:MIN SIZE TYPE                                    LABEL MOUNT
da4              1:77   14G GPT                                         - -
  da4p1          0:209 4.6G ms-basic-data                     gpt/ISO9660 /media/ISO9660
  da4p2          0:210 4.9M efi                             gpt/Appended2 -
  da4p3          0:211 300K ms-basic-data                        gpt/Gap1 -
  <FREE>         -:-   512B -                                           - -
root@mowa219-gjp4-zbook-freebsd:~ # gpart show /dev/da4
=>     64  9633481  da4  GPT  (14G) [CORRUPT]
       64  9622812    1  ms-basic-data  (4.6G)
  9622876    10068    2  efi  (4.9M)
  9632944      600    3  ms-basic-data  (300K)
  9633544        1       - free -  (512B)

root@mowa219-gjp4-zbook-freebsd:~ # tail -f -n 0 /var/log/messages
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: ugen0.15: <Kingston DataTraveler 3.0> at usbus0 (disconnected)
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: umass4: at uhub0, port 6, addr 23 (disconnected)
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: da4 at umass-sim4 bus 4 scbus9 target 0 lun 0
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: da4: <Kingston DataTraveler 3.0 PMAP>  s/n 08606E6D402DBF10471501BC detached
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: (da4:umass-sim4:4:0:0): Periph destroyed
May 11 19:38:46 mowa219-gjp4-zbook-freebsd kernel: umass4: detached
May 11 19:38:50 mowa219-gjp4-zbook-freebsd kernel: ugen0.15: <Kingston DataTraveler 3.0> at usbus0
May 11 19:38:50 mowa219-gjp4-zbook-freebsd kernel: umass4 on uhub0
May 11 19:38:50 mowa219-gjp4-zbook-freebsd kernel: umass4: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 24> on usbus0
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4 at umass-sim4 bus 4 scbus9 target 0 lun 0
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4: <Kingston DataTraveler 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4: Serial Number 08606E6D402DBF10471501BC
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4: 40.000MB/s transfers
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4: 14800MB (30310400 512 byte sectors)
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: da4: quirks=0x2<NO_6_BYTE>
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: (da4:umass-sim4:4:0:0): CACHE PAGE TOO SHORT data len 3 desc len 0
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: (da4:umass-sim4:4:0:0): Mode page 8 missing, disabling SYNCHRONIZE CACHE
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: GEOM: da4: the secondary GPT header is not in the last LBA.
May 11 19:38:51 mowa219-gjp4-zbook-freebsd kernel: GEOM: iso9660/Ubuntu%2023.04%20amd64: the secondary GPT header is not in the last LBA.
^C
root@mowa219-gjp4-zbook-freebsd:~ # lsblk /dev/da4
DEVICE         MAJ:MIN SIZE TYPE                                    LABEL MOUNT
da4              1:54   14G GPT                                         - -
  da4p1          1:55  4.6G ms-basic-data                     gpt/ISO9660 /media/ISO9660
  da4p2          1:56  4.9M efi                             gpt/Appended2 -
  da4p3          1:57  300K ms-basic-data                        gpt/Gap1 -
  <FREE>         -:-   512B -                                           - -
root@mowa219-gjp4-zbook-freebsd:~ # gpart show /dev/da4
=>     64  9633481  da4  GPT  (14G) [CORRUPT]
       64  9622812    1  ms-basic-data  (4.6G)
  9622876    10068    2  efi  (4.9M)
  9632944      600    3  ms-basic-data  (300K)
  9633544        1       - free -  (512B)

root@mowa219-gjp4-zbook-freebsd:~ # tail -f -n 0 /var/log/messages
May 11 19:54:49 mowa219-gjp4-zbook-freebsd kernel: ugen0.15: <Verbatim STORE N GO> at usbus0
May 11 19:54:49 mowa219-gjp4-zbook-freebsd kernel: umass4 on uhub0
May 11 19:54:49 mowa219-gjp4-zbook-freebsd kernel: umass4: <Verbatim STORE N GO, class 0/0, rev 2.00/1.00, addr 25> on usbus0
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4 at umass-sim4 bus 4 scbus9 target 0 lun 0
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4: <Verbatim STORE N GO PMAP> Removable Direct Access SPC-4 SCSI device
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4: Serial Number 90006B124620BD98
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4: 40.000MB/s transfers
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4: 7388MB (15130624 512 byte sectors)
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: da4: quirks=0x2<NO_6_BYTE>
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: (da4:umass-sim4:4:0:0): CACHE PAGE TOO SHORT data len 3 desc len 0
May 11 19:54:50 mowa219-gjp4-zbook-freebsd kernel: (da4:umass-sim4:4:0:0): Mode page 8 missing, disabling SYNCHRONIZE CACHE
^C
root@mowa219-gjp4-zbook-freebsd:~ # geom disk list /dev/da4
Geom name: da4
Providers:
1. Name: da4
   Mediasize: 7746879488 (7.2G)
   Sectorsize: 512
   Mode: r0w0e0
   descr: Verbatim STORE N GO
   ident: 90006B124620BD98
   rotationrate: unknown
   fwsectors: 63
   fwheads: 255

root@mowa219-gjp4-zbook-freebsd:~ # cd /media/t1000/VirtualBox/Linux/
root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # dd if=./ubuntu-23.04-desktop-amd64.iso of=/dev/da4 bs=1M conv=sync status=progress
  4932501504 bytes (4933 MB, 4704 MiB) transferred 1232.341s, 4003 kB/s
4704+0 records in
4704+0 records out
4932501504 bytes transferred in 1233.218608 secs (3999698 bytes/sec)
root@mowa219-gjp4-zbook-freebsd:/media/t1000/VirtualBox/Linux # exit
logout
grahamperrin@mowa219-gjp4-zbook-freebsd /u/h/grahamperrin>

grahamperrin · May 12, 2025, 8:52am

References:

statx(2) – get file status (extended)
systemd-journald(8) – journal service

ogra · May 12, 2025, 9:53am

Did you do an integrity check of the iso yet (there are checksum files in the download location to verify them)

grahamperrin · May 12, 2025, 10:12am

Thanks,

Done yesterday for ubuntu-25.04-desktop-amd64.iso (written to four drives).

IIRC not done for ubuntu-23.04-desktop-amd64.iso (written to two drives).

With a view to trying with alternative hardware: I’m rifling through a collection of old HP notebooks that are to be written off. Can’t find anything close to the Pavilion 15-ab252ne. Trying to get useful information from HP’s website is, too often, like pulling teeth. I’ll spare you the details

tea-for-one · May 12, 2025, 1:39pm

I get the impression that you are trying to re-purpose old laptops?

Do you have to use Ubuntu?
Often, Lubuntu or Xubuntu are more suitable for older devices?
https://ubuntu.com/desktop/flavors

grahamperrin · May 12, 2025, 3:15pm

In a nutshell:

my organisation will provide a new computer
I’ll take the opportunity to switch from FreeBSD to Linux
tested repeatedly in VirtualBox (Linux guest, FreeBSD host)
I want to test a handful of things on real hardware – anything that should be compatible with the distro – before arranging the new computer.

I chose Ubuntu for root-on-ZFS.

(Install Ubuntu, then switch to Kubuntu.)

rubi1200 · May 12, 2025, 3:44pm

I would like to suggest a different approach.

Note, I have not tested this and will only have time to do so later or tomorrow.

Instead of the Desktop edition, I would try installing with the Server edition.

Edit: at this stage I believe some magic needs to happen to set things up. I believe it is doable but not as easily as I thought.

Once installed successfully, then add the Kubuntu desktop:
sudo apt install kubuntu-desktop

grahamperrin · May 12, 2025, 4:07pm

That’s useful, thanks.

For now, I’ll continue with ubuntu-25.04-desktop-amd64.iso, maybe reach a proper conclusion.

rubi1200 · May 12, 2025, 4:33pm

I stand corrected, not sure this is possible with the server edition and I have limited knowledge in this area.

Perhaps @1fallen or @sgt-mike can offer some insights and tips.

1fallen · May 12, 2025, 5:52pm

Dose Kubuntu not support ZFS at install time?

Anyway this may be of interest:
https://medo64.com/posts/enctrypted-kubuntu-2410-with-zfs-and-hibernation/

NOTE: For partitions, He likes to have 4 of them. The first two partitions are unencrypted and in charge of booting (boot + EFI).

While I love encryption, I almost never encrypt the boot partitions in order to make my life easier as you cannot seamlessly integrate the boot partition password prompt with the later password prompt.

Thus encrypted boot would require you to type the password twice (or thrice if you decide to use native ZFS encryption on top of that).

Good Luck though @grahamperrin