From nobody Thu Jul 18 00:27:21 2024 X-Original-To: questions@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 4WPYXR3ZhVz5Qjtg for ; Thu, 18 Jul 2024 00:27:03 +0000 (UTC) (envelope-from wfdudley@gmail.com) Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WPYXQ0gbhz52Hn for ; Thu, 18 Jul 2024 00:27:02 +0000 (UTC) (envelope-from wfdudley@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=m+4lC2yY; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of wfdudley@gmail.com designates 2607:f8b0:4864:20::933 as permitted sender) smtp.mailfrom=wfdudley@gmail.com Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-80fa1509989so137858241.0 for ; Wed, 17 Jul 2024 17:27:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721262420; x=1721867220; darn=freebsd.org; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=sf0nHTvsHOtK0+zqdyPyl+Ex/wWr75v2pb0cenYsg0c=; b=m+4lC2yYvhz1MqxxIPZrqB7hggxyWlVQwEx7oagsIpqLHhIlAQ+nD3P6VaYrf9IJEX KBH5Mn2PEQvZ5icfGK5Npp5GG38psVftSwzNLRfrOxgeUAZzDe+webw9q5KT64Of4pdk W8L3a8GG5namn2ZUJnGdqBELESLL93yT8w+VEWm0fzRo1BF2VbIvFgII63rNTjwB8/3O lRp0QKVoFFz2IIuyjaddkbSUpDRHQuJHLaEchft2FvoqYLqHP7ArB+eCBI9dChojaePd hqEjDj3n2T+9hgq1lvwIkbcd6tPNnZf9w+jArpLoFnBGyWggmBsneC/Z5KDfsnFVBIz7 5TZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721262420; x=1721867220; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=sf0nHTvsHOtK0+zqdyPyl+Ex/wWr75v2pb0cenYsg0c=; b=ufCO1JQ9d8s6cLemX+3OZBJ1ISZRvhB8qSLfGKO1lr9w1bGtzR4yfPcg+PgjMTpqey YRYAZy5msrh8jQzuvYkhIglKr7Cn9Zks7KLtxAt1vUKszr3qT+pVtswcaxeA0Q0mhpJn VjQY8qQcA+MuFvGmB8DGkmBKm5XUQ3n12H6sYAuMpnA5BQuua/klruHQhgtswpl6qcw3 YyfkMYHlahgC6pxPEHD30NciD/5zKBa4rM9f79xyoXqNDhKT9mVk8SA0A7WtVRXo0fdR xa0yoXuOYDCnddJXneLXHTlnTO7ab2RLBIahL7Wjfuy9q9cvYiI131iP6ELbIsyU5TtX Z+Qw== X-Gm-Message-State: AOJu0YyYtFQhsIqKoUbnkimjTU+0yJyUiAYpQ6EUjj0P0wJgjZYAfgq8 0uNudSwhIhUfgx2UHE36+bBVyv6W4BDRxoksgtoZqyumJMxfP36qqRgIoELNlJPyf3GJfdg1Esq pknyqHLCIwOwfTBkxHM2Z/5X2lx8V55dA X-Google-Smtp-Source: AGHT+IGadaCFnYA+An69A6pbxZM3M9oy0jJTnd29vOb+rS5wQz6V0NIHN3Y1/dmzXU9CB3cQpRGHYRwTXZNngP5O0AY= X-Received: by 2002:a05:6102:3f92:b0:491:36b0:33a4 with SMTP id ada2fe7eead31-4925c25d1dfmr1640246137.14.1721262419085; Wed, 17 Jul 2024 17:26:59 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: William Dudley Date: Wed, 17 Jul 2024 20:27:21 -0400 Message-ID: Subject: Re: add in SATA card -- ada0 "moves" to ad1, breaking the boot process ? Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000000e1006061d7aa302" X-Spamd-Bar: / X-Spamd-Result: default: False [-0.93 / 15.00]; MISSING_TO(2.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.935]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::933:from] X-Rspamd-Queue-Id: 4WPYXQ0gbhz52Hn --0000000000000e1006061d7aa302 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I was able to fix my boot problem by doing: boot single user, tunefs -L 60Gboot-SATA /dev/ada1s1a reboot single user again, mount -rw / fix /etc/fstab to use the label, reboot into multi-user However, now, the swap partition has disappeared: tunefs -p /dev/ada1s1b tunefs: /dev/ada1s1b: No such file or directory Of course, I can evidence it once existed: ls /dev/ada1* /dev/ada1 /dev/ada1s1 /dev/ada1s1a /dev/ada1s1b Where did it go, and is it possible to use it, or is it gone forever? (I know I can create a swap file on ada1s1a, so it's not the end of the world.) Thanks, Bill Dudley On Wed, Jul 17, 2024 at 6:02=E2=80=AFPM William Dudley = wrote: > Thanks > > tunefs -L foo it is, then. > > Bill Dudley > This email is free of malware because I run Linux. > > > On Wed, Jul 17, 2024 at 4:33=E2=80=AFPM Matthew Seaman > wrote: > >> On 17/07/2024 20:58, William Dudley wrote: >> > How do I prevent the drive names from changing? Or can't I? >> > >> >> One of the following? >> >> * glabel(8) for gpart(8) disk partitions >> >> * tunefs(8) can add a label to UFS2 filesytems >> >> In either case a disk device using the label will appear under /dev, and >> you can use that in fstab(5) >> >> You might already have labels on your drive partitions: the FreeBSD >> installer creates them by default. Try `gpart show -l` to see. >> >> Or just use ZFS -- it knows its own drives, no matter what device the OS >> wants to call them. There's a fun party trick to take out the drives >> containing a ZFS pool, shuffle them around, reinstall and boot up again. >> >> Cheers, >> >> Matthew >> >> --0000000000000e1006061d7aa302 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was able to fix my boot problem by doing:

