Date: Sat, 13 Feb 2021 18:38:11 -0700 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: New Optane AIC does not show up in FreeBSD until . . . ? Message-ID: <CANCZdfrSZ%2BFpS%2B-U7owQPN66C8fkN4SaEo9E1AA7A20_DhXF2Q@mail.gmail.com> In-Reply-To: <85821016-60AA-4E9C-94DB-9FAD1E718182@yahoo.com> References: <9FAFDEE8-97DA-4FF7-AADB-4BFC14F07E13.ref@yahoo.com> <9FAFDEE8-97DA-4FF7-AADB-4BFC14F07E13@yahoo.com> <CANCZdfqOptgzp_kqxEVY67GsM%2B7tpeZcNt-O--CLFFyNz0_eyw@mail.gmail.com> <85821016-60AA-4E9C-94DB-9FAD1E718182@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 13, 2021, 6:36 PM Mark Millard <marklmi@yahoo.com> wrote: > > On 2021-Feb-13, at 16:40, Warner Losh <imp at bsdimp.com> wrote: > > > Are you aware of gpart create? > > > > Warner > > From which I derive that I had an implicit, incorrect > assumption that gpart show would in some way list > everything available that gpart could manipulate > (including for use in creation). > > So I need to find such a drive another way, something > I was not even trying to do. > > That answers my question. Thanks. > Nvmecontrol devlist is a good place to start. Or sysctl kern.disks Mark > > > >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current < > freebsd-current@freebsd.org> wrote: > >> I plugged in a new Optane and booted FreeBSD on the > >> ThreadRipper 1950X system but FreeBSD did not show > >> the drive in gpart show. (It is unique by size in the > >> context and so would be hard to miss for anything > >> that listed sizes. Lack of listing a size would also > >> stand out.) > >> > >> So I did what I've done in the past: shutdown FreeBSD, > >> boot Windows 10, go to its disk management utility, > >> answer its prompt for MBR vs. GPT for the new device > >> (picking GPT), shutdown Windows 10. Then boot FreeBSD > >> again --and the new drive shows up. > >> > >> Is there a way to avoid the round trip through > >> Windows 10 (or any other such round trip going > >> outside FreeBSD)? I'm just curious if I've missed > >> something: My work around enables my activity. > >> > >> > >> FYI, FreeBSD based on main 3acea07c1873 : > >> > >> # ~/fbsd-based-on-what-freebsd-main.sh > >> merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b > >> merge-base: CommitDate: 2021-02-08 19:15:21 +0000 > >> c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in > git context. > >> 3acea07c1873 (pure-src) Restore the augmented strlen commentary > >> FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT > mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 1400004 1400004 > >> > >> But this is not a new thing, more of a "still true" > >> thing. > > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrSZ%2BFpS%2B-U7owQPN66C8fkN4SaEo9E1AA7A20_DhXF2Q>