headers
Michael | 3 Jun 2003 02:02
Picon
Favicon

partition magic messed up my magic number

Hi, 

I've been foolish enough to let Partition-Magic move/resize/etc. my partitions without a prior backup.

My ext3 /dev/hda7 (was RH 9) is no longer recognised by fsck.
I tried fsck -b 8139, 32768 and 65536 - but am not quite sure 
about if these are the right ones to try.

So far I created another partition with same number of blocks and did a backup with

dd if=/dev/hda7 of=/dev/hda8

tried 

mke2fs -S /dev/hda8
fsck.ext3 -y /dev/hda8

but this one generates a zillion of errors and quits when it's fed up. Did I forget to specify block-size (or
the like) to dd, or is that my data is plain wiped ?
Or is there still other things to try?

Quite sad I lost about 1 year of emails ;(

________________________________________
Université de Nantes, http://www.univ-nantes.fr
Permalink | Reply | 2 comments |
headers
Marcel | 3 Jun 2003 00:15
Picon
Favicon

Check - ext3 on Red-hat 7.3


Is the FSCK or e2FSCK of the linux 7.3 can be used with ext3 ?

I have a partition with erros and want to fix it how should i  proceed ?
---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.481 / Virus Database: 277 - Release Date: 13/5/2003
Permalink | Reply | 1 comment |
headers
Andreas Dilger | 3 Jun 2003 00:42

Re: partition magic messed up my magic number

On Jun 03, 2003  00:02 +0200, Michael <at> univ-nantes.fr wrote:
> I've been foolish enough to let Partition-Magic move/resize/etc. my partitions without a prior backup.
> 
> My ext3 /dev/hda7 (was RH 9) is no longer recognised by fsck.
> I tried fsck -b 8139, 32768 and 65536 - but am not quite sure 
> about if these are the right ones to try.
> 
> So far I created another partition with same number of blocks and did a backup with
> 
> dd if=/dev/hda7 of=/dev/hda8
> 
> tried 
> 
> mke2fs -S /dev/hda8
> fsck.ext3 -y /dev/hda8
> 
> but this one generates a zillion of errors and quits when it's fed up. Did I forget to specify block-size (or
the like) to dd, or is that my data is plain wiped ?
> Or is there still other things to try?

First rule of data recovery - do not modify your disk further...  I can't
say offhand, but creating another partition and doing mke2fs on it is not
a great idea, because it is entirely possible that this overwrote some of
the data that you wanted back.

Whenever you are doing partition manipulation you are also well advised to
save the output of "sfdisk -l" or equivalent (i.e. start/end sectors for
each partition) so you have something to fall back on.

As for recovering email, what I would do is "strings /dev/hda7" or
(Continue reading)

Permalink | Reply | 1 comment |
headers
Stephen C. Tweedie | 3 Jun 2003 13:51
Picon
Favicon

Re: Check - ext3 on Red-hat 7.3

Hi,

On Mon, 2003-06-02 at 23:15, Marcel wrote:

> Is the FSCK or e2FSCK of the linux 7.3 can be used with ext3 ?

Yes, there shouldn't be any problem.

--Stephen
Permalink | Reply | 0 comments |
headers
Stephen C. Tweedie | 3 Jun 2003 13:54
Picon
Favicon

Re: partition magic messed up my magic number

Hi,

On Mon, 2003-06-02 at 23:42, Andreas Dilger wrote:

> First rule of data recovery - do not modify your disk further...  I can't
> say offhand, but creating another partition and doing mke2fs on it is not
> a great idea, because it is entirely possible that this overwrote some of
> the data that you wanted back.

Indeed.  If you _can_ get the entire disk contents onto another device,
though, a good way to start the recover attempt is with "gpart", which
tries to guess the location of "lost" partitions by searching for
superblock hints on the disk.

Cheers,
 Stephen
Permalink | Reply | 0 comments |
headers
Michael | 3 Jun 2003 17:30
Picon
Favicon

Re: partition magic messed up my magic number

I'll give both a try tonight and will tell you about it later on. Thank's a great lot to both of you. 
Cheers,

Michael

________________________________________
Université de Nantes, http://www.univ-nantes.fr
Permalink | Reply | 0 comments |
headers
Rahul Kalaskar | 5 Jun 2003 16:49

Hard Disk Failure

Hi  All,

I had to reboot a machine as I lost the ssh connectivity to it. I could
ping to it though. On rebooting, the dmesg buffer showed the following
messsage

hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
end_request: I/O error, dev 16:02 (hdc), sector 1820440
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800
end_request: I/O error, dev 16:02 (hdc), sector 1834800
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
end_request: I/O error, dev 16:02 (hdc), sector 1820440

Does this mean there is a hardware problem with the disk. 
The machine was running for about 250days. I am using IBM Travelstar hard disk. 
The machine is located in an NEMA box with maybe poor air circulation.

Thanks!
Rahul
Permalink | Reply | 5 comments |
headers
Marc-Christian Petersen | 5 Jun 2003 16:46
Picon

Re: Hard Disk Failure

On Thursday 05 June 2003 16:49, Rahul Kalaskar wrote:

Hi Rahul,

> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155,
> sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183,
> sector=1834800 end_request: I/O error, dev 16:02 (hdc), sector 1834800
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155,
> sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440
>
> Does this mean there is a hardware problem with the disk.
yes.

> The machine was running for about 250days. I am using IBM Travelstar hard
> disk. The machine is located in an NEMA box with maybe poor air
> circulation.
I still don't get it what this has to do with ext3 ML ;)

ciao, Marc
Permalink | Reply | 0 comments |
headers
Ralf Hildebrandt | 5 Jun 2003 16:46
Picon
Favicon

Re: Hard Disk Failure

* Rahul Kalaskar <rkalaskar <at> aethon.com>:

> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
> end_request: I/O error, dev 16:02 (hdc), sector 1820440
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800
> end_request: I/O error, dev 16:02 (hdc), sector 1834800
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
> end_request: I/O error, dev 16:02 (hdc), sector 1820440
> 
> Does this mean there is a hardware problem with the disk. 

It's dead, Jim.

--

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   Ralf.Hildebrandt <at> charite.de
Charite Campus Mitte                            Tel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
AIM: ralfpostfix
Permalink | Reply | 0 comments |
headers
Adam Williams | 5 Jun 2003 16:48
Picon

Re: Hard Disk Failure

yeah thats bad sectors.  you can possibly have linux ignore those secotrs
in the future and mark them as bad by unmounting the drive (or remounting
it read only) and then doing

e2fsck -c -y /dev/hdc1

			Adam

On 5 Jun 2003, Rahul Kalaskar wrote:

> Hi  All,
>
> I had to reboot a machine as I lost the ssh connectivity to it. I could
> ping to it though. On rebooting, the dmesg buffer showed the following
> messsage
>
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
> end_request: I/O error, dev 16:02 (hdc), sector 1820440
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800
> end_request: I/O error, dev 16:02 (hdc), sector 1834800
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
> end_request: I/O error, dev 16:02 (hdc), sector 1820440
>
> Does this mean there is a hardware problem with the disk.
> The machine was running for about 250days. I am using IBM Travelstar hard disk.
> The machine is located in an NEMA box with maybe poor air circulation.
>
(Continue reading)

Permalink | Reply | 2 comments |

Gmane