[SOLVED] LTS Kernel update system hangs on Started Host Name

USPMAN1.3 · 2023-07-17 04:50:36

I’m able to get into a tty.

I tried to update grub it updated but didn’t fix it

I tried disabling sddm and enabling light dm back and forth. Didn’t work

I tried startx and got an error.

I’m posting a pic of the log file where there are errors.

The file is /var/log/Xorg.0.log

https://ibb.co/XWD1hzG

Thanks in advance!

EDIT:
Make sure mkinitcpio is installed!!!

Last edited by USPMAN1.3 (2023-07-17 22:06:56)

seth · 2023-07-17 06:23:59

Don't post pictures of parts of text, post the text.

cat /var/log/Xorg.0.log | curl -F 'f:1=<-' ix.io

USPMAN1.3 · 2023-07-17 06:51:11

Says can’t resolve host.

I am hardwired in too

seth · 2023-07-17 06:59:41

Compare "uname -a" and "pacman -Q linux-lts", exact same number?

USPMAN1.3 · 2023-07-17 07:10:09

Uname says 6.1.38-1-lts

And Pac-Man says Linux-lts 6.1.38-2

seth · 2023-07-17 07:13:47

You either updated w/o a reboot or forgot to mount the /boot partition before updating.
W/ the symptoms, the latter is more likely.
In that case, mount the /boot partition and re-install the kernel.

cat /proc/cmdline

what is BOOT_IMAGE set to (exactly)?

USPMAN1.3 · 2023-07-17 07:21:34

/boot/vmlinuz-linux-lts root=UUID with many characters
Then rw nowatchdog nvme=load=yes loglevel=3

USPMAN1.3 · 2023-07-17 07:30:22

I made sure my HDD (only one on laptop) and listed in fdisk was mounted to /boot
When I run xinit

The father server error is EE no screens found EE

seth · 2023-07-17 07:35:45

You're not booting from any /boot partition
What's mounted to /boot when you run xinit is irrelevant, what matters is where the kernel udpates went.
Your x11 and network issues are most likely merely an outfall of that.

USPMAN1.3 · 2023-07-17 07:38:48

HALF-SOLVED:

I went into my pkg cache and downgraded to the last lts kernel.

Boots fine now…

Thanks for your help it got me thinking of the things needed to do.

In the future when I upgrade the kernel. What exactly do I do after?

I’m running systemd with grub2

Last edited by USPMAN1.3 (2023-07-17 15:19:11)

seth · 2023-07-17 12:49:32

jasonwryan wrote:

No, it didn't "fix" anything. It just shifted the brokeness one space to the right.

Post your /etc/fstab and the output of "mount".

USPMAN1.3 · 2023-07-17 15:19:00

I agree I did not fix anything...

I just reverted the Kernel, and when I try to update the kernel, and use the update-grub AUR package, it says the grub gets updated however, it simply doesn't work, and will fail to boot, and the only way around it is to downgrade via the pkg cache.

Here is the outputs:

https://pastebin.com/gPGUkRGZ

seth · 2023-07-17 15:53:04

UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 /boot              ext4    defaults,noatime 0 1
/dev/nvme0n1p1 on /boot type ext4 (rw,noatime)

You're not booting from there, comment the line in the fstab, "umount /boot" and re-install/update the kernel again.

USPMAN1.3 · 2023-07-17 16:12:01

seth wrote:

UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 /boot              ext4    defaults,noatime 0 1
/dev/nvme0n1p1 on /boot type ext4 (rw,noatime)
You're not booting from there, comment the line in the fstab, "umount /boot" and re-install/update the kernel again.

To be clear im writing this into the fstab file

UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 /boot ext4 defaults,noatime 0 1 umount /boot
/dev/nvme0n1p1 on /boot type ext4 (rw,noatime)

seth · 2023-07-17 16:23:26

No.
How did you come up with that idea?

Your fstab already has a bunch of commented lines. Apply that pattern to the one that mounts the /boot partition.
Then, in your interactive shell, umount /boot.
Then update the kernel.

USPMAN1.3 · 2023-07-17 16:55:34

I thought so. I am sorry about that one.

So after updating the kernel and updating the grub. with update-grub from the aur.

It is now hung up at Loading linux-lts and loading initial ramdisk

Downgrading to the cache pkg kernel, boots me in

seth · 2023-07-17 19:43:53

Nobody said anything about updating grub, let alone with some ported ubuntu script.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'f:1=<-' ix.io

Also post the complete log of the update.

pacman -S linux-lts 2>&1 | tee ~/update.log

will copy the entire output into ~/update.log

USPMAN1.3 · 2023-07-17 20:24:13

Again, thanks for your continued help seth!

 resolving dependencies...
looking for conflicting packages...

Package (1)     Old Version  New Version  Net Change

core/linux-lts  6.1.38-1     6.1.38-2       0.02 MiB

Total Installed Size:  115.96 MiB
Net Upgrade Size:        0.02 MiB

:: Proceed with installation? [Y/n] checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
upgrading linux-lts...
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Checking which packages need to be rebuilt

and this command:
sudo journalctl -b | curl -F 'f:1=<-' ix.io

does nothing in fish, and bash

I put it on github:

https://github.com/uspman/error-log/raw … journalctl

Last edited by USPMAN1.3 (2023-07-17 20:36:29)

seth · 2023-07-17 21:00:44

Why is there no mkinitcpio being run?
Your journal is 2.4 MB (mostly because of rtkit spam, it seems), you get quota'd by ix.io

Jul 17 09:55:48 thomas-latitude7480 systemd[1]: Mounting /boot...
Jul 17 09:55:48 thomas-latitude7480 systemd[1]: Mounted /boot.

