On 25/01/2017 22:37, Ángel wrote: > Bernhard wrote: >> Thank you Angel, for helping me. >> > You're welcome, Bernhard. > > >> and, as I said, nothing starts. I start thinking of a disaster-mode data >> recovery since I do not know how I could possibly unbrick a system that >> has no network anymore?! > That's just because most VMs depends on sys-net, and sys-net is not > available. Can you still edit them with Qubes VM Manager? The VMs should > at least start if you set their NetVM to none. Then you could create a > new sys-vm if it still doesn't get fixed. > > Best > Hello Angel, that worked. With "no net" I can start the VM's.
That solves a big pb, I can now backup data :) Before this trick, only with dom0 I would not have been able to attach the usb anywhere :)) 1) So, may I ask you some hint how to generate a new sys-net, please? 2) Another approach is this one: I looked at the guest-sys-net.log I cannot retype everything, so I give some extracts. The F24 part starts with fsck (?!) .. and after some time FAILED to start File System Check on Root Device. At this point one service after the next is Stopped, the log ends with : "Welcome to emergency mode" So, maybe I can first fsck the stopped sys-net fs from within dom0 by hand? How could I do that? I guess I loop /var/lib/qubes/(??) and then fsck it? Thank you, 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cfd04e81-1334-638b-0865-678e5e349e52%40web.de. For more options, visit https://groups.google.com/d/optout.
