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'm having problems installing redhat 7.2. A little background......
I'm trying to do a dual boot with win 98 (i used fips to create a second partion). I ran the installation, things were going dandy, until it started checking for bad blocks before formating the partitions i'd made with diskdruid. It froze...after an hour of nothing happening, i rebooted the machine, started installation again. Again, things went well until it tried to format the partitions (i didn't use the 'check for bad blocks' option this time). I got an error that the partitions couldn't be formatted for some reason or another (should have written it down, but didn't...). I wiped the whole drive away. formatted, removed all partions with fdisk, created a new partition with fdisk, etc etc. When I tried to install RH a third time I got the following (this is the last few lines):
RAMDISK: Compressed image found at block 0
invalid compressed format (err=2)Freeing initrd memory: 2046k freed
cramfs: wrong magic
isofs-read.super:bread failed dev=09:02, iso_blknum=16, block 32
Kernel panic: VFS: unable to mount root fs on 09:02
and it freezes. i formated AGAIN, fips, etc... got the same error. I'd been looking around and saw someone was having the same problem when installing RH 7.2, they said that after restarting the system several times, it eventually worked. Thats what I did. Now before it does ANYTHING I get:
I used this set of cd's on my old box, and with the exception of having to do things from the floppy and in text install, it worked fine. My roommate used this set to install it on her machine, and it worked fine....
So, to sum it all up, i'm stuck. Would scrapping the dual boot and going to just RH help? Is it my drive? Is it my mobo (i'm using AOpen AX59Pro - which isn't listed anywhere - that i can find - on the RH site as being supported)? Should I download a different iso from RH or go with a different distro altogether?
Any help would be greatly appreciated and sorry for the longwinded post!
Don't want to discourage you, but I had the same problem myself and ended up returning my hd for a replacement.
The crc (cyclic redundancy check) is an automatic error-checking method used by MS-DOS when writing data to a hard or floppy disk. When MS-DOS later reads data from the disk, the same erro-check is conducted, and the results of the two checks are compared to make sure that the data hasn't changed. This error signals serious problems with the disk. Obviously during the crc process your system is detecting problems.
arg, that doesn't sound good. Is there any way I can double check that the hd is bad? Its a new hd, so I shouldn't have any problems replacing it, but I'd rather not have to go through the ordeal of getting it replaced.
I don't think the hd is physically bad. Is just that after so many attempts to install/uninstall wahtever data this check is using to perform the redundancy test got corrupted. My drive I was telling you about was also a brand new Maxtor, and I was having some problems during the install that I re-install about 8 or 10 times before I got the crc error System halt. Not sure at what point the redundancy test kicks-in. So I'm not sure of what other test besides scandisck you can do.
hmm, mine is Maxtor as well. Perhaps Maxtor is just silly that way with some drives? In any case, thanks for the help and suggestions. I appreciate it! I may just install it on the other box and play around that way. Again, thanks for the help!