Re: New Optane AIC does not show up in FreeBSD until . . . ?
On Tue, Feb 16, 2021 at 1:48 AM Harry Schmalzbauer wrote: > Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: > > On 2021-Feb-13, at 16:40, Warner Losh 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). > > 'geom disk status' is my first choice for such a case. > Even nvd(4) should show up I think, nda(4) just changes the access path, > not geom(8) integration, afaik. > nvd and nda are mutually exclusive block device interfaces to the nvme driver. As far as geom is concerned, they are no different than da, ada or any of the other block device drivers we have that use the geom interface. sysctl kern.disks is a briefer version of that. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote: > Am 16.02.2021 um 11:08 schrieb Mark Millard: >> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: >>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh 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). >>> >>> 'geom disk status' is my first choice for such a case. >>> Even nvd(4) should show up I think, nda(4) just changes the access path, >>> not geom(8) integration, afaik. > > ... >> Thanks for the alternatives to sysctl kern.disks >> and to nvmecontrol devlist for making a list to >> compare to gpart show output in order to find >> what gpart show does not list (but can manipulate). > > gpart(8) doesn't enumerate disks without any supported partition scheme > present. > You can create new partition schemes with the help of gpart(8), but it's imho > correct not to show them, because 'gpart show' is meant to give information > about (existing) partition schemes - no scheme no info; thus your vanilla > disk is "unknown" to gpart(8). > > I remember that I always thought the geom(8) disk class is kind of hidden - > especially since the man page misses listing DISK in the > "Currently available classes which are aware of geom(8)" section! > > The "show" command was enriched to contain valuable details, such as NAA. > So 'geom disk' turned into one of the most useful mass storage admin > commands. imho. > Maybe somebody should correct the aforementioned man page section and add add > any hint in the SEE ALSO section, because there is no gdisk(8) aequivalent, > like for all other geom classes... > > -harry > > P.S. Put it on my loger-term todo to file a bug report with a proposed man > page diff... Looks like "geom -t" output avoids me having to compare two outputs to find mismatches in the list of names: its output is sufficient to identify the name(s) for drives that do not have the scheme information (and the names of those that do). This at least helps cut down what I have to coordinate, especially when only one device is in question. For example, ada2 in the below has only DISK and one DEV line, not multiple DEV's, no PART line, nor other such: . . . ada0 DISK ada0 ada0 PART ada0s1 ada0s1 DEV ada0 PART ada0s2 ada0s2 DEV ada0 DEV ada1 DISK ada1 ada1 PART ada1p1 ada1p1 DEV ada1 DEV ada2 DISK ada2 ada2 DEV da0DISK da0 da0 PART da0p1 da0p1 DEV da0 PART da0p2 da0p2 LABEL ntfs/VirtMachs ntfs/VirtMachs DEV da0p2 DEV da0 DEV . . . So I can infer that I need a gpart create on ada2 . (Presumes I know from the naming that the device is not analogous to a cd-drive with no media in the drive.) The output does span the nvd* devices. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Am 16.02.2021 um 11:08 schrieb Mark Millard: On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh 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). 'geom disk status' is my first choice for such a case. Even nvd(4) should show up I think, nda(4) just changes the access path, not geom(8) integration, afaik. ... Thanks for the alternatives to sysctl kern.disks and to nvmecontrol devlist for making a list to compare to gpart show output in order to find what gpart show does not list (but can manipulate). gpart(8) doesn't enumerate disks without any supported partition scheme present. You can create new partition schemes with the help of gpart(8), but it's imho correct not to show them, because 'gpart show' is meant to give information about (existing) partition schemes - no scheme no info; thus your vanilla disk is "unknown" to gpart(8). I remember that I always thought the geom(8) disk class is kind of hidden - especially since the man page misses listing DISK in the "Currently available classes which are aware of geom(8)" section! The "show" command was enriched to contain valuable details, such as NAA. So 'geom disk' turned into one of the most useful mass storage admin commands. imho. Maybe somebody should correct the aforementioned man page section and add add any hint in the SEE ALSO section, because there is no gdisk(8) aequivalent, like for all other geom classes... -harry P.S. Put it on my loger-term todo to file a bug report with a proposed man page diff... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: > Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: >> On 2021-Feb-13, at 16:40, Warner Losh 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). > > 'geom disk status' is my first choice for such a case. > Even nvd(4) should show up I think, nda(4) just changes the access path, not > geom(8) integration, afaik. Looks like "geom disk status" and "geom disk list" both list "disks" that do not have a partition scheme and spans the nvd* disks. (I only tested destroying a partition scheme on an ada* and then seeing what was displayed. I do not want to destroy such on any nvd* as stands.) "geom disk list" shows Mediasize and descr, which at times could be handy for identification, at least when the pair are unique in the system. Thanks for the alternatives to sysctl kern.disks and to nvmecontrol devlist for making a list to compare to gpart show output in order to find what gpart show does not list (but can manipulate). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh 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). 'geom disk status' is my first choice for such a case. Even nvd(4) should show up I think, nda(4) just changes the access path, not geom(8) integration, afaik. -harry ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-13, at 17:38, Warner Losh wrote: > On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote: > > On 2021-Feb-13, at 16:40, Warner Losh 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 > Turns out that sysctl kern.disks would not have directly helped on its own because the drive was replacing another: the set of names listed would be unchanged: # sysctl kern.disks kern.disks: da6 da5 cd0 da4 da3 da2 da1 da0 ada2 ada1 ada0 nvd5 nvd4 nvd3 nvd2 nvd1 nvd0 (I'd know it was one of the nvd*'s.) So for sysctl kern.disks use I'd need to look for a name (a nvd*) that gpart show had not listed and that would be the new one. So: use both commands. Good to know. nmvecontrol devlist does get into nvmeN/nvmeNns1 vs. the nvdN names listed in gpart show, and so for more complicated name matching. But, again, involves finding an unmatched name. In the actual context, the type and size happened to be unique and that would have made identification easy from nmvecontrol devlist output. Thanks for the notes, Mark > > >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current > >> 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 + > >> 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 144 144 > >> > >> 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) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote: > > On 2021-Feb-13, at 16:40, Warner Losh 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 + > >> 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 144 144 > >> > >> 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) > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-13, at 16:40, Warner Losh 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. Mark >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current >> 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 + >> 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 144 144 >> >> 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) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Are you aware of gpart create? Warner 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 + > 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 144 144 > > 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) > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
New Optane AIC does not show up in FreeBSD until . . . ?
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 + 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 144 144 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) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
