fsck unable to repair volumes

From: Kathleen Ellis (kathleen_at_umbc.edu)
Date: 02/21/05

  • Next message: Alistair McKeown: "Splitting a file into 10." 
    Date: Mon, 21 Feb 2005 10:34:08 -0500 (EST)
To: sunmanagers@sunmanagers.org

    I'm running Veritas Volume Manager on my Sun Fire v880 and I'm unable to
    mount several file systems managed by it. fsck is unable to help me out.
    iostat -En indicates some trouble with one of my disks.

    Summary will be posted, many thanks in advance.

    bash-2.05# fsck -y /dev/vx/rdsk/a1000G/fy02claims
    ** /dev/vx/rdsk/a1000G/fy02claims

    CANNOT READ: BLK 167688672
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05# fsck -y /dev/vx/rdsk/a1000F/updateclaims
    ** /dev/vx/rdsk/a1000F/updateclaims

    CANNOT READ: BLK 129253920
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05# fsck -y /data/mmis2/newerclaims/fy04claims2
    ** /dev/vx/rdsk/a1000F/fiscal

    CANNOT READ: BLK 167688672
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05# fsck -y /data/updates/text/claims
    ** /dev/vx/rdsk/a1000F/textclaims

    CANNOT READ: BLK 113097184
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05# fsck -y /data/mmis2/fiscal01/claims
    ** /dev/vx/rdsk/a5200dg/newclaims

    CANNOT READ: BLK 146716064
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05# fsck -y /data/projects/forbabi/forjo
    ** /dev/vx/rdsk/a5200dg/vol12forjo

    CANNOT READ: BLK 70647840
    CONTINUE? yes

    THE FOLLOWING SECTORS COULD NOT BE READ: 0 0 0 0
    bash-2.05#

    iostat -En

    c3t112d0 Soft Errors: 0 Hard Errors: 1 Transport Errors: 1
    Vendor: SEAGATE Product: ST19171FCSUN9.0G Revision: 7D7E Serial No:
    9818U31875
    Size: 9.06GB <9055065600 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 0 Predictive Failure Analysis: 0

    Kathleen M. Ellis, Unix Administrator
    Center for Health Program Development and Management
    SS 201 x6863
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Alistair McKeown: "Splitting a file into 10."

    Relevant Pages

    • fsck woes: no -b option?
      ... when running fsck, i get the ... 32 is not a file system superblock ... CANNOT READ BLK: 458687976 ... THE FOLLOWING DISK SECTORS COULD NOT BE READ: ...
      (freebsd-questions)
    • SUMMARY: fsck unable to repair volumes
      ... The file systems had mount points on a bad file system that had unreadable ... > CANNOT READ: BLK 167688672 ... > Center for Health Program Development and Management ...
      (SunManagers)
    • Re: Problems Cloning a disk
      ... > newfs, it reported the superblocks so they should be there. ... > CANNOT READ: BLK 16 ... Wha? ... device, but it looks like the 'fsck /u' was doing that, so it's unlikely ...
      (comp.unix.solaris)