Date: Sat, 02 Sep 2000 16:42:26 -0700 From: "Kevin Oberman" <oberman@es.net> To: Siegbert Baude <siegbert.baude@gmx.de> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@FreeBSD.ORG> Subject: Re: Problems with slice setup in Fujitsu disk Message-ID: <200009022342.e82NgQU27033@ptavv.es.net> In-Reply-To: Your message of "Sat, 02 Sep 2000 02:02:34 %2B0200." <39B0439A.482BEC72@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Sat, 02 Sep 2000 02:02:34 +0200 > From: Siegbert Baude <siegbert.baude@gmx.de> > Sender: owner-freebsd-questions@FreeBSD.ORG > > > If I try to use sysinstall to look at the slices, I get something > > similar. I tell it to use the whole disk for the first slice, but it > > shows that I have a slice ending at 26687807 and an unused space of > > 768 blocks. This matches the difference between 26688576 and > > 26687808.) > > > > Is this the cause of the errors and, if so, how can it be fixed? fdisk > > (in sysinstall) is adamant about leaving 768 blocks. > > Try fdisk from the command prompt. You can specify CHS begin and end addresses, > which fdisk will actually use. > > I had fdisk problems with some "automatic" corrections of cylinder boundaries, > which exactly were cylinder boundaries, but fdisk correction suggestions were > NOT. So I used those CHS values to enforce things. Worked then. Siegbert, Thanks for the suggestion, but I don't think it will work for my disk. It's 13.6 GB and the upper limit on CHS addressing, to the best of my knowledge, is 8.4 GB. Also, like many large disks, the number of sectors per track increases as you move to the outside of the disk from 286 to 502. The result is that it's really impossible to do CHS addressing. I suspect that the fact that the disk can't be treated in any way like a CHS disk may well have something to do with the problem. And it's also possible that the fact that it was initially sliced when using the old wd driver has some bearing on this. But thanks for the suggestion. I just wish I knew what the kernel errors were all about. I suspect that they would at least confirm which drive is the source of the errors! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009022342.e82NgQU27033>