<?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: fsck with &amp;quot;invalid device config entry found&amp;quot; response in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805197#M616684</link>
    <description>Running dd:&lt;BR /&gt;&lt;BR /&gt;# dd if=/dev/vg00/rlvol8 of=/dev/null bs=1024k&lt;BR /&gt;dd read error: I/O error&lt;BR /&gt;22+0 records in&lt;BR /&gt;22+0 records out&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;---------&lt;BR /&gt;&lt;BR /&gt;Running the other fsck and mount commands:&lt;BR /&gt;&lt;BR /&gt;# fsck -F vxfs -o full /dev/vg00/lvol8          &lt;BR /&gt;vxfs fsck: invalid device config entry found&lt;BR /&gt;log replay in progress&lt;BR /&gt;vxfs fsck: fsck read failure bno = 7553, off = 0, len = 8192&lt;BR /&gt;full file system check required, exiting ...&lt;BR /&gt;# mount /dev/vg00/lvol8 /var&lt;BR /&gt;vxfs mount: /dev/vg00/lvol8 is corrupted. needs checking&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Jun 2006 11:51:28 GMT</pubDate>
    <dc:creator>CARLOS ROY GOLET</dc:creator>
    <dc:date>2006-06-13T11:51:28Z</dc:date>
    <item>
      <title>fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805194#M616681</link>
      <description>Dear friends,&lt;BR /&gt;when I try to run fsck, I get an error:&lt;BR /&gt;.............&lt;BR /&gt;# fsck -F vxfs -y -o full /dev/vg00/rlvol8&lt;BR /&gt;vxfs fsck: invalid device config entry found&lt;BR /&gt;log replay in progress&lt;BR /&gt;............&lt;BR /&gt;so, according to some help in the forum, I have tried a different option, but the results are not good:&lt;BR /&gt;............&lt;BR /&gt;fsck -F vxfs -o full,nolog -y /dev/vg00/rlvol8&lt;BR /&gt;vxfs fsck: invalid device config entry found&lt;BR /&gt;pass0 - checking structural files&lt;BR /&gt;fileset 1 primary-ilist inode 33 (SuperBlock)&lt;BR /&gt;                failed validation clear? (ynq)y&lt;BR /&gt;fileset 1 primary-ilist inode 40 (DEV 1)&lt;BR /&gt;                failed validation clear? (ynq)y&lt;BR /&gt;fileset 1 primary-ilist inode 32 (State)&lt;BR /&gt;                failed validation clear? (ynq)y&lt;BR /&gt;fileset 1 primary-ilist inode 34 (Sumino)&lt;BR /&gt;                failed validation clear? (ynq)y&lt;BR /&gt;fileset 1 primary-ilist inode 42 (Mapino 1)&lt;BR /&gt;                failed validation clear? (ynq)y&lt;BR /&gt;pass1 - checking inode sanity and blocks&lt;BR /&gt;vxfs fsck: fsck read failure bno = 2912, off = 0, len = 8192&lt;BR /&gt;file system check failure, aborting ...&lt;BR /&gt;.........&lt;BR /&gt;&lt;BR /&gt;Any suggestion ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 13 Jun 2006 11:14:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805194#M616681</guid>
      <dc:creator>CARLOS ROY GOLET</dc:creator>
      <dc:date>2006-06-13T11:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805195#M616682</link>
      <description>have you tried running a dd to make sure it comes back clean?&lt;BR /&gt;&lt;BR /&gt;tried to check with dd if=/dev/vg00/rlvol8 of=/dev/null bs=1024k (blocks read test&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 11:29:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805195#M616682</guid>
      <dc:creator>Deoncia Grayson_1</dc:creator>
      <dc:date>2006-06-13T11:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805196#M616683</link>
      <description>Try this &lt;BR /&gt;&lt;BR /&gt;fsck -F vxfs -o full /dev/vg00/lvol8&lt;BR /&gt;&lt;BR /&gt;It will resolve the issue.&lt;BR /&gt;Mount lvol8 to /var, and check it with bdf.&lt;BR /&gt;You also want to ensure that you have the latest vxfs/fsck patches installed.&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 11:32:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805196#M616683</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-06-13T11:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805197#M616684</link>
      <description>Running dd:&lt;BR /&gt;&lt;BR /&gt;# dd if=/dev/vg00/rlvol8 of=/dev/null bs=1024k&lt;BR /&gt;dd read error: I/O error&lt;BR /&gt;22+0 records in&lt;BR /&gt;22+0 records out&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;---------&lt;BR /&gt;&lt;BR /&gt;Running the other fsck and mount commands:&lt;BR /&gt;&lt;BR /&gt;# fsck -F vxfs -o full /dev/vg00/lvol8          &lt;BR /&gt;vxfs fsck: invalid device config entry found&lt;BR /&gt;log replay in progress&lt;BR /&gt;vxfs fsck: fsck read failure bno = 7553, off = 0, len = 8192&lt;BR /&gt;full file system check required, exiting ...&lt;BR /&gt;# mount /dev/vg00/lvol8 /var&lt;BR /&gt;vxfs mount: /dev/vg00/lvol8 is corrupted. needs checking&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 11:51:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805197#M616684</guid>
      <dc:creator>CARLOS ROY GOLET</dc:creator>
      <dc:date>2006-06-13T11:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805198#M616685</link>
      <description>could you please check the lvol8, it looks like that lvol8 got corrupted or some issue with media as dd also returned read error.</description>
      <pubDate>Tue, 13 Jun 2006 12:02:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805198#M616685</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-06-13T12:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805199#M616686</link>
      <description>I am sorry, but I do not understand: what do you mean with "check lvol8" apart from running fsck ? how can we verify there is a media problem ?</description>
      <pubDate>Tue, 13 Jun 2006 12:22:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805199#M616686</guid>
      <dc:creator>CARLOS ROY GOLET</dc:creator>
      <dc:date>2006-06-13T12:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805200#M616687</link>
      <description># dd if=/dev/vg00/rlvol8 of=/dev/null bs=1024k&lt;BR /&gt;dd read error: I/O error&lt;BR /&gt;22+0 records in&lt;BR /&gt;22+0 records out&lt;BR /&gt;&lt;BR /&gt;This really says it all (well, almost). Almost certainly this is a disk hardware problem. This is a small probability that this could actually be a problem with the LVM metadata pointing to a bogus device.&lt;BR /&gt;&lt;BR /&gt;Do an lvdisplay -v /dev/vg00/lvol8 and note the PV(s) associated with this LVOL (e.g. /dev/dsk/c1t5d0). I suspect there is only one. Now run your dd against this raw disk device (e.g. /dev/rdsk/c1t5d0). &lt;BR /&gt;&lt;BR /&gt;e.g. dd if=/dev/rdsk/c1t5d0 bs=1024k of=/dev/null &lt;BR /&gt;&lt;BR /&gt;If this reports errors then you have a bad disk.</description>
      <pubDate>Tue, 13 Jun 2006 12:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805200#M616687</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-06-13T12:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805201#M616688</link>
      <description>I mean to say execute lvdisplay command and then check ioscan for the device belongs to this lv.&lt;BR /&gt;check syslog.log and event.log for any errors as dd cleary says there is some hardware issue.</description>
      <pubDate>Tue, 13 Jun 2006 13:02:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805201#M616688</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-06-13T13:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805202#M616689</link>
      <description>just a thought..&lt;BR /&gt;&lt;BR /&gt;# ll /dev/vg00/&lt;BR /&gt;&lt;BR /&gt;check the minor /major number for lvol8..&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 21:36:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805202#M616689</guid>
      <dc:creator>Albert_31</dc:creator>
      <dc:date>2006-06-13T21:36:34Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805203#M616690</link>
      <description>Hi ,&lt;BR /&gt;&lt;BR /&gt;Did you try fsck without any specific option. like. Please try this and let know the result.&lt;BR /&gt;&lt;BR /&gt;umount ..&lt;BR /&gt;fsck -F vxfs /dev/vg00/rlvol8&lt;BR /&gt;mount ...&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Srikanth</description>
      <pubDate>Wed, 14 Jun 2006 02:08:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805203#M616690</guid>
      <dc:creator>Srikanth Arunachalam</dc:creator>
      <dc:date>2006-06-14T02:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: fsck with "invalid device config entry found" response</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805204#M616691</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;the disk is c2t0d0 and &lt;BR /&gt;&lt;BR /&gt;dd if=/dev/rdsk/c2t0d0 of=/dev/null bs=1024k&lt;BR /&gt;&lt;BR /&gt;does not show any result after 2 hours.&lt;BR /&gt;A similar disk ends in 10 minutes without error.&lt;BR /&gt;&lt;BR /&gt;So, i suppose you are right and the disk has hw problem. I am going to open a hw issue with HP.&lt;BR /&gt;&lt;BR /&gt;My biggest problem is that the original /var directory has been lost and I have had to create an alternative /var in a new volume but some features do not run properly (cron, glance, swlist, etc.)</description>
      <pubDate>Wed, 14 Jun 2006 05:38:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsck-with-quot-invalid-device-config-entry-found-quot-response/m-p/3805204#M616691</guid>
      <dc:creator>CARLOS ROY GOLET</dc:creator>
      <dc:date>2006-06-14T05:38:35Z</dc:date>
    </item>
  </channel>
</rss>

