Thanks, with sudo `xl console [vmname]` I have been able to open a terminal in the damaged vm and solve the problem. The problem was that the block count of `xvdb`, the shrinked volume mounted in /rw , exceeded the size of the device. So I just set the device size with `lvresize` to a bigger one and everything seems to work.
On Monday, August 24, 2020 at 11:19:13 PM UTC+2 awokd wrote: > Filippo Merli: > > > > Hi, > > > > after shrink a standalone vm volume with lvresize is not possible > anymore > > access the volume data. > > The vm start but is not possible to open a terminal. Is there a way to > > access the data from another vm or from dom0? > > Enabling debug mode in Qube Settings might get you a terminal so you can > see what's wrong. Also can try sudo xl console [vmname] in dom0 when > it's powered on. It is possible to copy the volume to a file to attempt > recovery in another VM. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0d46524f-7973-4e4f-9a5f-fbfa34cd7a4an%40googlegroups.com.
