Date: 13 Oct 2005 10:58:18 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "Kamal R. Prasad" <kamalp@acm.org> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd has problems with bios Message-ID: <44y84xmpkl.fsf@be-well.ilk.org> In-Reply-To: <4F393520-539B-44F6-92BD-860CCF51A278@acm.org> References: <BA28DC66-E4C7-4C40-8332-D69D15B73FEF@acm.org> <57416b300510121719x1ae4033ue1f1af49e028512d@mail.gmail.com> <4F393520-539B-44F6-92BD-860CCF51A278@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kamal R. Prasad" <kamalp@acm.org> writes: > I have verified integrity of the hard disk and this problem shows up > on a new samsung 1604N hard disk too. It is a hard disk independet > problem. > > On 13-Oct-05, at 5:49 AM, Peter Clutton wrote: > > >> For some reason, the values of hard disk geometry (cylinders/head/ > >> sectors( are not accrptable to fdisk and when i agree to using > >> freebsd 's idea of disk geometryt, during sysinstall -I get an > >> error:-0 > >> UDMA_100 error:READWRITE Failure ICRC error. > >> > > > > > > Usually fdsisk asks you to check what the bios reports as the CHS > > and enter that > > manually, using the g option i believe. Have you tried this? > > > The bios has 4 modes auto, large, lba, chs in which to access the > hard disk. I ttried all 4 modes and it doesn't solve the problem. > > However as stated above, and looking at those errors, this may be a > > hardware problem. > > > The hardware is stable and I expect any hard disk to give the same > error essentially because the interaction between bios and freebsd is > the cause of the problem. A CRC error? Doesn't seem likely. Why do you say so? It's not like FreeBSD is using the BIOS at all at that point... Personally, I'd try another ATA cable; that's the most frequent cause of this particular symptom.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y84xmpkl.fsf>