The /boot partition still gets mounted.

Jul 17 09:55:45 thomas-latitude7480 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 rw quiet nowatchdog nvme_load=YES loglevel=3

but you're not booting from it.
What does your /etc/fstab look like now?

Edit:

Jul 17 09:55:48 thomas-latitude7480 systemd-fstab-generator[277]: Failed to create unit file '/run/systemd/generator/boot.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Jul 17 09:55:48 thomas-latitude7480 (sd-execu[271]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
…
Jul 17 09:55:48 thomas-latitude7480 systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.

Last edited by seth (2023-07-17 21:02:25)

USPMAN1.3 · 2023-07-17 21:03:47

 # /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 /boot             ext4    defaults,noatime 0 1
/dev/nvme0n1p1                    /boot     ext4     (rw,noatime)

and I ran pacman -S mkinitcpio and it updated

i ran mkinitcpio and it printed:

 mkinitcpio
==> Starting dry run: '6.1.38-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> ERROR: module not found: 'usbhid'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Dry run complete, use -g IMAGE to generate a real image

Last edited by USPMAN1.3 (2023-07-17 21:07:27)

seth · 2023-07-17 21:09:55

So instead of commenting the boot partition you removed the tmpfs and added the output line from the mount command?
Is this some sort of prank?
What do you think the comments in that file are? What do they have all in common?
Remove the line you added and restore the tmpfs line.
Then comment the line that starts w/ "UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43"

Jul 17 09:55:48 thomas-latitude7480 systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Jul 17 09:55:48 thomas-latitude7480 systemd[1]: Mounting Temporary Directory /tmp...
Jul 17 09:55:48 thomas-latitude7480 systemd[1]: Mounted Temporary Directory /tmp.

You probably also filled the /tmp path on your root partition with a bunch of garbage now.

USPMAN1.3 · 2023-07-17 21:16:31

Sorry about that... I get it now that was dumb.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 umount /boot              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

is what it looks like now.

seth · 2023-07-17 21:39:19

You're not serious are you?
A comment starts with a hashtag "#", everyhing after that in the line is ignored.
That is why human talk at the head starts every line this way.
The "umount /boot" has absolutely no business being there. It is a command. That you enter into your shell. And then the partition mounted into /boot gets, guess what, unmounted.

This is not meant as criticism against you, but I guess "you" installed arch using this <horrible swearing here> archinstall script that was added to the iso based on a bunch of ridiculously obvious lies* ?
You've been scammed.
You cannot use archlinux at this point. You'll have a hard enough time w/ ubuntu, but at least a fighting chance.
So try that first for a couple of years.

I mean that in the most benelovend way: You are, for now, not capable of running an arch system.
It'll be nothing but pain and frustration because you're being asked to maintain an engine, but are still trying to figure what the screwdriver and what the hammer is. This isn't going to work.

---
*The archinstall script is (was?) officially not meant to be used by end users to install archlinux.
https://wiki.archlinux.org/title/Archinstall - see the warning and also https://bbs.archlinux.org/viewtopic.php … 1#p1965851 - though idk where Alad got that from, doesn't seem on the archinstall homepage nor github, maybe some internal discussion.

USPMAN1.3 · 2023-07-17 21:42:54

I thought that's what you mean by comment. But usually I read "comment out" the line. And I didn't see that there, so I didn't want to make assumptions. I should have asked.

I've been on Arch based systems for years, and I just have never had to deal with any of the kernel boot issues, and I usually am able to figure 99% of things out without posting.

I didn't use a script I just followed a few different Youtube videos.

I am sorry for your frustration. And I really appreciate your help and patience with me thus far! I take no offense

Last edited by USPMAN1.3 (2023-07-17 21:44:37)

USPMAN1.3 · 2023-07-17 21:46:37

seth wrote:

UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 /boot              ext4    defaults,noatime 0 1
/dev/nvme0n1p1 on /boot type ext4 (rw,noatime)
You're not booting from there, comment the line in the fstab, "umount /boot" and re-install/update the kernel again.

I am going back in your helps, and following this now

my fstab looks like this now

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=5a8de79d-e69d-4618-93c4-62a3e7f59b43 umount /boot              ext4    defaults,noatime 0 1
tmpfs

i also made sure that the mkinitcpio re-generated the preset file saved in /etc/mkinitcpio.d/

Last edited by USPMAN1.3 (2023-07-17 21:56:36)

Arch Linux

#1 2023-07-17 04:50:36

[SOLVED] LTS Kernel update system hangs on Started Host Name

#2 2023-07-17 06:23:59

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#3 2023-07-17 06:51:11

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#4 2023-07-17 06:59:41

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#5 2023-07-17 07:10:09

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#6 2023-07-17 07:13:47

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#7 2023-07-17 07:21:34

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#8 2023-07-17 07:30:22

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#9 2023-07-17 07:35:45

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#10 2023-07-17 07:38:48

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#11 2023-07-17 12:49:32

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#12 2023-07-17 15:19:00

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#13 2023-07-17 15:53:04

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#14 2023-07-17 16:12:01

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#15 2023-07-17 16:23:26

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#16 2023-07-17 16:55:34

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#17 2023-07-17 19:43:53

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#18 2023-07-17 20:24:13

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#19 2023-07-17 21:00:44

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#20 2023-07-17 21:03:47

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#21 2023-07-17 21:09:55

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#22 2023-07-17 21:16:31

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#23 2023-07-17 21:39:19

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#24 2023-07-17 21:42:54

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

#25 2023-07-17 21:46:37

Re: [SOLVED] LTS Kernel update system hangs on Started Host Name

Board footer