From owner-freebsd-questions@FreeBSD.ORG Wed Apr 11 12:47:07 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 389AA16A404 for ; Wed, 11 Apr 2007 12:47:07 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.freebsd.org (Postfix) with ESMTP id F2F4113C489 for ; Wed, 11 Apr 2007 12:47:06 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.141] (helo=anti-virus02-08) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1HbcE5-0004B0-Lh; Wed, 11 Apr 2007 13:47:05 +0100 Received: from [62.31.10.181] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1HbcE4-0005Lx-1q; Wed, 11 Apr 2007 13:47:04 +0100 Message-ID: <461CD8C7.30902@dial.pipex.com> Date: Wed, 11 Apr 2007 13:47:03 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Taavi_T=E4navsuu?= References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Harddisk problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 12:47:07 -0000 Taavi T=E4navsuu wrote: > > I'm not yet very familiar with harddisks, filesystems, and FreeBSD,=20 > but is > there anything else i could try to make the disk usable again, or is it= > somehow physically damaged? There are two possibilities: 1) The disk is damaged. From your output that's what I'd think. =20 Download the Samsung diagnostics for your disk and try them. If the=20 disk fails those, then you should be able to get a warranty=20 replacement. Before that, you could try installing the "smartmontools"=20 port and running "smartctl -a /dev/{your disk}". That will tell you if=20 the disk itself thinks it is dying. 2) But before you do any of that, try changing the cable that connects=20 your disk. It may be as simple as that, but your errors are a bit too=20 specific for me to believe this is the problem. After changing the=20 cable try your fsck again. But really, this looks like a long shot. 3) Before any of those things, copy your files somewhere else, if you=20 can. Dying disks often get worse. Not quite sure how you'll manage=20 that given that you don't seem to be able to mount the disk. Maybe=20 someone here will have an idea. Something with dd ought to work, if you = have somewhere to dd to. --Alex