From owner-freebsd-virtualization@freebsd.org Wed Dec 6 09:06:44 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 69830E9A14B for ; Wed, 6 Dec 2017 09:06:44 +0000 (UTC) (envelope-from paul.g.webster@googlemail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 1E9DF699B0; Wed, 6 Dec 2017 09:06:44 +0000 (UTC) (envelope-from paul.g.webster@googlemail.com) Received: by mail-yw0-x229.google.com with SMTP id t189so1277799ywg.9; Wed, 06 Dec 2017 01:06:44 -0800 (PST) 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=AQPhIHxCn6lxVXFCmQ8pVgMkQguA38HNxmQY7aPWvsk=; b=RCZqqHyX88sJWWPrTGDbmuXEwyaftYA8r1XglAo8RnmEbeB4/2acdackblFnlHx2AU +18vtEzjwWb4WaM8UU1z1/SBP71C/1aXbBTR2tW7QXl5Lgvv+7sHwotpX+8eJ1xd9hMp /tlP8FDpq59gUzkLs7WPL8XH1MF7EssSdkRQvBLGHKcNsva/+MJvjLkAOwxS4xgE+Puu gegMYZEQ7YoZiBPS9C2AcEbeuoPwuL+CsuYJ4/f5Xb7xUgMn9UjAmJ7vb0rf8Ma0idNl bMD2zmwrNMAvXIruu1aoz4rYV0ChZsKo33WrJ1eUJf0Jc6z1JHZN03kTZtWGJmyywS6r 1qVg== X-Gm-Message-State: AJaThX5tTEkrbwv7Vq7qqKSbmWojJnFuHB9oA2sFND9nOuw+5d0ZP4mC w56PydtWSnfgJwNXdsXmJr4v4N2Fp/sJOprsWbY= X-Google-Smtp-Source: AGs4zMb6viJhfEwTZJqbqID47YyjIZ6Qwsk+kpg+i1HMJs02vZUIYyv0ewHki8En2HE9iXKJhyAqRXbvOFsHtd+U2Xk= X-Received: by 10.129.109.85 with SMTP id i82mr14687423ywc.444.1512551203229; Wed, 06 Dec 2017 01:06:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.165.8 with HTTP; Wed, 6 Dec 2017 01:06:42 -0800 (PST) In-Reply-To: References: <81d05d9d-044a-9cad-40e3-5ddf86da6570@freebsd.org> From: Paul Webster Date: Wed, 6 Dec 2017 09:06:42 +0000 Message-ID: Subject: Re: Recovering an ZFS vm To: Randy Terbush Cc: Peter Grehan , "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 09:06:44 -0000 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 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 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 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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubs >> cribe@freebsd.org" >> > >