Thanks Danny, that was indeed the problem.
For what it's worth, I had to use a last sector of 1953519871 instead of
1953519879, or 8 sectors shy of the "end" of the disk.
--
Eric Schoeller
Danny wrote:
On my ICH8R controller I have a 1.5TB partition and it works fine on
the latest Ubuntu with stock dmraid packages.
Is it possible that you are creating the 875GB partition larger than the device?
Try creating a 874GB partition, its possible that you are being
affected by the bug phillip was discussing on this list the other week
where it actually calculates the device size in a funny way.
On Thu, Jul 21, 2011 at 3:00 AM, Eric Schoeller
<eschoeller@xxxxxxxxxxxxxxxxxxxxx> wrote:
Hello list,
I recently acquired a system with an Intel 82801 SATA RAID controller. I'm
using dmraid to manage an RAID1 1TB volume. I created 3 partitions on this
RAID1 array, one of them being 875GB. When the system boots only the first
two partitions appear in /dev/mapper/isw_xxx_p[1-2]. And, of course the
volume group and logical volumes in the 3rd partition are nowhere to be
found. After running 'partprobe' the 3rd partition appears, along with my
logical volumes. If I remove the large 3rd partition and replace it with
something in the neighborhood of a 300GB partition, it works just fine upon
boot. I haven't figured out how large I can go before I hit this problem.
This is a fully updated kubuntu 11.04 machine running 2.6.38-10-generic.
dmraid version: 1.0.0.rc16
dmraid library version: 1.0.0.rc16
device-mapper version: 4.19.1
I poked around on the interwebs but couldn't find any info. Any help is
greatly appreciated!
--
Eric Schoeller
University of Colorado Boulder
Office of Information Technology
_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list
_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list
