[linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[Marco Antonelli]

Hello,
I have one LV (/home/hom_vg/home_lv) spanning over two PV. The PVs
were created on /dev/hdc1 and /dev/hdd1, both covering the entire
disks hdc (120 gb) and hdd (200 gb) respectively.
The mapping is linear.

My hdc is physically damaged... I could not even run fsck, badblocks
and dd_rescue. All of them give an output like this (from dmesg):


hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
low=512, sector=512
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 512
Buffer I/O error on device hdc, logical block 64
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
low=512, sector=512
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 512
Buffer I/O error on device hdc, logical block 64
Adding 690784k swap on /dev/hda4.  Priority:-1 extents:1 across:690784k
EXT3 FS on hda3, internal journal
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
low=447, sector=447
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 447
Buffer I/O error on device dm-0, logical block 0
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=455, high=0,
low=455, sector=455
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 455
Buffer I/O error on device dm-0, logical block 1
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=463, high=0,
low=463, sector=463
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 463
Buffer I/O error on device dm-0, logical block 2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=471, high=0,
low=471, sector=471
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 471
Buffer I/O error on device dm-0, logical block 3
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
low=447, sector=447
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 447
Buffer I/O error on device dm-0, logical block 0
fuse init (API version 7.8)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=449, high=0,
low=449, sector=449
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 449
EXT3-fs: unable to read superblock

Re: [linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[Heinz Mauelshagen]

On Tue, Jul 10, 2007 at 04:31:51PM +0200, Marco Antonelli wrote:
> Hello,
> I have one LV (/home/hom_vg/home_lv) spanning over two PV. The PVs
> were created on /dev/hdc1 and /dev/hdd1, both covering the entire
> disks hdc (120 gb) and hdd (200 gb) respectively.
> The mapping is linear.
> 
> My hdc is physically damaged... I could not even run fsck, badblocks
> and dd_rescue. All of them give an output like this (from dmesg):

You got to put the PVs on MD RAID >= 1 or use LVM mirring to avoid this.
Reach out for your backups :(

Regards,
Heinz    -- The LVM Guy --

> 
> 
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
> low=512, sector=512
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 512
> Buffer I/O error on device hdc, logical block 64
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
> low=512, sector=512
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 512
> Buffer I/O error on device hdc, logical block 64
> Adding 690784k swap on /dev/hda4.  Priority:-1 extents:1 across:690784k
> EXT3 FS on hda3, internal journal
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
> low=447, sector=447
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 447
> Buffer I/O error on device dm-0, logical block 0
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=455, high=0,
> low=455, sector=455
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 455
> Buffer I/O error on device dm-0, logical block 1
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=463, high=0,
> low=463, sector=463
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 463
> Buffer I/O error on device dm-0, logical block 2
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=471, high=0,
> low=471, sector=471
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 471
> Buffer I/O error on device dm-0, logical block 3
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
> low=447, sector=447
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 447
> Buffer I/O error on device dm-0, logical block 0
> fuse init (API version 7.8)
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on hda2, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=449, high=0,
> low=449, sector=449
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdc, sector 449
> EXT3-fs: unable to read superblock
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Storage Development                               56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            PHONE +49  171 7803392
                                                  FAX   +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[Marco Antonelli]

2007/7/10, Heinz Mauelshagen <mauelshagen@redhat.com>:

> You got to put the PVs on MD RAID >= 1 or use LVM mirring to avoid this.
> Reach out for your backups :(
>
> Regards,
> Heinz    -- The LVM Guy --

Yes, I will setup RAID these days, but... there is no way to read the
data on the good disk?? I have only an incomplete backup

Re: [linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[Jim Schatzman]

 From me the amateur. You appear to have lost some data. You probably have some files that are recoverable. You have a few choices:

1) Send your disks to a professional. See http://myharddrivedied.com, for example.

2) Replace the electronics PC board on your drive. See the same above website for more info on that. This might recover all your data. It also may make no change.

3) Use dmsetup to enable a partial VG (use vgchange -Pay as explained in the article). See
http://e2salvage.sourceforge.net/florian2.html
Retrieve what files you can.

You can also remove the bad drive entirely and do a partial VG.

4) Use dd ignoring errors to do a raw copy off the bad drive to an identical good drive. 
Use vgcfgbackup. Remove the bad drive. Install the new drive.

Edit the vgcfg backup, edit the id in the logical_volumes
sections, check your work carefully, and vgcfgrestore

as mentioned by Ryan Nelson.  This is probably going to get you about what #3 does.

Good luck-

Jim







At 08:31 AM 7/10/2007, you wrote:
>Hello,
>I have one LV (/home/hom_vg/home_lv) spanning over two PV. The PVs
>were created on /dev/hdc1 and /dev/hdd1, both covering the entire
>disks hdc (120 gb) and hdd (200 gb) respectively.
>The mapping is linear.
>
>My hdc is physically damaged... I could not even run fsck, badblocks
>and dd_rescue. All of them give an output like this (from dmesg):
>
>
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
>low=512, sector=512
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 512
>Buffer I/O error on device hdc, logical block 64
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=512, high=0,
>low=512, sector=512
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 512
>Buffer I/O error on device hdc, logical block 64
>Adding 690784k swap on /dev/hda4.  Priority:-1 extents:1 across:690784k
>EXT3 FS on hda3, internal journal
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
>low=447, sector=447
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 447
>Buffer I/O error on device dm-0, logical block 0
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=455, high=0,
>low=455, sector=455
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 455
>Buffer I/O error on device dm-0, logical block 1
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=463, high=0,
>low=463, sector=463
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 463
>Buffer I/O error on device dm-0, logical block 2
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=471, high=0,
>low=471, sector=471
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 471
>Buffer I/O error on device dm-0, logical block 3
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=447, high=0,
>low=447, sector=447
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 447
>Buffer I/O error on device dm-0, logical block 0
>fuse init (API version 7.8)
>kjournald starting.  Commit interval 5 seconds
>EXT3 FS on hda2, internal journal
>EXT3-fs: mounted filesystem with ordered data mode.
>hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=449, high=0,
>low=449, sector=449
>ide: failed opcode was: unknown
>end_request: I/O error, dev hdc, sector 449
>EXT3-fs: unable to read superblock
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@redhat.com
>https://www.redhat.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] Logical Volume on two disk, one is broken: how to restore data from the good disk?

[Marco Antonelli]

Thank you Jim, I'll try your suggestions; I'll let you now what will happen.
Bye,
Marco

2007/7/11, Jim Schatzman <james.schatzman@futurelabusa.com>:
>  From me the amateur. You appear to have lost some data. You probably have some files that are recoverable. You have a few choices:
>
> 1) Send your disks to a professional. See http://myharddrivedied.com, for example.
>
> 2) Replace the electronics PC board on your drive. See the same above website for more info on that. This might recover all your data. It also may make no change.
>
> 3) Use dmsetup to enable a partial VG (use vgchange -Pay as explained in the article). See
> http://e2salvage.sourceforge.net/florian2.html
> Retrieve what files you can.
>
> You can also remove the bad drive entirely and do a partial VG.
>
> 4) Use dd ignoring errors to do a raw copy off the bad drive to an identical good drive.
> Use vgcfgbackup. Remove the bad drive. Install the new drive.
>
> Edit the vgcfg backup, edit the id in the logical_volumes
> sections, check your work carefully, and vgcfgrestore
>
> as mentioned by Ryan Nelson.  This is probably going to get you about what #3 does.
>
> Good luck-
>
> Jim
>