make_dev_physpath_alias: WARNING ....

Status
Not open for further replies.
D

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
Here's my setup:

FreeNas 9.1.1​
Dell 440SC 2gb​
with lsi hba card -> 16 drive enclosure XJ-SA16-316R-B (only supports upto 1tb I believe)​

I am getting this message when I put in my new HD (1TB 3.5 SATA6 Seagate):

"make_dev_physpath_alias: WARNING - Unable to alias pass2 to enc@n50015b2180000a60/type@0/slot@1/elmdesc@Disk_0______________________/pass2 - path too long"​
​
zpool status gives me crazy long names for the disks, I assume because it can't properly alias the disks.
Here's the zpool status output from one pool:
***************​
pool: corpdata​
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
corpdata ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gptid/92a070e2-171e-11e3-9a70-002219074adf ONLINE 0 0 0
gptid/94e0aa03-171e-11e3-9a70-002219074adf ONLINE 0 0 0
errors: No known data errors​
***************​
​
​
I've attached the full output from dmesg and zpool status.

Is this something that I need to worry about?

Thanks-

dce
 

Attachments

  • 20130909_freenas_dmesg.txt
    22.6 KB · Views: 263
  • zpool_status.txt
    1.2 KB · Views: 251
D

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
No I haven't. Any suggestions? I have a HP DL380 G6 that I was going to move the LSI card to and try it there, but I haven't done that yet. I suspect I'll get the same thing.

Thanks for responding and any thoughts?

dce
 
wtfuar

wtfuar

Dabbler
Joined
Jun 25, 2013
Messages
36
Same problem here after upgrading 8.3 to 9.1.1

Code:
Sep 23 18:02:37 freenas manage.py: [storage.forms:2065]
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/65977639-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/65977639-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@5/elmdesc@Disk_#4_/gptid/65977639-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/66bc5d54-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/622428ec-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/622428ec-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@2/elmdesc@Disk_#1_/gptid/622428ec-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@3/elmdesc@Disk_#2_/gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/64712091-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/64712091-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@4/elmdesc@Disk_#3_/gptid/64712091-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli to enc@n5001e6714955800b/type@0/slot@1/elmdesc@Disk_#0_/gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli - path too long


Code:
zpool status
  pool: zfs
state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support feature
        flags.
  scan: resilvered 1.25T in 12h32m with 0 errors on Sat Aug 24 07:37:39 2013
config:
 
        NAME                                                STATE    READ WRITE CKSUM
        zfs                                                ONLINE      0    0    0
          raidz1-0                                          ONLINE      0    0    0
            gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli  ONLINE      0    0    0
            gptid/622428ec-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/64712091-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/65977639-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/66bc5d54-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
 
errors: No known data errors
 
D

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
Was your pool encrypted? I do not believe that mine was and didn't know why the Encryption stuff would be showing up.





wtfuar said:
Same problem here after upgrading 8.3 to 9.1.1

Code:
Sep 23 18:02:37 freenas manage.py: [storage.forms:2065]
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/65977639-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/65977639-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@5/elmdesc@Disk_#4_/gptid/65977639-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/66bc5d54-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/622428ec-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/622428ec-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@2/elmdesc@Disk_#1_/gptid/622428ec-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@3/elmdesc@Disk_#2_/gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/64712091-9d54-11e2-9312-000c29cec408.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/64712091-9d54-11e2-9312-000c29cec408.eli to enc@n5001e6714955800b/type@0/slot@4/elmdesc@Disk_#3_/gptid/64712091-9d54-11e2-9312-000c29cec408.eli - path too long
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Device gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli created.
Sep 23 18:02:37 freenas kernel: GEOM_ELI: Encryption: AES-XTS 128
Sep 23 18:02:37 freenas kernel: GEOM_ELI:    Crypto: hardware
Sep 23 18:02:37 freenas kernel: make_dev_physpath_alias: WARNING - Unable to alias gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli to enc@n5001e6714955800b/type@0/slot@1/elmdesc@Disk_#0_/gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli - path too long


Code:
zpool status
  pool: zfs
state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support feature
        flags.
  scan: resilvered 1.25T in 12h32m with 0 errors on Sat Aug 24 07:37:39 2013
config:
 
        NAME                                                STATE    READ WRITE CKSUM
        zfs                                                ONLINE      0    0    0
          raidz1-0                                          ONLINE      0    0    0
            gptid/27c029db-0c16-11e3-b6f5-002215ab012f.eli  ONLINE      0    0    0
            gptid/622428ec-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/634a7ede-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/64712091-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/65977639-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
            gptid/66bc5d54-9d54-11e2-9312-000c29cec408.eli  ONLINE      0    0    0
 
errors: No known data errors
Click to expand...
 
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
I have the same problem on my encrypted pool. Note that my unencrypted pool that is attached to the same physical SAS expander and M1015 doesn't have problems on bootup. I attached my messages to the ticket https://bugs.freenas.org/issues/3183 a few hours ago.

Just waiting for a response from a developer now. But it doesn't appear that anything is wrong, but I'm not sure what the aliases are for, so I could be wrong.
 
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
You just responded to a thread from 6 months ago. :)
 
Status
Not open for further replies.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "make_dev_physpath_alias: WARNING ...."

Similar threads

D
  • Locked
Memory leak?
Replies
3
Views
2K
mpfusion
M
Z
  • Locked
Error report more than two weeks late; alert indicator still green
Replies
8
Views
3K
Z300M
Z
N
  • Locked
volume manager throws error.
Replies
6
Views
2K
Ericloewe
Ericloewe
G
  • Locked
update to 201502271818 fail
Replies
4
Views
2K
giovannife
G
T
  • Locked
8.3.0 rc1 minor gui bug in volume status?
Replies
9
Views
4K
bernardc
bernardc
Top