Ian,
It looks like the error message is wrong - slice 7 overlaps slice 4 - note
that slice 4 ends at c6404, but slice 7 starts at c6394.
Slice 6 is also completely contained within slice 4's range of cylinders, but
that won't matter unless you attempt to use it.
Trev
Ian Collins wrote:
Trevor Watson wrote:
Ian,
It looks like the error message is wrong - slice 7 overlaps slice 4 -
note that slice 4 ends at c6404, but slice 7 starts at c6394.
Slice 6 is also completely contained within slice 4's range of
cylinders, but that won't matter unless you attempt to use it.
Ian Collins wrote:
Trevor Watson wrote:
Ian,
It looks like the error message is wrong - slice 7 overlaps slice 4 -
note that slice 4 ends at c6404, but slice 7 starts at c6394.
Slice 6 is also completely contained within slice 4's range of
cylinders, but that won't matter unless you
I don't suppose that it has anything to do with the flag being wm instead of
wu on your second drive does it? Maybe if the driver thinks slice 2 is
writeable, it treats it as a valid slice?
Trev
Ian Collins wrote:
Ian Collins wrote:
Trevor Watson wrote:
Ian,
It looks like the error
On Tue, 15 May 2007, Trevor Watson wrote:
I don't suppose that it has anything to do with the flag being wm
instead of wu on your second drive does it? Maybe if the driver thinks
slice 2 is writeable, it treats it as a valid slice?
If the slice doesn't take up the *entire* disk, then it
I have to drives with the same slices and I get an odd error if I try
and create a pool on one drive, but not the other:
Part TagFlag Cylinders SizeBlocks
0 swapwu 3 - 2642.01GB(262/0/0) 4209030
1 rootwm 265 -
