Date: Wed, 6 Dec 2017 12:51:03 -0700 From: Randy Terbush <randy@terbush.org> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtua." <freebsd-virtualization@freebsd.org> Subject: Re: Recovering an ZFS vm Message-ID: <CALmWkDZr%2BwPi8HvOE=gLfw8ND2pgKFN=zqF=Vf35mkmcs7h52w@mail.gmail.com> In-Reply-To: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> References: <CALmWkDbeqCW_OZGxL_0_6mK%2B6fnpx3veX7i6F1dmJQmabh97cA@mail.gmail.com> <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At the end of this all, it seemed that some change has taken away my need to be very specific about the grub partitions. By removing the grub_run0 and grub_run1 parameters from the vm-bhyve configs and running simply with the one below, (and showing a bit of patients while it repaired partitions), it booted as expected. I also see that once booted, the / filesystem is an ext4. I really cannot explain and it is entirely possible that this is a memory issue on my part. loader="grub" cpu=2 memory=8G network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0" disk0_dev="sparse-zvol" I appreciate all of you taking time out to reply. -- Randy On Tue, Dec 5, 2017 at 4:56 PM, Peter Grehan <grehan@freebsd.org> wrote: > Hi Randy, > > I have a Centos vm that has suddenly stopped booting. At the console, grub >> tells me the following if I attempt to list any of the available >> partitions. >> >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> Filesystem type xfs, UUID 7652ffda-f7c5-408a-b0ce-b554b66fc2e5 - >> Partition >> start at 2048 - Total size 2097152 sectors >> grub> >> >> Is there an easy way to recover this? This has happened more than once. >> Just so happens there is something on this image I would like to have >> access to... >> > > Looks like the grub partition was upgraded to the version of XFS that has > the CRC feature enabled (7.2 ?). Unfortunately this feature is not > understood by grub-bhyve :( > > One way to recover the disk is to create a new VM with the most recent > CentOS, but using UEFI for the bootloader. Then, add this disk to the > guest, and from within the guest I think you can run an XFS utility that > will disable the use of CRCs on that partition. > > The proper fix would be for grub-bhyve to be updated to the latest > version of grub2, though a workaround is to create guests with UEFI and not > use grub-bhyve. > > later, > > Peter. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALmWkDZr%2BwPi8HvOE=gLfw8ND2pgKFN=zqF=Vf35mkmcs7h52w>