Following the reboot of one VIO server (VIOS) in a redundant configuration, a client is showing
failed disk paths on some channels.
What is the most likely reason the disk paths have failed?

A.
MPIO drivers have not been installed on the client.

B.
VIOS Fibre Channel adapters have created a private loop as the attribute init_link has not been
set.

C.
vSCSI and disk attributes vscsi_err_recov, vscsi_path_to & hcheck_interval have not been
configured.

D.
Disk attributes on VIOS for the reserve policy on the disk is not set to no_reserve.

Explanation: