Date: Tue, 16 Jan 2007 22:54:40 +0100 From: Ivan Voras <ivoras@fer.hr> To: freebsd-questions@freebsd.org Subject: Re: hardware mirrors recognized as individual disks in fbsd Message-ID: <eojhbs$ajb$1@sea.gmane.org> In-Reply-To: <539c60b90701161033v5e316ef4m19332bd6e86ab67b@mail.gmail.com> References: <539c60b90701161033v5e316ef4m19332bd6e86ab67b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD5EBA33C1DA9EE17A319D8E7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Steve Franks wrote: > I want two 160GB mirrored volumes, not 4 unmirrored ones. The RAID is = an > ASUS P5DR1-VM motherboard with a ULI raid chipset onboard. Very nice s= etup > for the money. I don't know about the chipset or the controller, but judging from the symptoms it's highly likely you actually have a soft-RAID controller, and the actual RAID stuff was done by your Windows driver. **IF** the driver was benign enough, you could *maybe* reconstitute a mirrored volume with FreeBSD's software RAID driver, gmirror. See the man page for details, but a command like "gmirror label mydisk /dev/ad4 /dev/ad5" will create mirrored device /dev/mirror/mydisk which you can then try to mount (actually if it works you'll see individual partitions like /dev/mirror/mydisks1, etc.). BUT! 1. The above command will overwrite the last sectors on both drives with its data (which you'll have to clean if you don't want the mirror anymore). Usually they are unused but maybe the Windows driver used them so you won't be able to use them under Windows. 2. Be very very careful - if this doesn't result in a valid mirrored drive or the Windows driver did something unusual or nasty, you might destroy the data by writing to the mirrored drive (just reading it will not cause any damage). Mount the drive read-only first, and check you can see valid data. Be absolutely sure before mounting it read/write (and be careful about mounting NTFS read-write anyway - it's not risk-fre= e). --------------enigD5EBA33C1DA9EE17A319D8E7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrUmnldnAQVacBcgRAkHaAKDDKU781ROIB7SToz/pHaxOklOJkACdEIUi EroflzUCv8LAMyX9O33v03U= =QQ7n -----END PGP SIGNATURE----- --------------enigD5EBA33C1DA9EE17A319D8E7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eojhbs$ajb$1>