Anonymous_User Absent Member.
Absent Member.
1912 views

iSCSI targets don't connect on reboot

Hi all,

I've got two newly-installed SLES 10 x64 SP2 systems, and whenever i
reboot, their iSCSI associations disappear. My disk array is a Dell
MD3000i with 4 x iSCSI interfaces. I've done a normal discovery and
explicitly toggled all of them to automatic startup, yet after a reboot,
i have to manually reconnect. What gives?

Regards,
Paul
Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: iSCSI targets don't connect on reboot

Paul,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iSCSI targets don't connect on reboot

Had similar issue with a fiber based san

I would check /etc/sysconfig/kernel for the correct order of the modules
to be loaded, and don't forget tou make a mkinitrd



look for the section initrd in this doc


http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.3/suselinux-adminguide_en/cha.boot.html

hope that helps
marc


Paul Gear wrote:
> Hi all,
>
> I've got two newly-installed SLES 10 x64 SP2 systems, and whenever i
> reboot, their iSCSI associations disappear. My disk array is a Dell
> MD3000i with 4 x iSCSI interfaces. I've done a normal discovery and
> explicitly toggled all of them to automatic startup, yet after a reboot,
> i have to manually reconnect. What gives?
>
> Regards,
> Paul

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iSCSI targets don't connect on reboot

marck wrote:
> Had similar issue with a fiber based san
>
> I would check /etc/sysconfig/kernel for the correct order of the modules
> to be loaded, and don't forget tou make a mkinitrd
>
> ...
>
> Paul Gear wrote:
>> Hi all,
>>
>> I've got two newly-installed SLES 10 x64 SP2 systems, and whenever i
>> reboot, their iSCSI associations disappear. My disk array is a Dell
>> MD3000i with 4 x iSCSI interfaces. I've done a normal discovery and
>> explicitly toggled all of them to automatic startup, yet after a reboot,
>> i have to manually reconnect. What gives?


I'm not booting from iSCSI - there is a local hardware RAID1 set for the
operating system. The iSCSI disks come afterwards and are supposed to
be available before the OCFS2/heartbeat/Xen cluster starts.

If i connect the iSCSI targets manually in yast, everything works
perfectly, and they are set for automatic start, but after a reboot they
don't connect.

An earlier post (http://tinyurl.com/5ucns2) suggested network interfaces
might be coming up after the iSCSI client, but /var/log/messages
indicates that the iSCSI network interface (eth0) is coming up before
the iSCSI client attempts to start, so that's not likely to be the problem.

Occasionally i see messages like this in the kernel logs (i'm assuming
they're somehow symptomatic of the problem):

Nov 12 10:18:35 ezekiel kernel: ping timeout of 5 secs expired, last rx
4295324090, last ping 4295325340, now 4295326590
Nov 12 10:18:35 ezekiel kernel: connection3:0: iscsi: detected conn
error (1011)
Nov 12 10:18:35 ezekiel kernel: ping timeout of 5 secs expired, last rx
4295324091, last ping 4295325341, now 4295326591
Nov 12 10:18:35 ezekiel kernel: connection4:0: iscsi: detected conn
error (1011)
Nov 12 10:18:36 ezekiel iscsid: semop up failed 43
Nov 12 10:18:36 ezekiel iscsid: semop up failed 43
Nov 12 10:18:39 ezekiel iscsid: semop up failed 43
Nov 12 10:18:39 ezekiel iscsid: semop up failed 43

Where to next?

Paul
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.