Tumbleweed install wont boot possible borked update

English Install/Boot/Login
1

I run Tumbleweed as a 2nd OS on a spare drive. After initial setup I barely use it. I just boot into it to keep it up to date. I updated it a few days ago and there where no issues. I tried to boot into it yesterday and booting took an age so I hit Esc to see what was going on and it seemed to be getting stuck finding the drive and then timing out to a maintenence terminal. I have no idea how to proceed.

I can access the drive from my main OS and from rescue media. I have checked that the UUID is the same in grub as the drives UUID and it is. I dont know how to proceed to try and rescue this install.

2

Can you boot from a previous snapshot? In GRUB you can select the advanced options and select any previous version.

3

No Ive tried older snapshots and they all result in the same.

4

As you did not give any details it is hard to tell what happened and what to do next.

I guess you ended up in a emergency console. If that is the case you are asked to enter your root password and then inspect the log files (by some journalctl command shown in the message).

What was in the log files?

5

I did end up in the emergency console and I ran journalctl and ended up with thousands of lines of stuff that I have no idea what to look for. As its a terminal I dont know if I can save the information in any way.

6

You could try

journalctl -b 0 -p 3

That should show errors only.

7

Thank you that was helpful.

There seem to be 2 errors 1 referring to my Printer

error: Device hp:/usb/Photosmart_6520_series?serial=TH38J1702C05XP does not support or require firmware download

The 2nd erro seem to refer to my Gaming drive which is a NVME drive

Timed out waiting for device /dev/disk/by-uuid/8ef8bd2f-dbe6-42b6-aa88-f0cfc3745de6

I have just checked the blkid of the Gaming drive on my main OS and its 9d114ad4-ae56-4641-bb6c-4ebd657b14aa

Can the UUID change? It used to work. As far as I can remember I have the drives mounted via systemd mount as it said a mistake wouldn’t stop the system from booting

EDIT: No I just checked. Its not the Gaming drive it must be the main drive. The Gaming drives UUID is the same as the correct one on both systems.

EDIT 2: OK Im an idiot. Ive solved it. When I changed the mounts to systemd mounts I forgot to delete the fstab mounts. So they where duplicated and fstab had the wrong UUID. Thank you all for the pointers.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.