From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] My VG is gone...
Date: Tue, 4 Sep 2001 07:43:28 -0500 [thread overview]
Message-ID: <20010904074328.A29128@sistina.com> (raw)
In-Reply-To: <20010902200715.73773199.rasmus.wiman@sami.se>; from rasmus.wiman@sami.se on Sun, Sep 02, 2001 at 08:07:15PM +0200
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
On Sun, Sep 02, 2001 at 08:07:15PM +0200, Rasmus Wiman wrote:
> Joe Thornber <thornber@btconnect.com> skrev:
> > You're right sdb1 appears to have been added twice with seperate
> > UUID's. I'm at a loss to explain this at the moment. Did you run
> > pvcreate more than once on sdb1 ? (I want to know where that extra
> > uuid came from).
>
> Well here's the full story:
> I added the new disk, made a new LVM partition, ran pvcreate on it. Did a
> vgextend vg1 /dev/sdb1. Rebooted. No vg:s found, Panic: root not found.
> Spent a bunch of hours hackaing a Slackware 8 boot floppy with LVM 1.0
> support. It found the vg. Next idea: Maybe it's because of devfs. I hacked
> the disk a bit further yo use devfs, and now it didn't find the VG:s. I
> started looking for any LVM list archive, found something about small
> initrd:s so I put an 8 MB initrd image on the root floppy, and wow, the VG
> was there. Tried to put a larger initrd on the boot partition and re-ran
> lilo. Rebooted, no success. Later I realised that a initrd_size=8912k
> might have done the trick. Booted from the floppy again and did a vgreduce
> vg1 /dev/sdb1. Now it would boot. Here I should really have backed up
> everything to a non LVM partition, but instead I did a vgextend vg1 sdb1.
> Re-ran lvmcreate_initrd, re-ran lilo and rebooted. That's where I am now.
> Two SDB1:s with separate UUID's. Can this be fixed or should I format and
> reinstall? It would really feel bad because I've never had to format and
> reinstall a Linux system except for the occasional hardware failure.
Did you try the uuid_fixer program at ftp://ftp.sistina.com/pub/LVM/contrib
That may fix your problem, but it would be nice to get as much info out of
your system as possible before you use it to figure out what went wrong...
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3CD1 25EE DBE3 1B69 F3C7 A1FB 2A81 D686 34A2 2E9E
-----Begin Obligatory Humorous Quote----------------------------------------
Life's short and hard, kind of like a bodybuilding elf
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-09-04 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 5:15 [linux-lvm] My VG is gone Rasmus Wiman
2001-08-31 7:41 ` Rasmus Wiman
2001-08-31 9:22 ` Joe Thornber
2001-09-02 18:07 ` Rasmus Wiman
2001-09-02 19:03 ` svetljo
2001-09-04 12:43 ` AJ Lewis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 20:51 Diehl, Jeffrey
2001-09-05 8:04 ` Rasmus Wiman
2001-09-05 18:56 Diehl, Jeffrey
2001-09-05 20:41 ` AJ Lewis
2001-09-06 16:36 Diehl, Jeffrey
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=20010904074328.A29128@sistina.com \
--to=lewis@sistina.com \
--cc=linux-lvm@sistina.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