iSCSI on Ubuntu: working around boot order problems
Hi everyone
I am currently working towards a stable iSCSI connection between Ubuntu server edition (testing with 64bit 8.04.3 LTS and 9.04) and a QNAP TS-291P. A good basic set of instructions for iSCSI on Ubuntu 9.04 (which also works for 8.04) may be found on HowToForge.com. During my testing I hit on the following Bug: boot order wrong for iscsi. The last few postings of this thread claim that the bug was solved. However, my tests indicate the opposite! The problem is that the open-iscsi daemon and the resulting iSCSI connections are started before the network is started. This setup must fail since iSCSI is a network protocol. The easy part of the fix is moving the init script for open-iscsi further down in the boot order (as indicated by the valuable posting #15 of the aforementioned bug report): Code:
mv /etc/rcS.d/S25open-iscsi /etc/rcS.d/S42open-iscsi The problem, however, is the shutdown procedure. This is the relevant excerpt from /etc/init.d/open-iscsi: Code:
stoptargets() { $ADM -m node --logoutall=all where $ADM is replaced by iscsiadm. This instruction doesn't seem to work! I also tried executing the instruction manually at the command prompt. It doesn't work either. If, however, I explicitely logout from my QNAP iSCSI target like so: Code:
iscsiadm -m node --targetname "xxxxxxxx" --portal "xxx.xxx.xxx.xxx" --logout I also introduced the explicit logout command into /etc/init.d/open-iscsi: Code:
stoptargets() { Does anyone know, what the problem with the --logoutall=all command might be? Why doesn't it work? I'm grateful for your contributions. Thanks in advance. :hattip: |
When you tried:
Code:
iscsiadm -m node --logout--all |
Quote:
|
> Did it give any message?
No, that's one of the strange things. I couldn't find any special messages in the logs, nor did I get a message on the command line when typing the command directly. > I believe *except ones marked onboot* should be the problem. I did see this line in the manpage. However, the command was introduced into the init scripts by the Debian people... Do I know more about init scripts than them? - No, definitely not. Yes, it is possible that this is the problem. I consider it unlikely, though. Thank you for your replies. |
All times are GMT -5. The time now is 07:03 PM. |