Re: [qubes-users] Re: After last update system DEAD
'Evastar' via qubes-users: Again, what to do now? Never update or try to wait for month and then update? Short term, continue applying template updates as usual. If you run "sudo qubes-dom0-update", you can check for updates, but make sure to choose not to apply them with N. Wait for the next dom0 kernel release before trying to upgrade dom0 again, then pick and choose from my suggestions in the last email. :) -- 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/df0d5648-eb3f-4bba-d560-9c7661dc0a13%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: After last update system DEAD
> Did you notice any other errors around the soft lockup? Try searching > for them; it would be good to figure out what's causing the lockup, but > it can be hard to do. Only one error: all system very unresponsive, :) And as I'm already note 100% cpu usage by some processes. Also I saw strange "battary" icon at taskbar. It was like zero with some little dot image at the bottom corner of zero(gray) battery. System very quick take "dead lock" and freeze. Only Qubes Manager staring at this time. It freeze at 45%, at 91% and some time Qubes Manager load successfully, but after this system freeze. I guest problem not with some software, but how processor work with this kernel. > Most important thing is to backup your system before dom0 kernel updates. I have this idea on my mind after I install this new update and before reboot, but other mind come "what could be wrong. I update it since Q4 exists and never had problems with update :)". Again, what to do now? Never update or try to wait for month and then update? Thank you very much for your help! -- 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/XDiSl2Z1LU4w9tgvbWMQODym3wZrgZTqKQBc4oiDEjbOxDa62F7EV9jRHz5-S1xWapMkUI6MfjJoGnTiFsBUHGHbX8qO9xaF6NolU-OlVh0%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: By the way, I got the idea and switched to other tty before login to the system where Qubes Manager and other tasks start. It give me some time to use the system. And I found the bug at std error output: ! wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325] kernel changed successfully to previous one. What next? yes, now I will do new backups ASAP. But what next? Never run qubes-dom0-update? Did you notice any other errors around the soft lockup? Try searching for them; it would be good to figure out what's causing the lockup, but it can be hard to do. Most important thing is to backup your system before dom0 kernel updates. If uptime is a priority for you, wait for a week or so when dom0 kernel updates come out and monitor qubes-issues and the mailing lists to see if others are reporting problems. If so, hold off until they get addressed. If uptime is critical and you can afford it, get another machine with the same hardware configuration, and test out updates there first before applying them to your production system. See also Chris's suggestion https://www.mail-archive.com/qubes-users@googlegroups.com/msg27411.html. -- 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/230c659a-9e93-018c-f7a3-fc35b33324ac%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
By the way, I got the idea and switched to other tty before login to the system where Qubes Manager and other tasks start. It give me some time to use the system. And I found the bug at std error output: ! wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325] kernel changed successfully to previous one. What next? yes, now I will do new backups ASAP. But what next? Never run qubes-dom0-update? 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. 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/f8b4b009de708356a8b765b43a4fa3ee%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
Maybe it's possible to return to this emergency mode? System freeze until Qubes Manager start. It can freeze at 45% or at 91% or at any point. I see high cpu usage. It freeze because of this. I shutdown it before at this point and filesystem corrupt. Need the way to access /boot/efi without actual system load or I will lose all data and nothing will changed... -- 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/525fc0e42b6a4589f719abdb82d66d9a%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
Filesystem corruption is a different issue. In the emergency console, "fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks, then "reboot". If that lets you get back into Qubes, DO NOT DO ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as previously described. Thanks! Booted. I'm not sure that it's possible to make full backup now, because system freeze time to time with this kernel. But I will try. It's a good idea. -- 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/37b34f11d64009824f8a3be95f0c3249%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: On 2019-05-26 15:57, 'awokd' via qubes-users wrote: Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg it request to run fsch or e2fsck. What I must run first and how? Then if filesystem will be fixed, how to mount boot to change it? I guess this emergency console can help me, because dom0 console after boot not usable now (system can freeze). Here is a good point to change things. Hope that it's possible to recover filesystem here. Filesystem corruption is a different issue. In the emergency console, "fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks, then "reboot". If that lets you get back into Qubes, DO NOT DO ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as previously described. -- 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/51d2efbc-55cc-6e07-9e66-5ca7cc1706c5%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 15:57, 'awokd' via qubes-users wrote: Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg it request to run fsch or e2fsck. What I must run first and how? Then if filesystem will be fixed, how to mount boot to change it? I guess this emergency console can help me, because dom0 console after boot not usable now (system can freeze). Here is a good point to change things. Hope that it's possible to recover filesystem here. 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. 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/0b9ce701cd9af700435436ec0595f6f8%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 16:32, 'awokd' via qubes-users wrote: Yes, but be aware that it may mount the boot directory you're looking to edit underneath a different location, so watch the messages when you do. What is correct "mount" command to do this? And to fix filesystem then... -- 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/63c611b6eb33a0c34d7f8efcfc89b2f8%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: On 2019-05-26 15:57, awokd wrote: First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. Totally DEAD :( After reboot -> boot -> system freeze because high cpu ussage -> reboot... Now it boot only to console: generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue etc. Also this message say that it's possible to mount boot. Maybe it's good ideato mount it, change setting and then try to boot again? Yes, but be aware that it may mount the boot directory you're looking to edit underneath a different location, so watch the messages when you do. -- 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/6e80f360-640e-c519-03ec-4709c83cebc4%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
On 2019-05-26 15:57, awokd wrote: First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. Totally DEAD :( After reboot -> boot -> system freeze because high cpu ussage -> reboot... Now it boot only to console: generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue etc. Also this message say that it's possible to mount boot. Maybe it's good ideato mount it, change setting and then try to boot again? -- 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/c8d7bf962eb7f15855c0d0b0f2212e39%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: After last update system DEAD
evas...@firemail.cc: Okey... keep calm... Time to time I can use dom0 console without troubles (sudo qubes-dom0-update also still work by no fix still come :( ) I guess now need to somehow change new kernel to old one? How to do this? I guess I'm at UEFI mode (new notebook) 1) boot from some qubes installed usb flash and I will see recovery mode? Or not? 2) I tried to access /boot/efi/ to edit xen.cfg (only it must be edited?), but no access. sudo cd /boot/efi/ (success) then-> sudo ls show me my home folder. How to get access to /boot/efi and what I must edit to return to my old kernel? 3) or any other recovery methods please :) Thanks! First thing to try is to rollback the dom0 kernel update. If you're using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change the default kernel line at the top to point to the previous version number. Save and reboot. If you're not sure how to do that, send me your xen.cfg file. -- 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/f7ea68d7-6f55-9f2e-3a8c-fc4ba4e94855%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: After last update system DEAD
Okey... keep calm... Time to time I can use dom0 console without troubles (sudo qubes-dom0-update also still work by no fix still come :( ) I guess now need to somehow change new kernel to old one? How to do this? I guess I'm at UEFI mode (new notebook) 1) boot from some qubes installed usb flash and I will see recovery mode? Or not? 2) I tried to access /boot/efi/ to edit xen.cfg (only it must be edited?), but no access. sudo cd /boot/efi/ (success) then-> sudo ls show me my home folder. How to get access to /boot/efi and what I must edit to return to my old kernel? 3) or any other recovery methods please :) 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. 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/513ac84ee49fc40e0b7d3a97f4b896ef%40firemail.cc. For more options, visit https://groups.google.com/d/optout.
