Marco Peereboom <slash <at> peereboom.us> writes: > > Next problem: There are quite a number of bays available in my box, > > so that I can plug another drive for a local 'dump'. But irrespective > > where I plug it, it won't come up: > > Your trace shows that it comes up just fine.
> > softraid0: volume sd4 is roaming, it used to be sd3, updating metadata > > You inserted a disk in front of others. From where I am sitting it is > all working as designed. Hmm. I plugged the fourth 'before' and 'after'; or the tray above and the tray below that pair. Both acted the same: breaking the mirror. To me it *looks* as if any physical disk would go before the RAID, and therefore the RAID always be incremented whenever one inserts another drive. And since the RAID gets roamed, while fstab isn't, it will always break. No? > This is not a softraid problem this is an OpenBSD problem. We don't > have uuids or labels on disks so when disks move around bad things > happen. This is a fact of life today that needs to be deal with > accordingly. Yes and no. 'Move around' is not what I am doing, when I plug an extra drive *after* sd2 (in my case). However, the system makes that one sd3, and voilC , the s*** hits the fan, because the RAID volume is moved up one index. To me this seems a result of the sequence at boot: at first we identify the physical drives, that is sd0, sd1, sd2 and sd3 in this case, and only later do we get softraid up, sensibly roaming the RAID one up. Sensibly? Because fstab can't know and will want to mount partitions of a lower number (sd3 in this case), which is always impossible.
