Re: [qubes-users] Qubes won't boot
Qubes User: Hello, I was using Qubes for about 3 months and didn't use it last month. Yesterday it wouldn't boot. Using Qubes rescue didn't help. After typing passphrase it says Linux system not found so it doesn't mount. So i found a way to mount disk manually. Going through directories found out that boot folder is empty. Also if that is not an option i want to save my files but seems like private.img are missing. There is only icon.png file in VM folders. Is there any way to recover boot files so i can boot it again or at least save files from VMs somehow? Try booting with a LiveCD distribution. Scan and mount the LVM thin volumes with vgchange -ay. You may need to install a package to support LVM thin. You should be able to pull data from the VMs that way. -- - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f5eb34ec-a6c0-f198-1e75-2546be97620c%40danwin1210.me.
[qubes-users] Qubes won't boot
Hello, I was using Qubes for about 3 months and didn't use it last month. Yesterday it wouldn't boot. Using Qubes rescue didn't help. After typing passphrase it says Linux system not found so it doesn't mount. So i found a way to mount disk manually. Going through directories found out that boot folder is empty. Also if that is not an option i want to save my files but seems like private.img are missing. There is only icon.png file in VM folders. Is there any way to recover boot files so i can boot it again or at least save files from VMs somehow? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/trinity-b05fda5f-b9b7-48bc-94c1-aa98fb89ee53-1620324425410%403c-app-mailcom-lxa10.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
I have exactly the same problem with a Librem 15v3 laptop: hangs with blinking cursor. Only boots with 4.19.107. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4ff914d5-0094-4b53-9591-94dbb3161715o%40googlegroups.com.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
Tried kernels 5.6.x again and no luck. Still getting the black cursor only screen. Still stuck on 4.19.132-1 Em segunda-feira, 3 de agosto de 2020 às 22:05:02 UTC-3, pudding escreveu: > Update: kernel 4.19.128-1 boots fine on my laptop, but 4.19.132-1 that > comes with the newest dom0 update does not. I've set the install_limit > to 6 just in case. Will continue observing. > > > pudding > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1ecacf9c-4380-433b-b424-71c37b49934en%40googlegroups.com.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
Update: kernel 4.19.128-1 boots fine on my laptop, but 4.19.132-1 that comes with the newest dom0 update does not. I've set the install_limit to 6 just in case. Will continue observing. pudding -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f4c44c36-c6da-6d98-2ee0-1c18f461e080%40cock.li.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128
Quick update: Just ran the latest dom0 updates, kernel 4.19.132-1 booted normally. Still haven't tried the 5.6.x kernels again. Em sexta-feira, 31 de julho de 2020 às 12:44:00 UTC-3, Rafael Reis escreveu: > Hey, > > Just want to register I've suffered from the same bug. After latest > update, got stuck on a single cursor on top of a black screen right before > the GUI login box. > *Got around it by rolling back all the way to kernel 4.19.107-1.* Did it > by editing xen.cfg and setting default. > > I've been running kernel-latest very steadily for the past few months, and > Qubes for almost 2 years now. This was the first time I got a bad update. I > had even GPU IOMMU enabled with success. > I've share my HCL here before, I run a very well supported Dell Latitude > e5470 6th gen quad core 16GB ram. > > Hope to hear from Qubes team when it's safe again to go back to newer > kernels. > > Rafael > Em quarta-feira, 29 de julho de 2020 às 16:44:11 UTC-3, qu...@ixls.eu > escreveu: > >> On 7/26/20 12:56 PM, Frédéric Pierret wrote: >> > >> > >> > On 2020-07-26 12:50, qubes via qubes-users wrote: >> >> On 6/27/20 6:55 AM, qubes via qubes-users wrote: >> >>> On 6/26/20 10:14 PM, Qubes wrote: >> On 6/26/20 9:49 PM, qubes via qubes-users wrote: >> > On 6/13/20 5:36 PM, pudding wrote: >> >> I updated dom0 from the security-testing repo today due to the new >> CPU >> >> hardware bug. After finishing update and rebooting my laptop, it >> is >> >> stuck on the black screen forever, and will not load the LUKS >> decryption >> >> screen. >> >> .. >> > >> > Same problem on Lenovo t460 but "standard" repo/update. >> > >> > >> > >> That is a real problem. I guess it is game over without a backup. >> >> >>> >> >>> As pudding said, you can boot the old kernel, thank spaghettimonster. >> >>> But what is the real cause of the problem? >> >>> Can I do something about it or will the next Dom0-Update fix this >> >>> problem? Shall I reinstall the .125-Kernel? >> >>> Or - worst case scenario - will newer kernels stop working on this >> >>> laptop in the future anyway? >> >> >> >> >> >> The newest kernel (128) won't boot neither :-( >> >> So I am still using 4.19.107. >> >> But on next update I will be out. (unless I can "preserve" the old >> kernel) >> >> >> > >> > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher >> number to keep more kernel versions installed. Have you tried also >> kernel-latest? It's 5.7.X version. >> > >> >> Thanks for the advice. Or simply I don't do an update :-) >> >> > You say that you have black screen since kernel 4.19.125? >> >> True. Just a blinking cursor. >> >> >> >> >> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3c15e3da-92d2-47c7-a3b1-acd72c15b29en%40googlegroups.com.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128
Hey, Just want to register I've suffered from the same bug. After latest update, got stuck on a single cursor on top of a black screen right before the GUI login box. *Got around it by rolling back all the way to kernel 4.19.107-1.* Did it by editing xen.cfg and setting default. I've been running kernel-latest very steadily for the past few months, and Qubes for almost 2 years now. This was the first time I got a bad update. I had even GPU IOMMU enabled with success. I've share my HCL here before, I run a very well supported Dell Latitude e5470 6th gen quad core 16GB ram. Hope to hear from Qubes team when it's safe again to go back to newer kernels. Rafael Em quarta-feira, 29 de julho de 2020 às 16:44:11 UTC-3, qu...@ixls.eu escreveu: > On 7/26/20 12:56 PM, Frédéric Pierret wrote: > > > > > > On 2020-07-26 12:50, qubes via qubes-users wrote: > >> On 6/27/20 6:55 AM, qubes via qubes-users wrote: > >>> On 6/26/20 10:14 PM, Qubes wrote: > On 6/26/20 9:49 PM, qubes via qubes-users wrote: > > On 6/13/20 5:36 PM, pudding wrote: > >> I updated dom0 from the security-testing repo today due to the new > CPU > >> hardware bug. After finishing update and rebooting my laptop, it is > >> stuck on the black screen forever, and will not load the LUKS > decryption > >> screen. > >> .. > > > > Same problem on Lenovo t460 but "standard" repo/update. > > > > > > > That is a real problem. I guess it is game over without a backup. > > >>> > >>> As pudding said, you can boot the old kernel, thank spaghettimonster. > >>> But what is the real cause of the problem? > >>> Can I do something about it or will the next Dom0-Update fix this > >>> problem? Shall I reinstall the .125-Kernel? > >>> Or - worst case scenario - will newer kernels stop working on this > >>> laptop in the future anyway? > >> > >> > >> The newest kernel (128) won't boot neither :-( > >> So I am still using 4.19.107. > >> But on next update I will be out. (unless I can "preserve" the old > kernel) > >> > > > > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher > number to keep more kernel versions installed. Have you tried also > kernel-latest? It's 5.7.X version. > > > > Thanks for the advice. Or simply I don't do an update :-) > > > You say that you have black screen since kernel 4.19.125? > > True. Just a blinking cursor. > > > > > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dde2b994-0180-4341-b2d7-36916d772cb4n%40googlegroups.com.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128
On 7/26/20 12:56 PM, Frédéric Pierret wrote: > > > On 2020-07-26 12:50, qubes via qubes-users wrote: >> On 6/27/20 6:55 AM, qubes via qubes-users wrote: >>> On 6/26/20 10:14 PM, Qubes wrote: On 6/26/20 9:49 PM, qubes via qubes-users wrote: > On 6/13/20 5:36 PM, pudding wrote: >> I updated dom0 from the security-testing repo today due to the new CPU >> hardware bug. After finishing update and rebooting my laptop, it is >> stuck on the black screen forever, and will not load the LUKS decryption >> screen. >> .. > > Same problem on Lenovo t460 but "standard" repo/update. > > > That is a real problem. I guess it is game over without a backup. >>> >>> As pudding said, you can boot the old kernel, thank spaghettimonster. >>> But what is the real cause of the problem? >>> Can I do something about it or will the next Dom0-Update fix this >>> problem? Shall I reinstall the .125-Kernel? >>> Or - worst case scenario - will newer kernels stop working on this >>> laptop in the future anyway? >> >> >> The newest kernel (128) won't boot neither :-( >> So I am still using 4.19.107. >> But on next update I will be out. (unless I can "preserve" the old kernel) >> > > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher number > to keep more kernel versions installed. Have you tried also kernel-latest? > It's 5.7.X version. > Thanks for the advice. Or simply I don't do an update :-) > You say that you have black screen since kernel 4.19.125? True. Just a blinking cursor. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0ff7c834-3812-9f29-329b-50aef71fa0e8%40ixls.eu.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128
On 2020-07-26 12:50, qubes via qubes-users wrote: > On 6/27/20 6:55 AM, qubes via qubes-users wrote: >> On 6/26/20 10:14 PM, Qubes wrote: >>> On 6/26/20 9:49 PM, qubes via qubes-users wrote: On 6/13/20 5:36 PM, pudding wrote: > I updated dom0 from the security-testing repo today due to the new CPU > hardware bug. After finishing update and rebooting my laptop, it is > stuck on the black screen forever, and will not load the LUKS decryption > screen. > .. Same problem on Lenovo t460 but "standard" repo/update. >>> That is a real problem. I guess it is game over without a backup. >>> >> >> As pudding said, you can boot the old kernel, thank spaghettimonster. >> But what is the real cause of the problem? >> Can I do something about it or will the next Dom0-Update fix this >> problem? Shall I reinstall the .125-Kernel? >> Or - worst case scenario - will newer kernels stop working on this >> laptop in the future anyway? > > > The newest kernel (128) won't boot neither :-( > So I am still using 4.19.107. > But on next update I will be out. (unless I can "preserve" the old kernel) > In dom0, edit /etc/dnf/dnf.conf and change install_limit=3 to higher number to keep more kernel versions installed. Have you tried also kernel-latest? It's 5.7.X version. You say that you have black screen since kernel 4.19.125? Best, Frédéric -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d27aaec4-680e-b032-0434-392750cb8c76%40qubes-os.org. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel, neither on ...128
On 6/27/20 6:55 AM, qubes via qubes-users wrote: > On 6/26/20 10:14 PM, Qubes wrote: >> On 6/26/20 9:49 PM, qubes via qubes-users wrote: >>> On 6/13/20 5:36 PM, pudding wrote: I updated dom0 from the security-testing repo today due to the new CPU hardware bug. After finishing update and rebooting my laptop, it is stuck on the black screen forever, and will not load the LUKS decryption screen. .. >>> >>> Same problem on Lenovo t460 but "standard" repo/update. >>> >>> >>> >> That is a real problem. I guess it is game over without a backup. >> > > As pudding said, you can boot the old kernel, thank spaghettimonster. > But what is the real cause of the problem? > Can I do something about it or will the next Dom0-Update fix this > problem? Shall I reinstall the .125-Kernel? > Or - worst case scenario - will newer kernels stop working on this > laptop in the future anyway? The newest kernel (128) won't boot neither :-( So I am still using 4.19.107. But on next update I will be out. (unless I can "preserve" the old kernel) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8c63923f-b648-9fae-e8ec-6170c09eaa19%40ixls.eu.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
On 6/26/20 10:14 PM, Qubes wrote: > On 6/26/20 9:49 PM, qubes via qubes-users wrote: >> On 6/13/20 5:36 PM, pudding wrote: >>> I updated dom0 from the security-testing repo today due to the new CPU >>> hardware bug. After finishing update and rebooting my laptop, it is >>> stuck on the black screen forever, and will not load the LUKS decryption >>> screen. >>> .. >> >> Same problem on Lenovo t460 but "standard" repo/update. >> >> >> > That is a real problem. I guess it is game over without a backup. > As pudding said, you can boot the old kernel, thank spaghettimonster. But what is the real cause of the problem? Can I do something about it or will the next Dom0-Update fix this problem? Shall I reinstall the .125-Kernel? Or - worst case scenario - will newer kernels stop working on this laptop in the future anyway? > You should be able to get your files off of the disk. I am sure I read a > procedure in the documentation to mount the encrypted volume elsewhere > to recover your data. I have not checked if it is possible to decrypt > the drive while connected elsewhere, whether that is internal or > connected externally with USB. Or even booted with live media or > something like tinycore. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b2d93c51-9676-119e-7696-a1c7bae39c29%40ixls.eu.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
Qubes: > On 6/26/20 10:17 PM, 'awokd' via qubes-users wrote: >>> Should be able to boot with an older kernel. >>> https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel >>> > > That requires decrypting and booting, but the boot failing and you going > to a recovery screen from where you can change to an older kernel. You > cannot change anything while it is encrypted. > /boot is not encrypted, and can be edited by booting the computer from another OS. Xen.cfg is straight-forward to edit. Grub.cfg can also be edited, but I don't know what changes to make if you haven't enabled submenus previously. -- - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9bef6aa7-fbf6-e4f9-6bec-439210a17f2e%40danwin1210.me.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
On 6/26/20 10:17 PM, 'awokd' via qubes-users wrote: Should be able to boot with an older kernel. https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel That requires decrypting and booting, but the boot failing and you going to a recovery screen from where you can change to an older kernel. You cannot change anything while it is encrypted. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/142bd106-9794-b0f4-c397-3c334e4eec77%40ak47.co.za.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
Qubes: > On 6/26/20 9:49 PM, qubes via qubes-users wrote: >> On 6/13/20 5:36 PM, pudding wrote: >>> I updated dom0 from the security-testing repo today due to the new CPU >>> hardware bug. After finishing update and rebooting my laptop, it is >>> stuck on the black screen forever, and will not load the LUKS decryption >>> screen. >>> .. >> >> Same problem on Lenovo t460 but "standard" repo/update. >> >> >> > That is a real problem. I guess it is game over without a backup. > > You should be able to get your files off of the disk. I am sure I read a > procedure in the documentation to mount the encrypted volume elsewhere > to recover your data. I have not checked if it is possible to decrypt > the drive while connected elsewhere, whether that is internal or > connected externally with USB. Or even booted with live media or > something like tinycore. > Should be able to boot with an older kernel. https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel -- - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fd40d8c7-f112-ae66-62e7-bccf530d3b85%40danwin1210.me.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
On 6/26/20 9:49 PM, qubes via qubes-users wrote: On 6/13/20 5:36 PM, pudding wrote: I updated dom0 from the security-testing repo today due to the new CPU hardware bug. After finishing update and rebooting my laptop, it is stuck on the black screen forever, and will not load the LUKS decryption screen. .. Same problem on Lenovo t460 but "standard" repo/update. That is a real problem. I guess it is game over without a backup. You should be able to get your files off of the disk. I am sure I read a procedure in the documentation to mount the encrypted volume elsewhere to recover your data. I have not checked if it is possible to decrypt the drive while connected elsewhere, whether that is internal or connected externally with USB. Or even booted with live media or something like tinycore. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/076387b3-c3b6-9b97-fd25-e75557607fbd%40ak47.co.za.
Re: [qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
On 6/13/20 5:36 PM, pudding wrote: > I updated dom0 from the security-testing repo today due to the new CPU > hardware bug. After finishing update and rebooting my laptop, it is > stuck on the black screen forever, and will not load the LUKS decryption > screen. > .. Same problem on Lenovo t460 but "standard" repo/update. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/322bc337-d01d-12ae-0c42-7966af2737ff%40ixls.eu.
[qubes-users] Qubes Won't Boot with 4.19.125-1 Kernel
I updated dom0 from the security-testing repo today due to the new CPU hardware bug. After finishing update and rebooting my laptop, it is stuck on the black screen forever, and will not load the LUKS decryption screen. I have to go to the advanced options and select 4.19.107-1 kernel in order to boot normally. My laptop is a Librem 15v3. Is there any way to fix this? Thanks! -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ab338500-8763-2b30-bf67-1c861daa8916%40cock.li.
Re: [EXT] Re: [qubes-users] Qubes won't boot
On 6/1/20 1:59 AM, Boot problems wrote: Using fdisk -l /dev/xvdi shows me 2 partitions only, a 200m EFI System and xvdi2 a 931G Linux file system, there are no more partitions even if I decrypt, mount and fdisk -l /dev/xvdi2 luksopen won't add another partition; it will create /dev/mapper/ Maybe it's easier to check the out put of these commands (after having opened all the encrypted partitions): pvs vgs lvs (I don't think a pvscan is necessary after opening encrypted devices) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/97f5b0b9-d70b-a376-997a-4af58c7f80ee%40rz.uni-regensburg.de.
Re: [EXT] Re: [qubes-users] Qubes won't boot
On 5/31/20 10:02 PM, dhorf-hfref.4a288...@hashmail.org wrote: On Sun, May 31, 2020 at 12:45:22PM -0700, Boot problems wrote: Hello, I wanted to migrate from my old hhd to a new ssd, I installed [...] could it be a grub issue? What can I do? assuming you were NOT reinstalling because you were compromised... - just boot your new qubes system - with the old HDD attached (directly or through USB) - check if there are partitions on it (fdisk -l /dev/hdx) - open the luks container from the HDD (google: cryptopen) - you should now have access to the lvm volume of your old system - with that access, you can create replacement vms and dd over their private volumes. At least in the past there were issues when different devices had the same volume group name, especially when the devices were cloned. Maybe you need "pvchange -u ..." and "vgchange -u ...". To protext yourself, you should (at least temporarily) rename one of the two identical VGs (which can be a challenge by itself). see how far you can get on that list. ask more specific questions as required. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/acba8324-d742-7812-ac4c-daa503e0bec9%40rz.uni-regensburg.de.
Re: [qubes-users] Qubes won't boot
On Thu, Jun 04, 2020 at 01:45:26PM +0200, haaber wrote: > how do you use qvm-run if qubes won't boot? First step is a always > proper backup, on some external drive. That is what I wrote in my other > answer. i recommend to read what this thread is about. the user installed qubes to a new ssd and is trying to recover data from his old qubes install on a hdd. both are connected to the same computer and we already made it past the "lukeOpen and activate VG in VM" hurdles. afaict the initial "wont boot" problem was the computer having strong opinions about which of the devices it wanted to boot from. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200604121724.GJ1079%40priv-mua.
Re: [qubes-users] Qubes won't boot
qvm-run -p HELPERVM "sudo cat /dev/mapper/qubes_dom0-vm--VMOLD--private" | sudo dd conv=sparse of=/dev/mapper/qubes_dom0-vm--VMNEW--private how do you use qvm-run if qubes won't boot? First step is a always proper backup, on some external drive. That is what I wrote in my other answer. dd = disk destroyer. I there is the slightest chance of error, don't use it. that is really overly pessimistic, you can completely destroy your system with pretty much any tool when used the wrong way. yes, even with firefox. Correct, but with dd it is much more easy :) If the qubesbootingdrama was as experienced and skilled as you, he would not have asked, right? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8db0e622-2068-0e37-ee58-f0c1916ed4dd%40web.de.
Re: [qubes-users] Qubes won't boot
> On 6/3/20 10:58 PM, Boot problems wrote: > > How do I restore a mounted vm using dd? qvm-run -p HELPERVM "sudo cat /dev/mapper/qubes_dom0-vm--VMOLD--private" | sudo dd conv=sparse of=/dev/mapper/qubes_dom0-vm--VMNEW--private this assumes you have the old disk opened in HELPERVM, the old vm name is VMOLD and the new VM name is VMNEW. this needs to be run in dom0, as one line (or with a linebreak after the |) VMOLD and VMNEW can have the same name. VMNEW needs to be created and should not have been started before running this. if you started VMNEW already (or need to rerun the dd), run "blkdiscard /dev/mapper/qubes_dom0-vm--VMNEW--private" before the dd chain. the private volume for VMNEW needs to be same-or-bigger than the one of VMOLD. On Thu, Jun 04, 2020 at 01:20:43PM +0200, haaber wrote: > dd = disk destroyer. > I there is the slightest chance of error, don't use it. that is really overly pessimistic, you can completely destroy your system with pretty much any tool when used the wrong way. yes, even with firefox. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200604113641.GI1079%40priv-mua.
Re: [qubes-users] Qubes won't boot
On 6/3/20 6:47 AM, Boot problems wrote: I tried all that in my new ssd but could not make it work, however I made an Ubuntu live CD and it worked like a charm, I can mount and see the files on each vm, so at least my files are not lost forever, but you said that the Attr should not have an -a- and it does in every single one, is that a problem? At this point I think is better for me to save the files I really need and forget about the restoring the vms That is exact. If you can boot a live linux, first step is ALWAYS data recovery. Repair attempts come second. You could use an external drive for that. In this case, the emergency backup procedure is: cd /externaldrive (go to mounted external vlume) truncate -s 200G backup.luks (where 200G means 200 giga, change appropriately) losetup /dev/loop0 backup.luks (make the file a device) cryptsetup luksCreate /dev/loop0 (setup crypto, you may use your qubes disc-pwd.) cryptsetup luksOpen /dev/loop0 BACKUP (open it) mkfs.ext2 /dev/mapper/BACKUP (generate easy fs for backup purposes) mkdir /backup (make backup path) mount /dev/mapp/BACKUP /backup (mount it) Then create a subfolder for each VM and save all data in the right subdir. rsync -auv /path-to-vm//backup/vm-name/ THINK TO PUT the final "/" at both paths! -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/160fa5e5-4720-c80c-1946-0e746b45708e%40web.de.
Re: [qubes-users] Qubes won't boot
On 6/3/20 10:58 PM, Boot problems wrote: How do I restore a mounted vm using dd? dd = disk destroyer. I there is the slightest chance of error, don't use it. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/abfc262d-2158-b604-a802-650232eea8a0%40web.de.
Re: [qubes-users] Qubes won't boot
I tried all that in my new ssd but could not make it work, however I made an Ubuntu live CD and it worked like a charm, I can mount and see the files on each vm, so at least my files are not lost forever, but you said that the Attr should not have an -a- and it does in every single one, is that a problem? At this point I think is better for me to save the files I really need and forget about the restoring the vms -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48530958-5ab4-4a56-9edc-b0cf0d3cd305%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
Thabks for your help, kisses. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6752a3e5-7a3f-499d-8152-66457a76e76d%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
I could make it work -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5840499a-5390-4da8-ad0f-5e84277490b0%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
How do I restore a mounted vm using dd? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9b868a52-f36d-4c84-9714-3a14853e57ff%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
I couldn't do it from my new ssd, but I made an Ubuntu live usb and it worked like a charm I can see all my vms and mount them, all the files are still there, however all the attrs have an a in them, will that be a problem? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b0017699-c1dc-47af-9a14-2841364e48ca%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
On Sun, May 31, 2020 at 04:59:43PM -0700, Boot problems wrote: > Using fdisk -l /dev/xvdi shows me 2 partitions only, a 200m EFI System > and xvdi2 a 931G Linux file system, there are no more partitions even > if I decrypt, mount and fdisk -l /dev/xvdi2 after the luksOpen, check with lvm tools: run "sudo vgs -a". (if you dont have vgs installed: "sudo dnf -y install lvm2") does it report a qubes_dom0? good. now check for logical volumes: "sudo lvs -a" _lots_ of reports, with vm names in them? good! what are the attrs on those (third column)? "Vwi---tz--"? (the important part there is: no "a" in the attrs.) then you need to activate the volume group: "vgchange -ay qubes_dom0" after that, you should have a-plenty of new devices in /dev/mapper and the vm-private-volume ones are the ones with names ending in -private. you should be able to mount these. (or just restore them with dd to new vms) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200601110401.GE1079%40priv-mua.
Re: [qubes-users] Qubes won't boot
Using fdisk -l /dev/xvdi shows me 2 partitions only, a 200m EFI System and xvdi2 a 931G Linux file system, there are no more partitions even if I decrypt, mount and fdisk -l /dev/xvdi2 -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2293f05e-4d05-434c-9652-1e9ca6205d80%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
LuksOpen worked now, it was stupid of me to forget the sudo. Mounted it as oldhdd, using ls -al /dev/mapper/*-private says there is no such directory ls -al /dev/mapper/oldhdd-private says the same ls -al /dev/mapper/oldhdd returns only one line lrwxrwxrwx 1 root root 7 May 31 17:39 /dev/mapper/oldhdd -> ../dm-0 Tried those 3 ways with and without sudo I really appreciate you helping me, sorry to be so dumb for these stuff, I manage just fine for every day things. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/33d4d729-bc65-4f72-be9e-8cd80bc3c449%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
On Sun, May 31, 2020 at 01:57:24PM -0700, Boot problems wrote: > /dev/xvdi but using that it just says permission denied. so use "sudo fdisk -l /dev/xvdi" > the cryptsetup luksOpen /dev/xvdi2 name, then it says access denied, I so use "sudo cryptsetup luksOpen /dev/xvdi2 name" > can seemingly unencrypted it from the gnome-disks GUI but not mount it. it contains an lvm stack, so there will be many virtual volumes inside. after the luksOpen, check "ls -al /dev/mapper/*-private" and look for the devices with the names of your old VMs. you should be able to mount these. hint: use "sudo mount /dev/mapper/whatever-private /mnt/whatever" hint2: you will have to replace the "whatever" part there. hint3: you will have to "sudo mkdir /mnt/whatever" or create new VMs, and restore the whole private volumes with dd. > However I tried booting up the old hdd again and now it works as long > as the ssd is connected too but all my data is gone and is just a > clone of the new ssd, without the ssd connected it doesn't boot up > like before, I guess it has been formatted then, is there a way to that sounds more like you are just booting from your ssd into the fresh install. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200531211905.GD1079%40priv-mua.
Re: [qubes-users] Qubes won't boot
I attached the hdd to a VM and used the fdisk -l command, with /dev/hdx it says the directory did not exists so I brought up the gnome-disks GUI and saw that it was on the directory /dev/xvdi but using that it just says permission denied. I googled the cryptopen and if the command I'm supposed to enter is the cryptsetup luksOpen /dev/xvdi2 name, then it says access denied, I can seemingly unencrypted it from the gnome-disks GUI but not mount it. However I tried booting up the old hdd again and now it works as long as the ssd is connected too but all my data is gone and is just a clone of the new ssd, without the ssd connected it doesn't boot up like before, I guess it has been formatted then, is there a way to recover some of the lost information? I only really need a few files. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ee9b600c-c3e3-447f-83cb-fae9ab067fe4%40googlegroups.com.
Re: [qubes-users] Qubes won't boot
On Sun, May 31, 2020 at 12:45:22PM -0700, Boot problems wrote: > Hello, I wanted to migrate from my old hhd to a new ssd, I installed [...] > could it be a grub issue? What can I do? assuming you were NOT reinstalling because you were compromised... - just boot your new qubes system - with the old HDD attached (directly or through USB) - check if there are partitions on it (fdisk -l /dev/hdx) - open the luks container from the HDD (google: cryptopen) - you should now have access to the lvm volume of your old system - with that access, you can create replacement vms and dd over their private volumes. see how far you can get on that list. ask more specific questions as required. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200531200229.GC1079%40priv-mua.
[qubes-users] Qubes won't boot
Hello, I wanted to migrate from my old hhd to a new ssd, I installed Qubes on the new ssd and it works fine but now the old hhd won't boot, I tried the rescue option that is in the installation iso but it says there are no Linux partitions found, to be fair I don't know how to use the rescue tool neither, did I format my disk accidentally or could it be a grub issue? What can I do? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/46f9c2ba-427a-4ef3-a1cc-fa16735e826d%40googlegroups.com.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
pkw: > > > W dniu niedziela, 8 grudnia 2019 18:13:58 UTC+1 użytkownik pkw napisał: >> *sdc 8:32 0 465,8G 0 disk ├─sdc1 8:33 0 1G 0 part >> └─sdc2 8:34 0 464,8G 0 part└─qubes 253:00 464,8G 0 crypt* >> >> >> root@X230:/qubes# mount /dev/mapper/qubes /qubes >> *mount: /qubes: unknown filesystem type 'LVM2_member'.* Did you cryptsetup open somewhere in there? You may also need to install the LVM thin package, I think it's named thinprovisioningtools. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48f3dbae-b526-4bc6-462a-11491773ac01%40danwin1210.me.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
W dniu niedziela, 8 grudnia 2019 18:13:58 UTC+1 użytkownik pkw napisał: > > > > W dniu niedziela, 8 grudnia 2019 16:56:20 UTC+1 użytkownik awokd napisał: >> >> >> Check >> https://www.mail-archive.com/qubes-users@googlegroups.com/msg22764.html >> for some ideas. >> >> -- >> - don't top post >> Mailing list etiquette: >> - trim quoted reply to only relevant portions >> - when possible, copy and paste text instead of screenshots >> > > > I'm stuck ... > > root@X230:/qubes# ls -la /dev/mapper/ > total 0 > drwxr-xr-x 2 root root 80 Dec 8 17:50 . > drwxr-xr-x 21 root root4460 Dec 8 17:50 .. > crw--- 1 root root 10, 236 Dec 8 17:26 control > > *lrwxrwxrwx 1 root root 7 Dec 8 17:50 qubes -> ../dm-0* > > root@X230:/qubes# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 119,2G 0 disk > └─sda1 8:10 119,2G 0 part / > sdb 8:16 0 931,5G 0 disk > └─sdb1 8:17 0 930,6G 0 part /media/user/1tb-ext4 > > > > *sdc 8:32 0 465,8G 0 disk ├─sdc1 8:33 0 1G 0 part > └─sdc2 8:34 0 464,8G 0 part└─qubes 253:00 464,8G 0 crypt* > > > root@X230:/qubes# mount /dev/mapper/qubes /qubes > *mount: /qubes: unknown filesystem type 'LVM2_member'.* > > > root@X230:/qubes# lvmdiskscan > Incorrect metadata area header checksum on /dev/mapper/qubes at offset > 4096 > /dev/mapper/qubes [<464,76 GiB] LVM physical volume > /dev/sda1 [ 119,24 GiB] > /dev/sdb1 [ 930,61 GiB] > /dev/sdc1 [ 1,00 GiB] > /dev/sdc2 [ 464,76 GiB] > 0 disks > 4 partitions > 1 LVM physical volume whole disk > 0 LVM physical volumes > > > also: > root@X230:/qubes# vgscan Reading volume groups from cache. root@X230:/qubes# vgscan --cache Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096 Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096 Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096 Reading volume groups from cache. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0e0c81eb-9f71-492b-9034-19d678d501f8%40googlegroups.com.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
W dniu niedziela, 8 grudnia 2019 16:56:20 UTC+1 użytkownik awokd napisał: > > > Check > https://www.mail-archive.com/qubes-users@googlegroups.com/msg22764.html > for some ideas. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > I'm stuck ... root@X230:/qubes# ls -la /dev/mapper/ total 0 drwxr-xr-x 2 root root 80 Dec 8 17:50 . drwxr-xr-x 21 root root4460 Dec 8 17:50 .. crw--- 1 root root 10, 236 Dec 8 17:26 control *lrwxrwxrwx 1 root root 7 Dec 8 17:50 qubes -> ../dm-0* root@X230:/qubes# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 119,2G 0 disk └─sda1 8:10 119,2G 0 part / sdb 8:16 0 931,5G 0 disk └─sdb1 8:17 0 930,6G 0 part /media/user/1tb-ext4 *sdc 8:32 0 465,8G 0 disk ├─sdc1 8:33 0 1G 0 part └─sdc2 8:34 0 464,8G 0 part└─qubes 253:00 464,8G 0 crypt* root@X230:/qubes# mount /dev/mapper/qubes /qubes *mount: /qubes: unknown filesystem type 'LVM2_member'.* root@X230:/qubes# lvmdiskscan Incorrect metadata area header checksum on /dev/mapper/qubes at offset 4096 /dev/mapper/qubes [<464,76 GiB] LVM physical volume /dev/sda1 [ 119,24 GiB] /dev/sdb1 [ 930,61 GiB] /dev/sdc1 [ 1,00 GiB] /dev/sdc2 [ 464,76 GiB] 0 disks 4 partitions 1 LVM physical volume whole disk 0 LVM physical volumes -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/42e24317-6a1e-46c1-a1e0-00f7996d93d3%40googlegroups.com.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
pkw: > > > W dniu niedziela, 8 grudnia 2019 16:30:43 UTC+1 użytkownik pkw napisał: >> >> >> >> W dniu niedziela, 8 grudnia 2019 16:20:20 UTC+1 użytkownik awokd napisał: >>> >>> >>> Yes, you should be able to mount the drive either in another system or >>> with a rescue boot CD/image on the same system. Look for cryptsetup + >>> LVM recovery. >>> >>> -- >>> - don't top post >>> Mailing list etiquette: >>> - trim quoted reply to only relevant portions >>> - when possible, copy and paste text instead of screenshots >>> >> >> >> Thank you for the answer, just burning qubes usb. >> Once I mount main system, where to look for for the private VM files? I >> would like to copy it to some other drive, I suspect the one I have now is >> faulty. >> > > > not god... qubes rescue mode doesn't work.. > . > It asks to choose from 4 options, when I chose to mount as read-only it > asks me for LUKS password for sda2, > when I enter it there is a message that I don't have any Linux partitions.. > > Any clues how to proceed? > Check https://www.mail-archive.com/qubes-users@googlegroups.com/msg22764.html for some ideas. -- - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3f9a789f-3c3b-c186-fcf3-420f3cbc360f%40danwin1210.me.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
W dniu niedziela, 8 grudnia 2019 16:30:43 UTC+1 użytkownik pkw napisał: > > > > W dniu niedziela, 8 grudnia 2019 16:20:20 UTC+1 użytkownik awokd napisał: >> >> >> Yes, you should be able to mount the drive either in another system or >> with a rescue boot CD/image on the same system. Look for cryptsetup + >> LVM recovery. >> >> -- >> - don't top post >> Mailing list etiquette: >> - trim quoted reply to only relevant portions >> - when possible, copy and paste text instead of screenshots >> > > > Thank you for the answer, just burning qubes usb. > Once I mount main system, where to look for for the private VM files? I > would like to copy it to some other drive, I suspect the one I have now is > faulty. > not god... qubes rescue mode doesn't work.. . It asks to choose from 4 options, when I chose to mount as read-only it asks me for LUKS password for sda2, when I enter it there is a message that I don't have any Linux partitions.. Any clues how to proceed? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ffee5fa6-1f3f-48b6-bd90-55cac513ad85%40googlegroups.com.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
W dniu niedziela, 8 grudnia 2019 16:20:20 UTC+1 użytkownik awokd napisał: > > > Yes, you should be able to mount the drive either in another system or > with a rescue boot CD/image on the same system. Look for cryptsetup + > LVM recovery. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > Thank you for the answer, just burning qubes usb. Once I mount main system, where to look for for the private VM files? I would like to copy it to some other drive, I suspect the one I have now is faulty. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ed8752ae-43f8-45ec-b414-3bc05d48f231%40googlegroups.com.
Re: [qubes-users] ! qubes won't boot - no access to data - please help
IT Geek: > Hi, > > my qubes installation won't boot, I have no backup... :/ > > I started it today, dom0 started but any of the VMs could'nt start. there > was an error: > > "domain has failed to start volume qubes_dom0/vm... missing" - more less. I > cant remember exact error > > then I rebooted the machine and I failed completely... > > I have error: > > . > error: unknown filesystem > Entering rescue mode > grub rescue> > > > > Is it possible to mount drive with qubes in other system and rescue my > data? I have the encryption password > Yes, you should be able to mount the drive either in another system or with a rescue boot CD/image on the same system. Look for cryptsetup + LVM recovery. -- - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0c9ed376-8855-af5d-12cd-abb5227202e3%40danwin1210.me.
[qubes-users] ! qubes won't boot - no access to data - please help
Hi, my qubes installation won't boot, I have no backup... :/ I started it today, dom0 started but any of the VMs could'nt start. there was an error: "domain has failed to start volume qubes_dom0/vm... missing" - more less. I cant remember exact error then I rebooted the machine and I failed completely... I have error: . error: unknown filesystem Entering rescue mode grub rescue> Is it possible to mount drive with qubes in other system and rescue my data? I have the encryption password -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4705c2eb-b9da-476e-8650-9fea77a76734%40googlegroups.com.
[qubes-users] Qubes won't boot after installation
I have a Dell Precision 5530 with an i7-8850 and NVidia Quadro P2000. The hard drive is a Class 40 M.2. My issue is that after installing Qubes OS on my laptop the OS does not appear when booting. The message I get is "No bootable devices found". I have tried both the automatic formatting of the drive as well as several custom configurations. There is no other OS on the hard drive. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1ea6724-f77e-41b6-b9ab-b949c52b66f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes won't boot 'kernel panic', where is AppVm data?
Le lundi 12 mars 2018 01:21:31 UTC+1, awokd a écrit : > On Sun, March 11, 2018 10:03 pm, ale10203...@gmail.com wrote: > > Hello, I am currently locked out of my qubes system because of a "kernel > > panic" error I encounter when I boot the system, after the grub screen. I > > don't really know what to do. The only thing I did before this to happen > > is to try to install AEM (without success), it may be the reason for > > this. Is there any fix to this? > > Haven't tried AEM, unfortunately. > > > I still have my qubes installation media, > > I can run the troubleshooting mode. I have qubes R4-rc4. > > I am also searching for the place to search for my appvms data so I can > > backup them and then re-install qubes (I use qubes for some months now), > > I can't find the appvm data anywhere... thanks for your answers ! > > Qubes R4.0 uses LVM instead of files- each disk in each AppVM is a > separate LVM logical partition. Short version is you mount the decrypted > disk, then you scan it for LVM partitions, and then mount the filesystem > inside the LVM partition you want to recover. Have only done it once or > twice, can't remember exact commands, but search for something like LUKS > LVM rescue. Thanks a lot ! I got a little in trouble searching about LVM partitions but after all I managed to backup my important data on a removable media from a live system before reinstalling qubes. Thanks again ! -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fb77b50d-e69d-405d-b781-b23b1338172d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes won't boot 'kernel panic', where is AppVm data?
On Sun, March 11, 2018 10:03 pm, ale10203...@gmail.com wrote: > Hello, I am currently locked out of my qubes system because of a "kernel > panic" error I encounter when I boot the system, after the grub screen. I > don't really know what to do. The only thing I did before this to happen > is to try to install AEM (without success), it may be the reason for > this. Is there any fix to this? Haven't tried AEM, unfortunately. > I still have my qubes installation media, > I can run the troubleshooting mode. I have qubes R4-rc4. > I am also searching for the place to search for my appvms data so I can > backup them and then re-install qubes (I use qubes for some months now), > I can't find the appvm data anywhere... thanks for your answers ! Qubes R4.0 uses LVM instead of files- each disk in each AppVM is a separate LVM logical partition. Short version is you mount the decrypted disk, then you scan it for LVM partitions, and then mount the filesystem inside the LVM partition you want to recover. Have only done it once or twice, can't remember exact commands, but search for something like LUKS LVM rescue. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/19e47a061ac3f1be0da0883c24d3a355.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes won't boot "kernel panic", where is AppVm data?
Hello, I am currently locked out of my qubes system because of a "kernel panic" error I encounter when I boot the system, after the grub screen. I don't really know what to do. The only thing I did before this to happen is to try to install AEM (without success), it may be the reason for this. Is there any fix to this? I still have my qubes installation media, I can run the troubleshooting mode. I have qubes R4-rc4. I am also searching for the place to search for my appvms data so I can backup them and then re-install qubes (I use qubes for some months now), I can't find the appvm data anywhere... thanks for your answers ! -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bf7e1461-8946-416b-a9e3-cda06a93a3f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes won't boot, how to rescue system or save my data?
On 12/14/2017 04:16 PM, jerr...@openmailbox.org wrote: > i first tried setup for my printer which has USB connected to PC... > using the guide in Using and Managing USB Devices in qubes-os website in > docs.. > enabled sys-sub using the command > sudo qubesctl top.enable qvm.sys-usb > > then the command > sudo qubesctl state.highstate > > computer froze, restarted pc, the keyboard didn't work (in passphrase > encryption part), but if press a button only num lock color appears for a > second, and if i hold a button the num lock button is lighted.. > > i then tried installing new qubes, using manual partition configuration (not > the automatic), i think i didn't delete the partition with my data.. i tried > adding some new partitions.. > > now after installing qubes, after encryption password for disk, entering > password, it was counting number when clicking alt tab, and says unlimited... > > how can i rescue I emergency, Iwould rescue data externally: use a luks-enabled linux (tails for example) on a usb drive, then open the discs (cryptsetup luksOpen /dev/XXX and mount it). Inside /var/lib/qubes/ you will find private.img in each appvm. These can be mounted individually & rsync-ed to a rescue disc (I recommend a loopback device that is luks-crypted as well). Bernhard -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d631a153-c537-6dec-9a12-4392f0466d7f%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] qubes won't boot, how to rescue system or save my data?
i first tried setup for my printer which has USB connected to PC... using the guide in Using and Managing USB Devices in qubes-os website in docs.. enabled sys-sub using the command sudo qubesctl top.enable qvm.sys-usb then the command sudo qubesctl state.highstate computer froze, restarted pc, the keyboard didn't work (in passphrase encryption part), but if press a button only num lock color appears for a second, and if i hold a button the num lock button is lighted.. i then tried installing new qubes, using manual partition configuration (not the automatic), i think i didn't delete the partition with my data.. i tried adding some new partitions.. now after installing qubes, after encryption password for disk, entering password, it was counting number when clicking alt tab, and says unlimited... how can i rescue -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20171214211617.9C0254E2F34%40mta-1.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
