Re: unknown partition table
On Wed, Oct 30, 2002 at 04:12:05PM -0800, Philippe Troin wrote:
> Sven Lankes <firstname.lastname@example.org> writes:
> > On Mon, Oct 28, 2002 at 01:14:22AM -0500, Ben Collins wrote:
> > >>> Device Flag Start End Blocks Id System
> > >>> /dev/sdb1 0 2733 2077080 fd Linux raid autodetect
> > >>> /dev/sdb3 0 2733 2077080 5 Whole disk
> > >> Change that to be:
> > >> /dev/sdb1 1 2733 ??????? fd Linux raid autodetect
> > >> /dev/sdb3 0 2733 2077080 5 Whole disk
> > >> The partition table lies in the first sector.
> > Ok - that helped. The raid arrays work now.
> Glad to hear that.
> > > And any self-respecting filesystem doesn't touch the first sector of the
> > > partition for that very reason. Unless Linux raid autodetect partitions
> > > are broken.
> Actually, I've checked and I can confirm that LVM obliterates the
> first sector when one pvcreates a volume. It probably stores a
> signature (LVM UUID, etc...) there.
Somebody ~:^) might want to be careful with phrases like "... any
self-respecting filesystem doesn't touch the first sector ..." because I
don't think that the underlying filesystem type was ever mentioned, so
if could be ... well, anything. And the Politics of Linux File Systems
should itself be a graduate level course in the CS curriculum of most
And oh yeah, lvm isn't a filesystem. Yet. Stranger things ....
I've had problems with the raid code playing badly with the label/bdev code
from waaay back in 2.2 land. It's good to hear that you can work around
it with the starting sector thing now, 'cuz that never worked for me in 2.2.