Date: Sat, 13 Sep 1997 13:43:31 -0400 (EDT) From: "John T. Farmer" <jfarmer@sabre.goldsword.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jasonl@xinetron.com Cc: jfarmer@goldsword.com Subject: Re: Failed to install on WD WDC33100H HDD Message-ID: <199709131743.NAA09598@sabre.goldsword.com>
next in thread | raw e-mail | index | archive | help
On Fri, 12 Sep 1997 07:53:21 -0700 Jason Liao said: >I tried to install FreeBSD 2.2.1 and 2.2.2 to a Western Digital >WDC33100H IDE HDD (3.1G). The kernel booted off the floppy and detected >the correct model and size of the HDD. However, it hung after >displaying `/stand/sysinstall running as init on vty0'. Pressing Alt+F3 >made the computer scream and only a hard reset could stop it. >Installing to other HDDs is OK. > >Then I hooked the WDC33100H as a slave disk to an existing FreeBSD 2.2.1 >system. When I tried to fdisk, fdisk reported wrong geometry and the >kernel gave out lots of error messages: >wd1s1c: hard error reading fsbn 1wd1: status 59<rdy, seekdone, drq, err> >error 10<no_id> > >I connected the HDD back to a new system as the only HDD and booted with >a kernel from a floppy diskette. I issued the following command: >dd if=/dev/rwd0c of=/dev/null bs=1b count=512 >I got the error message: >wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: >status 0 error 0 >wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: >status 0 error 1 <no_dam> >The error messages repeated and the system hung. > >Any hints? Your help is appreciated. > >P.S. I tried this HDD on different computers ( Pentium and Pentium >PRO), the same result. The HDD is OK in DOS environment. I heard of >someone else encountered this problem on WD HDDs about 1 or 2 months >ago. I don't recall seeing the thread on WD drives, but I use the WD cavier drives (EIDE) models for all my clients' Win/Dos, etc. workstations AND for low end mail servers & routers. Matter of fact, I have one with the 2.1gb drive running on the build/burn-in bench now... What type of motherboard/controller are you using with the drive? It sounds like a BIOS/LBA type conflict, though the drive should be detectable. When you boot the board, what does the BIOS tell you? Is it auto-detecting the drive? Setting up any weird mappings? Are you setting the disk up to be used by both WinDos and FreeBSD? John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709131743.NAA09598>