<?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: disk name changed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045199#M604872</link>
    <description>Thanks again everyone!</description>
    <pubDate>Wed, 09 May 2007 15:48:52 GMT</pubDate>
    <dc:creator>Kaleung Tsou</dc:creator>
    <dc:date>2007-05-09T15:48:52Z</dc:date>
    <item>
      <title>disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045188#M604861</link>
      <description>&lt;!--!*#--&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I am running HP-UX 11.23 with the system connected to EVA 5000. This morning a HP service person did some maintenance on the SAN switch and when I boot my system, the disk name changed and the system is not able to mount the disks. &lt;BR /&gt;&lt;BR /&gt;The original disk names are below by running strings /etc/lvmtab&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&lt;BR /&gt;/dev/dsk/c2t1d0s2&lt;BR /&gt;/dev/dsk/c2t0d0&lt;BR /&gt;/dev/vg02&lt;BR /&gt;dKF1&lt;BR /&gt;/dev/dsk/c6t0d2&lt;BR /&gt;/dev/dsk/c7t0d2&lt;BR /&gt;/dev/vg03&lt;BR /&gt;dKF1&lt;BR /&gt;/dev/dsk/c6t0d3&lt;BR /&gt;/dev/dsk/c7t0d3&lt;BR /&gt;/dev/vg04&lt;BR /&gt;dKF1&lt;BR /&gt;/dev/dsk/c6t0d4&lt;BR /&gt;/dev/dsk/c7t0d4&lt;BR /&gt;/dev/vg06&lt;BR /&gt;dKF1&lt;BR /&gt;/dev/dsk/c6t0d6&lt;BR /&gt;/dev/dsk/c7t0d6&lt;BR /&gt;/dev/vg01&lt;BR /&gt;dKF1&lt;BR /&gt;/dev/dsk/c6t0d1&lt;BR /&gt;/dev/dsk/c7t0d1&lt;BR /&gt;/dev/vg05&lt;BR /&gt;dKFB&lt;BR /&gt;/dev/dsk/c6t0d5&lt;BR /&gt;/dev/dsk/c7t0d5&lt;BR /&gt;&lt;BR /&gt;The new disk names are below by running ioscan -funC disk&lt;BR /&gt;&lt;BR /&gt;disk      0  0/0/2/0.0.0.0   sdisk      CLAIMED     DEVICE       &lt;BR /&gt;                            /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0&lt;BR /&gt;disk      1  0/1/1/0.0.0     sdisk      CLAIMED     DEVICE      &lt;BR /&gt;3LC&lt;BR /&gt;                            /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0&lt;BR /&gt;disk      2  0/1/1/0.1.0     sdisk      CLAIMED     DEVICE      &lt;BR /&gt;3LC&lt;BR /&gt;                            /dev/dsk/c2t1d0     /dev/rdsk/c2t1d0&lt;BR /&gt;                            /dev/dsk/c2t1d0s1   /dev/rdsk/c2t1d0s1&lt;BR /&gt;                            /dev/dsk/c2t1d0s2   /dev/rdsk/c2t1d0s2&lt;BR /&gt;                            /dev/dsk/c2t1d0s3   /dev/rdsk/c2t1d0s3&lt;BR /&gt;disk     19  0/3/1/0.1.11.0.0.0.1  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d1   /dev/rdsk/c8t0d1&lt;BR /&gt;disk     22  0/3/1/0.1.11.0.0.0.2  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d2   /dev/rdsk/c8t0d2&lt;BR /&gt;disk     23  0/3/1/0.1.11.0.0.0.3  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d3   /dev/rdsk/c8t0d3&lt;BR /&gt;disk     24  0/3/1/0.1.11.0.0.0.4  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d4   /dev/rdsk/c8t0d4&lt;BR /&gt;disk     25  0/3/1/0.1.11.0.0.0.5  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d5   /dev/rdsk/c8t0d5&lt;BR /&gt;disk     26  0/3/1/0.1.11.0.0.0.6  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c8t0d6   /dev/rdsk/c8t0d6&lt;BR /&gt;disk     15  0/3/1/0.1.12.0.0.0.1  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d1   /dev/rdsk/c10t0d1&lt;BR /&gt;disk     16  0/3/1/0.1.12.0.0.0.2  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d2   /dev/rdsk/c10t0d2&lt;BR /&gt;disk     17  0/3/1/0.1.12.0.0.0.3  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d3   /dev/rdsk/c10t0d3&lt;BR /&gt;disk     18  0/3/1/0.1.12.0.0.0.4  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d4   /dev/rdsk/c10t0d4&lt;BR /&gt;disk     20  0/3/1/0.1.12.0.0.0.5  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d5   /dev/rdsk/c10t0d5&lt;BR /&gt;disk     21  0/3/1/0.1.12.0.0.0.6  sdisk      CLAIMED     DEVICE&lt;BR /&gt;SV110 (C)COMPAQ&lt;BR /&gt;                            /dev/dsk/c10t0d6   /dev/rdsk/c10t0d6&lt;BR /&gt;&lt;BR /&gt;Is there a way to name the new disk names back to the original so I can mount the disks. &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 May 2007 17:19:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045188#M604861</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-08T17:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045189#M604862</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Actually I believe that they changed the way in which the disks were connected, is not about change the disk name, the name is determine depending of how are they connected.&lt;BR /&gt;&lt;BR /&gt;Apparently you need to re-create the lvm structure.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Marco</description>
      <pubDate>Tue, 08 May 2007 18:33:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045189#M604862</guid>
      <dc:creator>Marco A.</dc:creator>
      <dc:date>2007-05-08T18:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045190#M604863</link>
      <description>Not to repeat what others already said about a similar problem, please see this thread:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=425790" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=425790&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;yes, it is possible to change the hardware paths, but, if I were you, I would do one or maybe two ignite recovery tapes, as this procedure, done with a little imperfection, may render your system not bootable.&lt;BR /&gt;&lt;BR /&gt;Hope this helps</description>
      <pubDate>Tue, 08 May 2007 19:00:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045190#M604863</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2007-05-08T19:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045191#M604864</link>
      <description>&lt;!--!*#--&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;     We will follow the steps for /dev/vg02. if it goes as expected we will do it for the rest of the VG's&lt;BR /&gt;&lt;BR /&gt;1:&lt;BR /&gt;vgexport -m /tmp/vg02_map /dev/vg02&lt;BR /&gt;2:&lt;BR /&gt;mkdir /dev/vg02&lt;BR /&gt;mknod /dev/vg02/group c 64 0x020000&lt;BR /&gt;3:&lt;BR /&gt;vgimport -v -m /tmp/vg02_map /dev/vg02 /dev/dsk/c8t0d2 /dev/dsk/c10t0d2&lt;BR /&gt;4:&lt;BR /&gt;vgchange -a y /dev/vg02&lt;BR /&gt;5:&lt;BR /&gt;vgdisplay -v /dev/vg02&lt;BR /&gt;6:&lt;BR /&gt;mount all the Lvols hosted from vg02&lt;BR /&gt;&lt;BR /&gt;   If the above steps are fine with vg02 then its time to repeat them for the rest of the VG's&lt;BR /&gt;&lt;BR /&gt;SK</description>
      <pubDate>Wed, 09 May 2007 00:06:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045191#M604864</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2007-05-09T00:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045192#M604865</link>
      <description>&lt;!--!*#--&gt;Hi Senthil,&lt;BR /&gt;&lt;BR /&gt;I am getting this message on step 3&lt;BR /&gt;&lt;BR /&gt;# vgimport -v -m /tmp/vg02_map /dev/vg02 /dev/dsk/c8t0d2 /dev/dsk/c10t0d2&lt;BR /&gt;Beginning the import process on Volume Group "/dev/vg02".&lt;BR /&gt;vgimport: Minor number of /dev/vg02/group is not unique. /dev/vg03/group has the same minor number.&lt;BR /&gt;&lt;BR /&gt;Any suggestions?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Wed, 09 May 2007 12:09:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045192#M604865</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-09T12:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045193#M604866</link>
      <description>By convention, vg01 uses 0x010000, vg02 uses 0x02000, ... vg10 uses 0x0a0000 but that is simply convention. Do an "ls -l /dev/vg*/group" to display all the current group monor device numbers and choose one that is not currently in use AND so that the first two hex digits are less than your maxvgs kernel tunable. Use that value as your monir device number and proceed with the vgimport.</description>
      <pubDate>Wed, 09 May 2007 12:14:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045193#M604866</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-05-09T12:14:53Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045194#M604867</link>
      <description>&lt;!--!*#--&gt;Here is what I got from:&lt;BR /&gt;&lt;BR /&gt;# ls -l /dev/vg*/group&lt;BR /&gt;crw-r-----   1 root       sys         64 0x000000 Mar 21 09:40 /dev/vg00/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x060000 Apr 27 04:10 /dev/vg01/group&lt;BR /&gt;crw-rw-rw-   1 root       sys         64 0x020000 May  9 10:04 /dev/vg02/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x020000 Apr 27 03:58 /dev/vg03/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x030000 Apr 27 04:06 /dev/vg04/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x070000 May  9  2007 /dev/vg05/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x040000 Apr 28 01:35 /dev/vg05old/group&lt;BR /&gt;crw-rw-r--   1 root       sys         64 0x050000 Apr 27 04:08 /dev/vg06/group&lt;BR /&gt;cr--r--r--   1 root       sys         64 0x040000 Apr 28 01:52 /dev/vg07old/group&lt;BR /&gt;&lt;BR /&gt;Can I use 0x010000 for vg02 as the minor number? Sorry for being so ignorant, I am a newbie.</description>
      <pubDate>Wed, 09 May 2007 12:20:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045194#M604867</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-09T12:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045195#M604868</link>
      <description>Yes, rm /dev/vg02/group  and then&lt;BR /&gt;mknod /dev/vg02/group c 64 0x010000&lt;BR /&gt;&lt;BR /&gt;Note: That all except vg00 are really out of sync with convention so in the future you might consider vgexporting and vgimporting and reassigning the minor device numbers to avoid confusion.</description>
      <pubDate>Wed, 09 May 2007 12:44:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045195#M604868</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-05-09T12:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045196#M604869</link>
      <description>&lt;!--!*#--&gt;I have all the vg back and I reassigned the minor numbers as suggested. However, when I try to mount below; I get a this error&lt;BR /&gt;&lt;BR /&gt;# mount /dev/vg03/orabase /oracle&lt;BR /&gt;UX:vxfs mount: ERROR: V-3-21268: /dev/vg03/orabase is corrupted. needs checking&lt;BR /&gt;&lt;BR /&gt;Thanks again.</description>
      <pubDate>Wed, 09 May 2007 13:25:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045196#M604869</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-09T13:25:40Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045197#M604870</link>
      <description>In that case, fsck -F vxfs /dev/vg03/rorabase&lt;BR /&gt;&lt;BR /&gt;You may need to specify the -o full or -o full,nolog options. Man fsck_vxfs for details.&lt;BR /&gt;&lt;BR /&gt;After fsck completes you should then be able to mount the file system.</description>
      <pubDate>Wed, 09 May 2007 13:53:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045197#M604870</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-05-09T13:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045198#M604871</link>
      <description>Everything is working now! Thanks for everyone's help especially Clay Stephenson and Senthil Kumar. You guys save the day!!! I really appreciate your time on this! You guys are awesome!!!&lt;BR /&gt;&lt;BR /&gt;Thanks again!!!</description>
      <pubDate>Wed, 09 May 2007 14:30:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045198#M604871</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-09T14:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: disk name changed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045199#M604872</link>
      <description>Thanks again everyone!</description>
      <pubDate>Wed, 09 May 2007 15:48:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-name-changed/m-p/5045199#M604872</guid>
      <dc:creator>Kaleung Tsou</dc:creator>
      <dc:date>2007-05-09T15:48:52Z</dc:date>
    </item>
  </channel>
</rss>

