iscsi-init-users Mailing List for Linux iSCSI boot initialization program (Page 2)
Brought to you by:
ifeoktistov
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(18) |
Sep
(5) |
Oct
(7) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(2) |
2009 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: James H. <Ja...@be...> - 2004-10-01 04:54:15
|
>> I don't want to specify a gateway in the kernel parameters as I use >> quagga for dynamic routing. I can specify 0.0.0.0 and iscsi-init >> complains but still works correctly, but I think it would be better to >> be able to leave off the gateway altogether. >=20 > That"ll be done in this release. Great! >> >> For setting up raid across multiple iSCSI targets, I need to be able >> to specify multiple (2 at least) targes in the kernel parameters. > I thought about it. The question is what is the best way to specify > several > targets in cmd line (it could be more than two)? Could be comma separated > list like below: >=20 > iscsi-target=3D<target_ip1>:<target_name1>,<target_ip2>:<target_name2>,..= . >=20 > Comma should not be used in a target name, right? >=20 > What about DHCP discovery? How to define several targets in dhcp? > It could be like below, but not sure. >=20 > option root-path > "<target_ip1>:<target_name1>, > <target_ip2>:<target_name2>,.../<initiator_name>" >=20 > What do you think? I think that what you have suggested is the best way to do it. >> I think it would make sense to combine this project with the >> linux-iscsi project as it is an excellent addition to it. I am finding >> that the linux-iscsi shutdown code also shuts down anything started by >> iscsi-init and if they were a combined project then linux-iscsi could be >> aware of iscsi-init and leave those connections alone. >=20 > I actually discussed this with Manish, linux-iscsi project manager. > He actually agreed at first time. Then there were some concerns from=20 > developers regarding running ipconfig and ioctl from a module. I do > believe there might be better integration than ioctl. I didn"t bother > too much to ask one more time ;) Does it have to be a module? A simple 'iscsi-init' tool that runs from userspace should be able to do what the iscsi-init module does. Before I found out that iscsi-init existed, I thought of creating a very cut down iscsid that just set up the connection and then died. With such a tool + ifconfig I'd be able to do what I'm doing now, although if I wanted to do dhcp it would be a bit more complicated. The nice thing about iscsi-init is that it's all rolled into one but that sounds like what Manish was objecting to. It would also be a bit harder to get it into initrd automatically but I already need to create the device node via script. > Regarding ungraceful reboots. > Commenting interfaces shutdown in "network" script > helps with graceful reboots. > But it does not help against "rmmod iscsi_sfnet" I put 'down /bin/false' in the interface definition in /etc/networks and it stops the interface being shutdown on system shutdown, but as you say this doesn't help when the iscsi init script shuts down all the connections. James |
From: Igor F. <ife...@ya...> - 2004-10-01 01:47:57
|
>From: "James Harper" <Ja...@be...> >To: <isc...@li...> > >It appears to work fine for me so far. > >Just a couple of suggestions for enhancements: > >. I don't want to specify a gateway in the kernel parameters as I use >quagga for dynamic routing. I can specify 0.0.0.0 and iscsi-init >complains but still works correctly, but I think it would be better to >be able to leave off the gateway altogether. That'll be done in this release. > >. For setting up raid across multiple iSCSI targets, I need to be able >to specify multiple (2 at least) targes in the kernel parameters. I thought about it. The question is what is the best way to specify several targets in cmd line (it could be more than two)? Could be comma separated list like below: iscsi-target=<target_ip1>:<target_name1>,<target_ip2>:<target_name2>,... Comma should not be used in a target name, right? What about DHCP discovery? How to define several targets in dhcp? It could be like below, but not sure. option root-path "<target_ip1>:<target_name1>,<target_ip2>:<target_name2>,.../<initiator_name> What do you think? > >. I think it would make sense to combine this project with the >linux-iscsi project as it is an excellent addition to it. I am finding >that the linux-iscsi shutdown code also shuts down anything started by >iscsi-init and if they were a combined project then linux-iscsi could be >aware of iscsi-init and leave those connections alone. I actually discussed this with Manish, linux-iscsi project manager. He actually agreed at first time. Then there were some concerns from developers regarding running ipconfig and ioctl from a module. I do believe there might be better integration than ioctl. I didn't bother too much to ask one more time ;) Regarding ungraceful reboots. Commenting interfaces shutdown in "network" script helps with graceful reboots. But it does not help against "rmmod iscsi_sfnet" > >Thanks > >James > > > _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com |
From: James H. <Ja...@be...> - 2004-09-30 23:31:19
|
It appears to work fine for me so far. Just a couple of suggestions for enhancements: . I don't want to specify a gateway in the kernel parameters as I use quagga for dynamic routing. I can specify 0.0.0.0 and iscsi-init complains but still works correctly, but I think it would be better to be able to leave off the gateway altogether. . For setting up raid across multiple iSCSI targets, I need to be able to specify multiple (2 at least) targes in the kernel parameters. . I think it would make sense to combine this project with the linux-iscsi project as it is an excellent addition to it. I am finding that the linux-iscsi shutdown code also shuts down anything started by iscsi-init and if they were a combined project then linux-iscsi could be aware of iscsi-init and leave those connections alone. Thanks James |
From: Igor F. <ife...@ya...> - 2004-09-30 21:03:37
|
A beta version is available here http://iscsi-init.sourceforge.net/iscsi-init-4.0.1.2.tar.gz Please let me know if it works for you so I can publish it on the web --------------------- > The new release which supports 4.0.1.9 will be > available sometime next week. Is there a beta version I can test now? I get corruption with 4.0.1.8 and so really do need to use 4.0.1.8! Thanks James __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail |
From: James H. <jam...@bi...> - 2004-09-29 11:21:09
|
> The new release which supports 4.0.1.9 will be > available sometime next week. Is there a beta version I can test now? I get corruption with 4.0.1.8 and so really do need to use 4.0.1.8! Thanks James |
From: Igor F. <ife...@ya...> - 2004-09-29 04:31:36
|
The new release which supports 4.0.1.9 will be available sometime next week. ------------------------------------------------------ Does anyone have a patch to make iscsi-init work with linux-iscsi 4.0.1.9? Thanks James ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail |
From: James H. <jam...@bi...> - 2004-09-29 01:28:04
|
Does anyone have a patch to make iscsi-init work with linux-iscsi 4.0.1.9? Thanks James |
From: James H. <jam...@bi...> - 2004-08-30 11:37:14
|
Here's the patch. It also makes it compile under 2.6.8.1, as a few syscalls were removed since 2.6.7. James > -----Original Message----- > From: Igor Feoktistov [mailto:ife...@ya...] > Sent: Monday, 30 August 2004 10:46 > To: jam...@bi... > Cc: isc...@li... > Subject: Re: [iscsi-init-users] readonly /dev in initrd > > James, > > yes, please submit a patch or send it to me. > I'll implement it in next release. > > Thanks, > Igor. > > -------------------- > At the time the iscsi-init module would be loaded > under Debian 3.1 (Sarge), > /dev is readonly and iscsi-init doesn't work if it > can't create > /dev/iscsictl (because one already exists or because > the filesystem is > readonly) > > I have modified the module to try and open > /dev/iscsictl first before trying > to create it, and not report an error if the first > opening succeeds and it > works well. > > I can submit a patch if the change isn't obvious. > > Great project btw, it makes the whole boot operation > very smooth!!! > > James > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic > Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Iscsi-init-users mailing list > Isc...@li... > https://lists.sourceforge.net/lists/listinfo/iscsi-init-users > > > > _______________________________ > Do you Yahoo!? > Win 1 of 4,000 free domain names from Yahoo! Enter now. > http://promotions.yahoo.com/goldrush |
From: Igor F. <ife...@ya...> - 2004-08-30 00:46:23
|
James, yes, please submit a patch or send it to me. I'll implement it in next release. Thanks, Igor. -------------------- At the time the iscsi-init module would be loaded under Debian 3.1 (Sarge), /dev is readonly and iscsi-init doesn't work if it can't create /dev/iscsictl (because one already exists or because the filesystem is readonly) I have modified the module to try and open /dev/iscsictl first before trying to create it, and not report an error if the first opening succeeds and it works well. I can submit a patch if the change isn't obvious. Great project btw, it makes the whole boot operation very smooth!!! James ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush |
From: James H. <jam...@bi...> - 2004-08-29 08:00:06
|
At the time the iscsi-init module would be loaded under Debian 3.1 (Sarge), /dev is readonly and iscsi-init doesn't work if it can't create /dev/iscsictl (because one already exists or because the filesystem is readonly) I have modified the module to try and open /dev/iscsictl first before trying to create it, and not report an error if the first opening succeeds and it works well. I can submit a patch if the change isn't obvious. Great project btw, it makes the whole boot operation very smooth!!! James |
From: Igor F. <ig...@ne...> - 2004-08-26 21:37:44
|
use linux-iscsi-4.0.1.8 >From: "Bryn Hughes" <bh...@vc...> >To: <isc...@li...> >Subject: [Iscsi-init-users] SuSE Enterprise Server 9 >Date: Thu, 26 Aug 2004 14:23:45 -0700 > >I'm trying to get iscsi-init working with SuSE Enterprise Server 9. >SuSE is using kernel 2.6.5 for SLES9 along with linux-iscsi-4.0.1. I've >tried compiling the driver a few times and have tried replacing SuSE's >linux-iscsi package with one I build myself but every time I'm getting >this error: > >ISCSI: ioctl size 2292, expected 2580 > >iscsi-init then fails with an error trying to establish the session. > >Any ideas? > >Bryn > >_______________________________ > >Bryn Hughes >Network Specialist >Information and Computing Services >Vancouver Community College > >ph: (604) 443-8515 >fax: (604) 443-8353 >email: bh...@vc... >_______________________________ > > |
From: Bryn H. <bh...@vc...> - 2004-08-26 21:23:41
|
I'm trying to get iscsi-init working with SuSE Enterprise Server 9. SuSE is using kernel 2.6.5 for SLES9 along with linux-iscsi-4.0.1. I've tried compiling the driver a few times and have tried replacing SuSE's linux-iscsi package with one I build myself but every time I'm getting this error: ISCSI: ioctl size 2292, expected 2580 iscsi-init then fails with an error trying to establish the session. Any ideas? Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ |
From: Igor F. <ife...@ya...> - 2004-08-26 03:56:28
|
I'm not sure regarding first question. I doubt it's iscsi-init related issue. However, second issue can be avoided by disabling shutdown network interfaces in /etc/init.d/network script. For example, in RedHat you just need to comment the strings below in /etc/init.d/network -- # shut down all interfaces (other than loopback) for i in $interfaces ; do eval $(fgrep "DEVICE=" ifcfg-$i) if [ -z "$DEVICE" ] ; then DEVICE="$i"; fi if ! check_device_down $DEVICE; then action $"Shutting down interface $i: " ./ifdown $i boot fi done -- Also enabling autofsk won't hurt. For example, in RedHat you just need to create the file /etc/sysconfig/autofsk with the content below: PROMPT=no AUTOFSCK_DEF_CHECK=yes ----------------------- Hi all, Now that I"ve got booting working reliably under SuSE Enterprise Server 8 I"m starting to notice some other problems: 1. Since there is always an iscsi session active I don"t seem to be able to see changes made on the target end such as additional volumes or volume expansions. Under a "normal" boot restarting the iscsi driver discovers these changes but after booting with iscsi_init I have to do a full system reboot to see new LUNs or use additional capacity on existing LUNs beyond what was there on the initial boot of the machine. 2. I seem to be having problems with reboots. Since the system is running off of an iscsi volume it doesn"t seem to have a way to shut itself down without causing at least a segfault. Any suggestions for dealing with this? I need to be able to reboot a machine with no operator intervention. Thanks in advance, Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Bryn H. <bh...@vc...> - 2004-08-19 02:55:48
|
Hi all, Now that I've got booting working reliably under SuSE Enterprise Server 8 I'm starting to notice some other problems: 1. Since there is always an iscsi session active I don't seem to be able to see changes made on the target end such as additional volumes or volume expansions. Under a 'normal' boot restarting the iscsi driver discovers these changes but after booting with iscsi_init I have to do a full system reboot to see new LUNs or use additional capacity on existing LUNs beyond what was there on the initial boot of the machine. 2. I seem to be having problems with reboots. Since the system is running off of an iscsi volume it doesn't seem to have a way to shut itself down without causing at least a segfault. Any suggestions for dealing with this? I need to be able to reboot a machine with no operator intervention. Thanks in advance, Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ |
From: Igor F. <ig...@ne...> - 2004-08-13 22:48:38
|
Thanks, I will include this as a reference for SuSE users. Igor. >Date: Fri, 13 Aug 2004 15:43:27 -0700 >From: "Bryn Hughes" <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) > Igor, Thanks for all your help - I just managed to get a working boot! I've still got some cleanup to do evidently but this is definitley progress. In case you're interested the linuxrc that worked is attached. Notice that SuSE doesn't mount root as part of linuxrc - no wonder I was having so much trouble. Also this script uses ash instead of nash. I've also attached my initrd tree. Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ >>>Igor Feoktistov <ig...@ne...> 08/13/04 2:36 pm >>> Try to adapt standard SuSE initrd image. Just delete everything unrelated to iSCSI boot such as local scsi drivers. And then just add in proper sequence all iSCSI related stuff similarly to linuxrc for redhat. If you were able to get sda drive during the boot, I believe you'll be able to boot. >Date: Fri, 13 Aug 2004 14:27:32 -0700 >From: Bryn Hughes <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) > >Hi Igor, > >The tg3 driver seems to be behaving much better - no more kernel panics >at DHCP time regardless of whether the machine was warm or cold booted. >That's progress! > >I'm still not having any luck - It still appears like portions of >linuxrc are being run multiple times. I'm not really sure what would >cause this. I get errors when mkdevices, mkrootdev and anything that >requires /dev to be there. I'm using nash from a Red Hat 7.3 install >right now - SuSE uses ash instead of nash which operates a little >differently. > >Bryn > >>>>Igor Feoktistov <ig...@ne...> 08/12/04 7:08 pm >>> > >It looks like you forgot to run mkdevices /dev > >See working example below. > >Also I've noticed you are using modules.conf. > >Try to avoid it from initrd. Just load all modules you need from > >linuxrc > >-- > >echo Creating block devices > >mkdevices /dev > >echo Creating root device > >mkrootdev /dev/root > >echo 0x0100 > /proc/sys/kernel/real-root-dev > >echo Mounting root filesystem > >mount -o defaults --ro -t ext3 /dev/root /sysroot > >pivot_root /sysroot /sysroot/initrd > >umount /initrd/proc > >-- > > >>Date: Thu, 12 Aug 2004 18:22:51 -0700 > >>From: Bryn Hughes <bh...@vc...> > >>To: <ig...@ne...> > >>Cc: <isc...@li...> > >>Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) > >>X-pstn-version: pmps:sps_solaris_1_1_0b3 pase:2.5 > >>X-pstn-levels: (C:51.8443 M:98.2169 P:95.9108 R:95.9108 S:76.6400 ) > >>X-pstn-settings: 3 (0.1000:0.1000) p:12 m:12 C:12 r:12 > >>X-pstn-addresses: from <bh...@vc...> > >> > >Thanks Igor, > > >Attached is a copy of my linuxrc file and a tree of my initrd. > >Everything is pretty much the same as your examples. > > >I'll give the NIC drivers you suggested a shot tomorrow - I'm out of > >time for today. > > >Bryn > > > > > >Bryn Hughes > >Network Specialist > >Information and Computing Services > >Vancouver Community College > > >ph: (604) 443-8515 > >fax: (604) 443-8353 > >email: bh...@vc... > > > > > >------------------------------------------------------- > >SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > >100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > >Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > >http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > >Iscsi-init-users mailing list > >Isc...@li... > >https://lists.sourceforge.net/lists/listinfo/iscsi-init-users ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
From: Igor F. <ig...@ne...> - 2004-08-13 21:36:32
|
Try to adapt standard SuSE initrd image. Just delete everything unrelated to iSCSI boot such as local scsi drivers. And then just add in proper sequence all iSCSI related stuff similarly to linuxrc for redhat. If you were able to get sda drive during the boot, I believe you'll be able to boot. >Date: Fri, 13 Aug 2004 14:27:32 -0700 >From: "Bryn Hughes" <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) > >Hi Igor, > >The tg3 driver seems to be behaving much better - no more kernel panics >at DHCP time regardless of whether the machine was warm or cold booted. >That's progress! > >I'm still not having any luck - It still appears like portions of >linuxrc are being run multiple times. I'm not really sure what would >cause this. I get errors when mkdevices, mkrootdev and anything that >requires /dev to be there. I'm using nash from a Red Hat 7.3 install >right now - SuSE uses ash instead of nash which operates a little >differently. > >Bryn > >>>>Igor Feoktistov <ig...@ne...> 08/12/04 7:08 pm >>> > >It looks like you forgot to run mkdevices /dev > >See working example below. > >Also I've noticed you are using modules.conf. > >Try to avoid it from initrd. Just load all modules you need from > >linuxrc > >-- > >echo Creating block devices > >mkdevices /dev > >echo Creating root device > >mkrootdev /dev/root > >echo 0x0100 > /proc/sys/kernel/real-root-dev > >echo Mounting root filesystem > >mount -o defaults --ro -t ext3 /dev/root /sysroot > >pivot_root /sysroot /sysroot/initrd > >umount /initrd/proc > >-- > > >>Date: Thu, 12 Aug 2004 18:22:51 -0700 > >>From: Bryn Hughes <bh...@vc...> > >>To: <ig...@ne...> > >>Cc: <isc...@li...> > >>Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) > >>X-pstn-version: pmps:sps_solaris_1_1_0b3 pase:2.5 > >>X-pstn-levels: (C:51.8443 M:98.2169 P:95.9108 R:95.9108 S:76.6400 ) > >>X-pstn-settings: 3 (0.1000:0.1000) p:12 m:12 C:12 r:12 > >>X-pstn-addresses: from <bh...@vc...> > >> > >Thanks Igor, > > >Attached is a copy of my linuxrc file and a tree of my initrd. > >Everything is pretty much the same as your examples. > > >I'll give the NIC drivers you suggested a shot tomorrow - I'm out of > >time for today. > > >Bryn > > > > > >Bryn Hughes > >Network Specialist > >Information and Computing Services > >Vancouver Community College > > >ph: (604) 443-8515 > >fax: (604) 443-8353 > >email: bh...@vc... > > > > > >------------------------------------------------------- > >SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > >100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > >Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > >http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > >Iscsi-init-users mailing list > >Isc...@li... > >https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
From: Bryn H. <bh...@vc...> - 2004-08-13 21:27:55
|
Hi Igor, The tg3 driver seems to be behaving much better - no more kernel panics at DHCP time regardless of whether the machine was warm or cold booted. That's progress! I'm still not having any luck - It still appears like portions of linuxrc are being run multiple times. I'm not really sure what would cause this. I get errors when mkdevices, mkrootdev and anything that requires /dev to be there. I'm using nash from a Red Hat 7.3 install right now - SuSE uses ash instead of nash which operates a little differently. Bryn >>>Igor Feoktistov <ig...@ne...> 08/12/04 7:08 pm >>> It looks like you forgot to run mkdevices /dev See working example below. Also I've noticed you are using modules.conf. Try to avoid it from initrd. Just load all modules you need from linuxrc -- echo Creating block devices mkdevices /dev echo Creating root device mkrootdev /dev/root echo 0x0100 > /proc/sys/kernel/real-root-dev echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot pivot_root /sysroot /sysroot/initrd umount /initrd/proc -- >Date: Thu, 12 Aug 2004 18:22:51 -0700 >From: Bryn Hughes <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) >X-pstn-version: pmps:sps_solaris_1_1_0b3 pase:2.5 >X-pstn-levels: (C:51.8443 M:98.2169 P:95.9108 R:95.9108 S:76.6400 ) >X-pstn-settings: 3 (0.1000:0.1000) p:12 m:12 C:12 r:12 >X-pstn-addresses: from <bh...@vc...> > Thanks Igor, Attached is a copy of my linuxrc file and a tree of my initrd. Everything is pretty much the same as your examples. I'll give the NIC drivers you suggested a shot tomorrow - I'm out of time for today. Bryn Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
From: Igor F. <ig...@ne...> - 2004-08-13 02:08:13
|
It looks like you forgot to run "mkdevices /dev" See working example below. Also I've noticed you are using "modules.conf". Try to avoid it from initrd. Just load all modules you need from linuxrc -- echo "Creating block devices" mkdevices /dev echo "Creating root device" mkrootdev /dev/root echo 0x0100 > /proc/sys/kernel/real-root-dev echo "Mounting root filesystem" mount -o defaults --ro -t ext3 /dev/root /sysroot pivot_root /sysroot /sysroot/initrd umount /initrd/proc -- >Date: Thu, 12 Aug 2004 18:22:51 -0700 >From: "Bryn Hughes" <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) >X-pstn-version: pmps:sps_solaris_1_1_0b3 pase:2.5 >X-pstn-levels: (C:51.8443 M:98.2169 P:95.9108 R:95.9108 S:76.6400 ) >X-pstn-settings: 3 (0.1000:0.1000) p:12 m:12 C:12 r:12 >X-pstn-addresses: from <bh...@vc...> > Thanks Igor, Attached is a copy of my linuxrc file and a tree of my initrd. Everything is pretty much the same as your examples. I'll give the NIC drivers you suggested a shot tomorrow - I'm out of time for today. Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ |
From: Igor F. <ig...@ne...> - 2004-08-13 00:03:21
|
That most likely bcm5700 driver related issue. Try to use another driver. I'm using tg3 driver for my BroadCom Tigon3 NIC (IBM x335). Also it works fine with Intell e1000 (IBM x345). I'm not sure if it will work with your 57xx. I've tested it in RH 9, Fedora 1 & 2, RH AS 3.0. Regarding troubles with mkrootdev. Send me please your linuxrc and initrd tree. >Date: Thu, 12 Aug 2004 16:30:51 -0700 >From: "Bryn Hughes" <bh...@vc...> >To: <ig...@ne...> >Cc: <isc...@li...> >Subject: Re: [Iscsi-init-users] Root? (was: Kernel Panic! ) Hi Igor, I was doing some more troubleshooting and I noticed that I DON'T get a kernel panic if the server is starting up from a cold boot (i.e. I physically power it off and then back on again). I DO get a panic if I restart it with Ctrl-Alt-Delete or using the BladeCenter's management module. Therefore it looks like the panic may be caused by something with the system itself as opposed to your code. I am still having problems however. After a cold boot the iscsi_init module sucessfully gets an IP address and manages to connect to my iSCSI target (I see the volume listed on the console plus I can see it on my target server's log). At that point it seems to try and run linuxrc again and of course generates a number of errors when trying to load modules which are already loaded. iSCSI: iscsi_set_if_addr: Bringing up network interface iSCSI: bus 0 target 255 = T-testlab-01 iSCSI: bus 0 target 255 portal 0 = address 10.0.0.1 port 3260 group 1 iSCSI: bus 0 target 255 trying to establish session f106e000 to portal 0, address 10.0.0.1 port 3260 group 1 iSCSI: iscsis_set_if_addr: Bringing up network interface iSCSI: bus 0 target 255 established session f106e000 #1, portal 0, address 10.0.0.1 port 3260 group 1 scsi singleddevice 0 0 255 0 Vendor: FALCON Model: IPSTOR DISK Rev: v1.0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 255, lun 0 resize_dma_pool: unknown device type 127 iSCSI session f106e000 recv_cmd cdfc2600, cdb 0x0, status 0x2, response 0x0, senselen 14, key 06, itt 248 task cdc7ff60 to (0 0 255 0), T-testlab-01 iSCSI: Sense 70000600 00000006 SCSI device sda: 15360000 512-byte hdwr sectors (7864 MB) sda: sda1 sda2 that is followed by a number of errors saying modules are already loaded, an error 16 trying to mount /proc (I assume this is because /proc was mounted when linuxrc ran the first time), mkrootdev failing with error 17 and then mount of the root filesystem (sda1) failing with error 16. iscsi-init version 3.4.3 iscsi initiator 3.4.3 kernel command line ro root=/dev/sda1 initrd=iscsi-init/initrd-2.4.21-215-smp-iscsi iscsi-if=eth1 option root-path 10.0.0.1:/T-testlab-01/iqn.2004-08.ca.vcc.testlab-01.00:0D:60:9C:50:10/0; The kernel panic is attached below but like I said this appears to only happen after a warm boot, not a cold boot. The working iscsi.conf file is just one line - DiscoveryAddress=10.0.0.1 initiatorname.iscsi is iqn.2004-08.ca.vcc.testlab-01.00:0D:60:9C:50:10 Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ >>>Igor Feoktistov <ig...@ne...> 08/12/04 1:34 pm >>> Bryn, please provide more details, such as: - iscsi-init version - linux-iscsi initiator version - kernel cmd line - dhcp config (root-path if you use it vs kernel cmd options) - an output from linux-iscsi module when it happens - an output from iscsi-init module when it loads - an output from kernel before it panics - /etc/fstab - working configuration for iscsid (/etc/iscsi.conf & /etc/initiatorname.iscsi) Igor. > >Hi All, >I just discovered this project a week or two ago - it looks like it will >do exactly what I want but I've yet to get it to work properly. >Here's the scenario: > >IBM HS20 Blade Server (BroadCom 57xx NIC, firmware 3.21) >SuSE Enterprise Server 8 (kernel 2.4.21-215-SMP) >iSCSI storage from a FalconStor IPStor storage server > >The storage volumes can be mounted fine from a non PXE booted machine so >I know the iSCSI end works. At the moment I'm getting a kernel panic >when the iscsi-init module trys to do a DHCP request. No idea why or >what to do about it, any help would be appreciated. The initial DHCP >request for the PXE portion of things works fine and all the other >kernel modules load without issue. I built the iscsi-init module on the >same machine as I'm trying to now boot with PXE/iSCSI. > >I can provide more details - let me know what would help. > >Bryn > > > >Bryn Hughes >Network Specialist >Information and Computing Services >Vancouver Community College > >ph: (604) 443-8515 >fax: (604) 443-8353 >email: bh...@vc... > > > ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 Iscsi-init-users mailing list Isc...@li... https://lists.sourceforge.net/lists/listinfo/iscsi-init-users |
From: Igor F. <ig...@ne...> - 2004-08-12 20:35:13
|
Bryn, please provide more details, such as: - iscsi-init version - linux-iscsi initiator version - kernel cmd line - dhcp config (root-path if you use it vs kernel cmd options) - an output from linux-iscsi module when it happens - an output from iscsi-init module when it loads - an output from kernel before it panics - /etc/fstab - working configuration for iscsid (/etc/iscsi.conf & /etc/initiatorname.iscsi) Igor. > >Hi All, >I just discovered this project a week or two ago - it looks like it will >do exactly what I want but I've yet to get it to work properly. >Here's the scenario: > >IBM HS20 Blade Server (BroadCom 57xx NIC, firmware 3.21) >SuSE Enterprise Server 8 (kernel 2.4.21-215-SMP) >iSCSI storage from a FalconStor IPStor storage server > >The storage volumes can be mounted fine from a non PXE booted machine so >I know the iSCSI end works. At the moment I'm getting a kernel panic >when the iscsi-init module trys to do a DHCP request. No idea why or >what to do about it, any help would be appreciated. The initial DHCP >request for the PXE portion of things works fine and all the other >kernel modules load without issue. I built the iscsi-init module on the >same machine as I'm trying to now boot with PXE/iSCSI. > >I can provide more details - let me know what would help. > >Bryn > >_______________________________ > >Bryn Hughes >Network Specialist >Information and Computing Services >Vancouver Community College > >ph: (604) 443-8515 >fax: (604) 443-8353 >email: bh...@vc... >_______________________________ > > |
From: Bryn H. <bh...@vc...> - 2004-08-12 19:18:12
|
I suppose I should add I'm using iscsi-init version 3.43. Bryn >>>Bryn Hughes <bh...@vc...> 08/12/04 12:11 pm >>> Hi All, I just discovered this project a week or two ago - it looks like it will do exactly what I want but I've yet to get it to work properly. Here's the scenario: IBM HS20 Blade Server (BroadCom 57xx NIC, firmware 3.21) SuSE Enterprise Server 8 (kernel 2.4.21-215-SMP) iSCSI storage from a FalconStor IPStor storage server The storage volumes can be mounted fine from a non PXE booted machine so I know the iSCSI end works. At the moment I'm getting a kernel panic when the iscsi-init module trys to do a DHCP request. No idea why or what to do about it, any help would be appreciated. The initial DHCP request for the PXE portion of things works fine and all the other kernel modules load without issue. I built the iscsi-init module on the same machine as I'm trying to now boot with PXE/iSCSI. I can provide more details - let me know what would help. Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ |
From: Bryn H. <bh...@vc...> - 2004-08-12 19:11:59
|
Hi All, I just discovered this project a week or two ago - it looks like it will do exactly what I want but I've yet to get it to work properly. Here's the scenario: IBM HS20 Blade Server (BroadCom 57xx NIC, firmware 3.21) SuSE Enterprise Server 8 (kernel 2.4.21-215-SMP) iSCSI storage from a FalconStor IPStor storage server The storage volumes can be mounted fine from a non PXE booted machine so I know the iSCSI end works. At the moment I'm getting a kernel panic when the iscsi-init module trys to do a DHCP request. No idea why or what to do about it, any help would be appreciated. The initial DHCP request for the PXE portion of things works fine and all the other kernel modules load without issue. I built the iscsi-init module on the same machine as I'm trying to now boot with PXE/iSCSI. I can provide more details - let me know what would help. Bryn _______________________________ Bryn Hughes Network Specialist Information and Computing Services Vancouver Community College ph: (604) 443-8515 fax: (604) 443-8353 email: bh...@vc... _______________________________ |