Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Did you let the Linux form the LVM using the two disks?
LVM is a manager layer that will handle the filing systems in side the LVM. THus sdb1 may be a device but it may be under the LVM control and not you, as you could have given up the previous control by telling Fedora "yes, go ahead, use all my disk space and disks to form a LVM". If this is the case you need to break up LVM to free sdb1.
but thats just the thing. I did not create using all free space. I set it up manually, so as not to touch this drive. And if I attempt to follow the directions for breaking up an LVM, it doesn't appear to be in the LVM. It seems to belong to nothing. Where is the LVM information stored? Is it on the drive or is there a record on the system drive? Can I just physically pull it , and format it ntfs to wipe this and reattach it and follow the given directions for initializing it as a vfat drive?
Wow this is driving me crazy!
Ok it took a little while I wanted to download the new knoppix...
that done I was able to issue the mkdosfs command. I was not able to mount it however. I came back to FC6 and it looks like not much has changed, it is still "not a valid block device" yet it is not a Logical Volume either. I have never been able to get this mounted since I purchased it, is there a hardware issue here?
I don't think it is a hardware issue. Your sdb is usable in another Linux, right? That proves it is OK.
I suspect it may be to do with the way you have set up the LVM making FC6 regarding sdb as under the LVM control. LVM is a managemant layer you introduced into FC6. You may be able to access it via the LVM's own commands/tools. I don't use LVM because and so cannot advise.
Is your sdb a Sata II hard disk that the mobo is incapable of supporting? Older mobo support older Sata I and may not be able to read a Sata II, no matter what system you use. If your Sata stamped with a 1.5Gb/s it is a Sata I. Sata II doubles it to 3Gb/s.
You can prove it easily by open up the box, pull off the electrical power to the other disk and see if XP installer can install on this new Sata disk.
Ok... I took it out to look at, and it seems to be a SATA II drive, that I have restrained to 1.5 Mb/s with a jumper. I dont think it is a M/B issue as the SATA controller recognizes that I have 2 SATA drives on POST. Do I need some kind of kernel support or the like??
Well I can not access the drive at all. No matter what I try it will not let me in. I didn't change the SATA setting either. It was set to 1.5 at the factory, so that is not the issue. Any other ideas ?