<?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 VxVM disk recognition questions in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105544#M49653</link>
    <description>I'm testing a Storage Foundation 4.1 (MP 4)&lt;BR /&gt;installation under RHEL4. Have an old, single port, CMD RAID box that appears to Linux as /dev/sda. The RAID has been labelled&lt;BR /&gt;with an empty partition table of type 'sun'.&lt;BR /&gt;&lt;BR /&gt; Despite creating an entry for CMD in /etc/vx/jbod.info scanning for disks never&lt;BR /&gt;listed anything - neither the RAID or  internal drives under /dev/cciss. Is this to be expected from DMP? In my experience of VxVM 3.5, under HP-UX, devices for all discs are automatically created under /dev/vx/dmp.&lt;BR /&gt;&lt;BR /&gt; So then I added the CMD RAID as a foreign device: Device 'sda' is now listed by the 'vxdisk' command as "online invalid" and recorded in /etc/vx/darecs. But&lt;BR /&gt;when I try to add 'sda'; using 'vxdiskadd' it reports "No matching disks were returned". How can I get this&lt;BR /&gt;command, or 'vxdiskadm' for that matter, to recognise my foreign device?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 25 Apr 2008 09:18:58 GMT</pubDate>
    <dc:creator>David Nixon</dc:creator>
    <dc:date>2008-04-25T09:18:58Z</dc:date>
    <item>
      <title>VxVM disk recognition questions</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105544#M49653</link>
      <description>I'm testing a Storage Foundation 4.1 (MP 4)&lt;BR /&gt;installation under RHEL4. Have an old, single port, CMD RAID box that appears to Linux as /dev/sda. The RAID has been labelled&lt;BR /&gt;with an empty partition table of type 'sun'.&lt;BR /&gt;&lt;BR /&gt; Despite creating an entry for CMD in /etc/vx/jbod.info scanning for disks never&lt;BR /&gt;listed anything - neither the RAID or  internal drives under /dev/cciss. Is this to be expected from DMP? In my experience of VxVM 3.5, under HP-UX, devices for all discs are automatically created under /dev/vx/dmp.&lt;BR /&gt;&lt;BR /&gt; So then I added the CMD RAID as a foreign device: Device 'sda' is now listed by the 'vxdisk' command as "online invalid" and recorded in /etc/vx/darecs. But&lt;BR /&gt;when I try to add 'sda'; using 'vxdiskadd' it reports "No matching disks were returned". How can I get this&lt;BR /&gt;command, or 'vxdiskadm' for that matter, to recognise my foreign device?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Apr 2008 09:18:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105544#M49653</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2008-04-25T09:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM disk recognition questions</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105545#M49654</link>
      <description>looks like the /dev/sda is not detected by the VxVM. did u do some thing similar tot pvcreate we do for LVM?</description>
      <pubDate>Mon, 28 Apr 2008 18:38:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105545#M49654</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-04-28T18:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM disk recognition questions</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105546#M49655</link>
      <description>The command to add a foreign device 'vxddladm'&lt;BR /&gt;is the equivalent of LVMs 'pvcreate'.&lt;BR /&gt;After this is run 'vxdisk' can list the device. These &lt;BR /&gt;commands are binaries and 'vxdiskadm'&lt;BR /&gt;is a shell script. &lt;BR /&gt;&lt;BR /&gt;So I suspect this might be&lt;BR /&gt;a scripting issue.&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Apr 2008 08:57:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105546#M49655</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2008-04-29T08:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM disk recognition questions</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105547#M49656</link>
      <description>It was an installation issue. Due to 'preun' and 'postun' scriptlet errors the update of some Maintenance Pack 4 rpms had failed.&lt;BR /&gt; With a complete  MP4 installation disc device discovery now works.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Mon, 12 May 2008 08:51:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vxvm-disk-recognition-questions/m-p/5105547#M49656</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2008-05-12T08:51:26Z</dc:date>
    </item>
  </channel>
</rss>

