On 26/10/2005, at 12:13 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
wrote:
jon and marco,
thx for the quick replies. this is more or less what i expected.
if you install through the RAID controller, shouldn't it
autodetect the number of actually available sectors (i.e. the
"full" size modulo that required for the RAID info)? that's
the thing that really surprised me.
If there is already a disklabel on the disk detailing its geometry
then it will use that rather than write a new one based on the
geometry reported by the driver. To blow away the existing details
boot the installer, dd some zeros over the start of the disk (dd if=/
dev/zero of=/dev/rsd0c bs=512 count=1024), and then reboot. When you
install onto the disk this time it should have the correct values
since there were no previous ones on disk to use.
If dd seems a bit harsh you could try fdisk -i /dev/rsd0c followed by
disklabel -dE sd0.
Let us know how you go.
dlg
dlg and I had a look at this and we concur with Jon. You can
move a single
disk RAID 0 from behind the ami controller and use it as a
single disk. What
you can't do is going the other way around (from SATA
controller to RAID 0).
After reading your email we gathered it is what you did.
Can you please confirm that these were your installation steps?
when i did try to install through the controller, as suggested
above, the following (from my original post) happened:
"i then tried to reinstall onto that disk from the CD drive i
have attached to the machine with the RAID controller in it.
when it came time to create the partitions with disklabel, i
got the same error as before and it occurred when my /home
partition was being initialized."
or do i have to "manually" calculate the number of sectors i
can allocate in disklabel?
i will try to reproduce this if you feel it necessary.
regards,
jake
