Re: [qubes-users] Re: qubes_dom0-root fsck failed with error code 4
On Sun, May 14, 2017 at 09:53:26PM -0700, qbert...@gmail.com wrote: > The Guest log for the VMs say the filesystems are read-only. > The fedora template also doesnt boot. > > I've rebooted once again to the usb install stick and try to rescue. Again I > chose option 1 to mount the partition, and when i run chmod /mnt/sysimage, i > dont get any errors. > >From here I woud like to run a checkdisk or something like in windows. Am I > >on the right track? > > If I coud just get these VMs to boot I could get my data off of them and do a > full reinstall. > Any help would be appreciated. > You dont *need* to get the VM to boot to get at the data. All the private data in a template based VM is stored in the private.img. You can get at the data just by mounting the private.img, and looking in /home. If I were you I would attach a backup drive, and copy off the files from /var/lib/qubes/appvms. I would do this in preference to using qvm-backup, (although once done you can try the backup route also.) First secure the data. Then try to get the systems running - or dont bother, and just reinstall from scratch. If you haven't tried the backup just mount your backup medium in a qube, mount the private.img files and copy the data cross to your newly created qubes. But get the data off the system first. Good luck unman -- 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/20170515191147.GA7592%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qubes_dom0-root fsck failed with error code 4
On 05/15/2017 01:43 AM, qbert...@gmail.com wrote: I'm unable to get the guest.log for the VMs off of the laptop, so I've attached a screenshot of the log of the most critical VM that i need to rescue. It appears it is going into emergency mode, but I can't run a terminal or anything as qrexec never connects. The qrexec.log is empty. Is there any way get this to boot, or to extract a few files from within it to dom0? Have you tried mounting an external drive and then running qvm-backup? -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/c01c5dce-ab04-a49d-6433-577b75be314c%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes_dom0-root fsck failed with error code 4
The Guest log for the VMs say the filesystems are read-only. The fedora template also doesnt boot. I've rebooted once again to the usb install stick and try to rescue. Again I chose option 1 to mount the partition, and when i run chmod /mnt/sysimage, i dont get any errors. >From here I woud like to run a checkdisk or something like in windows. Am I on >the right track? If I coud just get these VMs to boot I could get my data off of them and do a full reinstall. Any help would be appreciated. -- 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/8ccc7918-4b88-41ca-865d-5369bca4c78b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes_dom0-root fsck failed with error code 4
I went ahead and did fsck, saying yes to all prompts. It went a little crazy for a while, then finished. The shutdown command doesnt exist, so i lowered it off. The next boot progressed till it sat at a umts something or other. Another poweroff, and the next boot finished. I'm logged in now, but no VMs will start. -- 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/1b96b339-401c-49cc-ac92-addd6016729f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
