1

I have two identical 1TB external USB-disks which I have formatted under Linux using ext2fs. If I run lsusb in Linux I get the lines:

Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. 
Bus 004 Device 003: ID 174c:55aa ASMedia Technology Inc. 

Both drives have one partition taking up the whole disk. When I boot into FreeBSD, the two drives are reported as /dev/da0 and /dev/da1, with partitions /dev/da0s1 and /dev/da1s1. I can mount /dev/da0s1 without a problem with:

mount -t ext2fs /dev/da0s1 <path>

but when I want to mount the second drive with

mount -t ext2fs /dev/da1s1 <path>

I get the message

mount: /dev/da1s1: Invalid argument

I do not know if it can help, here is the output of gpart list for the two disks:

Geom name: da0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 1953525167
first: 63
entries: 4
scheme: MBR
Providers:
1. Name: da0s1
   Mediasize: 1000201224704 (932G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   rawtype: 131
   length: 1000201224704
   offset: 1048576
   type: linux-data
   index: 1
   end: 1953520064
   start: 2048
Consumers:
1. Name: da0
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e2

and

Geom name: da1
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 244190645
first: 63
entries: 4
scheme: MBR
Providers:
1. Name: da1s1
   Mediasize: 1000193654784 (932G)
   Sectorsize: 4096
   Stripesize: 0
   Stripeoffset: 262144
   Mode: r0w0e0
   attrib: active
   rawtype: 131
   length: 1000193654784
   offset: 262144
   type: linux-data
   index: 1
   end: 244187967
   start: 64
Consumers:
1. Name: da1
   Mediasize: 1000204886016 (932G)
   Sectorsize: 4096
   Mode: r0w0e0

EDIT

I tried removing the good disk and rebooting. Now the bad disk is detected as /dev/da0. Here is the output of dmesg:

da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <Intenso USB 3.0 device 0> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 30100000000000000263
da0: 400.000MB/s transfers
da0: 953869MB (244190646 4096 byte sectors)
da0: quirks=0x2<NO_6_BYTE>

and mounting it fails:

# mount -t ext2fs /dev/da0s1 mnt0
mount: /dev/da0s1: Invalid argument

With two disks, the output of dmesg is:

da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <Intenso USB 3.0 Device 0> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 30700000000000001682
da0: 400.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
...
da1 at umass-sim1 bus 1 scbus7 target 0 lun 0
da1: <Intenso USB 3.0 device 0> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 30100000000000000263
da1: 400.000MB/s transfers
da1: 953869MB (244190646 4096 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
...

The bad disk uses 4096-byte sectors while the good one uses 512-byte sectors. Can the sector size be the problem?

NOTE

I have not been able to solve this problem. I finally decided to format both disks with UFS, attach them to a FreeBSD Raspberrypi, and make them available to other computers via the network.

  • Did you try use only the "bad" disk? In this case it will be /dev/da0. Did you see output of dmesg? – uzsolt Nov 9 '16 at 7:55
  • What does the Mode: r0w0e0 mean in the gpart geom output? My guess is read off, write off. So that's maybe your problem. – wurtel Nov 9 '16 at 10:09
  • @wurtel: You mean read and write are disabled? I cannot find any complete documentation on the output of gpart geom so I do not know how to interpret the Mode field. – Giorgio Nov 9 '16 at 11:01
  • Yes, sector size in conjunction with (bad) partition alignment can be the problem. – dirkt Nov 9 '16 at 11:08
  • @dirkt: However, it works without any problems under Linux. In any case, should I repartition the disk? Is it possible to change the sector size using a partitioning tool? – Giorgio Nov 9 '16 at 11:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.