Proxmox VE 6.2 and multipath

[WUP]

Hi,

I have updated the Proxmox VE server to version 6.2 and cannot start the multipath service.
The configuration on version 5.4 works without any problems. I have no more ideas.
I've got te error : failed to issue vpd inquiry for pgc9
Can anybody help?

I've 2 fiber channel controlers to HP disk array.

I attach the log file with output of the multipath -v3 command.

my configuration:

multipaths {
    multipath {
        wwid    3600c0ff000193f68f17cb85101000000
        alias    hp-hda
    }
    multipath {
        wwid    3600c0ff000193f681201135801000000
        alias    hp-hdc
    }
}
blacklist{
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|sda)[0-9]*"
        devnode "^hd[a-z][[0-9]*]"
        devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
    wwid "1ATA_WDC.*"
}
defaults {
    polling_interval     5
    path_selector        "round-robin 0"
    user_friendly_names    yes
}
devices {
    device {
        vendor "HP"
        product "P2000 G3 FC|P2000G3 FC/iSCSI|P2000 G3 SAS|P2000 G3 iSCSI"
        path_grouping_policy "group_by_prio"
        path_checker "tur"
        features "0"
        hardware_handler "0"
        prio "alua"
        failback "immediate"
        rr_weight "uniform"
        no_path_retry 18
        rr_min_io 100
    }
}

 

[menk]

in 6.x version of proxmox the multipath configuration is change.....
this is mine:

defaults {
find_multipaths no
polling_interval 2
path_selector "round-robin 0"
path_grouping_policy multibus
uid_attribute ID_SERIAL
rr_min_io 100
failback immediate
no_path_retry queue
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^(td|hd)[a-z]"
devnode "^dcssblk[0-9]*"
devnode "^cciss!c[0-9]d[0-9]*"
}
blacklist_exceptions {
wwid "36001405c261c626dd18dd4bacd85e9d3"
}
multipaths {
multipath {
wwid "36001405c261c626dd18dd4bacd85e9d3"
alias mpathe
}
}

for reference:
https://forum.proxmox.com/threads/m...e-is-not-created-proxmox-6.57272/#post-264048

 

[WUP]

Thanks for your help, but unfortunately your setup didn't change anything.
I decided to roll back to version 5.4 . Maybe the producer will fix this in some time.