Re: ack! help!!!! something went dreadfully wrong!
Tobias Schlottke <[email protected]> Fri, 9 Jan 2004 09:21:09 +0100
| Newsgroups | gmane.linux.debian.kde.cvs |
|---|---|
| Organization | Virtual Minds AG |
| Message-ID | <[email protected]> |
Hi Sav, nice that you've got your system working again but I think your theory doesn't make sense at all (sorry ;)). I still believe that your harddisk is the one to blame, it's got some serious problems and you should replace it asap. The reason why it's working atm is (like someone else said before) that you reinstalled all files that where on the damaged sectors of your harddisk and placed them on other sectors - You'll get those errors again if you write onto those sectors some day, I'm nearly sure. Well, you may be lucky :) Have fun! Tobi On Freitag, 09. Januar 2004 03:12, Savanna wrote: > thanks. =) > > yes, but i can't get a hard drive right now because it's late and i > probably am going out tomorrow night and stuff (and seeing lots of friends > this weekend too) so i might have to put it off till monday i think. either > way, my system is up for now. it appears stable and works very well as far > as i can see. i have all the nice little addons like bouncing cursors when > i open an app, new themes, and stuff like that. so it appears to work fine > and *no* error messages whatsoever. > > here is what i think happened: > > i think that when i upgraded last night, i had such an old kernel that it > must have upgraded some drivers i couldn't use. > > when i installed kde last night, it installed them using those drivers and > thus, the problem emerged. i think that it may not be the hard drive at > all. > > after i installed the new kernel today, it still wouldn't work, but that's > because it was using the *old* configs. when i uninstalled kde completely, > and reinstalled it from scratch, it fixed itself because the new drivers > were put in place with the new kernel (2.4.23 on debian) and thus, the > problem was solved. that's the only reason i can think of that it's running > right now. if it really was the hard drive, it wouldn't be running and it > would still give me errors, right? i mean i didn't actually *do* anything > other than upgrade the kernel and reinstall from scratch. that wouldn't fix > a hardware error like that, would it? > > anyway, tell me what you think? does my theory make sense? if it does, then > it isn't a hardware problem like i thought it might not be =)