fdisk problem
Hello I exchange my harddisk in my notebook (old 53GB, new 76GB). The old one I divided in two partitions: 30 GB (Windows XP) / 23GB (FreeBSD 6.1). Now I moved over to the new one (43GB / 23GB) with Acronis TrueImage without any problems. Both os runs without any changes (I was very surpesed). Now I would mount the rest 10GB with a new slice to the existing one. Now I can create the slice with fdisk but not write the settings (typ w). I also see the following when I start fisk: ? Message ?? ?WARNING: A geometry of 165398/15/63 for ad0 is incorrect. Using ? ?a more likely geometry. If this geometry is incorrect or you ? ?are unsure as to whether or not it's correct, please consult ? ?the Hardware Guide in the Documentation submenu or use the ? ?(G)eometry command to change it now. ? ? ? ?Remember: you need to enter whatever your BIOS thinks the ? ?geometry is! For IDE, it's what you were told in the BIOS ? ?setup. For SCSI, it's the translation mode your controller is ? ?using. Do NOT use a ``physical geometry''. ? (100%)??? ? [ OK ] ? ??[ Press enter or space ]??? My fdisk output is: *** *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=165398 heads=15 sectors/track=63 (945 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=165398 heads=15 sectors/track=63 (945 blks/cyl) 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) start 63, size 69219297 (33798 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 239/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 69219360, size 65303280 (31886 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 239/ sector 63 The data for partition 3 is: The data for partition 4 is: The screen from fdisk * Disk name: ad0FDISK Partition Editor DISK Geometry: 9729 cyls/255 heads/63 sectors = 156296385 sectors (76316MB) Offset Size(ST)End Name PType Desc SubtypeFlags 0 63 62- 12 unused0 63 69219297 69219359ad0s1 4 NTFS/HPFS/QNX7 69219360 65303280 134522639ad0s2 8freebsd 165 134522640 21778848 156301487- 12 unused0 It seems like the fdisk output differs from the fdisk console output, but I'm not sure and very confused. Any ideas are welcome. -- Regards Martin Schweizer <[EMAIL PROTECTED]> PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; public key : http://www.pc-service.ch/pgp/public_key.asc; fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239; pgpIG0KaEcnJw.pgp Description: PGP signature
fdisk problem
Hello everybody we have a 2235Gb disk which we want to partition. If we use sysinstall->Configure->Fdisk and try to build a unique slice we get a message like 'Wrote FDISK partition information out successfully (100%)' but if we go back to fdisk it shows a freebsd slice of 187Gb plus an unused slice of 2048Gb. If we delete it and recreate a new slice, the problem persists. Is there any tutorial about using fdisk without using sysinstall? Thanks Valerio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fdisk problem
On 2005-07-18 15:47, Valerio daelli <[EMAIL PROTECTED]> wrote: > Hello everybody > we have a 2235Gb disk which we want to partition. > If we use sysinstall->Configure->Fdisk and try to build a unique slice > we get a message like > > 'Wrote FDISK partition information out successfully (100%)' > > but if we go back to fdisk it shows a freebsd slice of 187Gb > plus an unused slice of 2048Gb. > If we delete it and recreate a new slice, the problem persists. > Is there any tutorial about using fdisk without using sysinstall? If you're only going to use FreeBSD on the disk, you might find this post useful: http://keramida.serverhive.com/weblog/archives/2004-10-26/daemonizing-a-new-disk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fdisk problem [core dump]
Hi all, When I try to use fdisk with a Maxtor diamond plus 9 HD [ model 6Y080L0] I get an error during "Writing partition information to drive ad0" like "Segmentation fault (core dumped)" I do these steps: sysinstall-->configure-->fdisk A = Use Entire Disk w = Write Changes Boot Manager = Install the FreeBSD Boot Manager At this point I get the error while fdisk write information on disk: My system is: ---uname -a output:--- FreeBSD phoenix 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Motherboard: ASUS A7N8X deluxe processor AMD Athlon 2600 RAM: DDR 133 - 256 MB Could You help me? - Salve, il messaggio che hai ricevuto รจ stato inviato per mezzo del sistema di web mail interfree. Se anche tu vuoi una casella di posta free visita il sito http://club.interfree.it Ti aspettiamo! - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fdisk problem [core dump]
[EMAIL PROTECTED] () writes: > When I try to use fdisk with a Maxtor diamond plus 9 HD [ model 6Y080L0] I get an > error during "Writing partition information to drive ad0" like "Segmentation fault > (core dumped)" > I do these steps: > sysinstall-->configure-->fdisk > > A = Use Entire Disk > w = Write Changes > Boot Manager = Install the FreeBSD Boot Manager > > At this point I get the error while fdisk write information on disk: > > My system is: > ---uname -a output:--- > FreeBSD phoenix 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > Motherboard: ASUS A7N8X deluxe > processor AMD Athlon 2600 > RAM: DDR 133 - 256 MB > > Could You help me? Have you got the install completed? If so, try running fdisk directly. If not, see if 4.8 (the latest "production quality" release) exhibits the same symptoms. If you really need 5.x for some reason, ask on the -CURRENT list. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
