On 2020-01-23 04:08, Vít Šesták wrote:
*APL external email warning: *Verify sender
qubes-users+bncbct5hvg33eerbeofuxyqkgqeaao4...@googlegroups.com before
clicking links or attachments
Thank you! This has allowed me to mount the volume to a DVM, which has
allowed me to fix the issue. Just
Thank you! This has allowed me to mount the volume to a DVM, which has
allowed me to fix the issue. Just running fsck in the DVM was enough to fix
the issue.
Maybe I should create an issue (or find an existing one) for that.
Regards,
Vít Šesták 'v6ak'
--
You received this message because you
On 2020-01-22 12:22, Vít Šesták wrote:
*APL external email warning: *Verify sender
qubes-users+bncbct5hvg33eerbs4julyqkgqezk4s...@googlegroups.com before
clicking links or attachments
I have tried to debug it further. Unfortunately, I am unable to attach
the VM's drive to a DVM:
$
I have tried to debug it further. Unfortunately, I am unable to attach the
VM's drive to a DVM:
$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device
'mapper/qubes_dom0-vm--debian--10n--root'
How can I do that?
I have tried to debug it further. Unfortunately, I am unable to attach the
VM's drive to a DVM:
$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device
'mapper/qubes_dom0-vm--debian--10n--root'
How can I do that?
