Tumbleweed update - stalled boot

[nrickert]

Any idea why and what filled the drive?

Perhaps "btrfs" snapshots.

[karlmistelberger]

Solution: I reinstalled from a current Tumbleweed iso.

This kind of solution is around since the Ancient Greek: https://en.wikipedia.org/wiki/Sisyphus

Any idea why and what filled the drive?

Size of your /root is 11G. That's bigger than my entire system. My /root is 11M or 0.1% of yours. Only you can tell what you are doing.

https://www.cyberciti.biz/faq/linux-...space-command/

[mrmazda]

My /root is 11M or 0.1% of yours.

How is that happening? Just /boot/vmlinuz-5.8.14-1-default on my TW is 10M (10,402,064), with larger initrd.

[karlmistelberger]

How is that happening? Just /boot/vmlinuz-5.8.14-1-default on my TW is 10M (10,402,064), with larger initrd.

My /boot is:

erlangen:~ # du -hd1 /boot 
14M     /boot/efi 
5.3M    /boot/grub2 
133M    /boot 
erlangen:~ #

and /root is:

erlangen:~ # du -hd1 /root/
0       /root/.gnupg
0       /root/bin
11M     /root/.cache
32K     /root/inst-sys
16K     /root/.config
8.0K    /root/.dbus
4.0K    /root/.local
11M     /root/
erlangen:~ #

[idee]

Perhaps "btrfs" snapshots.

it was an ext4

[idee]

My /root is 11M or 0.1% of yours. Only you can tell what you are doing.

https://www.cyberciti.biz/faq/linux-...space-command/

Not really sure. It is a pretty straight forward tumbleweed installation that I update with zypper dup. I don't customize and haven't loaded many additional programs.
The new installation is approx 3 gigs at this point. I don't know what expanded the previous installation. It has been about 2 1/2 years since an installation.

[mrmazda]

My /root is 11M or 0.1% of yours.

How is that happening? Just /boot/vmlinuz-5.8.14-1-default on my TW is 10M (10,402,064), with larger initrd.

Obviously I misread /root as /boot.

# du -sh /root/
624M    /root/
# du -sh /boot/
515M    /boot/

[idee]

This kind of solution is around since the Ancient Greek: https://en.wikipedia.org/wiki/Sisyphus

The boulder has just rolled back on me again.

The primary install was up and running clean.
Now it was time to clean up the secondary.

The goal in the boot menu is to have:
(primary) Cinnamon Tumbleweed
(secondary) LXQT Tumbleweed
(lastly) Windows

The easiest and cleanest solution seemed to be a reinstall of Tumbleweed.
It was the generic install (ICE) all defaults.

It installed fine, but will now not boot.

I assume is has to due with Grub or boot manager.
On reboot, the process halts at Grub:

GNU GRUB version 2.04

Minimal BASH-like line editing is supported.  For the first word, TAB lists possible command completions.  Anywhere else TAB list possible device or file completions.

grub>

Primary is on sda2
Secondary is on sdc2

I reinstalled, but the same problem came up.
I used the Tumbleweed Rescue disk, YaST/bootloader, but it provides the following error:

YaST2

Error
Execution of command "[["/usr/bin/grib2-editenv","list"]]" failed.
Exit code:1
Error output: /usr/bin/grub2-editinv:error:failed to get canonical path of 'LiveOS_rootfs'.

Next I tried the Tumbleweed install disk again, but as an update.
The errors were all the same.

At this point I cannot get into any installation.


Any help is appreciated.

[karlmistelberger]

The goal in the boot menu is to have:
(primary) Cinnamon Tumbleweed
(secondary) LXQT Tumbleweed
(lastly) Windows

You may prepare a plan first: https://medium.com/@manujarvinen/set...ns-ca1fcf8d502

Since I found out that UEFI is the easiest mode I enter UEFI, load optimized defaults and disable CSM support. When installing the bootloader I always turn off secure boot. See also: https://forums.opensuse.org/showthre...ws-10-for-Free

[idee]

[QUOTE=karlmistelberger;2978311]You may prepare a plan first: https://medium.com/@manujarvinen/set...ns-ca1fcf8d502/QUOTE]

I like what I read about it, however as I start to check into it my bios is not EFI.
If there is still a way to do this, I would like to.

So I still need to get grub fixed somehow.