Recovering an ZFS vm

[Paul Webster]

Or as an alternative that just come to mind if your just wanting to 'save
the system' boot the gentoo live DVD from the UEFI loader, that will get
you a live XFS supportive shell you can then setup basic networking from
and sync your important stuff elsewhere

On 6 December 2017 at 09:04, Paul Webster <paul.g.webster at googlemail.com>
wrote:

> if you can get to a system that is running the same kernel, you could
> build A compativle kernel with xfs in it and what not, stick it on a small
> '/boot' of your own and include that on your bhyve line, so the kernel is
> booted and then it mounts your existing system
>
> On 6 December 2017 at 05:50, Randy Terbush <randy at terbush.org> wrote:
>
>> One of the other VM clones is running. What do I need to do to mount the
>> sparse-zvol dataset that is this disk image that won't boot?
>>
>> I'm still confused as to why one of these VM images would boot and not the
>> other. They are both Centos 7 1708. At any rate, before taking a chance of
>> shutting this image down, I'd appreciate any help to mount this other zvol
>> and make sure the crc feature is disabled.
>>
>> Thanks
>>
>> --
>> Randy
>>
>> On Tue, Dec 5, 2017 at 4:56 PM, Peter Grehan <grehan at 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.
>> >
>> _______________________________________________
>> freebsd-virtualization at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>> To unsubscribe, send any mail to "freebsd-virtualization-unsubs
>> cribe at freebsd.org"
>>
>
>