[opensuse] How to rerun dracut?
All, I have an old 42.3 laptop that is getting flaky (probably a capacitor) and apparently it had a hiccup during dracut running after a zypper up and it apparently caused problems with the modules config. I can boot the recover and chroot the system (and it is fine), but how do I re-run dracut so it finishes its configuration? (current problem is at the login: prompt, I can input username (or root) and pw, but then the system says unable to log in) So there are authentication modules that were not written that need to be written I suspect) -- 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 11/06/2019 22.06, David C. Rankin wrote:
All,
I have an old 42.3 laptop that is getting flaky (probably a capacitor) and apparently it had a hiccup during dracut running after a zypper up and it apparently caused problems with the modules config.
I can boot the recover and chroot the system (and it is fine), but how do I re-run dracut so it finishes its configuration?
mkinitrd Just that. But maybe you have to bind mount before the /proc, /sys and /run directories. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 06/11/2019 04:11 PM, Carlos E. R. wrote:
mkinitrd
Just that. But maybe you have to bind mount before the /proc, /sys and /run directories.
Yes, thanks Carlos, I'm good with the rest, I've just never dug into dracut itself and didn't know that mkinitrd would trigger the full configuration to run rather than just generating the kernel initrd image. When zypper runs you see about 8 section of blue text scrolling down the page and I couldn't put my finger on what command to run to make that happen again (SuSEconfig is what I recall) -- David C. Rankin, J.D.,P.E.
On 12/06/2019 02.03, David C. Rankin wrote:
On 06/11/2019 04:11 PM, Carlos E. R. wrote:
mkinitrd
Just that. But maybe you have to bind mount before the /proc, /sys and /run directories.
Yes, thanks Carlos,
I'm good with the rest, I've just never dug into dracut itself and didn't know that mkinitrd would trigger the full configuration to run rather than just generating the kernel initrd image. When zypper runs you see about 8 section of blue text scrolling down the page and I couldn't put my finger on what command to run to make that happen again (SuSEconfig is what I recall)
Yeah, well... mkinird might be overkill, but calling dracut directly I heard is complicated so I never bothered to learn, knowing that mkinitrd will call the correct incantation ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wednesday, 12 June 2019 10:28:57 ACST Carlos E. R. wrote:
On 12/06/2019 02.03, David C. Rankin wrote:
On 06/11/2019 04:11 PM, Carlos E. R. wrote:
mkinitrd
Just that. But maybe you have to bind mount before the /proc, /sys and /run directories.
Yes, thanks Carlos,
I'm good with the rest, I've just never dug into dracut itself and didn't
know that mkinitrd would trigger the full configuration to run rather than just generating the kernel initrd image. When zypper runs you see about 8 section of blue text scrolling down the page and I couldn't put my finger on what command to run to make that happen again (SuSEconfig is what I recall) Yeah, well... mkinird might be overkill, but calling dracut directly I heard is complicated so I never bothered to learn, knowing that mkinitrd will call the correct incantation ;-)
It's not complicated - I just use dracut -fM --kver `uname -r` (for the currently running kernel, or substitute the exact version number for whatever non-running kernel you want to rebuild initrd for. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/06/2019 11.54, Rodney Baker wrote:
On Wednesday, 12 June 2019 10:28:57 ACST Carlos E. R. wrote:
On 12/06/2019 02.03, David C. Rankin wrote:
On 06/11/2019 04:11 PM, Carlos E. R. wrote:
mkinitrd
Yeah, well... mkinird might be overkill, but calling dracut directly I heard is complicated so I never bothered to learn, knowing that mkinitrd will call the correct incantation ;-)
It's not complicated - I just use dracut -fM --kver `uname -r` (for the currently running kernel, or substitute the exact version number for whatever non-running kernel you want to rebuild initrd for.
That's complicated - too many parameters to remember. And my keyboard doesn't have back-ticks. :-p -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Hello, On Wed, 12 Jun 2019, Carlos E. R. wrote:
On 12/06/2019 11.54, Rodney Baker wrote:
It's not complicated - I just use dracut -fM --kver `uname -r` (for the [..] That's complicated - too many parameters to remember. And my keyboard doesn't have back-ticks. :-p
# dracut -fM --kver $(uname -r) # dracut -fM --kver (< /proc/sys/kernel/osrelease ) # uname -r | xargs dracut -fM --kver # cat /proc/sys/kernel/osrelease | xargs dracut -fM --kver Better? -dnh -- <joost> Do you mean to say that I can read mail with vi too? ;-) <Joey> Didn't you know that? <Joey> :r /var/spool/mail/jk -- debian-mentors -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David Haller schrieb am 12.06.19 um 13:30:
Hello,
On Wed, 12 Jun 2019, Carlos E. R. wrote:
On 12/06/2019 11.54, Rodney Baker wrote:
It's not complicated - I just use dracut -fM --kver `uname -r` (for the [..] That's complicated - too many parameters to remember. And my keyboard doesn't have back-ticks. :-p
# dracut -fM --kver $(uname -r) # dracut -fM --kver (< /proc/sys/kernel/osrelease ) # uname -r | xargs dracut -fM --kver # cat /proc/sys/kernel/osrelease | xargs dracut -fM --kver
Better?
-dnh
Yes, better :) But mkinitrd is still shorter and more easy to remember :) SCNR, Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/06/2019 13.30, David Haller wrote:
Hello,
On Wed, 12 Jun 2019, Carlos E. R. wrote:
On 12/06/2019 11.54, Rodney Baker wrote:
It's not complicated - I just use dracut -fM --kver `uname -r` (for the [..] That's complicated - too many parameters to remember. And my keyboard doesn't have back-ticks. :-p
# dracut -fM --kver $(uname -r) # dracut -fM --kver (< /proc/sys/kernel/osrelease ) # uname -r | xargs dracut -fM --kver # cat /proc/sys/kernel/osrelease | xargs dracut -fM --kver
Better?
I can't remember any of that. I would have to copypaste from my command archive. But I do remember "mkinitrd", so it stays. :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 06/12/2019 06:30 AM, David Haller wrote:
Hello,
On Wed, 12 Jun 2019, Carlos E. R. wrote:
On 12/06/2019 11.54, Rodney Baker wrote:
It's not complicated - I just use dracut -fM --kver `uname -r` (for the [..] That's complicated - too many parameters to remember. And my keyboard doesn't have back-ticks. :-p
# dracut -fM --kver $(uname -r) # dracut -fM --kver (< /proc/sys/kernel/osrelease ) # uname -r | xargs dracut -fM --kver # cat /proc/sys/kernel/osrelease | xargs dracut -fM --kver
Better?
-dnh
Thanks Rodney, dns, Carlos, all, I'll see if I can bring the old laptop back to life with dracut, and if not, sure will be sad to see it go :) -- 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 06/12/2019 06:26 PM, David C. Rankin wrote:
# dracut -fM --kver $(uname -r) # dracut -fM --kver (< /proc/sys/kernel/osrelease ) # uname -r | xargs dracut -fM --kver # cat /proc/sys/kernel/osrelease | xargs dracut -fM --kver
Better?
-dnh
Thanks Rodney, dns, Carlos, all, I'll see if I can bring the old laptop back to life with dracut, and if not, sure will be sad to see it go :)
Success, After chrooting under /mnt. Re-running mkinitrd succeeded, but failed to install the boot loader due to a bad /lib64/libcrypt.so.1, so forced reinstall of glibc, re-ran mkinitrd, noticed there were about 10 packages "not checked" due to not yet being downloaded? (grabbed the list and forced installed them), then re-ran mkinitrd a 3rd time and it succeeded. Exited the chroot, umounted the bind mounts on dev, proc, sys and umounted home, but the mount of / on /mnt would not umount due to device busy. Ran fuser -m /mnt which listed no opened files (strange), so had to do a hard shutdown at that point. Pulled the net-install CD (where recover was run from) and presto, machine back up and running fine. Thanks for all the help. -- 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
participants (5)
-
Carlos E. R. -
David C. Rankin -
David Haller -
Rodney Baker -
Werner Flamme