Fedora Linux Support Community & Resources Center
  #46  
Old 19th April 2006, 10:51 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
yes i have kernel 2.6.16-1.2080_FC5smp installed on my system now. i also did yum install iscsi-inititator-utils so what should i do next according to document.

thx for the help
Reply With Quote
  #47  
Old 24th April 2006, 03:36 AM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
plz help me wat next i need to proceed
Reply With Quote
  #48  
Old 24th April 2006, 04:06 AM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 26
Posts: 9,223
I have never used iscsi before, but if you read up on iscsi-inititator-utils it should give you some info. You can see what commands are avail. for iscsi with:
Code:
rpm -ql iscsi-initiator-utils | grep bin
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #49  
Old 24th April 2006, 05:40 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
I had update using yum and installed iscsi utils so now i
m running 2.6.16-1.2096_FC5smp.my doubt is previously i was running
2.6.15 release so i downloaded source rpm and compiled on it.
so in the same way do i need to download source code for
2.6.16-1.2096_FC5smp and compile it before running iscsi. plz let me
know this before i start.
also at
make KERNELSRC=<wat path do i need to give> previously for 2.6.15 i
was giving /usr/src/redhat/BUILD/kernel-2.6.15/linux-2.6.15.noarch/

i will wait for u r info and will start later.
Reply With Quote
  #50  
Old 24th April 2006, 09:43 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 26
Posts: 9,223
Please, as I said forget compiling. Your kernel is fully functional and the iscsi utils are now installed. You just need to configure it.
I looked at the RPM file, and you can try this for more info:
Code:
man iscsid
And from the readme:
Code:
4. Open-iSCSI daemon
====================

The daemon implements control path of iSCSI protocol, plus some management
facilities. For example, the daemon could be configured to automatically 
re-start discovery at startup, based on the contents of persistent 
iSCSI database (see next section).

For help, run:

	/usr/sbin/iscsid --help

Usage: iscsid [OPTION]

  -c, --config=[path]     Execute in the config file (/etc/iscsid.conf).
  -f, --foreground        run iscsid in the foreground
  -d, --debug debuglevel  print debugging information
  -u, --uid=uid           run as uid, default is current user
  -g, --gid=gid           run as gid, default is current user group
  -h, --help              display this help and exit
  -v, --version           display version and exit
That shoud give you a start...
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)

Last edited by Firewing1; 24th April 2006 at 09:48 PM.
Reply With Quote
  #51  
Old 24th April 2006, 09:45 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
ya but when i m trying to install iscsi target (not the initiator which u are talking about)

it asks for kernel path for make .

plz tell me wat i m supposed to since i only have kernel source for 2.6.15 and not the latest 2.6.16.
Reply With Quote
  #52  
Old 24th April 2006, 11:44 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 26
Posts: 9,223
To install kernel source do:
Code:
yum install kernel-devel
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #53  
Old 25th April 2006, 04:09 AM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
when i tried /etc/init.d/iscsi-target start

it said FATAL:iscsi_trgt failed

so i did insmod of iscsi_trgt.ko file but still i got the same error message can u plz let me know wat i need to know.

for fc5 core kernel the source i guess is not in /lib/modules/$(uname -r)/build and will be in /usr/src/redhat/BUILD/kernel-2.6.115/linux-2.6.15.noarch/ so have given that path

how can i download openssl-devel installed using yum utility or where can i find in google.
Reply With Quote
  #54  
