[opensuse] Tumbleweed boot difficulty
I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console) When it boots, it is working fine, I can do most everything I have tried. I see that /proc/cmdline says: BOOT_IMAGE=/boot/vmlinuz-5.3.2-1-default root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet mitigations=off The devices and UUID look correct. I'm just curious why the resume= and quite are listed twice. Could that be the problem? I know that the kernel was updated in all of this. The dracut is whatever the kernel packages does. I have not changed anything. I have tried various boot alternatives (rescue, a snapshot, etc). All do the same. This is a new one on me. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console)
When it boots, it is working fine, I can do most everything I have tried.
Have you tried re-installing the grub2 setup with 'grub2-install'? ISTR similar issues (quite some time ago) that got solved that way... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 11, 2019 at 3:12 PM Peter Suetterlin <pit@astro.su.se> wrote:
Have you tried re-installing the grub2 setup with 'grub2-install'? ISTR similar issues (quite some time ago) that got solved that way...
I have never used that program. And there are lots of options! What would a proper command for Tumbleweed (with a /boot partition) be? It would be expecting too much for it to be the defaults. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Fri, Oct 11, 2019 at 3:12 PM Peter Suetterlin <pit@astro.su.se> wrote:
Have you tried re-installing the grub2 setup with 'grub2-install'? ISTR similar issues (quite some time ago) that got solved that way...
I have never used that program. And there are lots of options! What would a proper command for Tumbleweed (with a /boot partition) be? It would be expecting too much for it to be the defaults.
I was running it without any options/arguments, I think its collecting the info from the installation? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 11, 2019 at 4:02 PM Peter Suetterlin <pit@astro.su.se> wrote:
I was running it without any options/arguments, I think its collecting the info from the installation?
I found the openSUSE docs and it was as you said - no options needed. I also rebuilt the grub.cgf file, as the docs described. I changed the grub config so that the repeated arguments were removed. I also did an update that installed the latest Tumbleweed kernel. It ran dracut after this. No difference. I tried editing the grub boot menu at boot time to use a kernel or initrd that does not exist, just to see that it complains. It does. So it seems to be finding the files. Could it be that the initrd is missing some driver? Maybe the install+update gets past this as it probes for everything. No idea. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 11, 2019 at 5:10 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
On Fri, Oct 11, 2019 at 4:02 PM Peter Suetterlin <pit@astro.su.se> wrote:
I was running it without any options/arguments, I think its collecting the info from the installation?
I found the openSUSE docs and it was as you said - no options needed. I also rebuilt the grub.cgf file, as the docs described.
I changed the grub config so that the repeated arguments were removed.
I also did an update that installed the latest Tumbleweed kernel. It ran dracut after this.
No difference.
I tried editing the grub boot menu at boot time to use a kernel or initrd that does not exist, just to see that it complains. It does. So it seems to be finding the files.
Could it be that the initrd is missing some driver? Maybe the install+update gets past this as it probes for everything. No idea.
I added a message after the initrd is loaded. So that seems to be happening. I'm not sure where to check next. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/2019 10:10 AM, Roger Oberholtzer wrote:
No difference.
I tried editing the grub boot menu at boot time to use a kernel or initrd that does not exist, just to see that it complains. It does. So it seems to be finding the files.
Could it be that the initrd is missing some driver? Maybe the install+update gets past this as it probes for everything. No idea.
Roger, Just a guess, try remaking the entire config with dracut, e.g. # dracut -fM --kver $(uname -r) That usually will do it. The only other thoughts I had regarding your grub.cfg was: Confirm - UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 is your / partition and Confirm - /dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 is swap -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Oct 15, 2019 at 8:48 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 10/11/2019 10:10 AM, Roger Oberholtzer wrote:
No difference.
I tried editing the grub boot menu at boot time to use a kernel or initrd that does not exist, just to see that it complains. It does. So it seems to be finding the files.
Could it be that the initrd is missing some driver? Maybe the install+update gets past this as it probes for everything. No idea.
Roger,
Just a guess, try remaking the entire config with dracut, e.g.
# dracut -fM --kver $(uname -r)
I have run this. But I cann0t check until I am at that machine again - in case it still does not boot as needed. FYI, this is what it reported: dracut: Executing: /usr/bin/dracut -fM --kver 5.3.4-1-default dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found! bash systemd systemd-initrd i18n drm plymouth btrfs kernel-modules kernel-modules-extra resume rootfs-block suse-btrfs suse-xfs terminfo udev-rules dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut-systemd haveged ostree usrmount base fs-lib shutdown suse dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done *** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing AuthenticAMD.bin *** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: resume=UUID=47f6ce02-3e5d-4507-a6f7-301fc4cb1e0d dracut: root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=268,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot dracut: *** Creating image file '/boot/initrd-5.3.4-1-default' *** dracut: *** Creating initramfs image file '/boot/initrd-5.3.4-1-default' done *** Could any of the thing listed at the start as not getting installed be a problem? I'm not using LVM. It is a default btrsf layout.
That usually will do it. The only other thoughts I had regarding your grub.cfg was:
Confirm - UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 is your / partition
02e67b6d-c8b5-4de1-8ac5-96a13174a855 is indeed root.
and
Confirm - /dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 is swap
Yes it is. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/15/2019 03:24 AM, Roger Oberholtzer wrote:
dracut: Executing: /usr/bin/dracut -fM --kver 5.3.4-1-default dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found!
I don't think those are issues, I see that is dracut telling you that you don't have that on your system (because you don't need it..), but I don't use btrfs, so I do not know if any of those are mandatory -- I don't think so. Let us know if it boots. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I ran: # dracut -fM --kver $(uname -r) This seems to have done the trick. I can once again boot directly in to the OS. No need to use the installer to get there. I'm curious what this does that a kernel RPM install does not do. I have tried the reboot once from a full power down. But I think it will boot each time. Thanks for the help! -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/10/2019 10.52, Roger Oberholtzer wrote:
I ran:
# dracut -fM --kver $(uname -r)
This seems to have done the trick. I can once again boot directly in to the OS. No need to use the installer to get there.
I'm curious what this does that a kernel RPM install does not do.
Maybe your boot information in /etc is not correct, thus when the scripts do it automatically they fail. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 21, 2019 at 12:31 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 21/10/2019 10.52, Roger Oberholtzer wrote:
I ran:
# dracut -fM --kver $(uname -r)
This seems to have done the trick. I can once again boot directly in to the OS. No need to use the installer to get there.
I'm curious what this does that a kernel RPM install does not do.
Maybe your boot information in /etc is not correct, thus when the scripts do it automatically they fail.
I don't see anything amiss. Of course, I could very well have missed something. I mainly looked at things that looked like disk references. And, wouldn't "dracut -fM --kver $(uname -r)" also be using the same configuration? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/10/2019 13.38, Roger Oberholtzer wrote:
On Mon, Oct 21, 2019 at 12:31 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 21/10/2019 10.52, Roger Oberholtzer wrote:
I ran:
# dracut -fM --kver $(uname -r)
This seems to have done the trick. I can once again boot directly in to the OS. No need to use the installer to get there.
I'm curious what this does that a kernel RPM install does not do.
Maybe your boot information in /etc is not correct, thus when the scripts do it automatically they fail.
I don't see anything amiss. Of course, I could very well have missed something. I mainly looked at things that looked like disk references.
And, wouldn't "dracut -fM --kver $(uname -r)" also be using the same configuration?
Dunno. It is 'grub2-mkconfig -o /boot/grub2/grub.cfg' and something else I forget. Yesteryear was in /etc/grub.conf mkinitrd. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 21, 2019 at 6:03 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
It is 'grub2-mkconfig -o /boot/grub2/grub.cfg' and something else I forget. Yesteryear was in /etc/grub.conf
Those are correct (I think). Earlier in this thread it was suggested that I update the grub stuff. It made no difference.
mkinitrd.
isn't that what dracut accomplishes instead? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/21/2019 01:56 PM, Roger Oberholtzer wrote:
On Mon, Oct 21, 2019 at 6:03 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
It is 'grub2-mkconfig -o /boot/grub2/grub.cfg' and something else I forget. Yesteryear was in /etc/grub.conf
Those are correct (I think). Earlier in this thread it was suggested that I update the grub stuff. It made no difference.
mkinitrd.
isn't that what dracut accomplishes instead?
Hope this is not off-topic: Using TW, revision cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190926" getting a message that I have over a thousand upgrades, but I am afraid to do the upgrade based on some of these messages. I do NOT want to have to reinstall everything with a new system. Is it safe to run the updater? Thanx--doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 22 oktober 2019 01:04:36 CEST schreef Doug McGarrett:
On 10/21/2019 01:56 PM, Roger Oberholtzer wrote:
On Mon, Oct 21, 2019 at 6:03 PM Carlos E. R.
<robin.listas@telefonica.net> wrote:
It is 'grub2-mkconfig -o /boot/grub2/grub.cfg' and something else I forget. Yesteryear was in /etc/grub.conf
Those are correct (I think). Earlier in this thread it was suggested that I update the grub stuff. It made no difference.
mkinitrd.
isn't that what dracut accomplishes instead?
Hope this is not off-topic: Using TW, revision
cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190926"
getting a message that I have over a thousand upgrades, but I am afraid to do the upgrade based on some of these messages. I do NOT want to have to reinstall everything with a new system. Is it safe to run the updater?
Thanx--doug That is Tumbleweed. I see hundreds sometimes, even though upgrading to every snapshot. Run 'zypper dup' and you should be fine. The plasma updater ditto.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/10/2019 01.04, Doug McGarrett wrote:
Hope this is not off-topic: Using TW, revision
cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190926"
getting a message that I have over a thousand upgrades, but I am afraid to do the upgrade based on some of these messages. I do NOT want to have to reinstall everything with a new system. Is it safe to run the updater?
That is normal in TW. And the more weeks you delay, the worst. Typically you upgrade every week, possibly with dozens, hundreds, sometime thousands, of updates. If you do not like the risk of updates, do not use TW and stay on Leap. And if you read this list, you will read about all the problems, not about all successes. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/21/2019 06:38 AM, Roger Oberholtzer wrote:
And, wouldn't "dracut -fM --kver $(uname -r)" also be using the same configuration?
dracut is more a overarching config manager what wraps all the individual pieces together (grub, mkinitrd, etc..) I'm no expert on it as I generally live a release or two behind, but in providing a config, dracut does more of a system exam than just reading the previously save config files in /etc/... I don't know where the line is, but dracut will more or less examine the system and determine what each config in the boot sequence needs to be and then writes a new configuration based on the current system rather than saved config files. A number of distros are going kicking and screaming to dracut. And for a number that are making the push, I happen to have a healthy respect for the past distro design choices they have made (SuSE/openSUSE included) So somewhat like systemd, we are going to have to make friends with it eventually... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
October 10, 2019 6:44 AM, "Roger Oberholtzer" <roger.oberholtzer@gmail.com> wrote:
I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console)
When it boots, it is working fine, I can do most everything I have tried.
I see that /proc/cmdline says:
BOOT_IMAGE=/boot/vmlinuz-5.3.2-1-default root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet mitigations=off
The devices and UUID look correct. I'm just curious why the resume= and quite are listed twice. Could that be the problem? I know that the kernel was updated in all of this. The dracut is whatever the kernel packages does. I have not changed anything.
I have tried various boot alternatives (rescue, a snapshot, etc). All do the same.
This is a new one on me.
-- Roger Oberholtzer
Could this be the chrony-wait service causing this? - Have you waited 10 minutes to see if it does boot? Here is a Reddit post from 2 months ago: https://www.reddit.com/r/openSUSE/comments/cqcu6k/clean_system_takes_too_lon... Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
David C. Rankin -
Doug McGarrett -
Knurpht-openSUSE -
Mark Petersen -
Peter Suetterlin -
Roger Oberholtzer