Date: Thu, 6 Jan 2011 03:54:24 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Ian Smith <smithi@nimnet.asn.au> Cc: Bruce Cran <bruce@cran.org.uk>, FreeBSD Questions <freebsd-questions@freebsd.org>, Chris Brennan <xaero@xaerolimit.net> Subject: Re: a new hard-drive in a 2y/o laptop Message-ID: <AANLkTimXQXmk2t8xBN1H7fWkyNo%2BFyasU8KaSeakpnUJ@mail.gmail.com> In-Reply-To: <20110106160720.B49334@sola.nimnet.asn.au> References: <20101229120038.3DFB0106591A@hub.freebsd.org> <20101230133126.O36121@sola.nimnet.asn.au> <AANLkTinCZuupW%2BGFMeL70nPO90tZAAJNj8g0SaOztsR3@mail.gmail.com> <20101231105353.S36121@sola.nimnet.asn.au> <AANLkTinSbE8d=iYES78GJmYO2PyOAGHMjwQ%2B2HT45yxc@mail.gmail.com> <20110102102255.00004f57@unknown> <20110102230702.N49334@sola.nimnet.asn.au> <20110103022619.O49334@sola.nimnet.asn.au> <AANLkTimkCdtULT9jfNtwKcfxF8R-TQ_j=qZgS-Y-YGfu@mail.gmail.com> <20110104143245.P49334@sola.nimnet.asn.au> <AANLkTi=Aqh4cpmdkHx1QsTyoYh7nhinEfDUuPO3fUAh5@mail.gmail.com> <alpine.BSF.2.00.1101041840310.14633@wonkity.com> <20110105152725.U49334@sola.nimnet.asn.au> <AANLkTinfVLGomOj-Nanvr4sgei-p=HQ9-Mh0rXQQ7E%2Bw@mail.gmail.com> <20110106160720.B49334@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 6, 2011 at 3:06 AM, Ian Smith <smithi@nimnet.asn.au> wrote > Your dd of the first 71 sectors looked right, MBR looks ok, sectors 1-62 > are zeroes, boot1 and boot2 from sector 63-70 seem normal, after you > used 'W' to write anyway; can't say for sure that the bsdlabel is ok, > but see no reason to suppose otherwise. What says 'bsdlabel ad4s1' > while you've still got one? > This is a pretty easy problem to replicate if you are pressing W, and that "issue" has existed for quite some time. If you press W then Q at sysinstall fdisk then attempt to force write disklabel screens you will get the error. Just setup the slices and partitions as you want and let sysinstall handle the writing of information. There is a big warning box that says not to use force write except under certain conditions and this is not one of them. If you google the error message in the OP, the first result is: http://forums.freebsd.org/showthread.php?t=1675 Failing that, I can't see other than a hardware issue, unless somehow > sysinstall is broken and you may do better manually running fdisk and > bsdlabel and newfs per Handbook and manuals? > This doesn't say hardware error to me at all, at least not a disk hardware issue. The message was present across two disks, and if there truly is a problem writing to the media a complete zeroing of the drive would be apparent then. While we're getting people to look at sysinstall and the auto resizing, it would be nice to get the "Unable to create the partition. Too big?" issue resolved. You can trigger this by auto-sizing the partitions, deleting a couple and recreating one that a different size than one autosize suggested. Then create the second partion using the auto-populated value in partition size box. Typically run into this when making / a little bigger on amd64 installs by borrowing some space from /usr. It's very tedious to slowly decrease the size of the second partition in your attempts to create it if you're trying to utilize the whole drive. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimXQXmk2t8xBN1H7fWkyNo%2BFyasU8KaSeakpnUJ>