Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Thanks in advance for any advice you can give me with this problem, I've hit a brick wall and need help!
This is the test setup:
--iSCSI target/server: Sharing 400GB raid1 via iSCSI, using an Open-E module.
--Laptop: WindowsXP and MS iSCSI initiator (driver), works flawlessy. Drive was mapped and formatted in minutes.
--1u Server: RHEL 4u1 64bit, tried a variety of initiators, none even come close to compiling properly.
Initiators I've tried:
--linux-iscsi : Compilation failed - reason still unknown
--Open-iscsi: Compilation failed - requires kernel 2.6.11-x, I have 2.6.9-11.
--UNH-iscsi: Compilation failed - x86_64 platform unknown, despite the fact I have all 32bit compat libraries installed.
Now if my clients servers were xp/w2k3 then there wouldn't be a problem (I hate it when MS get it right), but they have RHEL 64bit servers. I really need to find an initiator that will compile and function properly in RHEL 4u1. The problem with a few of the compilations seems to point towards incompatibilty with x86_64 architecture or kernel version; but I have all the compat/32 bit libraries and apps installed that I can find, and I dont know where to start to upgrade the kernel past 2.6.9-x.
Is there anything I can do to find out if 32-bit compatibility is available on my OS, and will kick in when required?
Does anyone have any pointers regarding compilation of 32 bit apps for 64 bit OS'?
Anyone have any tips for setting up an iSCSI environment?
Have you tried the packages included with RHEL? I think its something like iscsi-initiator-utils. I've run in CentOS 4 in VMware(32 bit) and it worked fine for my (extremely small and simple) tests. And CentOS's website shows there as being a package for x86_64. Here's a readme thing for it: http://people.redhat.com/mchristi/is...EL4/doc/readme
And I'm not sure how well running any of the iSCSI stuff as 32 bit on a 64 bit OS would work. I'm thinking that they use some kernel modules so I would almost presume that it probably wouldn't work too well, but I don't know that for sure.
I did a fresh install of 4u2 and found the iscsi-initiator-tools, which has done the business, after a little tweaking. I never noticed the option to install the tools when installing RHEL 4 or 4u1, but I might do an install just to check at some point. New rpm for 4u2?
If I install the initiator (plus dependancies) on a complete 4u1 machine, with the RPMs from Redhat, it has problems finding a module of some kind and cant start up. But maybe the best option is to update any 4u1 machines to 4u2, and try to add the iscsi-initiator-tools as part of the update...testing req'd I think.