Apr 3, 2019, 4:40 PM by jayen.de...@gmail.com: > On Wednesday, April 3, 2019 at 7:52:38 PM UTC+5:30, cub...@tutamail.com wrote: > >> Hi, >> >> Please help! >> >> I've shut down my Qubes 4 system last night and it wouldn't restart. After >> providing my disk encryption password the system is stucks at: >> >> >> >> "[ OK ] Reached target Basic System. " >> >> followed by numerous line with: >> >> [....] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting >> timeout scripts >> >> [....] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting >> timeout scripts >> >> [....] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting >> timeout scripts >> >> ..... >> >> [....] dracut -initqueue[338]: Warning: Could not boot. >> >> [....] dracut -initqueue[338]: Warning: /dev/mapper/qubes_dev0-root does not >> exist >> >> [....] dracut -initqueue[338]: Warning: /dev/qubes_dev0/root does not exist >> >> Starting Dracut Emergency Shell... >> >> >> >> This is very strange. I haven't even updated 'dom0' lately and the system >> shut down clean. But it just wouldn't start today. >> >> >> >> If I can't recover the Qubes-OS system as the whole please help me retrieve >> data/files that I have in my AppVM volumes. How can this be done. >> >> >> >> This is an emergency for me and I would be immensely grateful for somebody's >> help to either fix systms boot, so that it could start again, OR help to >> connect my system disk to other OS and retrieve the data. >> >> >> >> Thank you ! >> >> cubecub >> > > Have you tried rescue mode using installation media? You can try it and I > believe it should help. I had used rescue mode to edit my xen.cfg file which > had helped to me boot the system one again in case I had passed some wrong > parameters to xen.cfg. You can access rescue mode by pressing ctl+alt+f5. May > be it will help you. >
Hi, Thank you for your suggestion. I have given it a try but unfortunately the systems hasn't yet been restored. (I'm guessing you referred to the following commands to enter rescue mode: pkill -9 anaconda; anaconda --rescue; ) I also tried mounting my Qubes disk in LinuxMint, using commands: cryptsetup luksOpen /dev/sda2 qubes-disk; then pvscan, pvdisplay, vgscan, vgdisplay, lvscan, lvdisplay. These allowed me to see logical structure of my qubes_dom0 volumes, volumes representing AppVM, but I was unsuccessful mounting these volumes to get access to the data. Comman 'lvscan' shows LV status next to each volumes, and only 'swap' was marked as active. Everything else was 'NOT active', including 'root', 'pool00', and AppVM volumes. Do you, or anybody else, have any idea how to proceed? I must recover the data. I hope they didn't get corrupted, only the access point has gone missing. Please help with other suggestions or hopefully working solutions. Many thanks! > -- > 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 > <mailto:qubes-users+unsubscr...@googlegroups.com>> . > To post to this group, send email to > qubes-users@googlegroups.com > <mailto:qubes-users@googlegroups.com>> . > To view this discussion on the web visit > > https://groups.google.com/d/msgid/qubes-users/6079c7b0-acaa-4d1f-8c60-caec837d4...@googlegroups.com > > <https://groups.google.com/d/msgid/qubes-users/6079c7b0-acaa-4d1f-8c60-caec837d475b%40googlegroups.com>> > . > For more options, visit > https://groups.google.com/d/optout > <https://groups.google.com/d/optout>> . > -- 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/LbZS-_E--3-1%40tutamail.com. For more options, visit https://groups.google.com/d/optout.
