DebianThis forum is for the discussion of Debian 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.
Well in future, it's always a good idea to keep your old kernel around (and bootable) for just these kinds of occassions. Mind you that doesn't help you now.
Is your primary hard disc IDE or SCSI? If IDE, did you make sure to compile IDE support monolithically into the kernel? It looks like you did but I'm making sure. Did you also compile your primary filesystem(s) monolithically into the kernel?
Originally posted by adz Is your primary hard disc IDE or SCSI? If IDE, did you make sure to compile IDE support monolithically into the kernel? It looks like you did but I'm making sure. Did you also compile your primary filesystem(s) monolithically into the kernel?
yes and yes
actually, the default bootloader debian installed for me was grub.
i installed lilo manually and i swear i did setup an emergency kernel however even thats not booting but its error is completely different.
Have you tried to install a different distro since this error occured? If More distros report such errors then it's probably hardware. It's funny how the hardware can shit itself just when you change around the software.
There is no error like that with kernel 2.6.5, it just lists the drive specs.
I am able to boot into the system with the debian 2.6.5-1-k7 which is pre-compiled by debian but now i think i screwed up my kde cause that just sits there saying "intializing system" crap so i did a gnome terminal and did startkde and noticed it was giving tons of warnings about not being able to load ICONS from the /usr/share dir.
you know what also on a side note I always knew my HDs were crammed on each other and they might be causing heat So i removed the floppy drive completely and put the first hd where the floppy disk used to be. a bit more ream for cooling.
by the way, this is on a new MSI KT600 mb which has SATA however SATA is disabled.
If you have even the possibility that your HDD is beginning to fail (the fact that it works in Windows is no proof of continued stability), and you have one Linux boot that still works, I would seriously consider backing up important data while you have the chance before it stops working.
Partition Magic will claim to fix errors like the one you show (this has happened to me), but it won't/can't (it claims to work with ext3 partitions, but this is not true; the only Linux filesystem PM works reliably with is ext2).
The drive may be OK as a whole, but that partition is likely borked. I would suggest backing anything necessary off of it ASAP, because there's a fairly good chance that the error will migrate to your working boot, and you'll be forced to reformat the partition in any case. I think you ought to do so anyway, while you still have a modicum of control over the situation.
I'd go a little further even. I'd back up everything valuable and DEFINETLY format the partition. It looks like that partition (at the least) is cactus. You can try a shutdown -Fr now which will reboot and run fsck on startup. That may fix you up or give you some idea of what's going on.