<?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 disklabel create/copy in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222475#M51723</link>
    <description>hello, I'm working an exadata storage node issue with the boot disk mirrors ... a raid1 set where one disk was pulled and replaced ... without further action. RHEL 5. &lt;BR /&gt;&lt;BR /&gt;so I need to do the further action which I belive to be as simpe as create/write a new disklable to the effected device and run mdadm utility commands. I need help with the disklabel. fdisk, parted..... what about sfdisk ?&lt;BR /&gt;&lt;BR /&gt;first of all I don't know what type of disk label it is (dos,sun,bsd,other) ... I also don't know how to properly re4plicate the existing (or rather other mirror's) disklabel. see good disklabel below.&lt;BR /&gt;&lt;BR /&gt;please advise on how to replicate the 'good' disklabel (c0d1) to the "new" disklabel (c0d0).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;other questions: how to determine exact type of disklabel on a disk? how to set a partion as bootable?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;please advise.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thanks</description>
    <pubDate>Fri, 29 Jan 2010 20:14:21 GMT</pubDate>
    <dc:creator>Paul Wasik</dc:creator>
    <dc:date>2010-01-29T20:14:21Z</dc:date>
    <item>
      <title>disklabel create/copy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222475#M51723</link>
      <description>hello, I'm working an exadata storage node issue with the boot disk mirrors ... a raid1 set where one disk was pulled and replaced ... without further action. RHEL 5. &lt;BR /&gt;&lt;BR /&gt;so I need to do the further action which I belive to be as simpe as create/write a new disklable to the effected device and run mdadm utility commands. I need help with the disklabel. fdisk, parted..... what about sfdisk ?&lt;BR /&gt;&lt;BR /&gt;first of all I don't know what type of disk label it is (dos,sun,bsd,other) ... I also don't know how to properly re4plicate the existing (or rather other mirror's) disklabel. see good disklabel below.&lt;BR /&gt;&lt;BR /&gt;please advise on how to replicate the 'good' disklabel (c0d1) to the "new" disklabel (c0d0).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;other questions: how to determine exact type of disklabel on a disk? how to set a partion as bootable?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;please advise.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Fri, 29 Jan 2010 20:14:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222475#M51723</guid>
      <dc:creator>Paul Wasik</dc:creator>
      <dc:date>2010-01-29T20:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: disklabel create/copy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222476#M51724</link>
      <description>good disklabel:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Disk /dev/cciss/c0d1: 1000.1 GB, 1000171331584 bytes&lt;BR /&gt;255 heads, 32 sectors/track, 239394 cylinders&lt;BR /&gt;Units = cylinders of 8160 * 512 = 4177920 bytes&lt;BR /&gt;&lt;BR /&gt;           Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/cciss/c0d1p1   *           1          32      130544   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p2              33          33        4080   83  Linux&lt;BR /&gt;/dev/cciss/c0d1p3              34      231941   946184640   83  Linux&lt;BR /&gt;/dev/cciss/c0d1p4          231942      239394    30408240    5  Extended&lt;BR /&gt;/dev/cciss/c0d1p5          231942      234512    10489664   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p6          234513      237082    10485584   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p7          237083      237596     2097104   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p8          237597      238110     2097104   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p9          238111      238624     2097104   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p10         238625      238799      713984   fd  Linux raid autodetect&lt;BR /&gt;/dev/cciss/c0d1p11         238800      239394     2427584   83  Linux&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Jan 2010 22:21:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222476#M51724</guid>
      <dc:creator>Paul Wasik</dc:creator>
      <dc:date>2010-01-29T22:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: disklabel create/copy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222477#M51725</link>
      <description>the process for "miroring" exadata cell OS disks IS WAY NOT STRAIGHT FORWARD. found that I had to pull the disk from ASM, then pull the disk from the cell disk config ... and then a one command re-enable  did all the disklabel work ... but it took a L O N G time to get the disk pulled out and then "balanced" back in.</description>
      <pubDate>Sat, 30 Jan 2010 02:48:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disklabel-create-copy/m-p/5222477#M51725</guid>
      <dc:creator>Paul Wasik</dc:creator>
      <dc:date>2010-01-30T02:48:57Z</dc:date>
    </item>
  </channel>
</rss>

