From nobody Sun Feb 02 17:55:34 2025 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YmHNQ6RVRz5mZtk for ; Sun, 02 Feb 2025 17:55:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YmHNQ5whfz40k2 for ; Sun, 02 Feb 2025 17:55:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738518934; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=OIaqiE48rwc3N7MKs63qJgKp0qSj8i+R7nHOWnsjxlo=; b=L/Q06TIuBDj0HE/GDCFJ6vW8g0DPO2Fu4WOy/CsiqFaBnt+e/5dYfw/R50jtxTM4HmdUJX cfUxxFBQ4HLsPyUaGlFS/bRfislUqEJXaNkK+SaV/DwZqH7FZHurxa/+wgZBkzgyROsojk QjEBfhjPnAXJFWITJ+L0orDKymnxIoIh6DM7NnMW5EMxyzNuhxoicC0pA2NoTCCwsDASNp /bhRxjKI9bS8R7jfzGeh8Ca3R1eOkfE9boEtfX0JCuopg8PDlUkBUprPtJABGZrL/8khz2 X8MGt43D/3VwUSeb3dDRAzc1wgr6KXSOfHITUA+MFVYUQMoVeX0oY9JX4TC7hw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738518934; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=OIaqiE48rwc3N7MKs63qJgKp0qSj8i+R7nHOWnsjxlo=; b=WAKVDKb6be/qCF041K7aliupgc0/MnylkzbO6me4M1erTGPndrg5BAG9UMlnTJ78hwIMpC Fz5sWkeR7Dr2+yMElP4GJzqfNR0ntJ4rzs2HLek9z5x9WPK8OOqql2kvo8oLBUaKkSw3ox wdNztO7SignSnErl9DNqkF5G/vSE3vWZln6qYvPxmiAoPEEKDFuJn9ACeAO94gtkVU3xgs /29FjpkAJi15IgZBqBj3jJzq52XdsIAac2JHUwXS1lxUeJjCgMRCg0pdYRzHRHabsvD4iK hf1S/M+P43+xYMzi6LSFbHNh3BqA8s+OIVhExpIXV69USmfYXCgy/bPr97upeA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738518934; a=rsa-sha256; cv=none; b=eHxJZpU5kXEOpGuC3/acS7IcUzDxTxHoP/LK6kpJOkZ47nTjh8WGmTVdgqm92wsTi/Fbqf 6TWPE7fhE+9G+/L94eUbEKhhDdpK8qZrFfXjo4FLoDlv8v2woPcJNQsFPPh3ADV4Xg86r7 WQgV3pfJ6EcU6DSEjKWRBEpXbXzujbFkJbDH4Q97X54nk9PsdFCcTrmKQpaKVP2QUzBj/6 Da6ZTu2pdtiiUDeANo3snhHnni/lyw0TPoUEyNo2XRJZvtQ4TkZqBzyO5d3MII0FdAAbt2 zrjSMkl7SV1274p2h/7QMHZrDZk6tWyqg8N/SMUs4FeywrNe2edQEHYSZ1Lm0w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YmHNQ5HGtz10h7 for ; Sun, 02 Feb 2025 17:55:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 512HtYMm089077 for ; Sun, 2 Feb 2025 17:55:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 512HtYX8089076 for bugs@FreeBSD.org; Sun, 2 Feb 2025 17:55:34 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 284525] bsdinstall can make running system unbootable Date: Sun, 02 Feb 2025 17:55:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: barneywolff@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D284525 Bug ID: 284525 Summary: bsdinstall can make running system unbootable Product: Base System Version: 14.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: barneywolff@gmail.com Running bsdinstall on an existing system can make the system fail and be unbootable without manual console intervention. Script /usr/src/usr.sbin/bsdinstall/scripts/zfsboot line 804 forces export = of all existing zpools. There is NO warning of this, only that the disk/partit= ion being set up will be destroyed. The ASSumption seems to be that bsdinstall = is running on new hardware with the install medium as the only existing filesystem. Running bsdinstall on a working system to create a new system d= isk risks disaster. If the existing system has only a root zpool with all fbsd components, disaster is averted because the export fails. But if it has a r= oot zpool and a separate zpool for /usr, /var and so on, the system immediately fails, the session drops, and no new login is possible. What's worse, power cycling will not let the system come up, because the non-root zpool has been exported. If console access is available the operator can boot to single us= er and re-import the needed zpool. Otherwise, the system is out of service indefinitely. The basic issue here is that it's all but impossible to tell if there is a zpool on the install target, because the target may be described in a zpool status as either a device like da3p2 or diskid/..... or gpt/..... or ... . I certainly cannot predict how fbsd will choose to describe a given disk/partition. And once the system chooses a diskid/... the da3p2 descript= ion disappears. I have another system with a mirrored zpool where one of two identical disks is listed in the diskid form and the other in the da3p2 for= m. At the very minimum bsdinstall should not do zpool export -F, but just plain export if it's done at all. Or just display the zpool list to the user and = let the user decide whether there's a pool on the disk about to be destroyed. --=20 You are receiving this mail because: You are the assignee for the bug.=