Suse/NovellThis Forum is for the discussion of Suse Linux.
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.
It is important to know which device node is used for the drive. Since you said it is SCSI, I would assume /dev/sdb.
You can find out if /dev/sdb1 is correct by typing 'fdisk -l' as root. This should show all recognised disks and the device names.
If there is only one partition on the drive, try to add the following line to /etc/fstab:
You need to create the mountpoint (mkdir </path/name>) and specify the correct filesystem (ext2?). On the next reboot it will be mounted automatically, to mount it without reboot type 'mount /dev/sdb1'.
Don't do that!
This would mount your new harddrive as root filesystem with (probably) nothing on it. The '/' (root) contains the whole Linux structure and if you mount an empty HDD as root filesystem, you will end up with a disfunctional system.
I guess you want to include the new drive as some kind of continuous extension of the current space. AFAIK this is only possible with some kind of RAID setup (no expert here, sorry). However, in a simple case, you just need to create a new mountpoint (e.g. /data) to make the new space available under this folder. The line in /etc/fstab would look like this:
/dev/sdb1 /data ext2 defaults 0 2
The last number controls the checking of the filesystem (fsck). According to 'man fstab', '1' is used for the root-filesystem and '2' for all others. '0' would mean 'no check'. The other value ('0') controls something called 'dump' of which I have no idea what it does. So just leave it '0'. For additional options, see 'man mount' and 'man fstab'.
Yes, that is correct. I only want this disk to be an extenstion of the current disk. I'm just looking for added space. Right now the current disk is about full and I'm tried of just trying to delete stuff. 6G isn't enough these days in an office environment anyway.
I don't have a RAID setup in this server and I don't plan to do so.
It makes sense what you're saying, but before I go and try this, wouldn't the new disk need to have a /data partition setup before I can mount it?