All of lore.kernel.org
 help / color / mirror / Atom feed
From: Digimer <lists@alteeve.ca>
To: Tom+Dale <tdmyth@yahoo.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Logical Volume Inaccessible
Date: Sat, 11 Jan 2014 23:34:23 -0500	[thread overview]
Message-ID: <52D21B4F.50504@alteeve.ca> (raw)
In-Reply-To: <1389500888.48728.YahooMailNeo@web161702.mail.bf1.yahoo.com>

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?

  reply	other threads:[~2014-01-12  4:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12  4:28 [linux-lvm] Logical Volume Inaccessible Tom+Dale
2014-01-12  4:34 ` Digimer [this message]
2014-01-12  4:59   ` Tom+Dale
2014-01-12  5:17     ` Digimer
2014-01-12  9:38       ` Gabriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D21B4F.50504@alteeve.ca \
    --to=lists@alteeve.ca \
    --cc=linux-lvm@redhat.com \
    --cc=tdmyth@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.