<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: File system Corrupt in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031008#M742800</link>
    <description>Bsides the above-mentioned methods look in the /var/adm/syslog/syslog.log file for lbolt or SCSI errors. They are also a sign of failing hardware. You could try dmesg unless it has been overwritten due to its cyclic nature.</description>
    <pubDate>Thu, 05 Jul 2007 14:49:28 GMT</pubDate>
    <dc:creator>Sandman!</dc:creator>
    <dc:date>2007-07-05T14:49:28Z</dc:date>
    <item>
      <title>File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031003#M742795</link>
      <description>Hi,&lt;BR /&gt;i am using J5600 machine with OS 11.11.The problem is this, one file system mount name  /var is corrupted and unable to mount. when I manually try to mount the /dev/vg00/lvol8 on /var the error message appear  vxfs mount: /dev/vg00/lvol8 is corrupted. Needs checking. When I use fsck to repair the file system the below mention output received&lt;BR /&gt;fsck -o full vxfs /dev/vg00/rlvol8&lt;BR /&gt;fsck: /etc/default/fs is used for determining the file system type&lt;BR /&gt;vxfs fsck: cannot stat vxfs&lt;BR /&gt;vxfs fsck: file system had I/O error(s) on meta-data.&lt;BR /&gt;log replay in progress&lt;BR /&gt;pass0 - checking structural files&lt;BR /&gt;pass1 - checking inode sanity and blocks&lt;BR /&gt;vxfs fsck: fsck read failure bno = 352367, off = 0, len = 8192&lt;BR /&gt;file system check failure, aborting&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Jul 2007 00:15:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031003#M742795</guid>
      <dc:creator>aamak</dc:creator>
      <dc:date>2007-07-03T00:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031004#M742796</link>
      <description>It seems your disk drive may have failed.</description>
      <pubDate>Tue, 03 Jul 2007 00:29:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031004#M742796</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-07-03T00:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031005#M742797</link>
      <description>Any other possibilitiesâ ¦.any method available to verify that its hardware Issue.&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Jul 2007 01:44:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031005#M742797</guid>
      <dc:creator>aamak</dc:creator>
      <dc:date>2007-07-03T01:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031006#M742798</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you could verify the disk.&lt;BR /&gt;&lt;BR /&gt;# dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024k&lt;BR /&gt;&lt;BR /&gt;and wait for an i/o error.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Tue, 03 Jul 2007 03:30:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031006#M742798</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2007-07-03T03:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031007#M742799</link>
      <description>It looks like some sectors on /dev/vg00/var might have gone bad. The right syntax to fix corrupted FS with type as vxfs is :&lt;BR /&gt;#fsck -F vxfs -o full -y /var&lt;BR /&gt;&lt;BR /&gt;#fsck -F vxfs -o full -y    (to verify all FSs with single entry).&lt;BR /&gt;&lt;BR /&gt;If alternate disk is there, try booting from alternate disk.&lt;BR /&gt;&lt;BR /&gt;-Srini</description>
      <pubDate>Thu, 05 Jul 2007 14:24:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031007#M742799</guid>
      <dc:creator>Srinivas Thokala_1</dc:creator>
      <dc:date>2007-07-05T14:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: File system Corrupt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031008#M742800</link>
      <description>Bsides the above-mentioned methods look in the /var/adm/syslog/syslog.log file for lbolt or SCSI errors. They are also a sign of failing hardware. You could try dmesg unless it has been overwritten due to its cyclic nature.</description>
      <pubDate>Thu, 05 Jul 2007 14:49:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corrupt/m-p/4031008#M742800</guid>
      <dc:creator>Sandman!</dc:creator>
      <dc:date>2007-07-05T14:49:28Z</dc:date>
    </item>
  </channel>
</rss>

