Date: Fri, 11 Jul 1997 17:55:11 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: johns@cruz.isle.net (John Scharles) Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: disk Hard Error Message-ID: <199707110825.RAA23381@genesis.atrad.adelaide.edu.au> In-Reply-To: <3.0.1.32.19970710122500.0085c730@mail.isle.net> from John Scharles at "Jul 10, 97 12:25:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
John Scharles stands accused of saying: > On powering up our FreeBSD 2.1.6 this morning we were greeted with a "hard > error reading block such&such" message. This is a Dell machine with a built > in IDE controller. Start looking for your warranty documentation; it is likely that that disk is still covered. > After looking through the handbook and archives I haven't found much > information about trying to recover files off a dying drive (it has the > /usr directory, which of course has some files that are nowhere else!). Is > there way I can look at or force a mount? Recovering data from a toasted disk is a black art; it's something you learn the hard way by desperation, not something that can be documented or proceduralised. You have just discovered why people make Regular Backups. With any luck, you won't have to learn the same lesson twice. > Also I saw some reference to a full drive causing this type of > error...could this be the cause of a hard error? No. > John -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707110825.RAA23381>