Solved upgraded 13.1 to 13.2 now no longer able to mount previously used ufs disks

Hi,
I followed FreeBSD 13,2-RELEASE Installation Instructions after which I upgraded packages.
I use a number of spinning disks between 1TiB and 4TiB which were created on OpenBSD with MBR partitions
and these all previously worked on 13.1.

None of these will now mount although an ext4 spinning disk from my wife's machine mounts?
Some examples of one of the ufs disks used in a USB caddie, connecting directly to the motherboard controller
does not alter the outcome:

Thank you in advance for your assistance to everyone on this Forum.

Code:
# freebsd-update fetch
# freebsd-update install
 none required
# freebsd-update upgrade -r 13.2-RELEASE
# freebsd-update install
# shutdown -r now
# pkg-static upgrade
# shutdown -r now
Code:
# lsblk da0
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
da0              0:154 2.7T MBR                                               - -
  <FREE>         -:-   512B -                                                 - -
  da0s4          0:193 2.0T BSD                                               - -
    <FREE>       -:-   2.0T -                                                 - -
  <FREE>         -:-   2.7M -

# camcontrol identify da0
pass3: <ST3000DM001-1CH166 CC26> ATA8-ACS SATA 3.x device
pass3: 400.000MB/s transfers

protocol              ATA8-ACS SATA 3.x
device model          ST3000DM001-1CH166
(removed remaining output)

# gpart show da0
=>        63  4294967232  da0  MBR  (2.7T)
          63           1       - free -  (512B)
          64  4294961621    4  !166  [active]  (2.0T)
  4294961685        5610       - free -  (2.7M)
Code:
# mount /dev/da0 /mnt
mount: /dev/da0: Invalid fstype: Invalid argument

tried
Code:
# mount /dev/da0s4 /mnt
mount: /dev/da0s4: Invalid fstype: Invalid argument
tried
Code:
# mount /dev/da0p4 /mnt
mount: /dev/da0p4: Invalid fstype: Invalid argument
However :
an ext4 disk from my wife's machine mounts with
mount -t ext2fs <device><mountpoint>
 
da0, da0s4 and da0p4 are all wrong. It's MBR and a bsdlabel(8), so it's probably da0s1a. Which is the first partition (a) on the first slice (s1) of da0. If the disk doesn't have a bsdlabel(8) in that slice (gpart(8) doesn't show anything) then it's da0s1.
 
Thank you SirDice
I tested a number of drives and posted the info for the last drive which was in a USB caddie.

I have now repeated those with an internal drive and am still puzzled, thank you for your patience.

Info for the problematic internally connected drive :


Code:
# gpart show ada1
=>        63  3907029105  ada1  MBR  (1.8T)
          63           1        - free -  (512B)
          64  3907024001     4  !166  [active]  (1.8T)
  3907024065        5103        - free -  (2.5M)

 # lsblk ada1
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
ada1             0:109 1.8T MBR                                               - -
  <FREE>         -:-   512B -                                                 - -
  ada1s4         0:143 1.8T BSD                                               - -
    <FREE>       -:-    17G -                                                 - -
    ada1s4d      0:147 4.0G freebsd-ufs                                       - -
    <FREE>       -:-    36G -                                                 - -
    ada1s4f      0:149 6.0G freebsd-ufs                                       - -
    ada1s4g      0:151 1.0G freebsd-ufs                                       - -
    ada1s4h      0:153  20G freebsd-ufs                                       - -
    ada1s4i      0:193 2.0G freebsd-ufs                                       - -
    ada1s4j      0:195 6.0G freebsd-ufs                                       - -
    ada1s4k      0:197 300G freebsd-ufs                                       - -
    <FREE>       -:-   1.4T -                                                 - -
  <FREE>         -:-   2.5M -   
=>        63  3907029105  ada1  MBR  (1.8T)
          63           1        - free -  (512B)
          64  3907024001     4  !166  [active]  (1.8T)
  3907024065        5103        - free -  (2.5M)

=>         0  3907024001  ada1s4  BSD  (1.8T)
           0    35923072          - free -  (17G)
    35923072     8388576       4  freebsd-ufs  (4.0G)
    44311648    74991712          - free -  (36G)
   119303360    12582912       6  freebsd-ufs  (6.0G)
   131886272     2097152       7  freebsd-ufs  (1.0G)
   133983424    41943040       8  freebsd-ufs  (20G)
   175926464     4194304       9  freebsd-ufs  (2.0G)
   180120768    12582912      10  freebsd-ufs  (6.0G)
   192703680   629145600      11  freebsd-ufs  (300G)
   821849280  3085174721          - free -  (1.4T)

=>        63  3907029105  diskid/DISK-WD-WCC4M3PXKR9J  MBR  (1.8T)
          63           1                               - free -  (512B)
          64  3907024001                            4  !166  [active]  (1.8T)
  3907024065        5103                               - free -  (2.5M)

