Date: Fri, 01 Oct 1999 16:10:19 -0700 From: Darryl Okahata <darrylo@sr.hp.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: vinum and 3.2R -> 3.3R upgrade Message-ID: <199910012310.QAA29992@mina.sr.hp.com> In-Reply-To: Your message of "Wed, 29 Sep 1999 18:03:37 PDT."
next in thread | raw e-mail | index | archive | help
Ludwig Pummer <ludwigp@bigfoot.com> wrote:
> I had that problem when upgrading a 3.1-STABLE machine to 3.3-STABLE. I
> don't remember the exact process anymore, but the system is working fine
> and vinum doesn't list any bad volumes/plexes/subdisks. I fixed the
> disklabel in single user mode (took some work because /usr and /var are
> vinum volumes), rebooted, did a 'vinum makedev' (in single user mode)
> and rebooted. I think after that last time, it came up OK.
In upgrading one of my systems from 3.1-RELEASE to 3.3-RELEASE[*], I
couldn't get vinum to recognize my existing volume (it kept on thinking
that the disks were crashed). After a couple frustrating hours, I ended
up blowing away the volume and recreating it ("vinum resetconfig" is
your friend ;-). Fortunately, I backed up the system before upgrading
it. ;-)
[*] -- My 3.3-RELEASE subscription disk arrived in the mail, and I
thought, "What the hell -- it's about time I upgraded". Urg. I
knew I was in for some fun, as I'm using both vinum and
softupdates, but I wasn't expecting to actually *use* my backups
;-). I think it's time I moved that system to -stable, anyway.
--
Darryl Okahata
darrylo@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910012310.QAA29992>