MatthewSteinhoff
Guru
- Joined
- Feb 2, 2016
- Messages
- 574
TL;DR: When trying to replace a multipath disk under FreeNAS-9.10.2-U5 I get the message...
Unable to GPT format the disk "multipath/disk14"
Now what?
Long story...
I've been seeing this error grouping in my logs for a few weeks...
Drive
Selecting
Unable to GPT format the disk "multipath/disk14"
Here is the full log dump...
The drives and partitions do exist...
Unable to GPT format the disk "multipath/disk14"
Now what?
Long story...
I've been seeing this error grouping in my logs for a few weeks...
Code:
(da24:mps0:0:77:0): READ(10). CDB: 28 00 16 9d 6a 30 00 00 a0 00 (da24:mps0:0:77:0): CAM status: SCSI Status Error (da24:mps0:0:77:0): SCSI status: Check Condition (da24:mps0:0:77:0): SCSI sense: RECOVERED ERROR asc:17,6 (Recovered data without ECC - data auto-reallocated) (da24:mps0:0:77:0): Info: 0x169d6a49 (da24:mps0:0:77:0): Actual Retry Count: 12
Drive
da24
is also known as da8
which is multipath/disk18
. The drive multipath/disk18
is one of the seven drives that make up the RAIDZ2 volume group V-Live600
.Selecting
multipath/disk18
and clicking 'Replace' allows me to choose multipath/disk14
as the replacement. When I click 'Replace Disk', I get this message...Unable to GPT format the disk "multipath/disk14"
Here is the full log dump...
Code:
Jul 11 09:54:15 bulk GEOM_ELI: Device multipath/disk18p1.eli destroyed. Jul 11 09:54:15 bulk GEOM_ELI: Detached multipath/disk18p1.eli on last close. Jul 11 09:54:15 bulk notifier: geli: No such device: /dev/multipath/disk18p1. Jul 11 09:54:15 bulk notifier: dd: /dev/multipath/disk14: Invalid argument Jul 11 09:54:15 bulk notifier: 1+0 records in Jul 11 09:54:15 bulk notifier: 0+0 records out Jul 11 09:54:15 bulk notifier: 0 bytes transferred in 0.001323 secs (0 bytes/sec) Jul 11 09:54:15 bulk notifier: dd: /dev/multipath/disk14: Invalid argument Jul 11 09:54:15 bulk notifier: 1+0 records in Jul 11 09:54:15 bulk notifier: 0+0 records out Jul 11 09:54:15 bulk notifier: 0 bytes transferred in 0.001190 secs (0 bytes/sec) Jul 11 09:54:16 bulk manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to GPT format the disk "multipath/disk14"] Jul 11 09:54:16 bulk manage.py: [rollbar:1265] Got unexpected status code from Rollbar api: 403 Response: { "err": 1, "message": "project is not enabled" } Jul 11 09:54:16 bulk manage.py: [rollbar:1097] Exception while posting item ApiError(u'project is not enabled',) 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: project is not enabled
The drives and partitions do exist...
Code:
# ls -l /dev/multipath/disk18*
crw-r----- 1 root operator 0x1f6 Jun 19 09:46 /dev/multipath/disk18
crw-r----- 1 root operator 0x222 Jun 19 09:46 /dev/multipath/disk18p1
crw-r----- 1 root operator 0x224 Jun 19 09:46 /dev/multipath/disk18p2
# ls -l /dev/multipath/disk14*
crw-r----- 1 root operator 0x164 Jun 19 09:46 /dev/multipath/disk14[/CMD]
I see the GEOM being created at boot...
GEOM_MULTIPATH: disk14 created
GEOM_MULTIPATH: da34 added to disk14
GEOM_MULTIPATH: da34 is now active path in disk14
GEOM_MULTIPATH: da35 added to disk14
I seem to remember something about having to fully wipe the GPT headers and some scary sysctl tweaks but, before I try a procedures years old and a version or two behind, I thought it best to ask for advice.
Suggestions?
Cheers,
Matt
Last edited by a moderator: