[qubes-users] 4TB USB external disk - unable to attach to VM

[cubecub]

Hi, 
I've recently bought a high volume external USB 3.0 HDD to serve as a backup 
storage. Unfortunately when trying to attach the device using 'Qubes Devices' 
applet the disk is initally attached folllowed by immediate message "removed()".
I tried re-partitioning the volume from a single 4TB (3.7 TB) partition to a 
couple of smaller 1.7TB partitions, type 7 (under fdiks), formatted as NTFS. 
Unfortunately it didn't work. 

The only place it's showing up is directly withing sys-usb VM. I can access 
partitions there. But I want to be able to attach the disk / or one of the 
partitions/ directly to VM I need to copy data to/from. 

Any ideas? Suggestions? Advise how to connect my 4TB USB HDD into Qubes?

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/LsETa16--B-1%40tutamail.com.

Re: [qubes-users] qubes whonix - Tor Control Panel says connection established but I can't browse TOR

[cubecub]

Sep 22, 2019, 22:20 by cube...@tutamail.com:

>
>
> Sep 22, 2019, 19:52 by qubes-users@googlegroups.com:
>
>> cube...@tutamail.com:
>>
>>> And that's what I'm having a proplem with, unexpectedly. When I set up 
>>> 'sys-firewall' or 'sys-net' as netVM for 'whonix-sys' I can't get 
>>> 'anon-whonix' to establish Tor Browser connection, can't access any 
>>> website. Even whonix-sys 'Tor Control Panel' struggles with establishing 
>>> Tor connection. This is highly surprising as I don't live in a country 
>>> where ISP's prevent any onion/tor traffic. It should all work fine.
>>>
>>
>> Might be https://github.com/QubesOS/qubes-issues/issues/5331. TL;DR
>> version, try:
>>
>> qvm-features sys-whonix ipv6 ''
>>
>> and restart.
>>
>
> Thanks for pointing to related link and the fix. I executed the command, 
> rebooted and also played with changes to previous qubes-available kernel 
> version, although all within 4.19.* range. (*43, *67, *71). Unfortunately 
> successful connection has been made yet. 
> Are there more hints for potential solutions? Thanks.
>

I've just noticed that even though "Tor Control Panel" shows 'Connected to Tor 
network', when I check the status of the 'Time Synchronization Monitor' widget 
it's stuck on:
 "Last message from sys-whonix sdwdate: Initial time fetching in progress..."
for both whonix-sys and anon-whonix VM's. 
Strangely, the status doesn't get resolved. 
And as I mentioned the Tor-Control-Panel continues showing as "connected to Tor 
network". 

Such observation suggests there might be a problem with the 
TIme-Synchronisation-Monitor, or should I say, with sys-whonix obtaining valid 
timestamp in order to get started. 

Hopefully this additional comment would help someone with suggesting a 
solution. 

Thank you.


>> -- 
>> - 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/ee563d2f-bf9e-7234-2e26-8cf91b664b13%40danwin1210.me.
>>
>
>
>
>
> --
>  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/LpPcOeE--3-1%40tutamail.com 
> >
>  .
>

-- 
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/LpPenAH--3-1%40tutamail.com.

Re: [qubes-users] qubes whonix - Tor Control Panel says connection established but I can't browse TOR

[cubecub]

Sep 22, 2019, 19:52 by qubes-users@googlegroups.com:

> cube...@tutamail.com:
>
>> And that's what I'm having a proplem with, unexpectedly. When I set up 
>> 'sys-firewall' or 'sys-net' as netVM for 'whonix-sys' I can't get 
>> 'anon-whonix' to establish Tor Browser connection, can't access any website. 
>> Even whonix-sys 'Tor Control Panel' struggles with establishing Tor 
>> connection. This is highly surprising as I don't live in a country where 
>> ISP's prevent any onion/tor traffic. It should all work fine.
>>
>
> Might be https://github.com/QubesOS/qubes-issues/issues/5331. TL;DR
> version, try:
>
> qvm-features sys-whonix ipv6 ''
>
> and restart.
>

