linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Lee Gold" <leegold@operamail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Help to mount ext3 boot partiton which reports it's LVM2_member when I try to mount it
Date: Fri, 17 Jun 2011 08:59:58 -0700	[thread overview]
Message-ID: <1308326398.9219.1464298109@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1106170004310.20086@bmsred.bmsi.com>


  

On Fri, 17 Jun 2011 00:11 -0400, "Stuart D. Gathman" <stuart@bmsi.com>
wrote:
> On Thu, 16 Jun 2011, Lee Gold wrote:
> 
> > How can this be right? I clearly remember installing the /boot as an
> > ext3 partiton.
> >
> > sudo pvs says:
> >
> > PV        VG       Fmt   Attr   PSize    PFree
> >
> > /dev/sda1          lvm2  a-     190.00m  190.00m
> >
> > /dev/sda2 system   lvm2  a-      92.97g       0
> >
> > I can mount the partitons in /dev/sda2 by installing LVM2 while using
> > the live disk and some command-line - so I can recover the data if
> > necessay so all is not lost. But I would really like to know what is
> > going on and how to get the system booting again. Again the boot
> > partition was ext3 and separate, why can't I access it, fdisk
> > confirms...?  Thanks.
> 
> I would suspect that sda and sdb do not point to the disks you think
> they do.  BIOS often swaps these around without warning.  You don't
> mention
> your physical connection (IDE/SATA/USB/FW/iSCSI/...).  This would give a
> clue
> as to what BIOS might have done - although it really isn't an LVM
> question.
> This is why it is preferred to use filesystem/PV UUIDs or labels 
> rather that whatever the current device address happens to be.
> 
> So it looks like you made /boot into a PV, although pvcreate should have
> warned that the block device was mounted.
> 

In my opinion LVM2 should of flagged me when it went about changing my
config - which it did - the boot partition's location and spec could not
of changed on it's own and while the bios could shuffle things around
only an active script could of changed things as it did and it should
have warned me - that's Comp Sci 101 - when something happens pull over
to the side of the road AND put your indicator on too. Maybe I'm wrong
but if I am it's moot. "Once burned twice shy".

-- 
http://www.fastmail.fm - Access all of your messages and folders
                          wherever you are

  reply	other threads:[~2011-06-17 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 21:45 [linux-lvm] Help to mount ext3 boot partiton which reports it's LVM2_member when I try to mount it Lee Gold
2011-06-17  4:11 ` Stuart D. Gathman
2011-06-17 15:59   ` Lee Gold [this message]
2011-06-17 16:36     ` Ray Morris
2011-06-21 15:35     ` Phillip Susi
2011-06-29  8:47       ` [linux-lvm] Fedora 15 lvm root device not found Stamper, Brian P. (ARC-D)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]
2011-06-29 19:47         ` Stamper, Brian P. (ARC-D)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]
2011-07-01 15:05           ` Stuart D. Gathman
2011-07-19 19:13         ` [linux-lvm] Mail etiquette ( was: Fedora 15 lvm root device not found ) Phillip Susi

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=1308326398.9219.1464298109@webmail.messagingengine.com \
    --to=leegold@operamail.com \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).