Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!caen!math.ohio-state.edu!howland.reston.ans.net!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.questions Subject: Re: [Q] fsck and 'medium error' problems Date: 20 Dec 1994 03:34:23 GMT Organization: University of California, Berkeley Lines: 31 Message-ID: <3d5jbv$cun@agate.berkeley.edu> References: <YOCUM.94Dec19155436@sparticus.gateway.cybernet.com> NNTP-Posting-Host: violet.berkeley.edu In article <YOCUM.94Dec19155436@sparticus.gateway.cybernet.com>, todd yocum <yocum@cybernet.com> wrote: >and are receiving the following error messages from fsck everytime >on bootup: > >sd0(aha0:0:0): medium error, info = 848030 (decimal) > >Cannot read: BLK 663616 > >Continue(Y/N)? y > >sd0(aha0:0:0): medium error, info = 848030 (decimal) >sd0(aha0:0:0): medium error, info = 848031 (decimal) Several possible things: 1. Your controller is flakey. 2. Your cabling is bad. 3. Your disk is dying. Most common is #3, but I note the other two just so that you can eliminate them first. The controller is easy, just swap it with another one to see if the problem goes away, then check your cabling very carefully, checking for strains or connectors coming loose, then think about replacing that disk! I just had a PD1800 die in freefall with these same messages. It's now swapped out and will shortly be on its way back to the manufacturer. Most people don't realize that a good drive will have a 5 year (or longer) warrantee! Jordan