Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I have been banging into the wall on this over and over and it's starting to hurt.
I have installed SUSE LINUX ENTERPRISE SERVER 10 SP1- (SLES SP1) and am attempting to setup iscsi connectivity to our SAN. I've been successful in setting up the target and connection. Assigned a volume and even set it up utilizing LVM. I was able to see it at the mount point and write to it.
The problem always starts when I attempt to restart the server. At Checking file systems it fails on the new LVM Volume that is on the iscsi connection. I'm assuming this is because iSCSI isn't running yet, then goes into maintenance mode.
The iSCSI Target and Initiator where set for automatic startup, but I found that this only refers to when the service is started they will automatically start the connections.
I've been searching for some type of document or instruction on this specific problem, but to no avail. It's hard to believe that I can be this uniquely stupid!! (But I won't put up to hard of a debate if I can get some help) Thank you in advance.
Your advice regarding the fstab However, that option doesn't have any effect at all in SUSE Linux since the distribution has no netfs script anymore. Instead, SUSE steers the users to use the hotplug functions controlled by the HAL system.
The document I referenced above is helping me to guide my way through this issue. It's been a long time since I've had to work to learn something new, it's great.