From owner-freebsd-virtualization@freebsd.org Wed Dec 6 19:51:35 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89C44E8A75A for ; Wed, 6 Dec 2017 19:51:35 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5373180417 for ; Wed, 6 Dec 2017 19:51:35 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-ot0-x236.google.com with SMTP id v21so4403827oth.6 for ; Wed, 06 Dec 2017 11:51:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Kzj35NZQMPbvL9Oxe41AMFLWj9B7wCnu9JIZ0qKoI7g=; b=LeaAhK1LJnWKozWyCv4uUw3O/tXj9c0QKe8PEQIxkAEh4n91FFRtipvSfv+JS7FKci jw6rDw6rpcYJmhr6nFm22FwPUUstaw5QRUxKBxHS7gyXK+MjXop3IOM1xtLSIYA6GXgB RoQCWjw+5nrhvmVOFpuMx+aXsGBIFHmbLDFSg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Kzj35NZQMPbvL9Oxe41AMFLWj9B7wCnu9JIZ0qKoI7g=; b=Gs//hl2DxbXBdUZJqgnvalzbXMIDqvMMVugSW2b3dHfXn+eq/p8iiVgyFudsnwf/hy TCaSkVTKuDT8fR3FL6AP+uJE7YPQuUBZie4BNKDn+//rDm3DPkwWtuVN+dUAxb0/Z9aN 2fIrlTQlHrIj6BvVSe40JpGs58d3u/6puuCXaHeHs+enzjtHcCz3kYV3cDo5a7D0xlen G2Yudp1+TRJOgSIC82hTK3FHP5twKRUGctpWbo6W5VjsDtPgJMKZivYGVUEQ3iqj/2LA 80+VNzesCsssGm2RM5986XezCfccOv02Bc2F+pULZWAtpuSecgddgL2LODUBzts6sU2n 3sQw== X-Gm-Message-State: AJaThX7vWWwXDZk/yERHCzO6WTCFc799FOypkClXZ3uAmcBXjzzYOxaw wHqDi5FwJYgZ2Qg1gN31X54m4A+hTRD68aTbBrh4Ag== X-Google-Smtp-Source: AGs4zMbw51W2NteIA5AaJunwcvPPSSWIVa+J2BMROFtNhwLD3hr+QCpksHXS5Jb1hSlzmMGVla3NKpGW+IuO3A6ggXo= X-Received: by 10.157.37.106 with SMTP id j39mr24459556otd.294.1512589894130; Wed, 06 Dec 2017 11:51:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.168.67.10 with HTTP; Wed, 6 Dec 2017 11:51:03 -0800 (PST) In-Reply-To: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> References: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> From: Randy Terbush Date: Wed, 6 Dec 2017 12:51:03 -0700 Message-ID: Subject: Re: Recovering an ZFS vm To: Peter Grehan Cc: "freebsd-virtua." Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 19:51:35 -0000 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 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. >