boot single u= ser,
tunefs -L=C2=A060Gboot-SATA = /dev/ada1s1a
reboot singl= e user again,
mount -rw /
reboot into multi-user

However, now, the swap partition has dis= appeared:

tunefs -p /dev/ada1s1b
tunefs: /dev/ada1s1b: No such file or directory

Of course, I can evidence it once existed:

ls /dev/ada1* =C2=A0
/dev/ad= a1 =C2=A0 =C2=A0 =C2=A0 /dev/ada1s1 =C2=A0 =C2=A0 /dev/ada1s1a =C2=A0 =C2= =A0/dev/ada1s1b

Where did it go, and is it possible to us= e it, or is it gone forever?
(I know I can create a swap file on=C2=A0ada1= s1a, so it's not the end of the world.)

Thanks,
Bill Dudley



<= div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 17, 2024 at 6:02=E2=80=AFP= M William Dudley <wfdudley@gmail.c= om> wrote:
Thanks

tunefs -L foo it is, then.

Bill Dudley
This email is free of malware because I run Linux.<= /div>


On Wed, Jul 17, 2024 at 4:33=E2=80=AFPM Matthew Seaman= <matthew@freeb= sd.org> wrote:
On 17/07/2024 20:58, William Dudley wrote:
> How do I prevent the drive names from changing?=C2=A0 Or can't I?<= br> >

One of the following?

* glabel(8) for gpart(8) disk partitions

* tunefs(8) can add a label to UFS2 filesytems

In either case a disk device using the label will appear under /dev, and you can use that in fstab(5)

You might already have labels on your drive partitions: the FreeBSD
installer creates them by default.=C2=A0 Try `gpart show -l` to see.

Or just use ZFS -- it knows its own drives, no matter what device the OS wants to call them.=C2=A0 There's a fun party trick to take out the dri= ves
containing a ZFS pool, shuffle them around, reinstall and boot up again.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Cheers,

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Matthew

--0000000000000e1006061d7aa302--