Help, I broke my Qubes...
93 views
Skip to first unread message
Zeko
Nov 8, 2019, 9:23:29 PM11/8/19
to qubes...@googlegroups.com
Hello
I ran sudo qubesctl state.sls qvm.sys-usb on a LUKS install with USB keyboard and mouse. (Yeah bad idea)
I use a removable drive to boot since I multiboot on that PC and the drive was unmounted at the time so the command reported that 4 out of 5 steps succeeded while grubconfig failed. Then I restarted to try again and get the grubconfig done since remounting that drive as /boot never worked for some reason, didn't bother with that this time. (worse idea)
At the moment Qubes will boot, I get to the first (disk) password screen and the progress slider goes to about 60% and the computer resets.
Can anything be done? Unfortunately, my backups are a tad old. It seems I can at least get it to unlock the LVM partition, though...
Sent with ProtonMail Secure Email.
Claudia
Nov 12, 2019, 10:51:39 AM11/12/19
to qubes...@googlegroups.com
'Zeko' via qubes-users:
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
To be honest I don't completely understand what happened. But, have you
tried removing "rhgb quiet" (and "splash" if present) from your kernel
command line? This should disable the graphical boot screen and give you
messages from the kernel and systemd during boot. That way you can
hopefully at least see what's going on, and we can go from there.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
>
To be honest I don't completely understand what happened. But, have you
tried removing "rhgb quiet" (and "splash" if present) from your kernel
command line? This should disable the graphical boot screen and give you
messages from the kernel and systemd during boot. That way you can
hopefully at least see what's going on, and we can go from there.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Rafael Reis
Nov 13, 2019, 5:51:21 AM11/13/19
to qubes-users
Or you can just press F12, anytime during boot, it goes into verbose mode right away.
Zeko
Nov 21, 2019, 3:58:53 AM11/21/19
to qubes...@googlegroups.com
Sorry about the delay, I had a week of ddrescuing a failing drive to distract me. I've managed to boot the Qubes DVD (EFI settings were originally preventing me) but didn't get the rescue process to work, it keeps asking me for passwords to non-Qubes luks partitions. I can open the partition with the password tho.
Booted it without "rhgb quiet" and it gets to "Starting Start Qubes VM sys-usb", prints some messages about seizing and disconnecting a bunch of USB devices, then:
[ OK ] Stopped target Local File Systems
Unmounting /boot... (if it matters, boot is on a USB device)
[ 172.272900 ] usb 1-12: USB disconnect, device number 3
[ OK ] Unmounted /boot.
[ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet figured out which partition this is)
[ 172.287911 ] usb 1-13: USB disconnect, device number 4
Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a dump of CPU registers, and the machine reboots.
The cause of this all is me installing sys-usb following Qubes website instructions, because the instructions said not to do that if you have both USB mouse and kbd and I do and/or because one step of the install failed but I still rebooted my PC without trying to revert changes in dom0.
Zeko
Booted it without "rhgb quiet" and it gets to "Starting Start Qubes VM sys-usb", prints some messages about seizing and disconnecting a bunch of USB devices, then:
[ OK ] Stopped target Local File Systems
Unmounting /boot... (if it matters, boot is on a USB device)
[ 172.272900 ] usb 1-12: USB disconnect, device number 3
[ OK ] Unmounted /boot.
[ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet figured out which partition this is)
[ 172.287911 ] usb 1-13: USB disconnect, device number 4
Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a dump of CPU registers, and the machine reboots.
The cause of this all is me installing sys-usb following Qubes website instructions, because the instructions said not to do that if you have both USB mouse and kbd and I do and/or because one step of the install failed but I still rebooted my PC without trying to revert changes in dom0.
Zeko
awokd
Nov 21, 2019, 2:22:45 PM11/21/19
to qubes...@googlegroups.com
'Zeko' via qubes-users:
> [ 172.272900 ] usb 1-12: USB disconnect, device number 3
> [ OK ] Unmounted /boot.
> [ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet figured out which partition this is)
> [ 172.287911 ] usb 1-13: USB disconnect, device number 4
>
> Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a dump of CPU registers, and the machine reboots.
>
> The cause of this all is me installing sys-usb following Qubes website instructions, because the instructions said not to do that if you have both USB mouse and kbd and I do and/or because one step of the install failed but I still rebooted my PC without trying to revert changes in dom0.
Boot in rescue mode. Edit your xen.cfg and remove the option named
something like qubes.hideallusb. Edit /var/lib/qubes/qubes.xml and
locate sys-usb's autostart property, and set to False. Reboot.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
> [ OK ] Stopped target Local File Systems
> Unmounting /boot... (if it matters, boot is on a USB device)
Probably.
> Unmounting /boot... (if it matters, boot is on a USB device)
> [ 172.272900 ] usb 1-12: USB disconnect, device number 3
> [ OK ] Unmounted /boot.
> [ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet figured out which partition this is)
> [ 172.287911 ] usb 1-13: USB disconnect, device number 4
>
> Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a dump of CPU registers, and the machine reboots.
>
> The cause of this all is me installing sys-usb following Qubes website instructions, because the instructions said not to do that if you have both USB mouse and kbd and I do and/or because one step of the install failed but I still rebooted my PC without trying to revert changes in dom0.
something like qubes.hideallusb. Edit /var/lib/qubes/qubes.xml and
locate sys-usb's autostart property, and set to False. Reboot.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
Zeko
Nov 21, 2019, 4:51:04 PM11/21/19
to qubes...@googlegroups.com
‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> You received this message because you are subscribed to the Google Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fc6c6822-9a15-d219-a234-0999f93c9675%40danwin1210.me.
>
Automatic rescue process didn't work, had to go to shell and mount /dev/mapper/qubes_dom0-root manually.
Didn't find any mention of "usb" in xen.cfg, neither in the one in /boot/efi/EFI/qubes on the dom0 volume, nor on the boot USB. Both files' timestamps predate this problem.
I changed autostart to False in the qubes.xml entry for sys-usb but the OS still starts sys-usb and panicks like before.
Also if I didn't mention this earlier, when I ran the command that installed sys-usb, it reported progress on 5-6 steps and all succeeded except one. I believe the one that failed was editing something in /boot and I think I had umounted /boot and removed the stick some time before running that command.
On Thursday, November 21, 2019 8:22 PM, 'awokd' via qubes-users <qubes...@googlegroups.com> wrote:
> Boot in rescue mode. Edit your xen.cfg and remove the option named
> something like qubes.hideallusb. Edit /var/lib/qubes/qubes.xml and
> locate sys-usb's autostart property, and set to False. Reboot.
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Boot in rescue mode. Edit your xen.cfg and remove the option named
> something like qubes.hideallusb. Edit /var/lib/qubes/qubes.xml and
> locate sys-usb's autostart property, and set to False. Reboot.
>
>
> - don't top post
> Mailing list etiquette:
>
> - trim quoted reply to only relevant portions
> - when possible, copy and paste text instead of screenshots
>
> --
> - don't top post
> Mailing list etiquette:
>
> - trim quoted reply to only relevant portions
> - when possible, copy and paste text instead of screenshots
>
> You received this message because you are subscribed to the Google Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fc6c6822-9a15-d219-a234-0999f93c9675%40danwin1210.me.
>
Automatic rescue process didn't work, had to go to shell and mount /dev/mapper/qubes_dom0-root manually.
Didn't find any mention of "usb" in xen.cfg, neither in the one in /boot/efi/EFI/qubes on the dom0 volume, nor on the boot USB. Both files' timestamps predate this problem.
I changed autostart to False in the qubes.xml entry for sys-usb but the OS still starts sys-usb and panicks like before.
Also if I didn't mention this earlier, when I ran the command that installed sys-usb, it reported progress on 5-6 steps and all succeeded except one. I believe the one that failed was editing something in /boot and I think I had umounted /boot and removed the stick some time before running that command.
awokd
Nov 22, 2019, 3:42:53 AM11/22/19
to qubes...@googlegroups.com
'Zeko' via qubes-users:
>
> I changed autostart to False in the qubes.xml entry for sys-usb but the OS still starts sys-usb and panicks like before.
In that same file and general location, remove the line beginning with
<device backend-domain"="dom0" right after <devices class="pci">. This
will remove the USB PCI controller from sys-usb.
> Also if I didn't mention this earlier, when I ran the command that installed sys-usb, it reported progress on 5-6 steps and all succeeded except one. I believe the one that failed was editing something in /boot and I think I had umounted /boot and removed the stick some time before running that command.
OK, that's likely why you couldn't find the xen.cfg setting.
>
> I changed autostart to False in the qubes.xml entry for sys-usb but the OS still starts sys-usb and panicks like before.
<device backend-domain"="dom0" right after <devices class="pci">. This
will remove the USB PCI controller from sys-usb.
> Also if I didn't mention this earlier, when I ran the command that installed sys-usb, it reported progress on 5-6 steps and all succeeded except one. I believe the one that failed was editing something in /boot and I think I had umounted /boot and removed the stick some time before running that command.
Reply all
Reply to author
Forward
0 new messages