On Aug 25, 3:04 pm, Mike Christie <micha...@cs.wisc.edu> wrote: > On 08/24/2010 11:43 AM, agshekeloh wrote: > > > Hi, > > > I'm running open-iscsi 2.0-871, on Ubuntu 10.04 amd64, straight from > > the operating system package. Mounting an iSCSI drive works perfectly > > when booting from a hard drive, but not when booting diskless via > > NFS. > > For the solaris target do you have to setup ACLs by initiator name? For > these 2 root FSs is the /etc/iscsi/initiatorname.iscsi have the same > value? Or does the NFS one have iqn.1993-08.org.debian: > 01:cd00198dd976, and then the hard drive boot one have a different name?
The Ubuntu nodes have different iSCSI initiator names. (The diskless node was copied from the hard drive install, but I manually changed a few characters in /etc/iscsi/initiatorname.iscsi.) I've removed the ACL on all solaris targets during troubleshooting. The hard-drive based install is targeting a different opensolaris instance. (Both of those hosts are running on my ESXi crash box.) The diskless server and its target are in a different datacenter. Just to check things, I tried to mount an iSCSI disk from each Ubuntu machine to the remote solaris box. Both ubuntu machines can log into the remote iSCSI server, but neither server gets a device node for this iSCSI session in /dev/disk/by-path. Could this be due to the lag and very limited bandwidth (1.5Mbs) between the sites, or is something else weird going on here? If there was a straight solaris problem, I would expect the diskless node to get a device node from the test server, just like the hard drive based install does. Thanks, ==ml -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