Thanks for pointing to related link and the fix. I executed the command, 
rebooted and also played with changes to previous qubes-available kernel 
version, although all within 4.19.* range. (*43, *67, *71). Unfortunately 
successful connection has been made yet. 
Are there more hints for potential solutions? Thanks.


> -- 
> - 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/ee563d2f-bf9e-7234-2e26-8cf91b664b13%40danwin1210.me.
>

-- 
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/LpPcOeE--3-1%40tutamail.com.

[qubes-users] qubes whonix - Tor Control Panel says connection established but I can't browse TOR

[cubecub]

Hi, 
I have a problem with whonix on qubes 4.0.1 - manually upgraded to whonix-15, 
fedora-30, kernel 4.19. 

When whonix-sys networking VM is configured to my VPN VM, tor connection gets 
established which allows me to use TOR browser in 'anon-whonix'. Everything 
works fine, but... that's not the recommend way of connecting to TOR. When 
possible 'whonix-sys' should be set-up using ISP line directly ISP (non-VPN) so 
that Tor establishes the route between its 3 levels of nodes without having VPN 
server as a fixed entry/exit point. 

And that's what I'm having a proplem with, unexpectedly. When I set up 
'sys-firewall' or 'sys-net' as netVM for 'whonix-sys' I can't get 'anon-whonix' 
to establish Tor Browser connection, can't access any website. Even whonix-sys 
'Tor Control Panel' struggles with establishing Tor connection. This is highly 
surprising as I don't live in a country where ISP's prevent any onion/tor 
traffic. It should all work fine. 

I then tried playing with various clock settings on my host (dom0) to match the 
clock in UTC in sys-whonix (timedatectl command). Unfortunately the problem 
persists - I am able to connect to Tor via VPN VM but not directly via 'open' 
ISP sys-net or sys-firewall VM. 
I have an impression the problem started after whonix upgrade to version 15 and 
qubes introduction of the clock-synchronisation-monitor. I might be completely 
wrong about it, it's just the timing of the issue coincides with the introduced 
qubes changes.

Does anyone had a similar problem? Or better still, does anyone know the 
solution and how to fix it?
 Please help or point me to the right directly. 

Many thanks,
cubecub

-- 
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/LpOwegA--B-1%40tutamail.com.

Re: [qubes-users] Re: Qubes 4 boot stuck at: "[ OK ] Reached target Basic System. "

[cubecub]

Apr 3, 2019, 8:47 PM by qubes-users@googlegroups.com:

> cube...@tutamail.com >  wrote on 4/3/19 6:26 PM:
>
>> Thank you for your suggestion. I have given it a try but unfortunately the 
>> systems hasn't yet been restored. (I'm guessing you referred to the 
>> following commands to enter rescue mode: pkill -9 anaconda;  anaconda 
>> --rescue; )
>>
>> I also tried mounting my Qubes disk in LinuxMint, using commands:
>> cryptsetup luksOpen /dev/sda2 qubes-disk;
>> then pvscan, pvdisplay, vgscan, vgdisplay, lvscan, lvdisplay.
>>
>> These allowed me to see logical structure of my qubes_dom0 volumes, volumes 
>> representing AppVM, but I was unsuccessful mounting these volumes to get 
>> access to the data.
>> Comman 'lvscan' shows LV status next to each volumes, and  only 'swap' was 
>> marked as active. Everything else was 'NOT active', including 'root', 
>> 'pool00', and AppVM volumes.
>>
>> Do you, or anybody else, have any idea how to proceed? I must recover the 
>> data. I hope they didn't get corrupted, only the access point has gone 
>> missing.
>>
> You're in the right area, but I don't see a "vgchange -ay" in your list of 
> commands?
>

Hi, 
Yes, I've tried the command "vgchange -ay" and it gives me error message:
"Check of pool qubes_dom0/pool00 failed (status:1). Manual repair required!
1 logical volume(s) in volume group "qubes_dom0" now active. "

That single active volume is 'swap'. 
All other lv'sn (which I have 86) have "LV Status" set to "NOT available", and 
I can't turn them back to active. Also vgchange wasn't able to activate them. 

