FedoraThis forum is for the discussion of the Fedora Project.
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've had a number of problems with disk access while trying Fedora Core 2...
P3-600 on Gigabyte BX2000+ mobo - 256meg RAM
Maxtor 40 gig drive, one partition fat32 (30 gig) bootable for Win98, rest devoted to Linux partitions
Maxtor 160 gig drive - 3 fat32 partitiions about 40g each, one ext3 partition for extra linux data
Several times, disk write errors, usually when copying large amounts of data - "fat32 filesystem panic", according to /var/log/messages , usually setting the filesystem to readonly when this happens. Sometimes it says "attempt to read beyond end of media" with the ext3 partition on the big drive. Situations usually require unmounting and corrections with fsck and/or Windows scandisk. Seems to be confined to the big drive.
Reverting to Red Hat 9 seems to cure these problems, though now I'm more tuned in to things and I may see things now that I didn't notice before.
Have tried various formatting/partitioning options - just using parted on the big drive led to conflicts in the fat32 table (not enough entries in fat for number of clusters). Using a Maxtor utility to make the fat32 partitions made them look better to fsck, then made the ext3 partition with mkfs...
Hints? (I know - dedicate a machine to Linux - maybe later)