[HELP] umass device no longer recognised after recent upgrade

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[HELP] umass device no longer recognised after recent upgrade

Axel Rau
After installing the recent update to 12.1-RELEASE-p6 via freebsd-update, our USB backup device is no longer recognized. This USB 3.x device (Seagate serial NA9QFX4L) was never recognized by FreeBSD.
To get it to work, we used the integrated hub of another seagate disk (serial NA7DQ4JJ) which worked until now.

usbconfig output:
t# usbconfig
ugen0.1: <Intel EHCI root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.2: <vendor 0x8087 product 0x07db> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.3: <vendor 0x0000 product 0x0001> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
ugen0.4: <vendor 0x0557 product 0x2419> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (160mA)


Part of dmesg before update:
- - -
Root mount waiting for: usbus1 usbus0
uhub1: 8 ports with 8 removable, self powered
ugen0.2: <VIA Labs, Inc. USB3.0 Hub> at usbus0
uhub2 on uhub1
uhub2: <VIA Labs, Inc. USB3.0 Hub, class 9/0, rev 3.00/91.01, addr 1> on usbus0
Root mount waiting for: usbus1 usbus0
uhub2: 4 ports with 4 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen0.3: <Seagate Backup+ Hub> at usbus0
uhub3 on uhub2
uhub3: <Seagate> on usbus0
Root mount waiting for: usbus1 usbus0
uhub3: 3 ports with 3 removable, self powered
uhub0: 8 ports with 8 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen1.2: <vendor 0x8087 product 0x07db> at usbus1
uhub4 on uhub0
uhub4: <vendor 0x8087 product 0x07db, class 9/0, rev 2.00/0.02, addr 2> on usbus1
uhub4: 4 ports with 4 removable, self powered
ugen0.4: <Seagate Backup+ Hub BK> at usbus0
umass0 on uhub3
umass0: <Seagate Backup+ Hub BK, class 0/0, rev 3.10/1.00, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x0100
umass0:6:0: Attached to scbus6
da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <Seagate Backup+ Hub BK D781> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number NA9QFX4L
da0: 400.000MB/s transfers
da0: 7630885MB (15628053167 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
GEOM: da0: the primary GPT table is corrupt or invalid.
GEOM: da0: using the secondary instead -- recovery strongly advised.
ugen1.3: <vendor 0x0000 product 0x0001> at usbus1
uhub5 on uhub4
uhub5: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus1
Root mount waiting for: usbus1 usbus0
uhub5: 4 ports with 3 removable, self powered
ugen1.4: <vendor 0x0557 product 0x2419> at usbus1
ukbd0 on uhub5
ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus1
kbd1 at ukbd0
ugen0.5: <Seagate Backup+  Desk> at usbus0
umass1 on uhub3
umass1: <Seagate Backup+  Desk, class 0/0, rev 3.00/5.11, addr 4> on usbus0
umass1:  SCSI over Bulk-Only; quirks = 0x8100
umass1:7:1: Attached to scbus7
da1 at umass-sim1 bus 1 scbus7 target 0 lun 0
da1: <Seagate Backup+  Desk 0511> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number NA7DQ4JJ
da1: 400.000MB/s transfers
da1: 3815447MB (7814037167 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
Root mount waiting for: usbus0
ugen0.6: <VIA Labs, Inc. USB2.0 Hub> at usbus0
uhub6 on uhub1
uhub6: <VIA Labs, Inc. USB2.0 Hub, class 9/0, rev 2.10/91.00, addr 5> on usbus0
Root mount waiting for: usbus0
uhub6: 4 ports with 4 removable, self powered
ugen0.7: <Seagate Backup+ Hub> at usbus0
uhub7 on uhub6
uhub7: <Seagate Backup+ Hub, class 9/0, rev 2.10/48.85, addr 6> on usbus0
uhub7: MTT enabled
Root mount waiting for: usbus0

- - -
after update:
- - -
Root mount waiting for: usbus0
ugen0.2: <vendor 0x8087 product 0x07db> at usbus0
uhub1 on uhub0
uhub1: <vendor 0x8087 product 0x07db, class 9/0, rev 2.00/0.02, addr 2> on usbus0
uhub1: 4 ports with 4 removable, self powered
ugen0.3: <vendor 0x0000 product 0x0001> at usbus0
uhub2 on uhub1
uhub2: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus0
Root mount waiting for: usbus0
uhub2: 4 ports with 3 removable, self powered
ugen0.4: <vendor 0x0557 product 0x2419> at usbus0
ukbd0 on uhub2
ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
kbd1 at ukbd0
lo0: link state changed to UP
igb0: link state changed to UP
ums0 on uhub2
ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
ums0: 3 buttons and [Z] coordinates ID=0
- - -

Any help appreciated.
Axel
---
PGP-Key: CDE74120  ☀  computing @ chaos claudius


signature.asc (919 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [RESOLVED] umass device no longer recognised after recent upgrade

Axel Rau
After playing with Bios (re-enabling mass storage via USB) connecting directly via one hub and consolidating (flaky) power outlet resolved the issue.
zfs list displayed upall sets. (-:

Axel

> Am 14.06.2020 um 13:15 schrieb Axel Rau <[hidden email]>:
>
> After installing the recent update to 12.1-RELEASE-p6 via freebsd-update, our USB backup device is no longer recognized. This USB 3.x device (Seagate serial NA9QFX4L) was never recognized by FreeBSD.
> To get it to work, we used the integrated hub of another seagate disk (serial NA7DQ4JJ) which worked until now.
>


signature.asc (919 bytes) Download Attachment