Date: Fri, 7 Feb 2003 22:54:50 +0100 (CET) From: Michael Reifenberger <root@nihil.reifenberger.com> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-current@freebsd.org Subject: Re: vinum start & -current doesn't work as expected Message-ID: <20030207225249.O33219@nihil.reifenberger.com> In-Reply-To: <200302072056.h17KujgW073866@uriah.heep.sax.de> References: <20030207105857.T2514@nihil.reifenberger.com> <200302072056.h17KujgW073866@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Feb 2003, Joerg Wunsch wrote: > Date: Fri, 7 Feb 2003 21:56:45 +0100 (MET) > From: Joerg Wunsch <j@uriah.heep.sax.de> > Reply-To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> > To: freebsd-current@freebsd.org > Cc: Michael Reifenberger <root@nihil.reifenberger.com> > Subject: Re: vinum start & -current doesn't work as expected > > Michael Reifenberger <root@nihil.reifenberger.com> wrote: > > > After reboot, a `vinum start` gives me: > > ** no drives found: No such file or directory > > Do you perchance have a kernel without GEOM? -current without GEOM? :-) > > vinum start has now been changed to use sysctl kern.disks as the list > of devices to scan. Hmm. No, maybe not... I'm afraid i should > change the userland to perform the same as the early startup in the > kernel now does. > > What does your sysctl kern.disks say? (nihil)(root) # sysctl -a kern.disks kern.disks: da1 da0 ad1 ad0 > > As a workaround, you can try setting > > vinum_load=YES > vinum.autostart=YES > > in your /boot/loader.conf, /and/ remove the start_vinum line from > rc.conf. Please tell me whether this gives different results. > Will try. Thanks so far! Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030207225249.O33219>