Date: Wed, 4 Feb 2004 19:41:48 +0100 (CET) From: dontspamhenk@xs4all.nl To: freebsd-questions@freebsd.org Subject: Fixing vinum after removing a HDD Message-ID: <Pine.LNX.4.58.0402041701510.17812@shell.dds.nl>
next in thread | raw e-mail | index | archive | help
Dear all, I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile Thanks, Marc Disks currently in the system: ad0 (unused disk, to be removed from the system) ad1 <Maxtor 6Y080L0> (contains 1st vinum subdisk) ad2 <Maxtor 6Y080L0> (contains 2nd vinum subdisk) ad3 <Maxtor 6Y080L0> (contains 3rd vinum subdisk) da0 <QUANTUM ATLAS10K2-TY092L DDD6> (contains all system partitions) My current vinum.conf: drive a device /dev/ad1s1h drive b device /dev/ad2s1h drive c device /dev/ad3s1h volume BigDisk0 plex org concat sd length 78159m drive a sd length 78159m drive b sd length 78159m drive c Disks after removing the 1st disk ad0 <Maxtor 6Y080L0> (contains 1st vinum subdisk) ad1 <Maxtor 6Y080L0> (contains 2nd vinum subdisk) ad2 <Maxtor 6Y080L0> (contains 3rd vinum subdisk) da0 <QUANTUM ATLAS10K2-TY092L DDD6> (contains all system partitions) My future vinum.conf drive a device /dev/ad0s1h drive b device /dev/ad1s1h drive c device /dev/ad2s1h volume BigDisk0 plex org concat sd length 78159m drive a sd length 78159m drive b sd length 78159m drive c
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.58.0402041701510.17812>