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.
I've downloaded and installed kernel-image-2.4.27-2-586tsc.deb onto my Debian Woody box. However, when it boots up, it tries to read the hard drive as if it had the ext3 file system. I configured the hard drive to have an ext2 filesystem (for speed). So, when it boots, it repeatedly reports that it cannot read the disk (there are numerous disk time-out errors, 0x21), and (after about five minutes) quits, tries, and succeeds at reading the hard disk as ext2. I probably will never have an ext3 filesystem on the Debian Woody box (it's way too slow to have a journalised filesystem).
Anyway, how do I configure the kernel to automatically read my hard drive as ext2, rather than wait each time I boot for it to fall back on ext2 (after reading as ext3 fails)? My /etc/fstab describes the root partition (the only storage partition, aside from swap and proc) as having the ext2 filesystem, with "defaults" options (I've tried "noauto" and "errors=remount-ro" with no success). I've tried modifying the "append" stanza of the default image in /etc/lilo.conf and running /sbin/lilo -v with the options "root=/dev/hda1, rootfstype=ext2," but without success. The kernel loads the ext2 module during boot already. I've tried dpkg-reconfigure kernel-image-2.4.27-2-586tsc after setting the appropriate configuration options in /boot/config-2.4.27-2-586tsc (CONFIG_EXT3_FS=n, CONFIG_EXT2_FS=y), but with no success. With each boot, root is mounted as cramfs ("MKINITRD='mkcramfs %s %s > /dev/null" is set in /etc/mkinitrd.conf; I couldn't get the mkfs.ext2 script to work when making a new initrd.img file).
Where did you get the idea that ext3 is slower? Despite writing some data more than once, ext3 is often faster (higher throughput) than ext2 because ext3's journaling optimizes hard drive head motion.
Personally, I would never use ext2 for my root partition. But hey, it's your computer.
You don't need an initrd for an ext2 file system, it should be supported by the kernal by default.
The kernel is expecting to see the root file system as ext3 because normally nobody would use ext2 for this. As this is something that practially nobody does, I'm not sure what the answer would be. I'd highly recommend using ext3 or reiserfs for your root partition as they are more efficient and make recovery from an unclean shut down much faster.
Very well. Reformatting to ext3... (I read at wikipedia that journaling file systems tend to be slower because they need to write metadata AND data, whereas non-journaling file systems don't. The computer I'm using is slow enough )
The funny thing is that I've tried taking out the "initrd=..." stanza in the image configuration and running lilo already. I get a kernel panic --it says it can't find the root filesystem.
Okay, I reformatted the partition as ext3, but I still get weird errors when reading my hard drive at boot. I get a "late registration of driver" error, and then a bunch of DMA errors (type 0x21). Once they complete, the filesystem loads. How do I fix this?