Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Feb 2004 09:14:06 +0100
From:      "Axel S. Gruner" <axel.gruner@suedfactoring.de>
To:        freebsd-questions@freebsd.org
Subject:   vinum crashed
Message-ID:  <403DAACE.8010904@suedfactoring.de>

next in thread | raw e-mail | index | archive | help
Hi.

I setup a disk stripping with two disks and vinum. I was impressed about 
the quick and easy setup.
The configuration is, that i installed FreeBSD 5.2.1-RC2 on /, a little 
bit of swap, and the gave the rest for vinum.
So the two disks have both a bootable / and /usr and /var is on vinum.
All went fine and was working.
Yes, was...
A colleague of mine went to the server, took the first HD out, and tried 
to boot. Crash. Single user mode. Thats it. (strange guy...).
Ok, i put the second HD in, rebooted the server, and still found myself 
in single user.
fsck on vinum does not work (but the filesystem wants to do a fsck).
So i looked at "vinum ls" output an saw that vinum is marked as "crashed".

After a
#vinum
vinum --> start

the stripping was up again. Happy happy joy joy i thought and i booted 
into multiuser mode.
To test it out, i rebooted the machine, and, no more happy happy und no 
more joy joy, the system boots in single user mode, wants to fsck vinum, 
can not do that....

Yes, i know, it would be fine to post some error messages, but right now 
i dont have any access to that machine.
So, what could be the problem, and how to solve it.

I appreciate any hints.

asg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?403DAACE.8010904>