Menu
▾
▴
Re: [Iscsitarget-devel] Issue with sanbooting Server 2008R2
|
From: Ross S. W. W. <RW...@me...> - 2011-06-26 01:59:48
|
If the disk is greater then 2TB then it will make it GPY On Jun 25, 2011, at 9:57 PM, "Ryan Holt" <ry...@ry...> wrote: > OK I think I may have an idea as to the problem. The Windows installer disk is creating a GPT partition table on my physical disks and also trying to do the same thing on my iSCSI LUN. It appears that I can’t boot off a GPT partition table when it’s coming from the LUN, but when I boot from a local disk it works fine. > > > > My other server which boots off the iSCSI LUN has an MBR partition table. Trying to force the system to install on a MBR partition table now. > > > > Thanks, > > Ryan > > > > From: Ryan Holt > Sent: Saturday, June 25, 2011 8:48 PM > To: 'Ross S. W. Walker' > Cc: 'Hengesbach, Jeff'; 'isc...@li...' > Subject: RE: [Iscsitarget-devel] Issue with sanbooting Server 2008R2 > > > > I just attempted to install to a SATA drive and then copy the partitions into the iSCSI LUN per the guide here: > > > > http://www.etherboot.org/wiki/sanboot/win2k8_physical > > > > It will boot off the SAN but will reboot after it scrolls through a few of the loading Windows screens. > > > > Thanks, > > Ryan > > > > From: Ryan Holt > Sent: Saturday, June 25, 2011 8:24 PM > To: 'Ross S. W. Walker' > Cc: Hengesbach, Jeff; isc...@li... > Subject: RE: [Iscsitarget-devel] Issue with sanbooting Server 2008R2 > > > > My logs are pretty much identical to what’s posted here: > > > > http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/8568362a-0140-4fbd-930d-792a98bdc7c4/ > > > > He points to an issue with his Bios. I have the latest bios version available. Additionally, the working system has an identical bios setup as the non-working system. I believe the line: > > > > [0x0606cc] IBS DiskInfo: No available ARC path > > > > May point to the problem. > > > > Thanks, > > Ryan > > > > From: Ross S. W. Walker [mailto:RW...@me...] > Sent: Saturday, June 25, 2011 8:21 PM > To: Ryan Holt > Cc: Hengesbach, Jeff; isc...@li... > Subject: Re: [Iscsitarget-devel] Issue with sanbooting Server 2008R2 > > > > > > Ok, then is there a way to get more diagnostic info from Windows on why it finds the volume unacceptable? > > > > -Ross > > > > On Jun 25, 2011, at 8:07 PM, "Ryan Holt" <ry...@ry...> wrote: > > I'm using the latest trunk version as of 6/24. > > "Ross S. W. Walker" <RW...@me...> wrote: > > > > Which version is this again? > > > > If it's earlier then 1.4.20, make sure you define the ScsiId and ScsiSN, each LUN should have a different one. > > > > -Ross > > > > On Jun 25, 2011, at 3:57 PM, "Ryan Holt" <ry...@ry...> wrote: > > Hi Ross, > > Thanks for the tip. I changed everything back to Lun0 (dhcp and iet configuration. Problem persists. I also removed all other luns for the time being... problem persists. I've tried installing via a DVD and also the IPMI ISO mapping. Same results. Any other ideas? > > Thanks! > Ryan > > "Ross S. W. Walker" <RW...@me...> wrote: > > > > I believe Windows requires all boot volumes to be LUN 0 and besides that the SCSI requirement is that LUN 0 MUST exist before any other LUN on a target. > > > > > > -Ross > > > > On Jun 24, 2011, at 5:09 PM, "Ryan Holt" <ry...@ry...> wrote: > > Hi Jeff, > > You can change the LUN through the DHCP root-path line. I changes to LUN 2 just to test that theory out. Got the same result when I had it set to LUN 0. Hv01 is the one I can't get to boot. > > "Hengesbach, Jeff" <jrh...@ak...> wrote: > > Just a guess Ryan but does SAN boot require LUN 0? > > > > Is target “iqn.2011-04.local.lab.storage:hv01” the one you’re having trouble with? > > > > Jeff > > > > From: Ryan Holt [mailto:ry...@ry...] > Sent: Friday, June 24, 2011 2:05 PM > To: isc...@li... > Subject: [Iscsitarget-devel] Issue with sanbooting Server 2008R2 > > > > Hi Everyone, > > > > I’m pretty certain that I’ve got IET configured properly but would like a sanity check. I’ve got an OpenSuse server with the latest trunk version of IET serving out LVs to two physical servers that are diskless. I’ve burned iPXE into the NIC cards on those two servers and have configured DHCP to pass the proper LUN to the servers. One of the servers I built a few months ago and just recently got the second server. I was able to install Server 2008 R2 directly to the iSCSI LUN from within the setup media on the first server but now when I go to install Server 2008R2 on the second server I get notes that the location is invalid for installation. The server sees the LUN, just won’t install to it. > > > > I used DD to copy from the working LUN to the new LUN and the new server boots up fine. I’ve followed the guide located here: > > > > http://www.etherboot.org/wiki/sanboot/win2k8_iscsi_install > > > > Here’s my /etc/ietd.conf: > > > > > > storage:~ # cat /etc/ietd.conf > > Target iqn.2011-04.local.lab.storage:hv00 > > Lun 0 Path=/dev/StoragePool/hv00,Type=fileio > > MaxConnections 1 > > > > Target iqn.2011-04.local.lab.storage:hv01 > > Lun 2 Path=/dev/StoragePool/hv01,Type=fileio > > MaxConnections 1 > > > > Target iqn.2011-04.local.lab.storage:vmstorage > > Lun 0 Path=/dev/HVVMs/srv00,Type=fileio > > Lun 1 Path=/dev/HVVMs/srv01,Type=fileio > > > > I’m pretty certain that I have the LUN and IET configured correctly but feel like there’s some silly configuration I may be missing. Anybody have any pointers? > > > > Thanks, > > Ryan > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > > _______________________________________________ > Iscsitarget-devel mailing list > Isc...@li... > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel > > ______________________________________________________________________ > This e-mail, and any attachments thereto, is intended only for use by > the addressee(s) named herein and may contain legally privileged > and/or confidential information. If you are not the intended recipient > of this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify the sender and permanently delete the > original and any copy or printout thereof. > > ______________________________________________________________________ > This e-mail, and any attachments thereto, is intended only for use by > the addressee(s) named herein and may contain legally privileged > and/or confidential information. If you are not the intended recipient > of this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify the sender and permanently delete the > original and any copy or printout thereof. > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1388 / Virus Database: 1513/3726 - Release Date: 06/25/11 > > ______________________________________________________________________ > This e-mail, and any attachments thereto, is intended only for use by > the addressee(s) named herein and may contain legally privileged > and/or confidential information. If you are not the intended recipient > of this e-mail, you are hereby notified that any dissemination, > distribution or copying of this e-mail, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, > please immediately notify the sender and permanently delete the > original and any copy or printout thereof. > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1388 / Virus Database: 1513/3726 - Release Date: 06/25/11 ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof. |