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 ou
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 th
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
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
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.
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,
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 run
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 up
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 t
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 r
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
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
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
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
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
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 b
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
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/
Ma
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
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 a
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
> 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 nam
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-
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 s
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
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
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://
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
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
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 too
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:
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 unsubscr
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/mappe
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
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 t
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
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 too
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 /qub
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
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 pos
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
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 cr
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:
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 rebo
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 c
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 th
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
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
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.
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
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, t
51 matches
Mail list logo
