On 10/27/2010 10:45 AM, Michael Brown wrote: > On Wednesday 27 Oct 2010 01:17:50 Johnny Stenback wrote: >> ... and in fact hacking scsi_parse_lun() to force the lun to 1 >> (lun->u16[0] = htons ( 1 );) solves this issue here! That's obviously >> not a real solution here, but I think it points pretty clearly at what >> the issue is :) > > Yes, that's definitely your problem. You need to specify the correct LUN in > the iSCSI root path, as per RFC4173. In your case, you should change > > iscsi:10.0.0.1::::iqn.2010-10.com.direcpc.shire:gandalf.bud-pc > > to > > iscsi:10.0.0.1:::1:iqn.2010-10.com.direcpc.shire:gandalf.bud-pc
Yup, that was next on my list of things to test, but I had lost my reference to in between which ':'s that number should go :). And yes, adding that '1' there is exactly what I needed. Sure would be nice if this could be made more obvious someway, but I'm afraid I don't really know what that would be. I guess the wiki could point this out more clearly, especially in light of the fact that a common linux iSCSI target toolchain prevents you from using LUN 0. > Glad you figured out the problem, sorry I wasn't around in the past couple of > days to help with it! No worries, thanks for your reply and all your work on iPXE! > Michael > _______________________________________________ > ipxe-devel mailing list > ipxe-devel at lists.ipxe.org > https://lists.ipxe.org/mailman/listinfo/ipxe-devel > -- jst
