Installing Qubes 3.1 : dracut Warning: /dev/root does not exist
2,640 views
Skip to first unread message
Orlessan
Jan 7, 2016, 2:19:42 PM1/7/16
to qubes...@googlegroups.com
Hello I'm trying to install Qubes 3.1 but after booting in UEFI mode I
select `install Qubes` and the installer rapidly enters dracut emergency
shell.
here are the last lines of `cat /run/initramfs/rdsosreport.txt` :
dracut: Scanning for all btrfs devices (repeat 10times)
dracut Warning: Could not boot.
dracut Warning: /dev/root does not exist
Any idea on how to fix this ?
select `install Qubes` and the installer rapidly enters dracut emergency
shell.
here are the last lines of `cat /run/initramfs/rdsosreport.txt` :
dracut: Scanning for all btrfs devices (repeat 10times)
dracut Warning: Could not boot.
dracut Warning: /dev/root does not exist
Any idea on how to fix this ?
Marek Marczykowski-Górecki
Jan 7, 2016, 6:00:52 PM1/7/16
to Orlessan, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Can you send full /run/initramfs/rdsosreport.txt? You can for example
copy it to some USB stick (other than installation media).
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWju4dAAoJENuP0xzK19csaYIH+gPIOMw2M16QYBnFx01hCC/I
qonadd/hjb2b/vNrS7XpSoc7lxDk7BYSntuz93bnmqb3ezhxN4tuyiY3ZUtAa/Oh
Gcak3//NSNKh/XH5ZkzRMO3BAHvLFfPhy9p2Z/0p5RWNJMzL8DhkKSmqfE1rl21d
ku85JIP71ugBT7fqxjZk6vzFVcU8fzp9pZyNE+H6uU16VbzPZybuLJgiiRLLtn6+
quvwISjCHwNbSSB/N+n6ttWmN4Nekn1S48PXXubSphKG3EZtLzr/GBqmvnQui0qZ
vlgO8al1aURL2kDTbMP3uRwH3MiklWEOwXuyaKCxN5gbQ68rQ7UVEQK0j9aszig=
=EvAh
-----END PGP SIGNATURE-----
Hash: SHA256
copy it to some USB stick (other than installation media).
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWju4dAAoJENuP0xzK19csaYIH+gPIOMw2M16QYBnFx01hCC/I
qonadd/hjb2b/vNrS7XpSoc7lxDk7BYSntuz93bnmqb3ezhxN4tuyiY3ZUtAa/Oh
Gcak3//NSNKh/XH5ZkzRMO3BAHvLFfPhy9p2Z/0p5RWNJMzL8DhkKSmqfE1rl21d
ku85JIP71ugBT7fqxjZk6vzFVcU8fzp9pZyNE+H6uU16VbzPZybuLJgiiRLLtn6+
quvwISjCHwNbSSB/N+n6ttWmN4Nekn1S48PXXubSphKG3EZtLzr/GBqmvnQui0qZ
vlgO8al1aURL2kDTbMP3uRwH3MiklWEOwXuyaKCxN5gbQ68rQ7UVEQK0j9aszig=
=EvAh
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Jan 7, 2016, 7:20:31 PM1/7/16
to Orlessan, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Fri, Jan 08, 2016 at 12:57:55AM +0100, Orlessan wrote:
> Sure here is the full report. Thanks. (forgot to respond to googlegroups)
>
> Le 1/8/2016 12:00 AM, Marek Marczykowski-Górecki a écrit :
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA256
> >
> >On Thu, Jan 07, 2016 at 08:19:29PM +0100, Orlessan wrote:
> >>Hello I'm trying to install Qubes 3.1 but after booting in UEFI mode I
> >>select `install Qubes` and the installer rapidly enters dracut emergency
> >>shell.
> >>
> >>here are the last lines of `cat /run/initramfs/rdsosreport.txt` :
> >>
> >> dracut: Scanning for all btrfs devices (repeat 10times)
> >> dracut Warning: Could not boot.
> >> dracut Warning: /dev/root does not exist
> >>
> >>Any idea on how to fix this ?
> >Can you send full /run/initramfs/rdsosreport.txt? You can for example
> >copy it to some USB stick (other than installation media).
(...)
> Sure here is the full report. Thanks. (forgot to respond to googlegroups)
>
> Le 1/8/2016 12:00 AM, Marek Marczykowski-Górecki a écrit :
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA256
> >
> >On Thu, Jan 07, 2016 at 08:19:29PM +0100, Orlessan wrote:
> >>Hello I'm trying to install Qubes 3.1 but after booting in UEFI mode I
> >>select `install Qubes` and the installer rapidly enters dracut emergency
> >>shell.
> >>
> >>here are the last lines of `cat /run/initramfs/rdsosreport.txt` :
> >>
> >> dracut: Scanning for all btrfs devices (repeat 10times)
> >> dracut Warning: Could not boot.
> >> dracut Warning: /dev/root does not exist
> >>
> >>Any idea on how to fix this ?
> >Can you send full /run/initramfs/rdsosreport.txt? You can for example
> >copy it to some USB stick (other than installation media).
> + blkid
> /dev/sda2: LABEL="data" UUID="54B2D6E3B2D6C91E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="66979637-893c-48e7-b823-294bb1fbcb06"
> /dev/sda3: UUID="0b08d3cd-0d62-40da-b3e2-599f4c834b47" TYPE="ext4" PARTLABEL="d" PARTUUID="74cfdef3-4020-4ddc-8b0a-0652fe1736da"
> /dev/sr0: UUID="2015-07-10-09-57-16-00" LABEL="J_CCSA_X64FRE_FR-FR_DV5" TYPE="udf"
> /dev/nvme0n1p1: LABEL="RM-CM-)cupM-CM-)ration" UUID="464ACB184ACB0421" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c3272b63-2a9f-4ca0-a62c-c892f374b537"
> /dev/nvme0n1p2: UUID="74CD-BD33" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b790d826-8e17-4ec7-b89b-12d783ec520e"
> /dev/nvme0n1p4: UUID="0E3CEA073CE9E9A3" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="0362d1f2-58e5-4f76-b313-810b39a0bff5"
> /dev/sdb1: LABEL="USB Y" UUID="E456-F060" TYPE="vfat"
> /dev/sdc1: LABEL="USBV" UUID="5878-18AC" TYPE="vfat"
> /dev/sdd1: UUID="F220-30B3" TYPE="vfat" PARTUUID="429817b4-01"
> /dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="41bf5cda-772e-465f-be67-90cfc879c06b"
> /dev/nvme0n1: PTUUID="f9ca7213-905e-425e-aa19-3872c8801ada" PTTYPE="gpt"
> /dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="24da321d-672f-484b-be1f-6fee7e3b2304"
I can't see anything even close to Qubes installation media label. But
there are USB2.0 and USB3.0 devices detected, so probably not a driver
problem. Are you sure that you've written the installation image
correctly?
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Ife4f6xylaEILL+AoBUg7Oiv5ZtN+z9q9zLZYPyvSZJ2E7x5AhiSOZ2uyMMQQPkw
Wwt94cnckTE8T7rwxYIA0+iu9RXV3Z9uVeX/BFB+UL/lS4nNhnW4SI3CB8xQrdi/
DV5TUDy40bKzVX1xsytBP9WlF53MWNdTd/Gkqd7Wuus8WolgHn745ecDAmdT9+Jk
1wO6vezdDzwijdlkmfEZ0BnaH8RNAq7p7SAGqzvagatr4ebQVzNQP9wiEu6jD0L+
2b7qiYi00hqkXbu9gVNf3v8u73RqzjZcZ1H49FLh6xdOqqw18hCyERB6XjGCF2k=
=foqU
-----END PGP SIGNATURE-----
Orlessan
Jan 7, 2016, 8:53:40 PM1/7/16
to qubes...@googlegroups.com
Well you're right I extracted the .iso onto a FAT32 formated USB drive
because I thought it would be better for the UEFI boot. I remade a USB
installer using dd and now I have a new symptom :
If I select "Verify source and install Qubes" the process freezes after
the test passes.
If I select "Install Qubes" I got this :
Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only
And then the booting process freezes completely and I can only reboot
with ctrl+alt+del. I have to add that the Qubes graphical logo blinks
very briefly before it comes back to the command line and freezes.
Any idea on what is happening ? Is there a way to activate a verbose
mode so there is more detail on the failure reason ?
because I thought it would be better for the UEFI boot. I remade a USB
installer using dd and now I have a new symptom :
If I select "Verify source and install Qubes" the process freezes after
the test passes.
If I select "Install Qubes" I got this :
Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only
And then the booting process freezes completely and I can only reboot
with ctrl+alt+del. I have to add that the Qubes graphical logo blinks
very briefly before it comes back to the command line and freezes.
Any idea on what is happening ? Is there a way to activate a verbose
mode so there is more detail on the failure reason ?
Marek Marczykowski-Górecki
Jan 8, 2016, 8:07:06 PM1/8/16
to Orlessan, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Fri, Jan 08, 2016 at 02:53:32AM +0100, Orlessan wrote:
> Well you're right I extracted the .iso onto a FAT32 formated USB drive
> because I thought it would be better for the UEFI boot. I remade a USB
> installer using dd and now I have a new symptom :
>
> If I select "Verify source and install Qubes" the process freezes after the
> test passes.
> If I select "Install Qubes" I got this :
>
> Ignoring BGRT : invalid status 0 (expected 1)
> mce : unable to init device /dev/mcelog (rc:-16)
> /etc/vconsole.cong line 1: 1=: command not found
> /etc/vconsole.cong line 1: 1=: command not found
> sd 4:0:0:0:[sdb] no caching mode page found
> sd 4:0:0:0:[sdb] assuming drive cache : write through
> mount: /dev/sdb is write protected, mounting read-only
>
> And then the booting process freezes completely and I can only reboot with
> ctrl+alt+del. I have to add that the Qubes graphical logo blinks very
> briefly before it comes back to the command line and freezes.
>
> Any idea on what is happening ? Is there a way to activate a verbose mode so
> there is more detail on the failure reason ?
Since ctrl+alt+del does work, it isn't completely hanging. Most likely
> Well you're right I extracted the .iso onto a FAT32 formated USB drive
> because I thought it would be better for the UEFI boot. I remade a USB
> installer using dd and now I have a new symptom :
>
> If I select "Verify source and install Qubes" the process freezes after the
> test passes.
> If I select "Install Qubes" I got this :
>
> Ignoring BGRT : invalid status 0 (expected 1)
> mce : unable to init device /dev/mcelog (rc:-16)
> /etc/vconsole.cong line 1: 1=: command not found
> /etc/vconsole.cong line 1: 1=: command not found
> sd 4:0:0:0:[sdb] no caching mode page found
> sd 4:0:0:0:[sdb] assuming drive cache : write through
> mount: /dev/sdb is write protected, mounting read-only
>
> And then the booting process freezes completely and I can only reboot with
> ctrl+alt+del. I have to add that the Qubes graphical logo blinks very
> briefly before it comes back to the command line and freezes.
>
> Any idea on what is happening ? Is there a way to activate a verbose mode so
> there is more detail on the failure reason ?
some graphics driver issue. Are you able to switch to different console
(ctrl+alt+f2)?
As for verbose mode, its hard to enable in UEFI mode[1], you need to edit
xen.cfg file inside images/efiboot.img. I think the easiest way would be
mounting a second partition of the USB drive (yes, installation image
contains two partitions). Then find EFI/BOOT/xen.cfg and remove "quiet"
option.
[1] https://github.com/QubesOS/qubes-issues/issues/1598
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
ELA+tmMamORcvYZWZIK1cQs8wLetmOIeg5TA+UNaCW/DKRdbOlmwsDKLOWqGpcui
niEJxFN/x4/jZclTtTg6pMNqVtjrxgj1Utb7L/iQue5NUVOsGCVS6RnR1zCrme2c
NN+ZWnYr6lKFqoJIp9w5UZebR7zjEqLzCX5tEi5GPvoJ6qljbUejhVBm6ACdz9XL
t8sjCA0aeCSzQ6crgcHqPKGDIFkESsA2FcVwjPORxlA81g9MZpK6u4PyaQDg5RV6
3vOUudgXrZ2pJYGQXum/+6/u5yGbIFVRlsMv2HZ4A07WBU+k1b5dPbh43pRpJOg=
=hX7h
-----END PGP SIGNATURE-----
Orlessan
Jan 9, 2016, 9:57:51 AM1/9/16
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
It is true that ctrl+alt+del works and reboots 2sec after I hit that but
I can't change console with ctrl+alt+f2 or other.
I removed the quiet option but unfortunately it didn't help much since
the boot stops at random moments :
1st time : [OK] Started Load/Save Random Seed.
2nd time : [OK] Started Apply Kernel
3rd time : [OK] tarted Configure read-only root support
4 : [OK] Reached target Local file systems (pre)
It always stops after the logo blinks for less than a second. My
computer config is : http://pcpartpicker.com/p/3Z6pCJ
I have an Inno3D iChill GeForce GTX 980 Ti X3 Air Boss Ultra 6GB is it
compatible with Qubes ? Do you know if it's possible to buy a cheap
compatible card that I would stick into a second PCI slot and that would
get Qubes to work ?
I can't change console with ctrl+alt+f2 or other.
I removed the quiet option but unfortunately it didn't help much since
the boot stops at random moments :
1st time : [OK] Started Load/Save Random Seed.
2nd time : [OK] Started Apply Kernel
3rd time : [OK] tarted Configure read-only root support
4 : [OK] Reached target Local file systems (pre)
It always stops after the logo blinks for less than a second. My
computer config is : http://pcpartpicker.com/p/3Z6pCJ
I have an Inno3D iChill GeForce GTX 980 Ti X3 Air Boss Ultra 6GB is it
compatible with Qubes ? Do you know if it's possible to buy a cheap
compatible card that I would stick into a second PCI slot and that would
get Qubes to work ?
Orlessan
Jan 10, 2016, 10:55:48 AM1/10/16
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
I was able to fix the problem by adding "nomodeset" to xen.cfg. Now the
graphical installer runs normally but a new problem appears when I reach
the partitionning menu.
I make a partition for /, a partition for /boot and the EFI partition
is already existing from windows. Problem is that when I validate it says :
"you have not created a bootloader stage1 target device"
"you have not created a bootable partition"
this happens whether the /boot partition is formated in ext4 or EFI.
If I delete the /boot partition it simply says "failed to find a
suitable stage1 device".
How do I do get this to work ? I have to add that I have the same
problem when I try to install Fedora 23 vanilla.
graphical installer runs normally but a new problem appears when I reach
the partitionning menu.
I make a partition for /, a partition for /boot and the EFI partition
is already existing from windows. Problem is that when I validate it says :
"you have not created a bootloader stage1 target device"
"you have not created a bootable partition"
this happens whether the /boot partition is formated in ext4 or EFI.
If I delete the /boot partition it simply says "failed to find a
suitable stage1 device".
How do I do get this to work ? I have to add that I have the same
problem when I try to install Fedora 23 vanilla.
Reply all
Reply to author
Forward
0 new messages