Old 25th April 2006, 05:25 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
[root@iscsi2 iscsitarget-0.4.13]# make
KERNELSRC=/lib/modules/2.6.16-1.2096_FC5smp/build
make -C usr
make[1]: Entering directory
`/home/iscsitarget-0.4.13/iscsitarget-0.4.13/usr'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/home/iscsitarget-0.4.13/iscsitarget-0.4.13/usr'
make -C /lib/modules/2.6.16-1.2096_FC5smp/build
SUBDIRS=/home/iscsitarget-0.4.13/iscsitarget-0.4.13/kernel modules
make: *** /lib/modules/2.6.16-1.2096_FC5smp/build: No such file or
directory. Stop.
make: *** [mods] Error 2


[root@iscsi2 iscsitarget-0.4.13]# /etc/init.d/iscsi-target start
Starting iSCSI target service: FATAL: Module iscsi_trgt not found.
ipc fd
: Address already in use
[FAILED]
[root@iscsi2 iscsitarget-0.4.13]#


also when i try to to yum install kernel-dlevel


[root@iscsi2 iscsitarget-0.4.13]# yum install kernel-dlevel
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
core
[1/3]
extras
[2/3]
updates
[3/3]
Reading repository metadata in from local files
Parsing package install arguments
No Match for argument: kernel-dlevel
Nothing to do
[root@iscsi2 iscsitarget-0.4.13]# rpm -q kernel-dlevel
package kernel-dlevel is not installed


also i could not find /usr/src/kernels/2.6.16-1_2096.i686


thx for all the help
Reply With Quote
  #55  
Old 25th April 2006, 05:39 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
i got them downloaded and getting no error messages. i will update as soon as i find anything troublesome
Reply With Quote
  #56  
Old 25th April 2006, 10:29 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 26
Posts: 9,223
your kernel source is in /usr/src/kernels, I think.
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #57  
Old 11th May 2006, 06:27 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
Thx a lot Guyz. I have got great help from u guys in installin iSCSI and I really appreciate a lot for all the help provided.

For now I got all the help i needed but am still in process of working on linux. So if there is no problem in still keeping this topic open then it would be grt or else if that does not sound good then you can close the topic.

Once again thx a lot
Reply With Quote
  #58  
Old 11th May 2006, 10:00 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 26
Posts: 9,223
No problem
Just for reference, can you make a short checklist of what you did so someone else in your situation can solve it?
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #59  
Old 15th May 2006, 04:55 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
Here is the entire procedure in running iSCSI: I actually wanted to attach the file but could not so I am copying it over here.


I guess this would definitely help if others are looking to run iSCSI:




Link to download IET iSCSI Target:

http://iscsitarget.sourceforge.net/

Downloaded:iscsitarget-0.4.13.tar.gz

Installed FC5 release; 2.6.16-1.2096_Fc5smp kernel

Downloaded MicroSoft Initiator also:

http://www.microsoft.com/downloads/d...DisplayLang=en)

How to use MS iSCSI initiator isfound at MS iSCSI ini user guide in same download page and went through it.



Procedure to implement iSCSI:


* Write down the IP address of this target. In my case, my box IP is
1.1.1.1.

* By using "yum" updated the kernel to
latest one available, " 2.6.16-1.2096_FC5 " and can be checked with command "uname -a"

* FC5 has built in open-iscsi INITIATOR software. Check if you have it installed
already. run "rpm -q iscsi-initiator-utils"
if u see 'package iscsi-initiator-utils is not installed', then you do
not have this package, you can install it via
"yum install iscsi-initiator-utils"
run "rpm -q iscsi-initiator-utils" again,
and I saw msg like 'iscsi-initiator-utils-5.0.5.476-0.1'.

Also make sure that you do yum for these both on initiator and target:

yum -y install kernel-smp-devel
yum install openssl-devel
yum update

and you can check kernels installed using
rpm -qa | grep kernel



* start iscsi initiator service. by run command
"/etc/init.d/iscsi start",
you should be able to see
'iscsiadm: no records found!rvice: [ OK ]
[ OK ]'

by running that script, the script will load the needed kernel modules
for you, and start the iscsid service. you can then optionally run
"/etc/init.d/iscsi status" to check if iscsi initiator service is
running, the desired message should be 'iSCSI initiator is running.'

then go to cd /sbin which has iscsiadm,iscsid etc.

Initiator name is found by typin command cd/sbin ./iscsi-iname

Note: Do not enter this command multiple times because it gives new name everytime u do it.

* run "iscsiadm -m node" and get 'iscsiadm: no records found!'. this is
a fresh FC5 installation, so iscsi initiator does not have any target
record in it.

* run iscsiadm command with right options to discovery the target. the
command i used is

"./iscsiadm -m discovery -tst -p 1.1.1.1:3260"

where "-m" specify the mode or action we want to do. here we want to do a target
discovery, so it is "-m discovery". "-st" is to execute "sendtarget"
command to ask target to return all iscsi target names available on that
target. "-p" is to specify your target ip. my target ip address is 1,1,1,1.

this is the return msg i got

[28:d97ba5] 1.1.1.1:3260,1 iqn.2006-01.iscsi1.rdmadomain:storage.root


this told us that the iscsi initiator database now has a record, with
key d97ba5. so later we can use this key to identify the target in
related operations. also the target ip is 1.1.1.1. port is 3260.
ignore the 1 here, the target name is
iqn.2006-01.iscsi1.rdmadomain:storage.root. this should match the
target name u see in MS iSCSI initiator if you tried that or in linux iscsi initiator.

* we already discovery the target. so now it is time to connect. run


"./iscsiadm -m node --record d97ba5 --login"


this d97ba5 is the record key we got in
last step.

This command simply return and display no more message. i can find out more by running
"dmesg", it return me this

'scsi0 : iSCSI Initiator over TCP/IP, v.0.3
Vendor: IET Model: VIRTUAL-DISK Rev: 0
Type: Direct-Access ANSI SCSI revision: 04
0:0:0:0: Attached scsi generic sg0 type 0
SCSI device sdb: 134217728 512-byte hdwr sectors (68719 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 00 08
SCSI device sda: drive cache: write through
SCSI device sda: 134217728 512-byte hdwr sectors (68719 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 00 08
SCSI device sdb: drive cache: write through
sdb: unknown partition table
sd 0:0:0:0: Attached scsi disk sdb'

this told me that there is a new scsi device found by system. it is a
"direct access" type scsi device, or simply, a scsi disk type device.
the device attached to system as SDB. it has 68719MB capacity. The write
protection is off so this mean we can write to disk as well. 'unknown
partition table' told us that this is like a brand new disk without any
partition information on it"

!!! when u try this, if you already have scsi disk(s) in your system,
you might see sdb, or sdd, or any sdX in the message. be sure to
remember this name.

* so till now, we already run the open-iscsi, connect to target system,
and get an iSCSI disk. this iscsi disk will behave like a normal SCSI
disk in our system.

* for most users, we need to partition it, make a file system on it, and
then mount it somewhere before actually use it.

!!! before you do fdisk and mkfs on that SDB, you need to replace it
with the name you get. if you happen to have a real physical SCSI disk
in your system already and you still use sda here, you can ruin your
existing data.

* linux use "fdisk" to partition a new disk. this only need to be done
once for most users. "man fdisk" or "info fdisk" to get more information
about how to use fdisk.

fdisk /dev/sdb1

* assume u already create partitions like /dev/sdb1, /dev/sdb2,... in
last step. u need to make a file system on it. still "man mkfs" or "info
mkfs" will give you enough information on create a file system. the
simplest way is to run

"mkfs /dev/sdb1"

which will use a default file
system (it is ext2 in most of the time)

* now choose a place to mount it. "man mount" and "info mount" will give
you enough information on how to do mount. a typical command will look

like "mount /dev/sdb1 /mnt".


*Check fdisk -l which shows wat all devices are connected and df -h which gives wat all devices are mounted.



In Target Side create a new file:

vi /etc/ietd.conf and then type


Target iqn.2006-01.iscsi1.rdmadomain:storage.root
Lun 0 Path=/dev/sdb,Type=fileio
Alias iSCSIAlias
ImmediateData Yes

Note: Make sure there are no spaces.


Make sure you see the target device on target machine:

cat /proc/net/iet/volume and i got output like:

tid:1 name:iqn.2006-01.iscsi1.rdmadomain:storage.root
lun:0 state:0 iotype:fileio path:/dev/sdb



On Initiator Side if running in Linux then create:

vi /etc/iscsi.conf and type
DiscoveryAddress=1.1.1.1

Note: that is target's ip address


when installing Target iSCSI give kernel path as


make KERNELSRC=/lib/modules/2.6.16-1.2096_FC5smp/build/

Final step:

1) Start target and initiator
2)do not mount anything on target and make sure u see target scsi devices on the initiator using fdisk -l command
then if u want to copy anything into target scsi device from initiator then mount it on initiator.

copy it and unmount it on initiator.

3)to see the copied file go to target machine and mount it and u should be able to see the files copied.



When using microsoft iscsi initiator make sure that u start the service from :

start->programs->administrative tools->services-> and choose and double click Microsoft iSCSI Initiator service in it and choose Automatic option in Startup type shown in general window.

Once u do that open MS iSCSI and go to deiscovery tab and add the target device ip,port. i.e, 1.1.1.1 and 3260

then go to targets tab on the top and click on LogOn which shows connected at status on window and if u want to logoff that go to details and then choose and click logoff .


Then right click "My Computer" and click "manage" and choose "Storage" and then " Disk Management" and you should be able to see the target device.
Reply With Quote
  #60  
Old 15th May 2006, 04:58 PM
rahulgandhi Offline
Registered User
 
Join Date: Apr 2006
Posts: 58
One other help i need if possible from u guyz is how to install IO meter and Dynamo (related to IO Meter) on Fedora core 5 machines running latest 2.6 kernel.
Reply With Quote
Reply

Tags
core, fedora, upgrade

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrade from Fedora Core 1 to Core 5 nava Installation, Upgrades and Live Media 4 21st June 2006 03:54 PM
upgrade via yum frmo fedora core 2 to fedora core 3 ccole Installation, Upgrades and Live Media 1 4th May 2005 05:21 AM
Upgrade from Fedora Core 1 to Core 2 jayeshrode Installation, Upgrades and Live Media 2 8th June 2004 05:30 PM


Current GMT-time: 13:46 (Tuesday, 27-06-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat