[Bug 747772] New: iscsi: connection1:0: detected conn error (1020)
https://bugzilla.novell.com/show_bug.cgi?id=747772 https://bugzilla.novell.com/show_bug.cgi?id=747772#c0 Summary: iscsi: connection1:0: detected conn error (1020) Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: per@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0.1) Gecko/20100101 Firefox/8.0.1 I'm installing Factory x86_64 over PXE+iSCSI (root on iSCSI). When the system boots the first time after phase 1, I get the message: connection1:0: detected conn error (1020) which appears to be a disconnect from the iSCSI target. After lots of trial&error, I ended up removing boot.iscsid-early from the boot-sequence, which got the installation going so I could complete phase2. Only to run into the very same problem again, except later in the boot-up. I decided to remove iscsid from the boot-sequence, and now it works. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c1
Hannes Reinecke
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c
Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c2
--- Comment #2 from Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c3
--- Comment #3 from Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c4
--- Comment #4 from Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c5
--- Comment #5 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c6
--- Comment #6 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c7
--- Comment #7 from Per Jessen
I'd like to see the messages file from the case where both boot.iscsid-early and iscsid are present. Any chance you could reproduce? In the mean time, I'll try to reproduce ...
Hi Lee I've done a clean Factory install. This is a serial capture of the first boot-up after stage1 install. Initially it seems to work fine, but look for "Starting Remount API VFS..." at line 768. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c8
--- Comment #8 from Per Jessen
Any chance you could re-enable boot.iscsid-early and iscsid, and add "-d 6" to the ARGS in boot.iscsid-early so iscsid debugging is enabled?
I tried this, but saw no additional output on the console. I checked the iSCSI filesystem too, but nothing was written to /var/log/messages, presumably because rsyslog isn't started at this point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c9
--- Comment #9 from Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c10
Lee Duncan
[ 29.418498] connection1:0: detected conn error (1020)
Error 1020 means the target has dropped the connection. The question is why did it do this? What service is being started on line 768, where is says:
Starting Remount API VFS...
I found this reference to a problem with systemd and the remote-api-vfs service: http://lists.freedesktop.org/archives/systemd-devel/2010-November/000750.htm... You didn't happen to have usbfs enabled and in use, did you? I'm guessing something you are starting up is causing your target to disconnect. Is there any message from the target when this happens? And what type of target is it? I can try duplicating your test case, but if your error is target-specific then I might never see the same error. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c11
--- Comment #11 from Per Jessen
Per: I looked at this some more, and the first error you seem to be getting is on one line 769, where is says:
[ 29.418498] connection1:0: detected conn error (1020)
Error 1020 means the target has dropped the connection. The question is why did it do this?
I haven't played with this setup for quite some time, but I feel pretty certain that the target didn't drop the connection. There is simply no reason for the target to do so, except maybe the initiator misbehaving.
What service is being started on line 768, where is says:
Starting Remount API FS....
I don't know what that is - I guess it'll be in the initrd.
I found this reference to a problem with systemd and the remote-api-vfs service: http://lists.freedesktop.org/archives/systemd-devel/2010-November/000750.htm...
You didn't happen to have usbfs enabled and in use, did you?
I doubt it, certainly not explicitly.
I'm guessing something you are starting up is causing your target to disconnect. Is there any message from the target when this happens? And what type of target is it?
I'm using the openSUSE iscsitarget package. I don't know if there are any messages from the target, I'll see what state my test-system is in and see if I can reproduce.
I can try duplicating your test case, but if your error is target-specific then I might never see the same error.
If you've got time, just try to get a system to boot from iSCSI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c12
Lee Duncan
Starting Remount API VFS...
Is from /lib/systemd/systemd-remount-api-vfs. This command simply steps through /etc/fstab and runs "mount DIR -o remount" for directories found. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c13
Hans-Peter Raschke
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c14
--- Comment #14 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c15
--- Comment #15 from Per Jessen
I am planning on attempting an iSCSI root installation test for Monday, but in the mean time I tracked down the service that is running when you get an error.
The message:
Starting Remount API VFS
Is from /lib/systemd/systemd-remount-api-vfs. This command simply steps through /etc/fstab and runs "mount DIR -o remount" for directories found.
Hi Duncan If this remount is the culprit, I figured a work-around would be to simply comment out the root filesystems in /etc/fstab. I tried that, didn't work. Just as when I first reported this issue, my work-around of removing boot.iscsid-early and iscsid from the init-sequence worked. When the system has completed boot-up, there is no iscsid running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c16
--- Comment #16 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c17
--- Comment #17 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c18
--- Comment #18 from Lee Duncan
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c19
--- Comment #19 from Per Jessen
Per: I'm sorry I let this drop off my radar. So it sounds like it's working now? That's strange (but good, I guess).
Not really, the problem during the 2nd phase of installation still remains. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c20
--- Comment #20 from Hans-Peter Raschke
(In reply to comment #18)
Per: I'm sorry I let this drop off my radar. So it sounds like it's working now? That's strange (but good, I guess).
Not really, the problem during the 2nd phase of installation still remains.
This update should solve your problem: https://bugzilla.novell.com/show_bug.cgi?id=766300#c20 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c21
--- Comment #21 from Per Jessen
(In reply to comment #19)
(In reply to comment #18)
Per: I'm sorry I let this drop off my radar. So it sounds like it's working now? That's strange (but good, I guess).
Not really, the problem during the 2nd phase of installation still remains.
This update should solve your problem:
Thanks, I'm sure it will. Amazing that we had two reports covering exactly the same issue :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c22
--- Comment #22 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=747772
https://bugzilla.novell.com/show_bug.cgi?id=747772#c23
Lee Duncan
participants (1)
-
bugzilla_noreply@novell.com