SOLUTION BELOW
I have never been in a more confusing situation regarding Linux.
I have a Dell XPS 15 9560, which had a dual boot Windows 10 / EndeavourOS setup. It was running fine for months. 10 days ago I updated Linux and after restart it couldn't boot anymore. It got stuck at "A start job is running for /dev/disk/by-uuid/..." (which is the root partition).
First, with the help of a friend of mine who is quite knowledgeable about Linux (he runs vanilla Arch, etc), we spent 5 hours trying to fix it but had no luck.
Then I decided to back up everything and do a fresh install. Aaaand the same error happened again on the first boot. Then I though "ok, probably some problem with Arch, lets try Fedora". Nope. Some similar error about not finding the root partition. (Here I must say that the kernel which was shipped with the ISO was working fine, but after updating to the latest one, it failed.) Here I thought "ok, then it might be a problem with the latest kernel, let's install EndeavourOS with the LTS kernel." Nope, LTS kernel also didn't boot. Then I tried Ubuntu and it worked, but that's not solving the problem. Then I decided to put another nvme drive in the laptop and try there. The same error again.
Now the greatest part: If I put the nvme drive into an external usb case, EndeavourOS installs, updates, boots without any problem, no sign of the error.
So now I don't know how to proceed... Maybe there is something wrong with the pcie port in my laptop, but except for the booting problem, windows is working, I can also mount and access every partition in the ssd through a live usb. So no other signs of problem with the port whatsoever.
I would be grateful for any advice as I've lost several days trying to solve this and I am out of ideas...
Solution: The last working kernels are from 11. August 2023 (both linux and linux-lts) linux-6.4.10.arch1-1 and linux-lts-6.1.45-1. You can download them from here: linux / linux-lts and install them with
sudo pacman -U the_path_to_the_package
Thank you all for the help!
So this occurs after an update. Is it not possible to boot into the prior kernel?
If possible to boot into the prior kernel, can you inspect logs or the journal to see where your error is cropping up?
This issue sounds like a regression of sorts with a driver, but log/debug would help confirm. This would be one worth reporting to upstream if you can rescue some logs (I gather you can if you can boot the disk from another enclosure).
If you can boot into the machine, investigate note from the journal:
journalctl --list-bootsjournalctl -b -1,-- If you are booting into a live environment or are otherwise mounting the disk:
journalctl -D /var/log/journal/ID_GOES_HERE/var/log/journal/2dff8304d5114c44bfb1311357a3cd87-- Keep us posted.
If truly a driver regression, but you can boot from the prior kernel (if you don't have it, install it via livecd or so), definitely report this one and remain on the prior kernel until resolved. Bleeding edge things.
I have already wiped everything, so no logs... The only way to have it booting is to install EndeavourOS using the offline installer, which is using kernel 6.4.8. There is an option to install the LTS kernel alongside. So the system is booting with 6.4.8, but after updating, neither the new 6.4.12, or the LTS, which is 6.2, doesn't boot. I haven't tried booting with the LTS kernel before updating, to see if the same kernel is working before and after or not. I will try to reinstall it using the offline installer and then try to gather some logs after updating.
If you do go this route - try to update the kernel only, not the rest of the system. Yes, it's bad under normal circumstances, but I think we're way past those.
This would rule out some other part of system getting in the way - like systemd.
I updated only the kernel and I got the following:
(Continues in the second comment)
Did it boot or did it get stuck at the same spot again?
It got stuck at the same spot.
Implies it is the kernel. Mark it on hold and stick to the working kernel for the time being.
Does EndeavourOS use pacman?
You might consider modifying
/etc/pacman.confto include the optionIgnorePkg=linux linux-ltsuntil this is resolved.6.4.12.arch1-1was added ~4 days ago. If you check the releases arch linux kernel releases here, they have nearly a weekly cadence. This may be a case you can ride out until a newer kernel is released that might solve your issue.If you need access to older releases, see the archive.
For root cause analysis -- is it possible for you to extract/view the journal logs now that you have upgraded the kernel causing the issue? --
/var/log/journalis a good start. My time is limited, but I'm curious to see what's going on in there. In any case per your and Illecors' testing, it seems you have isolated the issue to thelinuxpackage.I just realized you're also on systemd-boot (I am too). I'll check into a way to revert back to prior kernels (for I also may run into a similar issue).
edit: updated IgnorePkg line to include both your mainline and LTS kernel (Pacman -Syu updates both) if you opt to hold them for updates.
This is the log https://ufile.io/p5wj1hu0
I'm not sure if this is relevant, but I added
pci=nommconfto the kernel parameters as I had errors similar to the one in this topic, otherwise the log was over 40 000 lines long.Edit: I'm not sure if this is exactly a kernel problem, as I get the same error when booting with the LTS kernel, which is older than the one installed with the offline installer.
No worries. When checking that output, it is for the working 6.4.8-arch1-1 kernel. The broken kernel boot attempt would be most useful, but I don't want to make you suffer to get it, if you are back to a working system. I think at this point it is safe to say your laptop isn't a fan of the newer kernels.
I would :
/etc/pacman.confto ignore updates to packageslinuxandlinux-lts--
Ideally: You could (from a working system) install a known working LTS image (pkg
linux-lts), and exclude that from updates until you land on a working kernel release (keep an eye ontestingandcorerepos once a week or so). in this way, you'll have a working LTS, and can upgrade/downgrade mainline kernels as you please, booting back into LTS to correct issues should they arise.edit: minor
I found the problem! It was actually the kernel, just both the latest and the lts versions released after 11th of August don't work. So for now I need to stick to the versions from 11th. Thank you very much for the help!
Edit: this is the bug