=>         0  3907024001  diskid/DISK-WD-WCC4M3PXKR9Js4  BSD  (1.8T)
           0    35923072                                 - free -  (17G)
    35923072     8388576                              4  freebsd-ufs  (4.0G)
    44311648    74991712                                 - free -  (36G)
   119303360    12582912                              6  freebsd-ufs  (6.0G)
   131886272     2097152                              7  freebsd-ufs  (1.0G)
   133983424    41943040                              8  freebsd-ufs  (20G)
   175926464     4194304                              9  freebsd-ufs  (2.0G)
   180120768    12582912                             10  freebsd-ufs  (6.0G)
   192703680   629145600                             11  freebsd-ufs  (300G)
   821849280  3085174721                                 - free -  (1.4T)

tried :
# mount /dev/ada1s1 /mnt
mount: /dev/ada1s1: Invalid fstype: Invalid argument

tried :
# mount /dev/ada1s4 /mnt
mount: /dev/ada1s4: Invalid fstype: Invalid argument
 
they look to be
Code:
    ada1s4f      0:149 6.0G freebsd-ufs                                       - -
    ada1s4g      0:151 1.0G freebsd-ufs                                       - -
    ada1s4h      0:153  20G freebsd-ufs                                       - -
    ada1s4i      0:193 2.0G freebsd-ufs                                       - -
    ada1s4j      0:195 6.0G freebsd-ufs                                       - -
    ada1s4k      0:197 300G freebsd-ufs
and you're doing
mount /dev/ada1s4 /mnt
when should it not be
mount /dev/ada1s4g /mnt

that letter after the 4 ? where ada1s4 0:143 1.8T BSD is just the major slice (partition/device whatevr it is called) that is chopped up into smaller slices that you should be trying to mount?

ada1s4 0:143 1.8T BSD is the entire hdd and BSD is just telling you its a BSD partition table on hdd ada1s4.
 
Thank you, if I understand you correctly

# mount /dev/ada1s4g /mnt
mount: /dev/ada1s4g: Invalid fstype: Invalid argument

the largest partition is :
64 3907024001 4 !166 [active] (1.8T)
as this is
ada1 0:109 1.8T MBR

What am I not getting here ?
 
Thank you, if I understand you correctly

# mount /dev/ada1s4g /mnt
mount: /dev/ada1s4g: Invalid fstype: Invalid argument

the largest partition is :
64 3907024001 4 !166 [active] (1.8T)
as this is
ada1 0:109 1.8T MBR

What am I not getting here ?
this is telling you
Code:
 # lsblk ada1
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
ada1             0:109 1.8T MBR                                               - -
  <FREE>         -:-   512B -                                                 - -
  ada1s4         0:143 1.8T BSD                                               - -
    <FREE>       -:-    17G -                                                 - -
    ada1s4d      0:147 4.0G freebsd-ufs                                       - -
    <FREE>       -:-    36G -                                                 - -
    ada1s4f      0:149 6.0G freebsd-ufs

the actual hdd is ada1 with a MBR partition table, that you made a BSD over top of it, making it ada1s4 (for whatever reason) then your partitions / slices are the ones proceeding that entry.

as you're getting a "mount: /dev/ada1s4g: Invalid fstype: Invalid argument" try fsck and clean the partitions/slice then try it.

i found this too

mount -t ufs -r -o ufstype=ufs2
 
What's the output of freebsd-version -uk? Just to know because it lacks a freebsd-update install in your upgrade as you wrote it.
 
this is telling you
Code:
 # lsblk ada1
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
ada1             0:109 1.8T MBR                                               - -
  <FREE>         -:-   512B -                                                 - -
  ada1s4         0:143 1.8T BSD                                               - -
    <FREE>       -:-    17G -                                                 - -
    ada1s4d      0:147 4.0G freebsd-ufs                                       - -
    <FREE>       -:-    36G -                                                 - -
    ada1s4f      0:149 6.0G freebsd-ufs

the actual hdd is ada1 with a MBR partition table, that you made a BSD over top of it, making it ada1s4 (for whatever reason) then your partitions / slices are the ones proceeding that entry.

as you're getting a "mount: /dev/ada1s4g: Invalid fstype: Invalid argument" try fsck and clean the partitions/slice then try it.

i found this too

mount -t ufs -r -o ufstype=ufs2
Thank you userxbw this partition was created with OpenBSD and I will try your advice a little later this evening
 
Generally speaking: when / if possibly confused by gpart partition and/or slice numbers, use
gpart show -p [geom]

Using show -p, GPT partitions are shown as (e.g.) ada0p1 etc and MBR/bsdlabel slices as ada0s1 etc, and within slices as ada0s1{a,b,d,e,f,g...} so less scope for confusion.
 
Hi,

The problem ended with a boot drive failure, I need to purchase a drive tomorrow and rebuild.

Than you for your assistance.
 
Back
Top