i have installed an Ubuntu Server from the installation ISO.
i then installed multipath support (multipath-tools and multipath-tools-boot).
i added an FCP device, format it, mount it and added to the fstab using it's /dev/mapper representation. everything worked fine...
i then reboot the server and it failed to start due to the missing /dev/mapper device that needs to be mounted (as the fstab states).
i get into maintenance mode.
i am not using cio_ignore and the devices are available in maintenance mode.
running multipath -ll will fail to show the device (as expected... that is why the boot failed).
running multipat without any parameters (to rescan) will find the devices and it will now show on multipath -ll.
i was able to get around this by rebuilding the initrd and running zipl... but that should not be the case. multipath should scan during reboot to find all the devices available.
i am attaching both an sosreport and dbginfo for you to review.
i hope this is something i am doing wrong but i don't think so...
either way i would love to get a quick workaround that will avoid this issue without rebuilding the initrd.
== Comment: #4 - Hendrik Brueckner <email address hidden> - 2016-06-06 06:44:53 ==
Hi Ofer,
(In reply to comment #0)
> i have installed an Ubuntu Server from the installation ISO.
> i then installed multipath support (multipath-tools and
> multipath-tools-boot).
> i added an FCP device, format it, mount it and added to the fstab using it's
that is after i vary the device online.
as i said the device comes online just fine... i can see all the /dev/sd* devices.
i am just missing the multipath device.
== Comment: #6 - Ofer Baruch <email address hidden> - 2016-06-06 07:11:09 ==
the missing file is:
/dev/mapper/3600507630bffc0470000000000002333
== Comment: #0 - Ofer Baruch <email address hidden> - 2016-06-06 06:37:19 ==
Hi,
i have installed an Ubuntu Server from the installation ISO. tools-boot) .
i then installed multipath support (multipath-tools and multipath-
i added an FCP device, format it, mount it and added to the fstab using it's /dev/mapper representation. everything worked fine...
i then reboot the server and it failed to start due to the missing /dev/mapper device that needs to be mounted (as the fstab states).
i get into maintenance mode.
i am not using cio_ignore and the devices are available in maintenance mode.
running multipath -ll will fail to show the device (as expected... that is why the boot failed).
running multipat without any parameters (to rescan) will find the devices and it will now show on multipath -ll.
i was able to get around this by rebuilding the initrd and running zipl... but that should not be the case. multipath should scan during reboot to find all the devices available.
i am attaching both an sosreport and dbginfo for you to review.
i hope this is something i am doing wrong but i don't think so...
either way i would love to get a quick workaround that will avoid this issue without rebuilding the initrd.
== Comment: #4 - Hendrik Brueckner <email address hidden> - 2016-06-06 06:44:53 ==
Hi Ofer,
(In reply to comment #0) tools-boot) .
> i have installed an Ubuntu Server from the installation ISO.
> i then installed multipath support (multipath-tools and
> multipath-
> i added an FCP device, format it, mount it and added to the fstab using it's
How did you add the FCP device?
== Comment: #5 - Ofer Baruch <email address hidden> - 2016-06-06 07:07:42 ==
using:
chzdev zfcp-host <fcp_vdev> -e -p
that is after i vary the device online.
as i said the device comes online just fine... i can see all the /dev/sd* devices.
i am just missing the multipath device.
== Comment: #6 - Ofer Baruch <email address hidden> - 2016-06-06 07:11:09 == 3600507630bffc0 470000000000002 333
the missing file is:
/dev/mapper/