On Tuesday, October 16, 2018 at 4:55:47 PM UTC+2, unman wrote: > On Tue, Oct 16, 2018 at 12:44:45AM -0700, Foppe de Haan wrote: > > So it appears that something went very wrong during a dom0 update. > > The emergency mode of the regular boot process does attempt to load, but > > hangs or stops before it finishes, so I can't get a shell that way either. > > Have also tried to 'rescue' the system via a qubes installation medium, but > > after entering the correct LUKS passphrase, it says something like 'no > > valid linux installation found', and stops. > > > > Anyone have suggestions as to what I might try next, if anything? > > > > Depending on how important your data is to you you might want to start > by cloning the disk. (I'd recommend clonezilla for ease of use.) > > You can check that your data is safe by booting from a live image - > kali, knoppix etc. > Then try to mount your Qubes partition - you'll need to use cryptsetup > luksOpen to decrypt the disk, and you should then be able to mount the > partition. > You don't say whether you are using 3.2 or 4.0, and the approach to take > will depend on that. In 4.0 individual qubes by default use thin pools > so you will need to identify the qubes you are interested in and check > in /dev/qubes-dom0 using 'ls -l' which of the device files in /dev > match. > You can then mount those devices and copy out the data. > > Once you've secured all your data, you can try for recovery of the > system. I've had some success in doing this but frankly it's almost > always better to reinstall, particularly as you don't know *what* went > wrong. > If you've got recent backups or don't care about the data, I would just > skip those steps and reinstall. > > If you need specific advice give a little more detail about how you had > the system configured and exactly what steps you've taken so far. > > Best of luck > > unman
Thanks, will do (wrt cloning). Last backup was from april, so I'd like to recover if possible. r4.0; as to what went wrong, not sure exactly; qubes-dom0-update finished properly, but fairly soon afterwards, I experienced a hard reboot, likely due to unstable memory settings, which I had been tinkering with a bit. So far all I've tried is to boot and/or repair the system, but I can't get the volume to mount, so haven't made any progress yet. -- 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/f63a2f06-e98d-4bab-bb9a-b533bff810c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
