Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i have connected my laptop to a iscsi target and mount the filesystem and put entry in fstab so it will mount again after boot,i have done chckconfig iscsi on.chkconfig iscsid on.
but when i reboot the machine and use :
df -h it dosent show my mounted iscsi target partition .
also,when i use
Code:
service iscsi status
it shows iscsi stoped although i have chkconfig the iscsi service.
same problem comes in case of nfs server,i have mounted the nfs shares to my laptop but again after reboot mount point gone .
due to which i have to mount the partitions again and again.
I do not suppose you could post your fstab file, or your output from chckconfig showing your settings for that service, or what DF or MOUNT return when you DO have things moounted?
Could you tell us what distribution and version number you're using? I'm just taking a hopefully educated guess.
In Fedora if the system was installed on a local disk and iscsi setup later the iscsi entry in the fstab will try to mount before the iscsi service actually starts (this happened to me in Fedora 14 and 15). So if your iscsi service is running correctly you'll have to mount the device later in the start up routine or manually. For the time being I put a mount command in /etc/rc.local (not ideal, but it works.)
Could you tell us what distribution and version number you're using? I'm just taking a hopefully educated guess.
In Fedora if the system was installed on a local disk and iscsi setup later the iscsi entry in the fstab will try to mount before the iscsi service actually starts (this happened to me in Fedora 14 and 15). So if your iscsi service is running correctly you'll have to mount the device later in the start up routine or manually. For the time being I put a mount command in /etc/rc.local (not ideal, but it works.)
In addition to this, make sure that fstab is exuted when the iSCSI client is started and the network is available. This means you should check the order of starting these services during booting.
Could you tell us what distribution and version number you're using? I'm just taking a hopefully educated guess.
In Fedora if the system was installed on a local disk and iscsi setup later the iscsi entry in the fstab will try to mount before the iscsi service actually starts (this happened to me in Fedora 14 and 15). So if your iscsi service is running correctly you'll have to mount the device later in the start up routine or manually. For the time being I put a mount command in /etc/rc.local (not ideal, but it works.)
i am using red hat enterprise linux 6,i am preparing for the red ha exam.
but when i reboot my machine and check the iscsi service ,it shows iscsi service is stopped although i have chkconfig the service.
Alright. I'm working with Fedora so this might not be exactly correct but it should be.
Two services actually manage the iscsi protocol, iscsi and iscsid. The iscsid is the one that should be running when you check it with a /etc/init.d/iscisd status. I think the iscsi is only around for start up stuff (not 100% sure on that one.) Obviously if you haven't ckconfiged iscsid you'll want to turn that on as well.
Alright. I'm working with Fedora so this might not be exactly correct but it should be.
Two services actually manage the iscsi protocol, iscsi and iscsid. The iscsid is the one that should be running when you check it with a /etc/init.d/iscisd status. I think the iscsi is only around for start up stuff (not 100% sure on that one.) Obviously if you haven't ckconfiged iscsid you'll want to turn that on as well.
no,again it dosent work for me,i have chkconfig both iscsi and iscsid but nothing works,main prob is when i reboot the machine and try to find out the status of iscsi service it shows service iscsi stoped although i have chkconfig the service ,yaa but iscsid service is running after chkconfig .
no again same result ,it says iscsi service id stopped ,is there a difference between chkconfig iscsi on and chkconfig --level 2345 on???? i have applied both but no result found
Last edited by magicalshashank31; 08-04-2011 at 01:05 AM.
Can you post your iSCSI client config? fstab is not really important as it will only call the block device to mount. The iSCSI service will attach the LUN to you distro as a block device. So if an iscsi service is not starting, then there must be an issue with your configuration or the boot order. To check the boot order you need to post the headers of the init scripts of fstab, iscsi and network.
By the way, are you trying to connect to iscsi over wlan? Because if so, that won't work when you are using NetworkManager to control your wireless network. When using NetworkManager you will only acquire a connection to the network when you log in to your laptop, not during booting.
The guy is telling you the service is stopped, and ON on all runlveles, and you are answering chkconfig !!!!
I have the same case if anyone has the right answer please post.
@nhajji : it is unclear exactly who you are being critical of.
The OP has not responded with all of the requested information. Nor has there been any reply to the last advice from Blue ICE. Until the exact situation is clear it will be difficult to provide exacting advice. Chill.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.