Re: Root partition on ext3 totally damaged (total frustration)
From: Jean-David Beyer (jdbeyer_at_exit109.com)
Date: 10/21/04
- Next message: Christopher Browne: "Re: This is the FSF's formal response Re: Distros and "Mere Aggregation"."
- Previous message: ray: "Re: [OT] GAWK question."
- In reply to: Massimiliano Adamo: "Root partition on ext3 totally damaged (total frustration)"
- Next in thread: Lawrence DčOliveiro: "Re: Root partition on ext3 totally damaged (total frustration)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 20 Oct 2004 23:07:51 -0400
Massimiliano Adamo wrote:
> Hi all.
>
> Yesterday I have shutdown Linux, without having any problem.
> Today I went to boot the machine, but I'was asked for root password, for
> maintenance reasons, on the root partition.
> It was a long time, that I didn't see this prompt, so I tought: it will
> be for the ususals 4 files damaged .....
> The filesystem is EXT3 (I hate that days when I decided to move to ext3).
>
> fsck says immediately that there are thousands of file damaged, and I
> have to use "-p" option to autocorrect, but there are too many
> incosistences and "-p" doesn't work. I try "-y" and it works fine.
> I wait for all operations to be finished, I reboot the system, and the
> system doesn't restart anymore (init not found and so on. before reboot
> I understood that there were thousands of file damaged: libraries and
> lot of binaries).
>
>
> What can I do?
Run badblocks on the partition in question, and if it is bad, buy a new
hard drive and restore all the files from your most recent backup tape.
If it tests good, just restore and reformat (mkfs) that partition and then
restore just that partition from your most recent backup tape.
>
> I could decide to never use EXT3 for the rest of my days, but that's not
> the point.
I have been running EXT3 since RHL 7.3 I think it was. I never had any
trouble with it. Of course, I never had any trouble with EXT2 starting
with RHL 5.0 either.
>
> The point is that the system is not liable at all and this a very bad
> news: I never saw a problem like that, even with FAT32 in Windows 95!
>
Either your processor, memory, disk controller, or hard drive is in
trouble. Or maybe loose cables or spikes on the power supply output. Have
you a UPS or serious surge protector properly connected to your computer?
>
> Again: what can I do now?
> for a short time I have used XFS (from Irix), and it looked to be nice,
> but kernel compilation with patches and support were not that nice.
>
> I could use JFS or reiser .... but, be honest with me: if you encounter
> a problem like that, will you still entrust the system that you are using?
>
I would not trust your system with any software until all the hardware
(including connecting cables) is checked. Then replace any defective
components and restore from your most recent backups.
-- .~. Jean-David Beyer Registered Linux User 85642. /V\ Registered Machine 241939. /( )\ Shrewsbury, New Jersey http://counter.li.org ^^-^^ 23:00:00 up 5 days, 10:31, 3 users, load average: 4.30, 4.23, 4.24
- Next message: Christopher Browne: "Re: This is the FSF's formal response Re: Distros and "Mere Aggregation"."
- Previous message: ray: "Re: [OT] GAWK question."
- In reply to: Massimiliano Adamo: "Root partition on ext3 totally damaged (total frustration)"
- Next in thread: Lawrence DčOliveiro: "Re: Root partition on ext3 totally damaged (total frustration)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
