THE FOLLOWING DISK SECTORS COULD NOT BE READ

Derek Ragona derek at computinginnovations.com
Thu Aug 21 15:51:34 UTC 2008


At 08:24 AM 8/21/2008, Marcel Grandemange wrote:
>On a different dilemma, I have a FreeBSD proxy server with what looks like a
>failing drive.
>
>The drive ONLY holds cache so is not critical for system operation however
>id still like to try something.
>
>It seem that no matter how many times I run fsck it still comes up with same
>result, is there a way to isolate the bad sectors and use the replacement
>ones on drive? Or even just isolate so that I can continue using the drive
>for now.
>
>
>
>su-2.05b# fsck -y /dev/ad1s1d
>
>** /dev/ad1s1d
>
>** Last Mounted on /mnt/cache
>
>** Phase 1 - Check Blocks and Sizes
>
>
>
>CANNOT READ BLK: 15430784
>
>UNEXPECTED SOFT UPDATE INCONSISTENCY
>
>
>
>CONTINUE? yes
>
>
>
>THE FOLLOWING DISK SECTORS COULD NOT BE READ: 15430836, 15430837, 15430838,
>1543                                  0839, 15430840, 15430841, 15430842,
>15430843, 15430844, 15430845, 15430846, 1543
>0847,
>
>** Phase 2 - Check Pathnames
>
>** Phase 3 - Check Connectivity
>
>** Phase 4 - Check Reference Counts
>
>** Phase 5 - Check Cyl groups
>
>366612 files, 8044663 used, 1423024 free (125376 frags, 162206 blocks, 1.3%
>frag                                  mentation)
>
>
>
>***** FILE SYSTEM STILL DIRTY *****
>
>
>
>***** PLEASE RERUN FSCK *****
>
>su-2.05b# fsck -y /dev/ad1s1d
>
>** /dev/ad1s1d
>
>** Last Mounted on /mnt/cache
>
>** Phase 1 - Check Blocks and Sizes
>
>
>
>CANNOT READ BLK: 15430784
>
>UNEXPECTED SOFT UPDATE INCONSISTENCY
>
>
>
>CONTINUE? yes
>
>
>
>THE FOLLOWING DISK SECTORS COULD NOT BE READ: 15430836, 15430837, 15430838,
>1543                                  0839, 15430840, 15430841, 15430842,
>15430843, 15430844, 15430845, 15430846, 1543
>0847,
>
>** Phase 2 - Check Pathnames
>
>** Phase 3 - Check Connectivity
>
>** Phase 4 - Check Reference Counts
>
>** Phase 5 - Check Cyl groups
>
>366612 files, 8044663 used, 1423024 free (125376 frags, 162206 blocks, 1.3%
>frag                                  mentation)
>
>
>
>***** FILE SYSTEM STILL DIRTY *****
>
>
>
>***** PLEASE RERUN FSCK *****

Sounds like the media has failed.  You can try running diagnostics from the 
hard drive manufacturer and test the disk, but you likely need to replace it.

         -Derek

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



More information about the freebsd-questions mailing list