From owner-freebsd-questions@FreeBSD.ORG Wed Apr 11 12:24:31 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 A95BE16A400 for ; Wed, 11 Apr 2007 12:24:31 +0000 (UTC) (envelope-from tanavst@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 21D1613C45B for ; Wed, 11 Apr 2007 12:24:30 +0000 (UTC) (envelope-from tanavst@googlemail.com) Received: by ug-out-1314.google.com with SMTP id 71so100632ugh for ; Wed, 11 Apr 2007 05:24:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=qZb4Av/JB/LW/cJZRVaJi/ZNhPtUrKJVpVeFAEUf2UZ05BkwcgtGvK6cSPI3IdDEJf/QIgbbQdw99hElARvSDn5pyLChYQUvwcKR2kpBbSMVaXtxsV6nByVdYLddxtyPzk+A5fi1Odhe8H/8nioyLjdD2f9j3XwnlQ973qhs1sU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=afy4wqV1GnTBkzxbsKQSVGn+SOeoEWLFakU0xI3wD0t9Xy8qUWcz5bkzn16ezrtVzn0VyTKPmasC+hzhuflsfiakZembKrmtqCa0pSfqv/xvg/24Y/vnzQ4VtUfnGn35YXPI5Qy/u40A7vZQmKiXUKHsyeU6H5TmoNJVIaYNGSw= Received: by 10.67.27.15 with SMTP id e15mr396496ugj.1176292564080; Wed, 11 Apr 2007 04:56:04 -0700 (PDT) Received: by 10.66.241.7 with HTTP; Wed, 11 Apr 2007 04:56:04 -0700 (PDT) Message-ID: Date: Wed, 11 Apr 2007 14:56:04 +0300 From: "=?ISO-8859-1?Q?Taavi_T=E4navsuu?=" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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:24:31 -0000 Hi, Got a brand new Samsung 250 GB IDE harddisk, added it to my home PC running FreeBSD 5.3, created FreeBSD filesystem there. I have been using it for several months, keeping relatively large (5-10 GB) home video files there, and it has been working fine. But now suddenly got the following problem: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# fsck -f /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, PARTIALLY TRUNCATED INODE I=3D4498435 SALVAGE? [yn] y INCORRECT BLOCK COUNT I=3D4498438 (673600 should be 667584) CORRECT? [yn] y INCORRECT BLOCK COUNT I=3D4498439 (467936 should be 459392) CORRECT? [yn] y INCORRECT BLOCK COUNT I=3D19595269 (838304 should be 829248) CORRECT? [yn] y PARTIALLY TRUNCATED INODE I=3D20843652 SALVAGE? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) ***** FILE SYSTEM STILL DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK ***** pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) ***** FILE SYSTEM STILL DIRTY ***** ***** PLEASE RERUN FSCK ***** pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) ***** FILE SYSTEM STILL DIRTY ***** ***** PLEASE RERUN FSCK ***** pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I'm not yet very familiar with harddisks, filesystems, and FreeBSD, but is there anything else i could try to make the disk usable again, or is it somehow physically damaged? -taavi "k6ps" t=E4navsuu