Is there any other way to to get to the lv's of the LUKS encrypted qubes disk?

 Are there are any dedicated LUKS / LVM2 recovery tools (somebody mentioned 
'scalpel' but I have't tried it yet)? 
I would be grateful for any hints into good direction of retrieving data from 
my luks encrypted qubes disk. 

Thank you.


>
> -- 
> 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/70a61521-d7dc-9e17-eae1-7872d2e79...@danwin1210.me
>  
> >
>  .
> For more options, visit > https://groups.google.com/d/optout 
> > .
>

-- 
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/Lbdbxds--3-1%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4 boot stuck at: "[ OK ] Reached target Basic System. "

[cubecub]

Apr 3, 2019, 4:40 PM by jayen.de...@gmail.com:

> On Wednesday, April 3, 2019 at 7:52:38 PM UTC+5:30, cub...@tutamail.com wrote:
>
>> Hi,
>>
>> Please help! 
>>
>> I've shut down my Qubes 4 system last night and it wouldn't restart. After 
>> providing my disk encryption password the system is stucks at:
>>
>>
>>
>> "[ OK ] Reached target Basic System. "
>>
>> followed by numerous line with:
>>
>> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
>> timeout scripts
>>
>> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
>> timeout scripts
>>
>> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
>> timeout scripts
>>
>> .
>>
>> [] dracut -initqueue[338]: Warning: Could not boot.
>>
>> [] dracut -initqueue[338]: Warning: /dev/mapper/qubes_dev0-root does not 
>> exist
>>
>> [] dracut -initqueue[338]: Warning: /dev/qubes_dev0/root does not exist
>>
>> Starting Dracut Emergency Shell...
>>
>>
>>
>> This is very strange. I haven't even updated 'dom0' lately and the system 
>> shut down clean. But it just wouldn't start today. 
>>
>>
>>
>> If I can't recover the Qubes-OS system as the whole please help me retrieve 
>> data/files that I have in my AppVM volumes. How can this be done. 
>>
>>
>>
>> This is an emergency for me and I would be immensely grateful for somebody's 
>> help to either fix systms boot, so that it could start again, OR help to 
>> connect my system disk to other OS and retrieve the data. 
>>
>>
>>
>> Thank you !
>>
>> cubecub
>>
>
> Have you tried rescue mode using installation media? You can try it and I 
> believe it should help. I had used rescue mode to edit my xen.cfg file which 
> had helped to me boot the system one again in case I had passed some wrong 
> parameters to xen.cfg. You can access rescue mode by pressing ctl+alt+f5. May 
> be it will help you. 
>

Hi, 
Thank you for your suggestion. I have given it a try but unfortunately the 
systems hasn't yet been restored. (I'm guessing you referred to the following 
commands to enter rescue mode: pkill -9 anaconda;  anaconda --rescue; )

I also tried mounting my Qubes disk in LinuxMint, using commands:
cryptsetup luksOpen /dev/sda2 qubes-disk;
then pvscan, pvdisplay, vgscan, vgdisplay, lvscan, lvdisplay. 

These allowed me to see logical structure of my qubes_dom0 volumes, volumes 
representing AppVM, but I was unsuccessful mounting these volumes to get access 
to the data. 
Comman 'lvscan' shows LV status next to each volumes, and  only 'swap' was 
marked as active. Everything else was 'NOT active', including 'root', 'pool00', 
and AppVM volumes. 

Do you, or anybody else, have any idea how to proceed? I must recover the data. 
I hope they didn't get corrupted, only the access point has gone missing. 

Please help with other suggestions or hopefully working solutions. 

Many 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 
> <mailto:qubes-users+unsubscr...@googlegroups.com>> .
> To post to this group, send email to > qubes-users@googlegroups.com 
> <mailto:qubes-users@googlegroups.com>> .
> To view this discussion on the web visit > 
> https://groups.google.com/d/msgid/qubes-users/6079c7b0-acaa-4d1f-8c60-caec837d4...@googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-users/6079c7b0-acaa-4d1f-8c60-caec837d475b%40googlegroups.com>>
>  .
> For more options, visit > https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>> .
>

