Unable to boot Q4.0 Dracut Emergency Shell /dev/qubes_dom0/root does not exist etc

120 views
Skip to first unread message

cicero

unread,
Apr 19, 2018, 5:37:09 PM4/19/18
to qubes...@googlegroups.com
Hello,

The system has been fine , till I did a reboot (there were some debian
and Fed Template updates but)

The last message in journalctl says kernel: audit: type=1131
....../usr/lib/systemd/systemd hostname=? audit=? terminal=?


dracut-initqueue timeout etc



any help appreciated

john

unread,
Apr 20, 2018, 2:06:54 AM4/20/18
to qubes...@googlegroups.com
how would I regenerate my initramfs ?

or this is what Marek said on the usergroup: You should get your system
mounted as
/mnt/sysimage or sth like that


so how do I mount /mnt/sysimage ?







I am really not looking forward to another reinstall of Qubes 4.0 ,
only thing I did different is I didn't shutdown all the VMs before
doing sudo shutdown -h now ; as I get fatigued from all the
shutdown starts of the VMs .... I keep thinking it may stabilize but
not so far re: how often I have to mess with opening and closing the
VMs...

awokd

unread,
Apr 20, 2018, 4:15:50 PM4/20/18
to john, qubes...@googlegroups.com
On Fri, April 20, 2018 6:06 am, john wrote:
> On 04/19/18 11:36, cicero wrote:
>
>> Hello,
>>
>>
>> The system has been fine , till I did a reboot (there were some debian
>> and Fed Template updates but)
>>
>> The last message in journalctl  says kernel: audit: type=1131
>> ....../usr/lib/systemd/systemd  hostname=? audit=?  terminal=?
>>
>>
>>
>> dracut-initqueue timeout  etc
>>
>>
>>
>> any help appreciated
>>
>
> how would I regenerate my initramfs ?
>
> or this is what Marek said on the usergroup: You should get your system
> mounted as /mnt/sysimage or sth like that
>
>
>
> so how do I mount /mnt/sysimage ?

Boot in rescue mode and it will get you there. To regenerate do:

sudo dracut -f /boot/efi/EFI/qubes/initramfs-$(uname -r).img $(uname -r)

>
> I am really not looking forward to another reinstall of Qubes 4.0 ,
> only thing I did different is I didn't shutdown all the VMs before doing
> sudo shutdown -h now ; as I get fatigued from all the shutdown starts
> of the VMs .... I keep thinking it may stabilize but not so far re:
> how often I have to mess with opening and closing the VMs...

That shouldn't matter. Maybe it was a recent update?


cicero

unread,
Apr 20, 2018, 4:21:30 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
On 04/20/18 10:15, awokd wrote:
> On Fri, April 20, 2018 6:06 am, john wrote:
>> On 04/19/18 11:36, cicero wrote:
>>
>>> Hello,
>>>
>>>
>>> The system has been fine , till I did a reboot (there were some debian
>>> and Fed Template updates but)
>>>
>>> The last message in journalctl  says kernel: audit: type=1131
>>> ....../usr/lib/systemd/systemd  hostname=? audit=?  terminal=?
>>>
>>>
>>>
>>> dracut-initqueue timeout  etc
>>>
>>>
>>>
>>> any help appreciated
>>>
>>
>> how would I regenerate my initramfs ?
>>
>> or this is what Marek said on the usergroup: You should get your system
>> mounted as /mnt/sysimage or sth like that
>>
>>
>>
>> so how do I mount /mnt/sysimage ?
>
> Boot in rescue mode and it will get you there. To regenerate do:

thanks for responding, don't hate me, but ? rescue mode ? ; do you mean
where it dumpts me to the dracut shell or do you mean my Q4 installer
USB stick, I can't seem to get it to stop from flashing past to the
installer ...... I did make a Live Fedora USB drive and have it booted
up now, but I am stuck at the basics about how to "mount the system" lol


>
> sudo dracut -f /boot/efi/EFI/qubes/initramfs-$(uname -r).img $(uname -r)
>
>>
>> I am really not looking forward to another reinstall of Qubes 4.0 ,
>> only thing I did different is I didn't shutdown all the VMs before doing
>> sudo shutdown -h now ; as I get fatigued from all the shutdown starts
>> of the VMs .... I keep thinking it may stabilize but not so far re:
>> how often I have to mess with opening and closing the VMs...
>
> That shouldn't matter. Maybe it was a recent update?

I did not dom0 updates at all lately, there were some template updates ,
but AFAIK that should not effect booting ?


>
>

cicero

unread,
Apr 20, 2018, 4:31:03 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
please disregard, I found rescue mode ......

cicero

unread,
Apr 20, 2018, 4:39:51 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
@ choose '1' to /mnt/sysimage, it wants the sda2 LUKS passphrase, but
then hangs, maybe I should 3) skip to shell .....and then ? :)
cheers

cicero

unread,
Apr 20, 2018, 4:45:42 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
in the shell
#dracut
bash: dracut: command not found

so maybe I should give up don't want to bother you

awokd

unread,
Apr 20, 2018, 4:47:53 PM4/20/18
to cicero, aw...@danwin1210.me, qubes...@googlegroups.com
On Fri, April 20, 2018 8:39 pm, cicero wrote:
> @ choose '1' to /mnt/sysimage, it wants the sda2 LUKS passphrase, but
> then hangs, maybe I should 3) skip to shell .....and then ? :) cheers

Try giving it a minute then rebooting and try again. It didn't work 100%
of the time for me either. Skip to shell won't help.


cicero

unread,
Apr 20, 2018, 4:50:07 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
I did notice that the reason I wasn't seeing the "rescue mode" is
because if the installation usb drive is set in the bios as UEFI mode it
doesn't show, just goes right to the installer just the green bar is
there for a 2nd but not responsive ; in regular mode the media *Does
show

Maybe I am outta luck I've tried twice with the LUKS for sda2 just
hangs, but I am confused if /boot is on sda1 why does sda2 matter
.... oh well

cicero

unread,
Apr 20, 2018, 5:10:36 PM4/20/18
to aw...@danwin1210.me, qubes...@googlegroups.com
actually after 15 minutes it actually says:
"you don't have any linux partitions" ; enter to exit to shell, so
therefore I guess I give up and reinstall ?

awokd

unread,
Apr 20, 2018, 5:17:54 PM4/20/18
to cicero, aw...@danwin1210.me, qubes...@googlegroups.com
That might be faster than trying to troubleshoot, but it would be nice to
know what happened! I'm not sure how to troubleshoot it though at this
point...


Reply all
Reply to author
Forward
0 new messages