Date: Thu, 15 Mar 2001 18:51:17 -0600 From: "J. Seth Henry" <jshenry@net-noise.com> To: "FreeBSD Questions" <freebsd-questions@FreeBSD.ORG> Message-ID: <EBEDLIEDDOIIJDGEKFFDOEMGCAAA.jshenry@net-noise.com>
next in thread | raw e-mail | index | archive | help
Fair enough. When I restart vinum with the new blank, but partitioned, disk - it shows up as "crashed" (which I would expect). I try to start it, using "start mmvolc.p0.s0", and it reports that it can't because the drive is down "drive is down (5)". I next tried to "setstate obsolete mmvolc.p0.s0" followed by "start mmvolc.p0.s0", but I still get the "drive is down" error. I then tried "init mmvolc.p0.s0", and it first reports that it can't because of read/write failure. If I then stopped vinum, and restarted it, and it then inited the plex, and reported it as up. Unfortunately, at this point it corrupts the volume. (naturally, because it is nothing but zeros). So, I "setstate down mmvolc.p0.s0", and the array is fine, but degraded. Then, I tried "setstate obsolete mmvolc.p0.s0" followed by "start mmvolc.p0.s0", but it reports that the drive is down (back to square one almost). Any attempts to start the subdisk result in corruption to the array, and I can't seem to get it to rebuild. Seth Henry jshenry@net-noise.com Date: Fri, 16 Mar 2001 10:50:23 +1030 From: Greg Lehey <grog@lemis.com> Subject: Re: Vinum disk replacement On Wednesday, 14 March 2001 at 23:26:08 -0600, J. Seth Henry wrote: > Ok, does anyone know the proper way to replace a drive in a vinum RAID5 > array? I thought I did, but apparently not. > > I tried pulling the disk, replacing it with another disk having the same > SCSI ID, and creating a label for it - ala the vinum web page. (this is > after partitioning and changing the partition type with disklabel). When I > start vinum, it shows the RAID5 plex as degraded, and the affected disk as > down. So far, so good - the file system is slow, but fine. Next, I init the > plex, using "init mmvolc.p0.s2". Ok, so how do I rebuild parity from here? I > try starting the plex, and it comes up. No rebuilding parity, nothing. but > when I try to mount the file system, it is trashed. (presumably because one > of the disks is full of zeros!). > > I tried the step by step on the website, but it didn't work. Well, how about describing *how* it didn't work? 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?EBEDLIEDDOIIJDGEKFFDOEMGCAAA.jshenry>