• Feeling isolated? You're not alone.

    Join 20,000+ people who understand exactly how your day went. Whether you're newly diagnosed, self-identified, or supporting someone you love – this is a space where you don't have to explain yourself.

    Join the Conversation → It's free, anonymous, and supportive.

    As a member, you'll get:

    • A community that actually gets it – no judgment, no explanations needed
    • Private forums for sensitive topics (hidden from search engines)
    • Real-time chat with others who share your experiences
    • Your own blog to document your journey

    You've found your people. Create your free account

A Harddisk Drive error ?

GoofKing

All your bases are belong to us
Okay, so after rebooting my computer (or pulling the power plug from behind) after Debian seemed to freeze when watching a video, the whole thing seemed to have died on me.

It got so far as to FSCK disk check part of the startup and it gave an error I think about the disk already being populated or not being able to be populated as well as the screen turning off with an orange light.

I've tried reinstalling Debian but it did the same thing. In fact, Slitaz Linux is the only distro that doesn't do the weird thing that Debian did. I was thinking it was because I installed a LVM filesystem type and that it was too much for the disk to handle. This had it's own /home and / partition and the usual swap as well and I'm also thinking that because the disk has about 23 bad sectors, that something tried to write to that bad area and boogied everything up ...

Well, now it doesn't seem to want to boot even Slitaz 5.0 RC2 in live CD mode. I'm confused as heck and not sure if it's my RAM, disk or something in Debian and the new 7.7.0 that's it's not liking :(

I'm hoping someone might help point me to a resource or try to help figure out this problem because I hope it's not my disk failing or dying one me :|
 
I dunno if this would help, but here's the log

Code:
Checking filesystem on : /dev/sda1
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1: 94856/610800 files (6.9% non-contiguous), 951622/2441216 blocks
Remounting rootfs read/write...
 
Have you checked all your connections and cables? They sometimes seem to work loose after a while
 
Hmmm. It doesn't sound good. If it were my drive I'd probably be inclined to strip it and do a low-level format...just to determine/reassess how many physical bad sectors the drive actually has.

Then repartition the drive and attempt to reinstall the OS. Assuming of course you can format from a boot disk to begin with....if even possible. One thing for sure, once you have physical bad sectors on a hard drive, it's simply a matter of a rate of decay. An inherently unforgiving process.
 
Last edited:
Top Bottom