[SOLVED] A start job is running for /dev/disk/by-uuid

lattimro · 12-10-2023, 02:58 PM

Quote:

Originally Posted by colorpurple21859

show output of blkid

what flag to use with blkid?

colorpurple21859 · 12-10-2023, 03:03 PM

no flag

lattimro · 12-10-2023, 03:54 PM

Quote:

Originally Posted by colorpurple21859

no flag

AFAIK the online upgrade is supported only with the official Tumbleweed repos. If you know otherwise please advise. My repos are as follow:

Code:

root@gecko:/home/brad# zypper lr
Repository priorities in effect:                                                   (See 'zypper lr -P' for details)
      90 (raised priority)  :  1 repository
      97 (raised priority)  :  1 repository
      98 (raised priority)  :  2 repositories
      99 (default priority) :  3 repositories
     115 (lowered priority) :  2 repositories

#  | Alias                  | Name                   | Enabled | GPG Check | Refresh
---+------------------------+------------------------+---------+-----------+--------
 1 | Google-chrome          | Google-chrome          | Yes     | (r ) Yes  | Yes
 2 | Google-talkplugin      | Google-talkplugin      | Yes     | (r ) Yes  | Yes
 3 | Packman_Tumbleweed     | Packman_Tumbleweed     | Yes     | (r ) Yes  | Yes
 4 | Tumbleweed_OSS         | Tumbleweed_OSS         | Yes     | (r ) Yes  | Yes
 5 | Tumbleweed_OSS-updates | Tumbleweed_OSS-updates | Yes     | (r ) Yes  | Yes
 6 | Tumbleweed_non-OSS     | Tumbleweed_non-OSS     | Yes     | (r ) Yes  | Yes
 7 | google-chrome          | google-chrome          | Yes     | (r ) Yes  | Yes
 8 | google-chrome-beta     | google-chrome-beta     | No      | ----      | ----
 9 | skype-stable           | skype (stable)         | Yes     | (r ) Yes  | Yes
10 | teamviewer             | TeamViewer - x86_64    | Yes     | (r ) Yes  | No
root@gecko:/home/brad#

colorpurple21859 · 12-11-2023, 12:31 AM

Did you try booting the vmlinuz-6.5.9-1-default kernel with root=/dev/sdc4?

lattimro · 12-11-2023, 08:27 AM

Quote:

Originally Posted by colorpurple21859

Did you try booting the vmlinuz-6.5.9-1-default kernel with root=/dev/sdc4?

Yes, I did.

lattimro · 12-11-2023, 12:27 PM

Quote:

Originally Posted by goumba

Fonts have nothing to do with it. You'd just get a warning message and possibly a display that doesn't look great.

I asked that question because I noticed above "UUID blabla no-limit" message the Virtual Console Setup service failed. I masked the service but did not make any difference.

mrmazda · 12-11-2023, 12:37 PM

Quote:

Originally Posted by lattimro

...the Virtual Console Setup service failed. I masked the service but did not make any difference.

You should unmask it. By the time it actually becomes needed it should have become active.

colorpurple21859 · 12-11-2023, 06:10 PM

What about chroot into the system and run dracut for one of the kernel versions to see what happens?

lattimro · 12-11-2023, 06:19 PM

Quote:

Originally Posted by colorpurple21859

What about chroot into the system and run dracut for one of the kernel versions to see what happens?

I can do that but you need to tell me the command ... I mean dracut what? and what is the expected outcome? I am not sure if I can regenerate initrd.img from a chroot

colorpurple21859 · 12-11-2023, 08:00 PM

mount the root partition, mount --bind appropriate directories, choot

Code:

dracut --kver 6.6.3-1-default --force

mrmazda · 12-11-2023, 08:43 PM

To be sure of a reasonable answer (before colorpurple21859's post #55), I booted Slowroll, where the newest installed kernel is 6.5.9, and chrooted into TW 20231121, where the newest installed kernel is also 6.5.9. It had a corresponding 16,704,252 byte initrd with a 22 November timestamp. I issued:

Code:

dracut -f

It resulted in a currently timestamped 16,596,340 byte 6.5.9 initrd. If you're actually running Tumbleweed, and chrooting from a TW rescue media of close enough matching date, I would expect an equivalent result for you.

I dumped output from lsinitrd from each of the two initrds to files. I diff'd the two files and the result was 987 lines.

I then saved the new initrd, restored the original initrd, and booted TW directly to run dracut -f again. This one came out to 16,702,240 bytes. I saved it too. Then I successfully rebooted directly into TW, restored the 1st initrd rebuild, and rebooted successfully again. A diff between the 1st and 3rd initrds was 994. Between 2nd and 3rd was 981.

I suppose it could somehow become necessary to run dracut specifically identifying the version to get the correct kernel rebuilt. So, I booted Ubuntu 22.04 and chrooted into TW. Next I ran dracut -f -k 6.4.12-1-default, which resulted in error messages and no new initrd. So did dracut -f -k /usr/lib/modules/6.4.12-1-default, which also failed. Next I followed one of the error message instructions: export DRACUT_KMODDIR_OVERRIDE=1, but it didn't help. Next try, without thinking to first nullify DRACUT_KMODDIR_OVERRIDE=1, worked, 16,019,264 bytes:

Code:

dracut -f --kver 6.4.12-1-default

Thus I can't say whether DRACUT_KMODDIR_OVERRIDE=1might have been necessary. I suppose not. The 6.4.12 boots with its new initrd too.

Chroot process used:

mount the target filesystem: mount /dev/foo /mnt
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
mount -o bind /proc /mnt/proc
chroot /mnt

lattimro · 12-11-2023, 09:37 PM

a chrooted and zypper up solved the issue. Rebooted and the issue solved, I can't understand, maybe you can.
6.5.9-1 and recovery also works fine.

I deleted root=UUID=... from grub and also booted OK. I wish I had done this before.

mrmazda · 12-11-2023, 10:17 PM

If you are in the habit of using zypper up without also using zypper dup, that explains any number of problems. Only dup should be used, or if up is used, it needs to be done with the awareness of the possible consequences. TW is a rolling release. Each edition of TW is an upgrade. Thus, only dup can complete the process, so required package changes can be left undone by doing only up.

goumba · 12-11-2023, 11:39 PM

Quote:

Originally Posted by lattimro

a chrooted and zypper up solved the issue. Rebooted and the issue solved, I can't understand, maybe you can.
6.5.9-1 and recovery also works fine.

Likely a new kernel was installed and therefore your initrds were rebuilt for you.

As mrmazda and pretty much every source of documentation says for TW, use zypper dup with Tumbleweed.

Quote:

I deleted root=UUID=... from grub and also booted OK. I wish I had done this before.

Leave that alone, it's there for a reason.

lattimro · 12-12-2023, 07:59 AM

Quote:

Originally Posted by goumba

Likely a new kernel was installed and therefore your initrds were rebuilt for you.

As mrmazda and pretty much every source of documentation says for TW, use zypper dup with Tumbleweed.

Leave that alone, it's there for a reason.

I just wanted to replicate the initial issue with booting because so far we do not know why the root partition "was not found". I expected you can explain why was able to boot without that line I temporarily removed for testing purpose.