Re: please help, lost my partition
LeVA <email@example.com> writes:
> I lost my partition. One of my most important ones... It is a 100gb
> partition with all my personal datas, emails, documents etc...
You might be better off, given what you describe, getting a new hard
drive and then restoring the data from backups.
> I had a crash in kde, and I had to reset the computer. After the boot, the
> boot process said that it can not mount /dev/hda2. Unfortunatelly, I can not
> write you exactly the output, because I can't copy/paste, so I have just my
> brain to remember the lines.
> It says Can't find ext3 filesystem on dev ide0(3,2).
> mount: wrong fs type, bad option, bad superblock on /dev/hda2,
> or too many mounted file systems.
"It broke." This "shouldn't" happen if you're using ext3; if the
system spontaneously crashed, the filesystem should be more-or-less okay.
> But then probably I made a huge mistake: typed fsck /dev/hda1. It
> asked me a lot (realy lot), so I ctrl+c'd, and typed fsck -y
> /dev/hda1. It worked a lot (20-30mins), and wrote a lot of things,
> like bad imagic number (or like that), and wrong inode etc... but
> the question was always the same: Clear?<y>. I couldn't choose. Yes,
> clear... After fsck finished, I had a still unusable partition,
> could not mount it, and couldn't fix it, because after that, every
> time I typed fsck /dev/hda2, it said can not find superblock,
> specify another superblock with -B option. I tried a lot of number
> but neither of them worked. So I lost that partition.
When this happened on my laptop, I really strongly suspected bad
hardware. I eventually came to the conclusion that, sometimes, bit 2
on the IDE channel was getting set to zero, regardless of what it
should have been, and this was somewhat unsurprisingly nuking
important filesystem data. Given that you've had similar problems
with this hard drive before, I'd really strongly suspect hardware
> When I type cfdisk /dev/hda it can not detect that /dev/hda2 is an
> ext3 fs, so under the FS Type column it writes Linux, instead of
> Linux ext3.
Linux pretty much ignores the filesystem-type word in the partition
table. Also, ext3 *is* ext2, just with an added journal file. So
this isn't really indicative of anything; you'd get the same results
on a healthy system.
David Maze firstname.lastname@example.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell