Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
This is about trouble reading files from a particular partition. The volume is my home directory from the prior (now deleted) Fedora 9 system. Linux doesn't list the partition in /dev/disk/by-uuid. When I try to fsck it, I see a report that there are problems and a check is forced. Then after a while fsck asks to make some changes and after making them it seems to finish successfully. But when I mount the volume there is gibberish for file names. Now the first time fsck reported errors I was surprised. The drive had been closed down properly I thought and had been working in the prior system. So I booted Knoppix and saw similar gibberish when the partition was mounted; and I ran fsck there for the first time. It forced a check and when it was done, I mounted the partition and all the file names appeared. But when I mounted it in the new distributions both had the problem as described above. When I reloaded Knoppix again, the files were there without fsck.
Originally I was running Fedora 9 and decided to try Fedora 10 and Ubuntu 8.1. Also I've reinstalled Ubuntu 7.1 which I used before Fedora 9 and the same problem appears there. So Ubuntu 7.1, 8.1 and Fedora 10 have problems with the partition but not Knoppix??
My hardware is an Asus M2n-SLI. It has the nforce 570 chipset. Lspci reports it as MCP55 SATA controller. This board also has a JMicron 20360/20363 hot-swapping controller and I've gotten the problem with both. The hard drive is a SATA I Maxtor-Maxline III Model 7L300S0. The drive is in a Supermicro hot-swapping box.
There are several inconsistencies that require clarification. Your mtab and fstab do not make sense if they are from the same running distribution. sdb5 appears to be swap in one and vfat in the other. sdb1 appears to be root in fstab but sda1 in mtab.
How many physical disks are attached to the computer? As posted from the output of /dev/disk it only appears like one. From the output of mtab is appear that you have more then one. If only one then what is the output of the command
fdisk -l (must be root and that is a small L)
My guess is that /home/antbat is a partition label and has nothing to do with how it is actually mounted. You can verify with the e2label command. And do not run fsck on a mounted partition.
Thank you both very much. I didn't see that mtab had the drive as vfat. Using "mount -t ext3 ...", it now mounts correctly manually. I wonder why it's vfat but I'm sure an entry in fstab will fix everything.
To answer your questions, MichaelK: Fstab and mtab were from the same distribution but different runs. There were two physical drives on the computer, (1) the system drive, a true SCSI on an Adaptec controller card and the problem drive on one of the board controllers. I remember trying it on different slots in the drive box to try both controllers and also maybe ran the system without the problem drive and hot-plugged it. I can't post new examples because I reinstalled 8.1. I appreciate your explaining about the /home/antbat label. It did verify with e2label.