-- 
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/LbZS-_E--3-1%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4 boot stuck at: "[ OK ] Reached target Basic System. "

[cubecub]

Hi,
Please help! 
I've shut down my Qubes 4 system last night and it wouldn't restart. After 
providing my disk encryption password the system is stucks at:

"[ OK ] Reached target Basic System. "
followed by numerous line with:
[] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
timeout scripts
[] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
timeout scripts
[] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
timeout scripts
.
[] dracut -initqueue[338]: Warning: Could not boot.
[] dracut -initqueue[338]: Warning: /dev/mapper/qubes_dev0-root does not 
exist
[] dracut -initqueue[338]: Warning: /dev/qubes_dev0/root does not exist
Starting Dracut Emergency Shell...

This is very strange. I haven't even updated 'dom0' lately and the system shut 
down clean. But it just wouldn't start today. 

If I can't recover the Qubes-OS system as the whole please help me retrieve 
data/files that I have in my AppVM volumes. How can this be done. 

This is an emergency for me and I would be immensely grateful for somebody's 
help to either fix systms boot, so that it could start again, OR help to 
connect my system disk to other OS and retrieve the data. 

Thank you !
cubecub



-- 
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/LbYZnUP--3-1%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Custom 16:9 dispay resolution to be applied at qubes-os startup (Q4.0rc4)

[cubecub]

Hi,
Could anyone help me with figuring out how to set one of the custom display 
resolution as startup default? 

Qubes 4.0 rc 4 comes with many predefined resolutions but unfortunately only 
one with the aspect ration of 16:9. 

I then created various custom resolution modes and added them to desplay 
options. I used the following commands:
cvt - to get new mode parameters
xrandr --newmode - to define new resolution mode
xrandr --addmode - to add newly defined resolution mode to deplay drop-down box
xrandr --output - to apply new, desired resolution to the current display. 

What I can't work out is how to make of my new, custom resolution to be used by 
qubes-os as default. 
What qubes-os configuration files should I modify and how in order to achieve 
that? Do I need to interfere with xen.config? 

If you already have a solution please share. 

Thank you
Paul






-- 
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/L5ezclA--3-0%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HP 1040 G3 laptop - wireless toggle button doesn't work

[cubecub]

Hi, 
I've installed Qubes-OS 4.0 rc4 on HP 1040 G3 laptop. 
It seems HP has changed the rules of the game and introduced dedicated driver 
for the physical wireless toggle button (located above the keyboard, next to 
the audio on/off button). 
I actually test installed Windows 10 on the laptop to confirm the new feature. 
And indeed, without installing "wireless button driver" pressing the button 
would not cause any effect. 
The same holds true with Qubes-OS installed on the laptop. 

Is there any way of forcing this button to work? It works fine on older HP 
laptop models but they seems to be tightening their hardware architecture even 
further. 

My alternative approach for now is to create scrips in sys-net VM to load / 
unload kernel modules (sudo rmmod iwlmvm / sudo rmmod iwlwifi / sudo modprobe 
iwlwifi). This does work fine but is not as elegant as pressing dedicated 
button. 

Please share your thoughts and suggestions on forcing HP 1040 G3 to behave. 

Thank you
Paul







-- 
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/L5eSbDB--3-0%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HP laptop - issue with "pulsating" fan, ramping up and down every 3s

[cubecub]

Hi, 
I've recently bought an HP 1040 G3 laptop to use with Qubes-OS. The latest 
version has been installed (4.0 rc4) but I have few issues that I'm trying to 
sort out. 

One of them is the issue with fan speed. As the qubes OS starts the fan is 
constantly on, but the speeed seems to insrease ever so slightly every 3s. That 
creates an "pulsting" effect of the fan noise which, when using the laptop for 
a longer time, becomes really disturbing. 

I tried to find solutions online but as of now was unsuccessful. In Power 
Management settings of quebes there is no reference to fan speed or settings 
that could influence it. 

Could anyone advise how to setup and control fan speed with qubes-os? 

Many 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 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/L5ePVnF--3-0%40tutamail.com.
For more options, visit https://groups.google.com/d/optout.