Re: Invalid fdisk partition table found (fwd)

2011-11-28 Thread Robert
) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg

Re: Invalid fdisk partition table found (fwd)

2011-11-28 Thread Warren Block
to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found [robert@dell64] ~ sudo gpart destroy da1 Password: gpart: Device busy gpart won't destroy a GEOM unless it's unused. So either delete all the partitions

Re: Invalid fdisk partition table found (fwd)

2011-11-28 Thread Robert
On Mon, 28 Nov 2011 08:02:55 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Mon, 28 Nov 2011, Robert wrote: Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. Before giving up, a few more suggestions. First, check the BIOS

Re: Invalid fdisk partition table found (fwd)

2011-11-28 Thread Warren Block
On Mon, 28 Nov 2011, Robert wrote: I did discover that an external card reader I was using on the Windows XP computer is defective. It had a bent pin and another recessed pin. I hope that is not what damaged these cards. Ouch. That sounds like a logical cause. Although the card itself has

Re: Invalid fdisk partition table found (fwd)

2011-11-26 Thread Robert
sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg

Re: Invalid fdisk partition table found (fwd)

2011-11-26 Thread Warren Block
=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts

Re: Invalid fdisk partition table found (fwd)

2011-11-26 Thread Fbsd8
Robert wrote: Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. You can get a small script that erases the primary GPT table from the front of the HD and the secondary GPT table from the end of the

Re: Invalid fdisk partition table found (fwd)

2011-11-26 Thread Fbsd8
heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS

Re: Invalid fdisk partition table found

2011-11-25 Thread Lowell Gilbert
sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag

Re: Invalid fdisk partition table found (fwd)

2011-11-25 Thread Robert
disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512

Re: Invalid fdisk partition table found (fwd)

2011-11-25 Thread Warren Block
*** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector

Re: Invalid fdisk partition table found (fwd)

2011-11-24 Thread Julian H. Stacey
extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts

Re: Invalid fdisk partition table found (fwd)

2011-11-24 Thread Robert
/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl

Re: Invalid fdisk partition table found (fwd)

2011-11-24 Thread Warren Block
to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition

Invalid fdisk partition table found

2011-11-23 Thread Robert
partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1

Re: Invalid fdisk partition table found

2011-11-23 Thread Julian H. Stacey
blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active

Re: Invalid fdisk partition table found

2011-11-23 Thread Carl Johnson
Julian H. Stacey j...@berklix.com writes: @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 echo unplug, reinsert newfs /dev/da1a 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 It

Re: Invalid fdisk partition table found

2011-11-23 Thread Julian H. Stacey
Hi, Reference: From: Carl Johnson ca...@peak.org Date: Wed, 23 Nov 2011 14:53:41 -0800 Message-id: 87bos2e9hm.fsf@oak.localnet Carl Johnson wrote: Julian H. Stacey j...@berklix.com writes: @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 echo unplug,

Re: Invalid fdisk partition table found

2011-11-23 Thread Warren Block
On Wed, 23 Nov 2011, Julian H. Stacey wrote: 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 But that's not quite correct. Setting debugflags to 16 allows writes to a partition that's mounted, something

Fw: Invalid fdisk partition table found

2011-11-23 Thread Robert
Just noticed that I did not include questions@. It has been a long day. Begin forwarded message: Date: Wed, 23 Nov 2011 19:21:54 -0800 From: Robert travelin...@cox.net To: Julian H. Stacey j...@berklix.com Subject: Re: Invalid fdisk partition table found Julian and Warren thanks