On Saturday 18 June 2005 16:51:16, Steve Bertrand wrote:
> Hence, the aftermath on a properly booted system:
>
> pearl# atacontrol status 1
> ar1: ATA RAID1 subdisks: ad4 ad6 status: READY
>
> pearl# atacontrol status 0
> ar0: ATA RAID1 subdisks: ad2 ad0 status: READY
>
> pearl# df -h
>
> Filesyst
> You might use loader(8) to set the root device ("rootdev"
> variable) explicitly to ar1s1a. Then you should also update
> fstab to reflect the numbering change.
> I don't know of any way to change the ata numbering scheme.
> Mainboard controllers always seem to be probed (and numbered)
> firs
> You might use loader(8) to set the root device ("rootdev"
> variable) explicitly to ar1s1a. Then you should also update
> fstab to reflect the numbering change.
> I don't know of any way to change the ata numbering scheme.
> Mainboard controllers always seem to be probed (and numbered)
> first
Here is what I did, and the subsequent effect:
(Remember, ad4 and ad6 (promise drives) make up the bootable ar0):
# after 2 brand new drives installed:
- atacontrol create RAID1 ad0 ad2
...at which point it said it was successful, and designated the new RAID
config as ad1.
After reboot, the se
> Please clarify. You said you added two new disks to the
> 'regular ide chain' and then created another RAID1 config for
> those disks.
>
> Are the new drives connected to the Promise RAID controller,
> or the motherboard's IDE controllers?
>
The original RAID, 2 ide drives connected to the
On Jun 17, 2005, at 2:36 PM, Steve Bertrand wrote:
Hey all,
I've been running my 4.11 box on a Promise RAID one card with no
difficulty.
Today I added 2 new disks to the regular IDE chain, and used
atacontrol
to create a second RAID1 configuration for those 2 new disks. After I
created wit
