Date: Thu, 6 Jun 2019 12:04:20 +0000 (UTC) From: Filippo Moretti <filippomore@yahoo.com> To: FreeBSD Stable ML <stable@freebsd.org> Subject: Problem with 12_STABLE on amd64 Message-ID: <1799954470.420960.1559822660430@mail.yahoo.com> References: <1799954470.420960.1559822660430.ref@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have the following problem on amd-64 STABLE-12for some odd reason my custom kernel no longer boot while I could build GENERIC and that would boot fine.Today I wrote a new configuration kernel file removing only the devices I do not have.Unfortunately the working kernel was not moved to kernel.old as it would be expected and now I am locked out of the system as the new kernel fail to bott with error sis cannot find zroot/ROOT/default.Is there a way to recover my system?SincerelyFilippo From owner-freebsd-stable@freebsd.org Thu Jun 6 15:16:39 2019 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54F2715B660A for <freebsd-stable@mailman.ysv.freebsd.org>; Thu, 6 Jun 2019 15:16:39 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C6AF870DD4 for <freebsd-stable@freebsd.org>; Thu, 6 Jun 2019 15:16:38 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: by mailman.ysv.freebsd.org (Postfix) id 8520F15B6607; Thu, 6 Jun 2019 15:16:38 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 603A615B6605 for <stable@mailman.ysv.freebsd.org>; Thu, 6 Jun 2019 15:16:38 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: from enterprise.ximalas.info (enterprise.ximalas.info [IPv6:2001:700:1100:1::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ximalas.info", Issuer "Hostmaster ximalas.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AD83D70DD2 for <stable@freebsd.org>; Thu, 6 Jun 2019 15:16:37 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: from enterprise.ximalas.info (Ximalas@localhost [127.0.0.1]) by enterprise.ximalas.info (8.15.2/8.15.2) with ESMTPS id x56DBOZI003585 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 6 Jun 2019 15:11:24 +0200 (CEST) (envelope-from trond.endrestol@ximalas.info) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ximalas.info; s=default; t=1559826684; bh=kjwzXLxDD3zTy0NdjcrjxiXPfaB3r5k7mLJMcNsROUU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=RqcYJgslqIl584A0q+sjeQpIyNOingS9gBOzls8Q2eSgPk5BoH/bUzAebN4bMIdnd Iazgi07lgRA8kj/nd90RDXORmpQp7QKK0RoKVmdhKWeMzGsyEudh4kQv2sWsukeU0E qC1ah+KqMxIu8CBeJKX7F9yOHydiFjyD8bMCfJkVkXH+LSY+yB1inWGxheE+jbEXlR 2sk9Pz777rOvtcIRm/8H5CfArybkZl8e3IdfAFMDHwt82W3E0ypmQbPLfb7tW9KrNQ DWc9gbBvG6PXNsfGZIq1yBxLZ7j844vGyg+muIh4tXxZJMEJXrWCNM1Pt4iDyp9JHV /phepGt2vPjZQ== Received: from localhost (trond@localhost) by enterprise.ximalas.info (8.15.2/8.15.2/Submit) with ESMTP id x56DBNhQ003582; Thu, 6 Jun 2019 15:11:24 +0200 (CEST) (envelope-from trond.endrestol@ximalas.info) X-Authentication-Warning: enterprise.ximalas.info: trond owned process doing -bs Date: Thu, 6 Jun 2019 15:11:23 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> Sender: Trond.Endrestol@ximalas.info To: Filippo Moretti <filippomore@yahoo.com> cc: FreeBSD Stable ML <stable@freebsd.org> Subject: Re: Problem with 12_STABLE on amd64 In-Reply-To: <1799954470.420960.1559822660430@mail.yahoo.com> Message-ID: <alpine.BSF.2.21.9999.1906061456140.5734@enterprise.ximalas.info> References: <1799954470.420960.1559822660430.ref@mail.yahoo.com> <1799954470.420960.1559822660430@mail.yahoo.com> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) OpenPGP: url=http://ximalas.info/about/tronds-openpgp-public-key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on enterprise.ximalas.info X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Jun 2019 15:16:39 -0000 On Thu, 6 Jun 2019 12:04-0000, Filippo Moretti via freebsd-stable wrote: > I have the following problem on amd-64 STABLE-12for some odd reason > my custom kernel no longer boot while I could build GENERIC and that > would boot fine.Today I wrote a new configuration kernel file > removing only the devices I do not have.Unfortunately the working > kernel was not moved to kernel.old as it would be expected and now I > am locked out of the system as the new kernel fail to bott with > error sis cannot find zroot/ROOT/default.Is there a way to recover > my system?SincerelyFilippo Press 3 in the boot loader to enter the command line. Type in these commands: unload load /boot/kernel/kernel load /boot/kernel/opensolaris.ko load /boot/kernel/zfs.ko boot -s Your keyboard layout is "US" at the moment. The hyphen (minus) key is usually on the plus key when the US keyboard layout is active and you're using a non-US keyboard, and slash is usually on the hyphen key. Once you get to a proper Unix shell, you might want to change the keyboard layout to something sensible using: kbdcontrol -l <layout> If you have physical access to your system and bootable install media at hand, you could boot from said install media, select shell, and import your pool using: zpool import -Nf zroot Manually mount your rootfs, e.g.: mount -t zfs zroot/ROOT/default /mnt If one of these routes was successful, edit your /boot/loader.conf or /mnt/boot/loader.conf using edit, ed, ee, or vi, to include: zfs_load="YES" Mount other filesystems as needed, or reboot to see if your system has recovered. -- Trond.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1799954470.420960.1559822660430>