mageia3 iscsi targets not connected at boot time

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

mageia3 iscsi targets not connected at boot time

Postby pfaff » Oct 11th, '13, 22:26

On my mageia3 systems, iSCSI targets connections are not established at boot time.

Once the system is up I can establish these connections manually with the command:

iscsiadm -m node --loginall=automatic

journalctl shows me only that the open-iscsi.service has successfully started. There is no other information about any attempts to establish connections to iSCSI targets.

My workaround solution is to run iscsiadm from rc.local, and that works, but this also requires me to then restart any services that depend on filesystems on the iSCSI targets. This is bit kludgy and I'd rather have something that integrates more cleanly with the systemd start of the iSCSi service and other services.
pfaff
 
Posts: 11
Joined: Feb 13th, '12, 20:13

Re: mageia3 iscsi targets not connected at boot time

Postby jiml8 » Oct 12th, '13, 18:05

You might try running dracut in order to have your initrd re-written. I would expect the iscsi driver to get picked up and installed in the initrd then.

If that doesn't work, put the name of the iscsi driver into the file /etc/modules. I believe that driver is named iscsi, so you would put the string "iscsi" (minus quotes) on a line by itself in modules. That should cause it to be picked up early in the boot process.
jiml8
 
Posts: 1254
Joined: Jul 7th, '13, 18:09

Re: mageia3 iscsi targets not connected at boot time

Postby pfaff » Oct 13th, '13, 00:35

Thanks for your response.

This isn't something I need done in initrd since I don't need access to the iSCSI targets until much later in the boot process.
Please note, as I said in my first message, the open-iscsi.service is starting successfully at boot time which implies that the necessary drivers modules are already loaded at that time (or are loaded by the systemd startup of the open-iscsi.service). It just seems that the systemd startup of the open-iscsi service is not doing the equivalent of what I have to do later with the iscsiadm command to attach known, persistent targets).

Both this and the other problem I recently posted about in this thread:

viewtopic.php?f=8&t=6219&p=40812#p40812

seem to me to be bugs in the control of some systemd services in mageia3. I'd be happy to help diagnose and debug these problems if someone more knowledgeable of mageia3 systemd can work with me on this and give me some guidance.
pfaff
 
Posts: 11
Joined: Feb 13th, '12, 20:13


Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest