* [linux-lvm] Logical Volume Inaccessible
@ 2014-01-12 4:28 Tom+Dale
2014-01-12 4:34 ` Digimer
0 siblings, 1 reply; 5+ messages in thread
From: Tom+Dale @ 2014-01-12 4:28 UTC (permalink / raw)
To: linux-lvm@redhat.com
I am hoping that someone can assist me with a problem that I have on a
single 500GB drive that was partitioned by "Mythdora" a (now defunct)
distribution of Fedora + MythTV.� I had this system in use for several
years and recently the motherboard died.� When I put the hard disk into a different machine it would not boot up (no surprise); however, I also
was unable to access the partitions from a Knoppix Live CD (I tried both 5.1 and 7.0).� When I tried with Knoppix to mount the partitions I
discovered that something is wrong with the partition tables or logical
volumes.� Here are some examples of the commands that I tried along with the results.� Will you please give me some advice about the best way to recover data from sda2 (the recordings)?� Thank you in advance!
-Tom
---------------------------------------------
root@Microknoppix:/# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000537fa
�� Device Boot����� Start�������� End����� Blocks�� Id� System
/dev/sda1�� *��������� 63����� 409662����� 204800�� 83� Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2��������� 409663�� 976768064��
488179201�� 8e� Linux LVM
Partition 2 does not start on physical sector boundary.
root@Microknoppix:/# parted -l
Model: ATA WDC WD5000AADS-1 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number� Start�� End��� Size�� Type���� File system� Flags
�1����� 32.3kB� 210MB� 210MB� primary� ext4�������� boot
�2����� 210MB�� 500GB� 500GB� primary�������������� lvm
Warning: Unable to open /dev/fd0 read-write (Read-only file system).� /dev/fd0
has been opened read-only.
Error: /dev/fd0: unrecognised disk
label��������������������������������
Warning: Unable to open /dev/sr0 read-write (Read-only file system).� /dev/sr0
has been opened read-only.
Error: /dev/sr0: unrecognised disk label��������������������������������
Error: /dev/zram0: unrecognised disk label������������������������������
Warning: Unable to open /dev/cloop0 read-write (Read-only file system).�
/dev/cloop0 has been opened read-only.
Error: /dev/cloop0: unrecognised disk
label�����������������������������
root@Microknoppix:/# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
� MBR: MBR only
� BSD: not present
� APM: not present
� GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E9B4E83E-86F3-4843-801E-495E6864F682
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 8-sector boundaries
Total free space is 5099 sectors (2.5
MiB)
Number� Start (sector)��� End (sector)� Size������ Code� Name
�� 1������������� 63��������� 409662�� 200.0 MiB�� 8300� Linux filesystem
�� 2��������� 409663������ 976768064�� 465.6 GiB�� 8E00� Linux LVM
root@Microknoppix:/# vgchange -ay
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� No volume groups found
root@Microknoppix:/# lvscan
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read
failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� No volume groups found
root@Microknoppix:/# lvm lvdisplay
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� No volume groups found
root@Microknoppix:/# vgscan --mknodes
� Reading all physical volumes.� This may take a while...
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� No volume groups found
� No volume groups found
root@Microknoppix:/#
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Logical Volume Inaccessible
2014-01-12 4:28 [linux-lvm] Logical Volume Inaccessible Tom+Dale
@ 2014-01-12 4:34 ` Digimer
2014-01-12 4:59 ` Tom+Dale
0 siblings, 1 reply; 5+ messages in thread
From: Digimer @ 2014-01-12 4:34 UTC (permalink / raw)
To: Tom+Dale, LVM general discussion and development
What does 'pvscan; vgscan; lvscan' show? If the LVs show 'inactive', try
'lvchange -ay <lv_path>', then 'lvscan' should show the LV as 'ACTIVE'.
If so, try mounting the LV.
On 11/01/14 11:28 PM, Tom+Dale wrote:
>
>
> I am hoping that someone can assist me with a problem that I have on a
> single 500GB drive that was partitioned by "Mythdora" a (now defunct)
> distribution of Fedora + MythTV. I had this system in use for several
> years and recently the motherboard died. When I put the hard disk into a different machine it would not boot up (no surprise); however, I also
> was unable to access the partitions from a Knoppix Live CD (I tried both 5.1 and 7.0). When I tried with Knoppix to mount the partitions I
> discovered that something is wrong with the partition tables or logical
> volumes. Here are some examples of the commands that I tried along with the results. Will you please give me some advice about the best way to recover data from sda2 (the recordings)? Thank you in advance!
> -Tom
>
> ---------------------------------------------
> root@Microknoppix:/# fdisk -l
>
> Disk /dev/sda: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disk identifier: 0x000537fa
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 63 409662 204800 83 Linux
> Partition 1 does not start on physical sector boundary.
> /dev/sda2 409663 976768064
> 488179201 8e Linux LVM
> Partition 2 does not start on physical sector boundary.
> root@Microknoppix:/# parted -l
> Model: ATA WDC WD5000AADS-1 (scsi)
> Disk /dev/sda: 500GB
> Sector size (logical/physical): 512B/4096B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 32.3kB 210MB 210MB primary ext4 boot
> 2 210MB 500GB 500GB primary lvm
>
>
> Warning: Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0
> has been opened read-only.
> Error: /dev/fd0: unrecognised disk
> label
>
> Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
> has been opened read-only.
> Error: /dev/sr0: unrecognised disk label
>
> Error: /dev/zram0: unrecognised disk label
>
> Warning: Unable to open /dev/cloop0 read-write (Read-only file system).
> /dev/cloop0 has been opened read-only.
> Error: /dev/cloop0: unrecognised disk
> label
>
> root@Microknoppix:/# gdisk -l /dev/sda
> GPT fdisk (gdisk) version 0.8.5
>
> Partition table scan:
> MBR: MBR only
> BSD: not present
> APM: not present
> GPT: not present
>
>
> ***************************************************************
> Found invalid GPT and valid MBR; converting MBR to GPT format.
> ***************************************************************
>
> Disk /dev/sda: 976773168 sectors, 465.8 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): E9B4E83E-86F3-4843-801E-495E6864F682
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 976773134
> Partitions will be aligned on 8-sector boundaries
> Total free space is 5099 sectors (2.5
> MiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 63 409662 200.0 MiB 8300 Linux filesystem
> 2 409663 976768064 465.6 GiB 8E00 Linux LVM
> root@Microknoppix:/# vgchange -ay
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No volume groups found
> root@Microknoppix:/# lvscan
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read
> failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No volume groups found
> root@Microknoppix:/# lvm lvdisplay
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No volume groups found
> root@Microknoppix:/# vgscan --mknodes
> Reading all physical volumes. This may take a while...
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No volume groups found
> No volume groups found
> root@Microknoppix:/#
>
> _______________________________________________
> 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/
>
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Logical Volume Inaccessible
2014-01-12 4:34 ` Digimer
@ 2014-01-12 4:59 ` Tom+Dale
2014-01-12 5:17 ` Digimer
0 siblings, 1 reply; 5+ messages in thread
From: Tom+Dale @ 2014-01-12 4:59 UTC (permalink / raw)
To: Digimer, LVM general discussion and development
>What does 'pvscan; vgscan; lvscan' show? If the LVs show 'inactive', try
>'lvchange -ay <lv_path>', then 'lvscan' should show the LV as 'ACTIVE'.
>If so, try mounting the LV.
>--
>Digimer
>Papers and Projects: https://alteeve.ca/w/
>What if the cure for cancer is trapped in the mind of a person without
>access to education?
Here is what I got:
[root@localhost ~]# pvscan
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� No matching physical volumes found
[root@localhost ~]# lvscan
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
[root@localhost ~]# vgscan
� Reading all physical volumes.� This may take a while...
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
[root@localhost ~]# lvchange -ay /dev/sda2
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
� /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
� /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
� Volume group "sda2" not found
� Skipping volume group sda2
[root@localhost ~]#
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Logical Volume Inaccessible
2014-01-12 4:59 ` Tom+Dale
@ 2014-01-12 5:17 ` Digimer
2014-01-12 9:38 ` Gabriel
0 siblings, 1 reply; 5+ messages in thread
From: Digimer @ 2014-01-12 5:17 UTC (permalink / raw)
To: Tom+Dale, LVM general discussion and development
On 11/01/14 11:59 PM, Tom+Dale wrote:
>
>> What does 'pvscan; vgscan; lvscan' show? If the LVs show 'inactive', try
>
>> 'lvchange -ay <lv_path>', then 'lvscan' should show the LV as 'ACTIVE'.
>> If so, try mounting the LV.
>> --
>> Digimer
>> Papers and Projects: https://alteeve.ca/w/
>> What if the cure for cancer is trapped in the mind of a person without
>> access to education?
>
> Here is what I got:
>
> [root@localhost ~]# pvscan
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No matching physical volumes found
> [root@localhost ~]# lvscan
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> [root@localhost ~]# vgscan
> Reading all physical volumes. This may take a while...
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> [root@localhost ~]# lvchange -ay /dev/sda2
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> Volume group "sda2" not found
> Skipping volume group sda2
> [root@localhost ~]#
Eep,
That looks like the drive might be failing. If you don't have a good
backup, then you might want to stop. If the data on the drive is very
valuable, I would do nothing more and call a data recovery house. If
that's not feasible, then the first thing I would do is connect another
drive of equal or larger size and dd the bad drive to the other drive.
For example, if the bad drive comes up as /dev/sdb and the
spare/backup drive comes up as /dev/sdc, you would want to run something
like 'dd if=/dev/sdb of=/dev/sdc bs=8k'. That will clone, byte for byte,
sdb onto sdc (and erase whatever was on sdc, of course). Then set aside
the failing drive and try to recover the data on sdc (possibly copy it
again to a 3rd drive, just to be extra safe). This way, if something
goes wrong, you can start over.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Logical Volume Inaccessible
2014-01-12 5:17 ` Digimer
@ 2014-01-12 9:38 ` Gabriel
0 siblings, 0 replies; 5+ messages in thread
From: Gabriel @ 2014-01-12 9:38 UTC (permalink / raw)
To: LVM general discussion and development
[-- Attachment #1: Type: text/plain, Size: 2941 bytes --]
Perhaps it would be better to use ddrescue[1] for this (instead of dd).
[1] http://www.gnu.org/software/ddrescue/
On Jan 12, 2014 7:21 AM, "Digimer" <lists@alteeve.ca> wrote:
> On 11/01/14 11:59 PM, Tom+Dale wrote:
>
>>
>> What does 'pvscan; vgscan; lvscan' show? If the LVs show 'inactive', try
>>>
>>
>> 'lvchange -ay <lv_path>', then 'lvscan' should show the LV as 'ACTIVE'.
>>> If so, try mounting the LV.
>>> --
>>> Digimer
>>> Papers and Projects: https://alteeve.ca/w/
>>> What if the cure for cancer is trapped in the mind of a person without
>>> access to education?
>>>
>>
>> Here is what I got:
>>
>> [root@localhost ~]# pvscan
>> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
>> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
>> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
>> No matching physical volumes found
>> [root@localhost ~]# lvscan
>> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
>> [root@localhost ~]# vgscan
>> Reading all physical volumes. This may take a while...
>> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
>> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
>> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
>> [root@localhost ~]# lvchange -ay /dev/sda2
>> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
>> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
>> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
>> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
>> Volume group "sda2" not found
>> Skipping volume group sda2
>> [root@localhost ~]#
>>
>
> Eep,
>
> That looks like the drive might be failing. If you don't have a good
> backup, then you might want to stop. If the data on the drive is very
> valuable, I would do nothing more and call a data recovery house. If that's
> not feasible, then the first thing I would do is connect another drive of
> equal or larger size and dd the bad drive to the other drive.
>
> For example, if the bad drive comes up as /dev/sdb and the spare/backup
> drive comes up as /dev/sdc, you would want to run something like 'dd
> if=/dev/sdb of=/dev/sdc bs=8k'. That will clone, byte for byte, sdb onto
> sdc (and erase whatever was on sdc, of course). Then set aside the failing
> drive and try to recover the data on sdc (possibly copy it again to a 3rd
> drive, just to be extra safe). This way, if something goes wrong, you can
> start over.
>
>
>
> --
> Digimer
> Papers and Projects: https://alteeve.ca/w/
> What if the cure for cancer is trapped in the mind of a person without
> access to education?
>
> _______________________________________________
> 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/
>
[-- Attachment #2: Type: text/html, Size: 4105 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-01-12 9:38 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-12 4:28 [linux-lvm] Logical Volume Inaccessible Tom+Dale
2014-01-12 4:34 ` Digimer
2014-01-12 4:59 ` Tom+Dale
2014-01-12 5:17 ` Digimer
2014-01-12 9:38 ` Gabriel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox