Hi,
A recent update with new kernel has broken my boot. This is what happens: I boot in through grub. Pretty soon, I get:
Generating "/run/initramfs/rsdsosreport.txt" Welcome to emergency mode! After loggin in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into defauly mode. Give root password for maintenance. (or press Control-D to continue):
I do not have root on this machine, so I am not sure what to do (I have sudo status). What am I supposed to do? (I may say Ctrl-D does get me the login screen, but why this message and rigmarole)?
This is the third time this has happened, on a laptop. The other two laptops had this issue at different times towards the fag end of F20 and could only be fixed by a reinstall of the OS.
Any suggestions/pointers would be appreciated. Happy to provide more information as possible.
Best wishes, Ranjan
On Thu, Dec 18, 2014 at 10:06 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
A recent update with new kernel has broken my boot. This is what happens: I boot in through grub. Pretty soon, I get:
Generating "/run/initramfs/rsdsosreport.txt" Welcome to emergency mode! After loggin in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into defauly mode. Give root password for maintenance. (or press Control-D to continue):
I do not have root on this machine, so I am not sure what to do (I have sudo status). What am I supposed to do? (I may say Ctrl-D does get me the login screen, but why this message and rigmarole)?
It sounds like something required wasn't ready, and caused boot to get dropped at emergency.target. By the time you control-D to continue, the require thing is ready so boot continued. Speculation.
Anyway, if you can locate /run/initramfs/rdsosreport.txt and post it somewhere, that'd be useful at figuring out what the problem is. Also include version of dracut: $ rpm -q dracut
Hi,
Thanks for offering to help!
On Thu, 18 Dec 2014 10:14:37 -0700 Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 18, 2014 at 10:06 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
A recent update with new kernel has broken my boot. This is what happens: I boot in through grub. Pretty soon, I get:
Generating "/run/initramfs/rsdsosreport.txt" Welcome to emergency mode! After loggin in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into defauly mode. Give root password for maintenance. (or press Control-D to continue):
I do not have root on this machine, so I am not sure what to do (I have sudo status). What am I supposed to do? (I may say Ctrl-D does get me the login screen, but why this message and rigmarole)?
It sounds like something required wasn't ready, and caused boot to get dropped at emergency.target. By the time you control-D to continue, the require thing is ready so boot continued. Speculation.
Anyway, if you can locate /run/initramfs/rdsosreport.txt and post it somewhere, that'd be useful at figuring out what the problem is. Also include version of dracut: $ rpm -q dracut
So, I do not know what to do here:
I try the following (sudo to be sure):
$ sudo cat /run/initramfs/rdsosreport.txt cat: /run/initramfs/rdsosreport.txt: No such file or directory
Indeed:
$ sudo locate rdsosreport [sudo] password for maitra: /usr/lib/dracut/modules.d/99base/rdsosreport.sh
So, where is this file?
Btw, here is the other output you asked for:
$ rpm -q dracut dracut-038-31.git20141204.fc21.x86_64
I am happy to provide more information as needed.
Many thanks again for helping!
Best wishes, Ranjan
____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium
On Thu, Dec 18, 2014 at 11:08 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Thanks for offering to help!
On Thu, 18 Dec 2014 10:14:37 -0700 Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 18, 2014 at 10:06 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
A recent update with new kernel has broken my boot. This is what happens: I boot in through grub. Pretty soon, I get:
Generating "/run/initramfs/rsdsosreport.txt" Welcome to emergency mode! After loggin in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into defauly mode. Give root password for maintenance. (or press Control-D to continue):
I do not have root on this machine, so I am not sure what to do (I have sudo status). What am I supposed to do? (I may say Ctrl-D does get me the login screen, but why this message and rigmarole)?
Yeah I'm actually confused on this point too, now that I've tried it.
The installer allows installation to complete, without setting a root password, so long as a user has been created. But emergency shell requires a root password. So... basic boot time troubleshooting is incompatible with an installer that allows no root password being set.
I think the easiest, maybe least desirable, and possibly against your local policy, would be to complete the boot (control-d) and then set a root password: sudo passwd root
$ sudo cat /run/initramfs/rdsosreport.txt cat: /run/initramfs/rdsosreport.txt: No such file or directory
I'm going to guess, that this file goes away after boot completes, it doesn't get moved anywhere. And since you can't login as root, you can't copy it somewhere else. So... to get that report you'd going to need to be root.
For security purposes, you could make the root password temporary for troubleshooting, then change it again from your regular (admin) account: sudo passwd root, and make it an impossible password that you don't record anywhere, you could even has the proposed password through shasum and use that as the password and not record it anywhere. Basically deep six root. It's no different than root without a password. If any wheel account is hacked, they can change the root password in any case.
On Thu, 18 Dec 2014 12:33:06 -0700 Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 18, 2014 at 11:08 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Thanks for offering to help!
On Thu, 18 Dec 2014 10:14:37 -0700 Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 18, 2014 at 10:06 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
A recent update with new kernel has broken my boot. This is what happens: I boot in through grub. Pretty soon, I get:
Generating "/run/initramfs/rsdsosreport.txt" Welcome to emergency mode! After loggin in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into defauly mode. Give root password for maintenance. (or press Control-D to continue):
I do not have root on this machine, so I am not sure what to do (I have sudo status). What am I supposed to do? (I may say Ctrl-D does get me the login screen, but why this message and rigmarole)?
Yeah I'm actually confused on this point too, now that I've tried it.
The installer allows installation to complete, without setting a root password, so long as a user has been created. But emergency shell requires a root password. So... basic boot time troubleshooting is incompatible with an installer that allows no root password being set.
I think the easiest, maybe least desirable, and possibly against your local policy, would be to complete the boot (control-d) and then set a root password: sudo passwd root
$ sudo cat /run/initramfs/rdsosreport.txt cat: /run/initramfs/rdsosreport.txt: No such file or directory
I'm going to guess, that this file goes away after boot completes, it doesn't get moved anywhere. And since you can't login as root, you can't copy it somewhere else. So... to get that report you'd going to need to be root.
Thank you very much again! I did as you suggested and copied the file over to /tmp and uploaded it over.
$ fpaste /tmp/rdsosreport.txt Uploading (5.2KiB)... http://ur1.ca/j5tak -> http://paste.fedoraproject.org/161093/89317911
Many thanks again!
Best wishes, Ranjan
____________________________________________________________ Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/manager
On Thu, Dec 18, 2014 at 12:45 PM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Thank you very much again! I did as you suggested and copied the file over to /tmp and uploaded it over.
$ fpaste /tmp/rdsosreport.txt Uploading (5.2KiB)... http://ur1.ca/j5tak -> http://paste.fedoraproject.org/161093/89317911
5.2KiB is too small, did it get truncated? Is the original /run/initramfs/rdsosreport.txt that small? Normally rdsosreport is too big for fpaste in my experience (?) but I forget what the fpaste limits are.
Anyway, if the rdsosreport is really that small, then you're going to need to extract more information than you currently have.
mount /dev/usb /sysroot journalctl -l -o short-monotonic > /sysroot/journal.txt umount /sysroot exit
Now you can put the journal.txt somewhere.
ACTUALLY before you go to the trouble of all of that, there is a newer dracut, so I would do this instead first:
dnf upgrade dracut --enablerepo=updates-testing dracut -f
That'll get you dracut-038-32.git20141216.fc21, and a new initramfs built with that. See if that fixes boot. And if it doesn't THEN you can write out a journal and post it somewhere.
Thanks very much again! I upgraded dracut using the instructions suggested but no major visible changes.
$ fpaste /tmp/rdsosreport.txt Uploading (5.2KiB)... http://ur1.ca/j5tak -> http://paste.fedoraproject.org/161093/89317911
5.2KiB is too small, did it get truncated? Is the original /run/initramfs/rdsosreport.txt that small? Normally rdsosreport is too big for fpaste in my experience (?) but I forget what the fpaste limits are.
Anyway, if the rdsosreport is really that small, then you're going to need to extract more information than you currently have.
Yes, it is that small.
mount /dev/usb /sysroot journalctl -l -o short-monotonic > /sysroot/journal.txt umount /sysroot exit
I was unable to get the mount working but I did do the journalctl command and piped it to /tmp. THe file is 50MB long.
Is there a place I can put this? fpaste is not happy!
Many thanks, Ranjan
____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
-
Chris Murphy -
Ranjan Maitra