Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe

View: New views

7 Messages — Rating Filter: Alert me

	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by linimon :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Old Synopsis: GEOM_PART_* fails with sliced gstripe New Synopsis: [geom] GEOM_PART_* fails with sliced gstripe Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu Sep 17 10:20:28 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138891 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Synopsis: [geom] GEOM_PART_* fails with sliced gstripe State-Changed-From-To: open->closed State-Changed-By: marcel State-Changed-When: Thu Sep 17 20:25:11 UTC 2009 State-Changed-Why: Your disk partitioning is invalid. You cannot have both a MBR and a BSD disk label in the same place and independently of each other. ace# fdisk /dev/stripe/raid0 ace# bsdlabel /dev/stripe/raid0 If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is not the one that should be used. Fix the problem by wiping out the second sector on the disk. BTW: the problem is caused by creating a dangerously dedicated installation. It's known to be broken and should not be used. FYI, http://www.freebsd.org/cgi/query-pr.cgi?pr=138891 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message marcel@... wrote: > Your disk partitioning is invalid. You cannot have both a MBR and > a BSD disk label in the same place and independently of each other. > ace# fdisk /dev/stripe/raid0 > ace# bsdlabel /dev/stripe/raid0 > If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 > and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD > disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the > BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is > not the one that should be used. > Fix the problem by wiping out the second sector on the disk. > BTW: the problem is caused by creating a dangerously dedicated > installation. It's known to be broken and should not be used. > FYI, > After wiping out the second sector or the drive (dd seek=1 count=1 if=/dev/zero of=/dev/stripe/raid0) fdisk now reports "invalid fdisk partition table found" but GEOM_PART_* still does not locate the a slice and the b/d slices will not mount. I have never had a /dev/stripe/raid0s* node, just /dev/stripe/raid0[a-d]. Is there any way to fix this short of a full backup/restore? (The reason I used DD mode here was that since the gstripe wouldn't be visible to the BIOS -- or anything other than FreeBSD -- slicing seemed silly.) _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sep 22, 2009, at 5:12 PM, Stephen Hurd wrote: > > After wiping out the second sector or the drive (dd seek=1 count=1 > if=/dev/zero of=/dev/stripe/raid0) > fdisk now reports "invalid fdisk partition table found" but > GEOM_PART_* still does not locate the a slice and the b/d slices > will not mount. What is the sector size? > Is there any way to fix this short of a full backup/restore? I don't know yet... -- Marcel Moolenaar xcllnt@... _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Marcel Moolenaar wrote: >> After wiping out the second sector or the drive (dd seek=1 count=1 >> if=/dev/zero of=/dev/stripe/raid0) >> fdisk now reports "invalid fdisk partition table found" but >> GEOM_PART_* still does not locate the a slice and the b/d slices will >> not mount. > > What is the sector size? 512 according to diskinfo and gstripe list: > diskinfo /dev/stripe/raid0 /dev/stripe/raid0 512 42934992896 83857408 > gstripe list Geom name: raid0 State: UP Status: Total=4, Online=4 Type: AUTOMATIC Stripesize: 262144 ID: 40432321 Providers: 1. Name: stripe/raid0 Mediasize: 42934992896 (40G) Sectorsize: 512 Mode: r3w3e4 Consumers: 1. Name: da0s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 0 2. Name: da1s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 1 3. Name: da2s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 2 4. Name: da3s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 3 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sep 22, 2009, at 6:23 PM, Stephen Hurd wrote: > Marcel Moolenaar wrote: >>> After wiping out the second sector or the drive (dd seek=1 count=1 >>> if=/dev/zero of=/dev/stripe/raid0) >>> fdisk now reports "invalid fdisk partition table found" but >>> GEOM_PART_* still does not locate the a slice and the b/d slices >>> will not mount. >> >> What is the sector size? > > 512 according to diskinfo and gstripe list: Ok, so nothing weird. What I do see is that you created a RAID within MBR slices, so you can't have a MBR on top of the RAID. In other words, it's invalid to do: fdisk /dev/stripe/raid0 The correct location for the BSD disklabel would be sector 2 of the RAID. Can you dump sector 64 & 65 of raid0? (i.e. dd if=/dev/stripe/raid0 of=/tmp/raid0-64.dmp iseek=63 bs=512 count=2) -- Marcel Moolenaar xcllnt@... _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Marcel Moolenaar wrote: >>>> fdisk now reports "invalid fdisk partition table found" but >>>> GEOM_PART_* still does not locate the a slice and the b/d slices >>>> will not mount. >>> >>> What is the sector size? >> >> 512 according to diskinfo and gstripe list: > > Ok, so nothing weird. > > Can you dump sector 64 & 65 of raid0? > (i.e. dd if=/dev/stripe/raid0 of=/tmp/raid0-64.dmp iseek=63 bs=512 > count=2) All zeros. > dd if=/dev/stripe/raid0 iseek=63 bs=512 count=2 \| hd -C 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 \|................\| 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 \|................\| * 2+0 records in 2+0 records out 1024 bytes transferred in 0.004813 secs (212759 bytes/sec) 00000400 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."

	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by linimon :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Old Synopsis: GEOM_PART_* fails with sliced gstripe New Synopsis: [geom] GEOM_PART_* fails with sliced gstripe Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu Sep 17 10:20:28 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138891 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Synopsis: [geom] GEOM_PART_* fails with sliced gstripe State-Changed-From-To: open->closed State-Changed-By: marcel State-Changed-When: Thu Sep 17 20:25:11 UTC 2009 State-Changed-Why: Your disk partitioning is invalid. You cannot have both a MBR and a BSD disk label in the same place and independently of each other. ace# fdisk /dev/stripe/raid0 ace# bsdlabel /dev/stripe/raid0 If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is not the one that should be used. Fix the problem by wiping out the second sector on the disk. BTW: the problem is caused by creating a dangerously dedicated installation. It's known to be broken and should not be used. FYI, http://www.freebsd.org/cgi/query-pr.cgi?pr=138891 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message marcel@... wrote: > Your disk partitioning is invalid. You cannot have both a MBR and > a BSD disk label in the same place and independently of each other. > ace# fdisk /dev/stripe/raid0 > ace# bsdlabel /dev/stripe/raid0 > If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 > and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD > disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the > BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is > not the one that should be used. > Fix the problem by wiping out the second sector on the disk. > BTW: the problem is caused by creating a dangerously dedicated > installation. It's known to be broken and should not be used. > FYI, > After wiping out the second sector or the drive (dd seek=1 count=1 if=/dev/zero of=/dev/stripe/raid0) fdisk now reports "invalid fdisk partition table found" but GEOM_PART_* still does not locate the a slice and the b/d slices will not mount. I have never had a /dev/stripe/raid0s* node, just /dev/stripe/raid0[a-d]. Is there any way to fix this short of a full backup/restore? (The reason I used DD mode here was that since the gstripe wouldn't be visible to the BIOS -- or anything other than FreeBSD -- slicing seemed silly.) _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sep 22, 2009, at 5:12 PM, Stephen Hurd wrote: > > After wiping out the second sector or the drive (dd seek=1 count=1 > if=/dev/zero of=/dev/stripe/raid0) > fdisk now reports "invalid fdisk partition table found" but > GEOM_PART_* still does not locate the a slice and the b/d slices > will not mount. What is the sector size? > Is there any way to fix this short of a full backup/restore? I don't know yet... -- Marcel Moolenaar xcllnt@... _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Marcel Moolenaar wrote: >> After wiping out the second sector or the drive (dd seek=1 count=1 >> if=/dev/zero of=/dev/stripe/raid0) >> fdisk now reports "invalid fdisk partition table found" but >> GEOM_PART_* still does not locate the a slice and the b/d slices will >> not mount. > > What is the sector size? 512 according to diskinfo and gstripe list: > diskinfo /dev/stripe/raid0 /dev/stripe/raid0 512 42934992896 83857408 > gstripe list Geom name: raid0 State: UP Status: Total=4, Online=4 Type: AUTOMATIC Stripesize: 262144 ID: 40432321 Providers: 1. Name: stripe/raid0 Mediasize: 42934992896 (40G) Sectorsize: 512 Mode: r3w3e4 Consumers: 1. Name: da0s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 0 2. Name: da1s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 1 3. Name: da2s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 2 4. Name: da3s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r3w3e5 Number: 3 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Marcel Moolenaar-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sep 22, 2009, at 6:23 PM, Stephen Hurd wrote: > Marcel Moolenaar wrote: >>> After wiping out the second sector or the drive (dd seek=1 count=1 >>> if=/dev/zero of=/dev/stripe/raid0) >>> fdisk now reports "invalid fdisk partition table found" but >>> GEOM_PART_* still does not locate the a slice and the b/d slices >>> will not mount. >> >> What is the sector size? > > 512 according to diskinfo and gstripe list: Ok, so nothing weird. What I do see is that you created a RAID within MBR slices, so you can't have a MBR on top of the RAID. In other words, it's invalid to do: fdisk /dev/stripe/raid0 The correct location for the BSD disklabel would be sector 2 of the RAID. Can you dump sector 64 & 65 of raid0? (i.e. dd if=/dev/stripe/raid0 of=/tmp/raid0-64.dmp iseek=63 bs=512 count=2) -- Marcel Moolenaar xcllnt@... _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."
	Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe by Stephen Hurd :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Marcel Moolenaar wrote: >>>> fdisk now reports "invalid fdisk partition table found" but >>>> GEOM_PART_* still does not locate the a slice and the b/d slices >>>> will not mount. >>> >>> What is the sector size? >> >> 512 according to diskinfo and gstripe list: > > Ok, so nothing weird. > > Can you dump sector 64 & 65 of raid0? > (i.e. dd if=/dev/stripe/raid0 of=/tmp/raid0-64.dmp iseek=63 bs=512 > count=2) All zeros. > dd if=/dev/stripe/raid0 iseek=63 bs=512 count=2 \| hd -C 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 \|................\| 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 \|................\| * 2+0 records in 2+0 records out 1024 bytes transferred in 0.004813 secs (212759 bytes/sec) 00000400 _______________________________________________ freebsd-geom@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."