From owner-freebsd-virtualization@freebsd.org Wed Dec 6 05:50:34 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 90A75E91A49 for ; Wed, 6 Dec 2017 05:50:34 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::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 56CF163E99 for ; Wed, 6 Dec 2017 05:50:34 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-oi0-x236.google.com with SMTP id j17so1857869oih.3 for ; Tue, 05 Dec 2017 21:50:34 -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=qqwq3K09i5kSCOfw6XapPiWhcFDbtv05gpFe+BuLHtM=; b=h/Th5c9oJ34i5UOE5kTa7NdT9L3y3j2m2XXmH3zojvksFhMNyF7QkLZjxOUDy7AmFg H2tLvReSnfxfzutYRlc2UMD+aNQjXfvIlbi1I5savU8YK5JDjGAyyCHCc+xdhInjCLTg x4qIZc+5IzlLOir5K5PWao+CWrEMLz3vbprdo= 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=qqwq3K09i5kSCOfw6XapPiWhcFDbtv05gpFe+BuLHtM=; b=bxZmszfhz69cBXqApNxY4DHvkoZp4RUErW9GLmlWZKbVxWLT8P1x5pxFx6wQZltUwy G1AM3+WBKv0eS7jz+8gQMsAk3AMr9QZ3fjX1e5u/AQ9dkcT1yFIZ/DCSRXLXt1KTVAex 30t66JoYsIRbuesA/cM7RW5EUjRcQbedH76HXtnfsrJxxdGuiO9EUr9mAzSlks2uMVvA CaaKivBfAFawkx6yd230IWZOsy7qoFVVADYAGTJl+RhpMvm25DAZ6Hjjb+6XtihsGLz5 4YeAFtWBywI27vS5vAkv9bup6Rp3eiwv5PI5HzhXWozYauYIjw9uQZ040if65WFTZAZN 6Cgw== X-Gm-Message-State: AJaThX6EBzjTDLEYZIaH4dW66ck3Rz7CQwsjCxUT2nvTi29L7ekudIuR /BUuRh7dUeKWwKuIM1iifWpchLxMCt/Gc78220cjow== X-Google-Smtp-Source: AGs4zMYu8OK8h/BbMiAZg5kqU4sa9s9PNqjcUcvCzRA3PNNAimSUzHqIY69qw4AzWY8aq7C6e4bTqAAgl1ZsnGyI1MY= X-Received: by 10.202.5.132 with SMTP id 126mr19900119oif.276.1512539433403; Tue, 05 Dec 2017 21:50:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.168.67.10 with HTTP; Tue, 5 Dec 2017 21:50:02 -0800 (PST) In-Reply-To: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> References: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> From: Randy Terbush Date: Tue, 5 Dec 2017 22:50:02 -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 05:50:34 -0000 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 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. >