SUSE / openSUSEThis Forum is for the discussion of Suse 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.
I'm not sure how to interpret 394A. If this is merely a block designation in hexidecimal, then it looks like a bad block about 7MB into your XP partition. Does it make any mention as to what it is measuring? It may well be some other drive geometry measurement.
I'd recommend getting your hands on a knoppix CD for this type of thing. The SuSE install CD's do have a console on them, but it is rather limited. (alt+F9 before YaST, ctrl+alt+F6 durring - has more tools)
I think "fdisk -l" may help get geometry info. "badblocks -wvs /dev/hda" will destroy anything on the drive, but will identify any bad blocks in the process. (I mention this only because you say that you have repartitioned)
When you say YaST cannot read your drive, what does it say? Does your drive show up in cat /proc/partitions?
jlangelier: Yes, SuSE can use the mkfs command. YaST can do it for you though. Besides, he originaly was simply trying to upgrade in a working environment (SuSE has options for this) (this puzzles me a bit).
I'm taking a chance here, is there a way _after_ you discover bad blocks to fix/repair them, or just bypass them all together in the boot process? Right now, when doing a filesystem check, my Redhat finds a couple bad blocks, then offers me to fix them with fsck, i do, but then upon reboot, i have to do it all over again. I know the simple solution is to get a new drive, but is there something else in the meantime?
Originally posted by matrim I'm taking a chance here, is there a way _after_ you discover bad blocks to fix/repair them, or just bypass them all together in the boot process? Right now, when doing a filesystem check, my Redhat finds a couple bad blocks, then offers me to fix them with fsck, i do, but then upon reboot, i have to do it all over again. I know the simple solution is to get a new drive, but is there something else in the meantime?
I wish I knew more details for you. If I remember correctly, there is a spot on the drive where the filesystem keeps track of bad blocks. If a block is mentioned, the system should already know to avoid it. You should NOT need to run fsck each time you boot. Once should be sufficient (hypothetically).
The only thing I can think to check at the moment is the exit code of fsck. Imedietly after fsck finishes, try "echo $?". Compare that to "man fsck". If you can't make heads or tails of it, then post the number here.
Sorry. Maybe someday I'll know enough to give a better answer.