dracut-initqueue[291]: Warning: Could not boot.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
dracut-initqueue[291]: Warning: Could not boot.
dracut-initqueue[291]: Warning: /dev/disk/by-path/ccw-0.0.3120-part1 does not exist
dracut-initqueue[291]: Warning: /dev/disk/by-uuid/30f85989-86ac-474d-b696-1d6689da5832 does not exist
dracut-initqueue[291]: Warning: /dev/disk/by-uuid/431a0543-dc6b-4b92-8688-6f9087affd65 does not exist
dracut-initqueue[291]: Warning: /dev/disk/by-uuid/b273239f-1943-4607-ad44-2e007624ee1b does not exist
Starting Dracut Emergency Shell...
Warning: /dev/disk/by-path/ccw-0.0.3120-part1 does not exist
Warning: /dev/disk/by-uuid/30f85989-86ac-474d-b696-1d6689da5832 does not exist
Warning: /dev/disk/by-uuid/431a0543-dc6b-4b92-8688-6f9087affd65 does not exist
Warning: /dev/disk/by-uuid/b273239f-1943-4607-ad44-2e007624ee1b does not exist
Warning: Boot has failed. To debug this issue add "rd.shell rd.debug" to the kernel command line.
dracut-initqueue[291]: Job for dracut-emergency.service failed. See "systemctl status dracut-emergency.service" and "journalctl -xn"
for details.
dracut-initqueue[291]: Warning: Not all disks have been found.
dracut-initqueue[291]: Warning: You might want to regenerate your initramfs.
I am able to boot on the previous kernel.
I issued: dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg
I receive the same results.
filesystems are using “btfs”
ccw-0.0.3120-part1 is ext2.
If you boot to your previous kernel (which you indicated works) and check
your disk space for things like /boot and the root (/) filesystem, do you
have a fair bit (GiBs, not MiBs) free/available? Also, are your initrd
files similar sizes? What you describe seems odd to me but if you have a
bad/missing initrd for the newer kernel, or if you did not get all of the
new kernel modules installed (usually for space reasons) then it would
explain a fair bit.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
I have some questions? I did not perform the update so I do not know if any problems occurred during this process.
I tried to find a YAST log but I was unable to find one in /var/log/YaST2 but I am not sure what the name would be!
linux33:/var/log/YaST2 # ls
_dev_dasda curl_log macro_inst_initial.ycp signal y2log
arch.info disk_dasda.info mkinitrd.log tmpfs.info y2log-1.gz
config_diff_2014_12_19.log disk_dasda.info-1 pbl-instsys.log vncserver.log y2logmkinitrd
config_diff_2017_01_04.log free.info perl-BL-standalone-log y2changes y2start.log
I see that /etc/os-release does not state SLES12-SP1. Is this because I am on the previous kernel or that the update may have failed?
linux33:/var/log # cat /etc/os-release
NAME="SLES"
VERSION="12"
VERSION_ID="12"
PRETTY_NAME="SUSE Linux Enterprise Server 12"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12"
At this point is it possible to perform the update to SP1?
Is there any cleanup that need to be done, like removing initrd files or any other files?
Are you using BtrFS, I presume? If so, we may want to ask the btrfs tools
about filesystem usage too; overall this disk seems really small, and I’d
still probably bet on a space being an influencer unless you can duplicate
the problem (presumably with a kernel patch) on another system:
btrfs filesystem usage /
btrfs filesystem usage /boot
snapper list
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
On 01/06/2017 09:34 AM, mikenash wrote:[color=blue]
I have some questions? I did not perform the update so I do not know if
any problems occurred during this process.
I tried to find a YAST log but I was unable to find one in
/var/log/YaST2 but I am not sure what the name would be!
y2log is the main log if Yast was used, or else you may want to look for a
zypper log file: /var/log/zypper.log
[color=blue]
I see that /etc/os-release does not state SLES12-SP1. Is this because I
am on the previous kernel or that the update may have failed?
Code:
linux33:/var/log # cat /etc/os-release
NAME=“SLES”
VERSION=“12”
VERSION_ID=“12”
PRETTY_NAME=“SUSE Linux Enterprise Server 12”
ID=“sles”
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:suse:sles:12”
--------------------[/color]
It should be updated by the package that owns it, which apparently was not
upgraded to SP1; you can find that package using the following command:
rpm -qf /etc/os-release
[color=blue]
At this point is it possible to perform the update to SP1?
Is there any cleanup that need to be done, like removing initrd files or
any other files?[/color]
I would still address disk space before doing anything else. Performing
an SP upgrade (distribution upgrade probably, meaning ‘zypper dup’) with
less-than 1 GiB free, particularly when you likely have BtrFS snapshots,
seems like a bad idea.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…