Chandra Seetharaman wrote:
> Hello,
> Installation completed fine.
> Boot started fine, iSCSI daemon started, logged into iface, found the
> storage.
> While fsck'ing had a connection error, and immediately int started had
> another connection error, and just hung there.
> --------------
> Waiting for device 
> /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2 to appear:  ok
> fsck 1.41.1 (01-Sep-2008)
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a 
> /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2 
> /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2: recovering 
> journal
>  connection1:0: detected conn error (1011)
> /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2: clean, 
> 154441/1310720 files, 1022000/5235168 blocks
> fsck succeeded. Mounting root device read-write.
> Mounting root /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2
> mount -o rw,acl,user_xattr -t ext3 
> /dev/disk/by-id/scsi-360a98000486e5a76464a53614a394461-part2 /root
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on sdi2, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> mount: can't find /root/proc in /etc/fstab or /etc/mtab
> INIT: version 2.86 booting
> iscsi: can not broadcast skb (-3)
>  connection1:0: detected conn error (1011)

Is this fsck is started from the init scripts during boot up? If so, the 
reason for the hang is probably that iscsid is not up and cannot handle 
the connection error. For fedora/RHEL, I think we did some hack where if 
network storage is used we delayed the fsck from the init boot scripts.

Not sure about the reaosn for the conn error. Can you turn on debugging?

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to