Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

8.1 Pre-release gpart, isn't setting type correctly

0 views
Skip to first unread message

Phil

unread,
May 31, 2010, 3:00:57 AM5/31/10
to
Performing the following gpart commands on either a hard disk or
usb memory stick doesn't correctly store the gpart type information.

What we're doing, using FreeBSD 8.1-PRERELEASE, csuped as at
30-May-2010 23:59 UTC (*default date=2010.05.30.23.59.59)

# gpart create -s GPT da1
# gpart add -s 1G -t freebsd-ufs da1
# gpart show da1

=> 34 7827325 da1 GPT (3.7G)
34 2097152 1 !00000000-0000-0000-0000-000000000000 (1.0G)
2097186 5730173 - free - (2.7G)

Expected to see something like:
34 2097152 1 freebsd-ufs (1.0G)

# gpart list da1
Geom name: da1
fwheads: 255
fwsectors: 63
last: 7827358
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: da1p1
Mediasize: 1073741824 (1.0G)
Sectorsize: 512
Mode: r0w0e0
rawtype: 00000000-0000-0000-0000-000000000000
label: (null)
length: 1073741824
offset: 17408
type: !00000000-0000-0000-0000-000000000000
index: 1
end: 2097185
start: 34
Consumers:
1. Name: da1
Mediasize: 4007624704 (3.7G)
Sectorsize: 512
Mode: r0w0e0

If I reboot the machine, only the /dev/da1 devices is recognised, there is
no /dev/da1p1. Also "gpart modify -i 1 -t freebsd-ufs da1" did not have
any effect on the "gpart list"

We have a similar outcome when using the HDD,
=> 34 976773101 ada0 GPT (466G)
34 128 1 !00000000-0000-0000-0000-000000000000 (64K)
162 8388608 2 !00000000-0000-0000-0000-000000000000 (4.0G)
8388770 4194304 3 !00000000-0000-0000-0000-000000000000 (2.0G)
12583074 25165824 4 !00000000-0000-0000-0000-000000000000 (12G)
37748898 33554432 5 !00000000-0000-0000-0000-000000000000 (16G)
71303330 4096 6 !00000000-0000-0000-0000-000000000000 (2.0M)
71307426 10485760 7 !00000000-0000-0000-0000-000000000000 (5.0G)
81793186 33554432 8 !00000000-0000-0000-0000-000000000000 (16G)
115347618 566231040 9 !00000000-0000-0000-0000-000000000000 (270G)
681578658 16384 10 !00000000-0000-0000-0000-000000000000 (8.0M)
681595042 4194304 11 !00000000-0000-0000-0000-000000000000 (2.0G)
685789346 290983789 12 !00000000-0000-0000-0000-000000000000 (139G)

Hardware: Used two different motherboards: Gigabyte (without ahci available)
and
VIA SN1800 (with ahci available and enabled); two hard disks (WD500AAKS)and
one
usb memory stick.

Initially I thought it was the ahci timeouts, but using different
motherboards,
and a usb drive disproved that association.

If there is anything that I can do, or provide to help resolve this, I'm
happy
to do so.

Regards, Phil
Sydney Australia (GMT+10 hours)

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"

Hiroki Sato

unread,
May 31, 2010, 4:04:17 AM5/31/10
to
"Phil" <ph...@amdg.etowns.org> wrote
in <580CA5B8F8654FC782CC1137614582C3@HS>:

ph> Performing the following gpart commands on either a hard disk or
ph> usb memory stick doesn't correctly store the gpart type information.
ph>
ph> What we're doing, using FreeBSD 8.1-PRERELEASE, csuped as at
ph> 30-May-2010 23:59 UTC (*default date=2010.05.30.23.59.59)
ph>
ph> # gpart create -s GPT da1
ph> # gpart add -s 1G -t freebsd-ufs da1
ph> # gpart show da1
ph>
ph> => 34 7827325 da1 GPT (3.7G)
ph> 34 2097152 1 !00000000-0000-0000-0000-000000000000 (1.0G)
ph> 2097186 5730173 - free - (2.7G)

This is probably the same issue reported at
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F142174 and already
fixed on CURRENT. I guess the fix will be merged to 8.X soon.

-- Hiroki

0 new messages