<?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: Full fsck problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/7182060#M493052</link>
    <description>&lt;P&gt;Repair Root File System&lt;BR /&gt;Enter the boot menu and choose Advanced Options.&lt;BR /&gt;Select the Recovery mode and then “fsck”.&lt;BR /&gt;When prompted to remount the root file system choose “Yes”.&lt;BR /&gt;Once done, resume the normal boot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rachel Gomez&lt;/P&gt;</description>
    <pubDate>Fri, 03 Feb 2023 06:59:05 GMT</pubDate>
    <dc:creator>rachelgomez_123</dc:creator>
    <dc:date>2023-02-03T06:59:05Z</dc:date>
    <item>
      <title>Full fsck problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904242#M493048</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We had an electrical problem on our enviroment and after the rp4440 connected to DS2120 storage the "vg01" shows an error message during mounting a filesystem.&lt;/P&gt;&lt;P&gt;I tried to check with fsck but without success, and I would like to know if there anything that I can do to mount, without formating and restore data back.&lt;/P&gt;&lt;P&gt;#fsck -F vxfs -o full -y /dev/vg01/rlvol1&lt;BR /&gt;log replay in progress&lt;BR /&gt;vxfs fsck: fsck read failure bno = 3838776, off = 0, len = 8192&lt;BR /&gt;full file system check required, exiting ...&lt;/P&gt;&lt;P&gt;Please let me know if you know anything to help me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2016 16:18:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904242#M493048</guid>
      <dc:creator>Wilder Mellotto</dc:creator>
      <dc:date>2016-10-03T16:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Full fsck problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904377#M493049</link>
      <description>&lt;P&gt;The read failure indicates a disk problem. You should also see errors in the output from the command: dmesg&lt;BR /&gt;You will should also see errors logged in the file /var/adm/syslog/syslog.log&lt;/P&gt;&lt;P&gt;If the lvols in vg01 are mirrored (vgdisplay -v vg01). you can replace the bad disk (identified in syslog.log). Otherwise, you'll have to replace the bad disk and rebuild&amp;nbsp;vg01 and restore the lvol(s) from your backups.&lt;/P&gt;&lt;P&gt;One other possibility: did someone use the lvreduce command?&lt;BR /&gt;The read error may be caused by trying to read beyond the end of the lvol.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2016 01:39:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904377#M493049</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2016-10-04T01:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Full fsck problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904436#M493050</link>
      <description>&lt;P&gt;Routine question: was the filesystem check done against a &lt;EM&gt;mounted&lt;/EM&gt; filesystem (probably the rlvol1 was moutned read-only)?&lt;/P&gt;&lt;P&gt;A filesystem check should always be performed against an &lt;STRONG&gt;un&lt;/STRONG&gt;&lt;EM&gt;mounted&lt;/EM&gt; filesystem...so try first to unmount (umount) the filesystem which is experiencing the issue and repeat that exact fsck command against it once you're sure it is cleanly unmounted.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2016 07:56:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6904436#M493050</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2016-10-04T07:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: Full fsck problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6905103#M493051</link>
      <description>&lt;P&gt;I had no luck with cleaning the filesystem.&lt;/P&gt;&lt;P&gt;After the server and storage went down because a power outage, the fsck failed even when I tried to boot in low maintenance mode, always returing the same message "vxfs fsck: fsck read failure bno = 3838776, off = 0, len = 8192"&lt;/P&gt;&lt;P&gt;I have created a new VG with a new lvol and I did a restore data from a tape drive.&lt;/P&gt;&lt;P&gt;Sadly I lost about 6 hours in this restore procedure, but thanks to all for your answers, because I tried your sugestions before anything else.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2016 18:21:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/6905103#M493051</guid>
      <dc:creator>Wilder Mellotto</dc:creator>
      <dc:date>2016-10-05T18:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: Full fsck problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/7182060#M493052</link>
      <description>&lt;P&gt;Repair Root File System&lt;BR /&gt;Enter the boot menu and choose Advanced Options.&lt;BR /&gt;Select the Recovery mode and then “fsck”.&lt;BR /&gt;When prompted to remount the root file system choose “Yes”.&lt;BR /&gt;Once done, resume the normal boot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rachel Gomez&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 06:59:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full-fsck-problem/m-p/7182060#M493052</guid>
      <dc:creator>rachelgomez_123</dc:creator>
      <dc:date>2023-02-03T06:59:05Z</dc:date>
    </item>
  </channel>
</rss>

