Hi Ivan,
Thanks a lot for the clarification! That was indeed it, I was trying to mount
the whole device.
I was able to fix the `/etc/fstab` and get my VM back up! (celebrations!)
Really appreciate all your help with this!
Fabio
‐‐‐ Original Message ‐‐‐
On Tuesday, November 27, 2018
Hi Fabio,
On 11/27/18 2:33 AM, 'Fabio' via qubes-users wrote:
Thanks for the reply Ivan.
I was able to mount `dom0:/dev/qubes_dom0/vm-...-private vmname` successfully,
however when trying to mount `dom0:/dev/qubes_dom0/vm-...-root vmname`, I still
get the `wrong fs type, bad option, bad
Thanks for the reply Ivan.
I was able to mount `dom0:/dev/qubes_dom0/vm-...-private vmname` successfully,
however when trying to mount `dom0:/dev/qubes_dom0/vm-...-root vmname`, I still
get the `wrong fs type, bad option, bad superblock...` error.
I can confirm that I get this same error
On 11/26/18 1:46 PM, 'Fabio' via qubes-users wrote:
I made an accidental edit to /etc/fstab which is causing my TemplateVM to
timeout on boot with error Cannot connect to qrexec agent for 60 seconds
Is there a way to edit a particular VM's etc/fstab without booting it up? Can I
perhaps
I made an accidental edit to /etc/fstab which is causing my TemplateVM to
timeout on boot with error Cannot connect to qrexec agent for 60 seconds
Is there a way to edit a particular VM's etc/fstab without booting it up? Can I
perhaps mount it's root filesystem?
Attempted solutions
1.
