fdisk: ERROR: failed to adjust; setting sysid to 0
Hi, I was wondering what is the proper procedure for using fdisk to setup slices on large disks/arrays? I seem to be getting an ERROR when fdisk tries to adjust the partition to start on a head boundary and end on a cylinder boundary. Should I ignore the warning re: partition does not end on a cylinder boundary and write the partition table? Or should I attempt to set all the correct numbers by hand, since the automatic correction fails? I've attached the warnings and errors I saw on fdisk. --mark fileserver1# fdisk -u *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=364716 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=364716 heads=255 sectors/track=63 (16065 blks/cyl) Do you want to change our idea of what BIOS thinks ? [n] 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 1564195181 (763767 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 165/ sector 59 Do you want to change it? [n] The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 1564195248, size 2147478417 (1048573 Meg), flag 0 beg: cyl 86/ head 166/ sector 1; end: cyl 640/ head 254/ sector 63 Do you want to change it? [n] The data for partition 3 is: UNUSED Do you want to change it? [n] yes Supply a decimal value for sysid (165=FreeBSD) [0] 165 Supply a decimal value for start [0] 3711673665 Supply a decimal value for size [0] 2147490495 fdisk: WARNING: partition does not end on a cylinder boundary fdisk: WARNING: this may confuse the BIOS or some operating systems Correct this automatically? [n] y fdisk: ERROR: could not adjust partition to start on a head boundary and end on a cylinder boundary. fdisk: ERROR: failed to adjust; setting sysid to 0 Explicitly specify beg/end address ? [n] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk: ERROR: failed to adjust; setting sysid to 0
--- mark burdett [EMAIL PROTECTED] wrote: Hi, I was wondering what is the proper procedure for using fdisk to setup slices on large disks/arrays? I seem to be getting an ERROR when fdisk tries to adjust the partition to start on a head boundary and end on a cylinder boundary. Should I ignore the warning re: partition does not end on a cylinder boundary and write the partition table? Or should I attempt to set all the correct numbers by hand, since the automatic correction fails? I've attached the warnings and errors I saw on fdisk. --mark fileserver1# fdisk -u *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=364716 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=364716 heads=255 sectors/track=63 (16065 blks/cyl) Do you want to change our idea of what BIOS thinks ? [n] 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 1564195181 (763767 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 165/ sector 59 Do you want to change it? [n] The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 1564195248, size 2147478417 (1048573 Meg), flag 0 beg: cyl 86/ head 166/ sector 1; end: cyl 640/ head 254/ sector 63 Do you want to change it? [n] The data for partition 3 is: UNUSED Do you want to change it? [n] yes Supply a decimal value for sysid (165=FreeBSD) [0] 165 Supply a decimal value for start [0] 3711673665 Supply a decimal value for size [0] 2147490495 fdisk: WARNING: partition does not end on a cylinder boundary fdisk: WARNING: this may confuse the BIOS or some operating systems Correct this automatically? [n] y fdisk: ERROR: could not adjust partition to start on a head boundary and end on a cylinder boundary. fdisk: ERROR: failed to adjust; setting sysid to 0 Explicitly specify beg/end address ? [n] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] As long as your not using DOS/Winblows/OS-2 you shouldn't have problems. Microsft/PC os's have the requirement that partition boundarys end on and begin on cylinder boundaries. The main thing is the BIOS, some of them will accept it some won't as they are setup to use DOS, et al. And I belive it would only mess up booting the system. This can be hit or miss so I would try it. If they aren't boot drives, and newfs completes sucessfully on the partitions then all should be ok. Any particular reason you are partitioning multiple partitions for FreeBSD? this should only be done if your planning on having multiple versions of FreeBSD/OpenBSD/NetBSD going. bsdlabel is where you slice the drive into different pieces for your filesystems. I have a scsi setup that I used a dangerously dedicated mode whose scsi bios says the partition table is corrupt, low level format required on one or more drives but FreeBSD don't care and boots up fine. These aren't the boot drives, but if BSD is only warning you then it won't care in the end. It just likes to try and play nice with other OSs unlike the other OSs. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk: ERROR: failed to adjust; setting sysid to 0
should be ok. Any particular reason you are partitioning multiple partitions for FreeBSD? this For some reason, when we ordered the server w/ freebsd pre-installed, the vendor created a slice which was less than half the size of the full raid array (2TB). Perhaps because sysinstall was having trouble with a slice larger than 2TB? This page -- http://www.freebsd.org/projects/bigdisk/ -- may be out of date, but it reports: sysinstall Not doneA full audit is needed. Reports exist of problems with 1TB partitions. --mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk: ERROR: failed to adjust; setting sysid to 0
--- mark burdett [EMAIL PROTECTED] wrote: should be ok. Any particular reason you are partitioning multiple partitions for FreeBSD? this For some reason, when we ordered the server w/ freebsd pre-installed, the vendor created a slice which was less than half the size of the full raid array (2TB). Perhaps because sysinstall was having trouble with a slice larger than 2TB? This page -- http://www.freebsd.org/projects/bigdisk/ -- may be out of date, but it reports: sysinstallNot doneA full audit is needed. Reports exist of problems with 1TB partitions. --mark wish I could say I had problems getting my system to see a full 2TB as one partition... informative link though, it sounds like when they implement what they want the only solution to upgrade is to pray. That or hope once the userland suite is update is complete; some kind of update, dump, use the new tools to prepare the drives, and restore. can't wait for that one. although I don't have the problem of having Terabytes to worry about yet... good luck -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
