HardDrive Help!!

beppler_at_comcast.net
Date: 06/20/05

  • Next message: Davor: "system slow on upgraded OSV 5.0.7" 
    Date: Mon, 20 Jun 2005 19:56:20 +0000
To: sco-misc@lists.celestial.com

    This is on SCO v5.07, I have a filesystem that was mounted and working fine last week. The system crashed this morning and 1 filesystem did not come back up.
     
    Mount Dir Filesystem blocks used free %used
    / /dev/root 10240000 8858384 1381616 87%
    /stand /dev/boot 61440 23390 38050 39%
    /appl /dev/appl 57339564 53345116 3994448 94%
    /mm_protot /dev/proto 102000 97270 4730 96%
    /appl/help cwc01:/cwc_web 2000000 1592918 407082 80%
    /wimg taz:/v/usr2/printout 14208140 13274456 933684 94%
    /cwc1 /dev/FS_3 71118480 54603008 16515472 77%
    /fs1 /dev/FS_1 71106240 34720788 36385452 49% ß--------- Works here, This was from last week
    /fs2 /dev/FS_2 35561248 9527600 26033648 27%
    /fs4 /dev/FS_4 71118480 2587320 68531160 4%
    /pph /dev/FS_5 142236960 14229218 128007742 11%
     
    When I attempt to mount I get the following:
     
    pluto # mount /dev/FS_1 /fs1
    mount: possibly damaged file system, mount failed: No space left on device (error 28)
    pluto #
     
    I tried to run fsck on it but I get the following:
     
    pluto # fsck -ofull /dev/FS_1
     
    /dev/FS_1
    HTFS File System: FS_1 Volume: FS_1
     
    ** Phase 1 - Check Blocks and Sizes
    DANGER: Filesystem being checked is larger than the device in which it is
            stored (/dev/FS_1). The filesystem is 35553120K while the
            device is 17776560K. Backup filesystem and recreate as soon as possible.
     
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Synchronous Write Log
    ** Phase 6 - Check Free List Bitmap
     
    CANNOT READ: BLK 35563516
    CONTINUE? [yn] y
     
    THE FOLLOWING DISK SECTORS COULD NOT BE READ: 35563516, 35563517,
    disk error reading logical block 17781758
     
     
    Am I hosed???
     
    Thanks
     
    Brandt
     
     
     
    Wm. Brandt Eppler, Jr.
    Unix Systems Administrator
    Practice Management Partners, Inc.
    Direct Phone: 443.544.2221
    Cell Phone: 443.677.3539

  • Next message: Davor: "system slow on upgraded OSV 5.0.7"

    Relevant Pages

    • Re: mount() function problem !
      ... mount() attaches the filesystem specified by source (which is often a device name, ... point within a file system. ... details of the options available for each filesystem type. ... Specifies the journalling mode for file data. ...
      (comp.lang.c)
    • Re: [autofs] [RFC] Towards a Modern Autofs
      ... >entangling autofs with that work. ... >filesystem it's willing to export. ... >>map is mounted. ... The result is that some users will see mount points ...
      (Linux-Kernel)
    • Re: UFS Bug: FreeBSD 6.1/6.2/7.0: MOKB-08-11-2006, CVE-2006-5824, MOKB-03
      ... They can simply mount a filesystem with any number of SUID ... root binaries on it and have their way with the box. ... They have physical access to the machine. ...
      (FreeBSD-Security)
    • Re: Xenix Filesystem
      ... > how do I mount a new filesystem in SCO Open Server 5.0.5? ... There is probably at least 2 or 3 divvy partitions within that fdisk ...
      (comp.unix.sco.misc)
    • cannot boot-up linux, unable to read superblock
      ... mount: error 22 mounting ext3 ... enable lvm and tried fsck for the volumes (one is empty volume? ... Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00 ...
      (RedHat)