Can not attach same disk to mirror - device too small

[zimon]

Hello,
I am running FreeNAS-9.10.2-U1 (86c7ef5) and

I have the following pool:

Code:

    NAME        STATE     READ WRITE CKSUM

    freenas-boot  ONLINE       0     0     0

      mirror-0  ONLINE       0     0     0

        da0p2   ONLINE       0     0     0

        da1p2   ONLINE       0     0     0

where da0p2 and da1p2 are both the same 16GB flash drive.

Now I want to attach the another (completely similar) 16GB flash drive to the pool via the WEBGUI.
When I try to is get the followin error:

Error: Failed to attach disk: cannot attach da2p2 to d0p2: device too small.

This is what the log shows:

Code:

Dec  4 12:22:45 theVault GEOM: da2: the primary GPT table is corrupt or invalid.
Dec  4 12:22:45 theVault GEOM: da2: using the secondary instead -- recovery strongly advised.
Dec  4 12:22:45 theVault notifier: 32+0 records in
Dec  4 12:22:45 theVault notifier: 32+0 records out
Dec  4 12:22:45 theVault notifier: 33554432 bytes transferred in 2.553235 secs (13141930 bytes/sec)
Dec  4 12:22:49 theVault notifier: dd: /dev/da2: short write on character device
Dec  4 12:22:49 theVault notifier: dd: /dev/da2: end of device
Dec  4 12:22:49 theVault notifier: 33+0 records in
Dec  4 12:22:49 theVault notifier: 32+1 records out
Dec  4 12:22:49 theVault notifier: 33595392 bytes transferred in 4.321919 secs (7773258 bytes/sec)
Dec  4 12:22:56 theVault ZFS: vdev state changed, pool_guid=15607185754263842137 vdev_guid=16657468669737480713
Dec  4 12:22:58 theVault manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to attach disk: cannot attach da2p2 to da0p2: device is too small
]
Dec  4 12:22:59 theVault manage.py: [rollbar:1265] Got unexpected status code from Rollbar api: 403
Response:
{
  "err": 1,
  "message": "access token not found: caf06383cba14d5893c4f4d0a40c33a9"
}
Dec  4 12:22:59 theVault manage.py: [rollbar:1097] Exception while posting item ApiError(u'access token not found: caf06383cba14d5893c4f4d0a40c33a9',)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1095, in _send_payload
    _post_api('item/', payload, access_token=access_token)
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1138, in _post_api
    return _parse_response(path, SETTINGS['access_token'], payload, resp)
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1274, in _parse_response
    raise ApiError(json_data.get('message') or 'Unknown error')
ApiError: access token not found: caf06383cba14d5893c4f4d0a40c33a9

What is the problem? And how can I solve it?

 

[dlavigne]

Completely similar may not be the same. Refer to the note in https://www.ixsystems.com/documentation/freenas/11/system.html#mirroring-the-boot-device .

 

[zimon]

where da0p2 and da1p2 are both the same 16GB flash drive.

As I mentioned the usb flash drives are all the exact same model. To be precise they are all Intenso Micro Line 16GB.

 

[danb35]

As I mentioned the usb flash drives are all the exact same model.

The text you quoted doesn't say this; it only says that da0 and da1 are "the same 16GB flash drive". But even now that you've clarified that, that doesn't show that they're necessarily the same capacity--USB sticks are notorious for varying in capacity. What's the output of diskinfo -v da0, diskinfo -v da1, and diskinfo -v da2?

 

[zimon]

Well the size is not identical:

Code:

diskinfo -v da1

da1

    512             # sectorsize

    16219373568     # mediasize in bytes (15G)

    31678464        # mediasize in sectors

    0               # stripesize

    0               # stripeoffset

    1971            # Cylinders according to firmware.

    255             # Heads according to firmware.

    63              # Sectors according to firmware.

    16060008004567    # Disk ident.



diskinfo -v da2

da2

    512             # sectorsize

    15640600576     # mediasize in bytes (15G)

    30548048        # mediasize in sectors

    0               # stripesize

    0               # stripeoffset

    1901            # Cylinders according to firmware.

    255             # Heads according to firmware.

    63              # Sectors according to firmware.

    4904000000002997    # Disk ident.

But the difference is minmal. Is that the reason?

 

[danb35]

Is that the reason?

Yes, it is.