[Bug 270904] Same Block Device over SATA and USB gpart(8) Broken

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 17 Apr 2023 21:59:16 UTC

            Bug ID: 270904
           Summary: Same Block Device over SATA and USB gpart(8) Broken
           Product: Base System
           Version: 13.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: vermaden@interia.pl


While we have new and shiny FreeBSD 13.2-RELEASE it still has the same issue of
treating THE SAME block device differently depending if its attached via SATA
or mSATA slot and by USB adapter.

  # dmesg | tail
  (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00
  (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
  (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
  (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid
command operation code)
  (probe0:umass-sim0:0:0:0): Error 22, Unretryable error
  da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
  da0: <Generic External 0110> Fixed Direct Access SPC-4 SCSI device
  da0: Serial Number 533333474E58304A323032383735572020202020
  da0: 40.000MB/s transfers
  da0: 238475MB (488397167 512 byte sectors)
  da0: quirks=0x2<NO_6_BYTE>
  GEOM: da0: corrupt or invalid GPT detected.
  GEOM: da0: GPT rejected -- may not be recoverable.

  # gpart show da0
  gpart: No such geom: da0.

This particular example is mSATA SSD attached via mSATA USB adapter to USB 2.0
(and same results in USB 3.0/3.1 port).

There is whole FreeBSD 13.1-RELEASE-p* installation on it ... and I (and many
other people) able to get to its contents because of this bug.

Please fix this at least for 14.0-RELEASE.

Its REALLY EASY to replicate this problem.



You are receiving this mail because:
You are the assignee for the bug.