system doesn't boot after update

101 views
Skip to first unread message

Jovani

unread,
Oct 28, 2018, 10:43:38 AM10/28/18
to qubes-users
Greetings all,

I have recently updated dom0 and fedora template and now cannot load the system

Even old kernels are not loading

System shows qubes screen, after selecting the kernel it is asking for luks password and then fail

I tried to regenrate initframe and regenerate grub but still not loading

Red errors I am getting

Fsck failed with error 4
Failed to start file system check on /Dec/mapper/luks-******
Dependency failed for /sysroot
Dependency failed for initrd root file system
Dependency failed for reload configuration from the real root


Please help

Thanks

awokd

unread,
Oct 28, 2018, 6:57:54 PM10/28/18
to qubes...@googlegroups.com


Jovani:
> Greetings all,
>
> I have recently updated dom0 and fedora template and now cannot load the system
>
> Even old kernels are not loading
>
> System shows qubes screen, after selecting the kernel it is asking for luks password and then fail
>
> I tried to regenrate initframe and regenerate grub but still not loading
>
> Red errors I am getting
>
> Fsck failed with error 4
> Failed to start file system check on /Dec/mapper/luks-******

Does it really say "Dec" there, or is that a typo? If it's really "Dec",
find where it's trying to load that and change it to "dev" instead.

joeh...@gmail.com

unread,
Oct 29, 2018, 12:39:03 AM10/29/18
to qubes-users
Me too, I did qvm-dom0-update yesterday and when it tried to re-boot it got in a boot loop, and I'll re-type the messages here:
---------------------
Xen 4.8.4 (c/s) EFI loader
Using configuration file 'xen.cfg'
vmlinux-4.14.74-1.pvops.qubes.x86_64: 0x00000000495ae000-0x0000000049b8db20
initramfs-4.14.74-1.pvops.qubes.x86_64.img: 0x0000000049002000-0x00000000495ae000
0x0000:0x01:0x00.0x0: ROM: 0x19400 bytes at 0x5302e018
0x0000:0x00:0x02.0x0: ROM: 0x10000 bytes at 0x5300c018
---------------------
[ 0.179397] ACPI Error: [\_SB_.PCIO.XHC_.?HUB.HS11] Namespace lookup failure
AE-NOT_FOUND (20170720/dswload-210)
[ 0.179406] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170720/psobject-252)
[ 0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading table (20170728/tbxfload-220)
[ 0.188039] ACPI Error: 1 table load failures, 11 successful (20170728/tbxflad-246)
[ 0.508657] Initramfs unpacking failed: read error
[ 2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on unknown-block(0.0)
[ 2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted 4.1474-1.pvops.qubes.x86_64 #1
[ 2.762790] Hardware name: LENOVO , BIOS N1TET41W (1.15) 10/20/2017
[ 2.762813] Call Trace:
[ 2.762826] dump_stack+0x5c/0x85
[ 2.762839] panic+0xc4/0x252
[ 2.762851] mount_block_root+0x35b/0x52c
[ 2.762865] ? do_early_param+0x16e/0x16e
[ 2.762879] prepare_namespace+0x278/0x245
[ 2.762892] ? do_early_param+0x16e/0x16e
[ 2.762905] kernel_init_freeable+0x2c8/0x324
[ 2.762920] ? rest_init+0xb0/0xb0
[ 2.762932] kernel_init+0xa/0x101
[ 2.762945] ret_from_fork+0x35/0x40
[ 2.762964] Kernel Offset: disabled
------------------------

I anyone could help me get my qubes running again I'd be much obliged.

stas...@gmail.com

unread,
Oct 29, 2018, 3:53:55 AM10/29/18
to qubes-users
Hello

Sorry, it was a typo. It is dev
I will try to paste a whole log later today

Thanks

joeh...@gmail.com

unread,
Oct 29, 2018, 4:20:37 AM10/29/18
to qubes-users

I just see there was another one with the same problem:
https://groups.google.com/forum/#!topic/qubes-users/ftXn36ipklQ
I'm going to try the solution proposed there and will continue in that thread, as it is more related than this one.

Sorry for the wrong posting here.

Fidel Ramos

unread,
Oct 29, 2018, 5:22:45 AM10/29/18
to joeh...@gmail.com, qubes-users
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 29, 2018 4:39 AM, <joeh...@gmail.com> wrote:

> Me too, I did qvm-dom0-update yesterday and when it tried to re-boot it got in a boot loop, and I'll re-type the messages here:
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Xen 4.8.4 (c/s) EFI loader
> Using configuration file 'xen.cfg'
> vmlinux-4.14.74-1.pvops.qubes.x86_64: 0x00000000495ae000-0x0000000049b8db20
> initramfs-4.14.74-1.pvops.qubes.x86_64.img: 0x0000000049002000-0x00000000495ae000
> 0x0000:0x01:0x00.0x0: ROM: 0x19400 bytes at 0x5302e018
> 0x0000:0x00:0x02.0x0: ROM: 0x10000 bytes at 0x5300c018
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> [ 0.179397] ACPI Error: [\SB.PCIO.XHC_.?HUB.HS11] Namespace lookup failure
> AE-NOT_FOUND (20170720/dswload-210)
> [ 0.179406] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170720/psobject-252)
> [ 0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading table (20170728/tbxfload-220)
> [ 0.188039] ACPI Error: 1 table load failures, 11 successful (20170728/tbxflad-246)
> [ 0.508657] Initramfs unpacking failed: read error
> [ 2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on unknown-block(0.0)
> [ 2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted 4.1474-1.pvops.qubes.x86_64 #1
> [ 2.762790] Hardware name: LENOVO , BIOS N1TET41W (1.15) 10/20/2017
> [ 2.762813] Call Trace:
> [ 2.762826] dump_stack+0x5c/0x85
> [ 2.762839] panic+0xc4/0x252
> [ 2.762851] mount_block_root+0x35b/0x52c
> [ 2.762865] ? do_early_param+0x16e/0x16e
> [ 2.762879] prepare_namespace+0x278/0x245
> [ 2.762892] ? do_early_param+0x16e/0x16e
> [ 2.762905] kernel_init_freeable+0x2c8/0x324
> [ 2.762920] ? rest_init+0xb0/0xb0
> [ 2.762932] kernel_init+0xa/0x101
> [ 2.762945] ret_from_fork+0x35/0x40
> [ 2.762964] Kernel Offset: disabled
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> I anyone could help me get my qubes running again I'd be much obliged.


I found this post in an Archlinux forum that has the same error: https://bbs.archlinux.org/viewtopic.php?id=131785 The problem was that the /boot partition ran out of space. Try checking the available space in your boot partition and if it's zero or low remove some of the old kernels, then recreate the initramfs images.

stas...@gmail.com

unread,
Nov 15, 2018, 7:28:18 AM11/15/18
to qubes-users
Hello

Thanks for reply

I deleted new kernel from /boot but it still not loading with old one

Any other suggestions

Thanks

Reply all
Reply to author
Forward
0 new messages