doc-exports/docs/cce/umn/cce_faq_00263.html
Dong, Qiu Jian 86fb05065f CCE UMN for 24.2.0 version -20240428
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-06-10 08:19:07 +00:00

43 lines
4.2 KiB
HTML

<a name="cce_faq_00263"></a><a name="cce_faq_00263"></a>
<h1 class="topictitle1">What Should I Do If the vdb Disk of a Node Is Damaged and the Node Cannot Be Recovered After Reset?</h1>
<div id="body1586941360830"><div class="section" id="cce_faq_00263__section06301525458"><h4 class="sectiontitle">Symptom</h4><p id="cce_faq_00263__p12884929754">The vdb disk of a node is damaged and the node cannot be recovered after reset.</p>
<p id="cce_faq_00263__p155892305151"><strong id="cce_faq_00263__b72937143611">Error Scenarios</strong></p>
<ul id="cce_faq_00263__ul0433731192919"><li id="cce_faq_00263__li1843317318297">On a normal node, delete the LV and VG. The node is unavailable.</li><li id="cce_faq_00263__li174331231162913">Reset an abnormal node, and a syntax error is reported. The node is unavailable.<p id="cce_faq_00263__p10396122911298"><a name="cce_faq_00263__li174331231162913"></a><a name="li174331231162913"></a>The following figure shows the details.</p>
<p id="cce_faq_00263__p1114113138157"><span><img id="cce_faq_00263__image81418139152" src="en-us_image_0000001851585280.png"></span></p>
</li></ul>
</div>
<div class="section" id="cce_faq_00263__section172501961191"><h4 class="sectiontitle">Fault Locating</h4><p id="cce_faq_00263__p1452120217167">If the volume group (VG) on the node is deleted or damaged and cannot be identified, you need to manually restore the VG first to prevent your data disks from being formatted by mistake during the reset.</p>
</div>
<div class="section" id="cce_faq_00263__section9225153031616"><h4 class="sectiontitle">Solution</h4><ol id="cce_faq_00263__ol121131415101711"><li id="cce_faq_00263__li1711315156178"><span>Log in to the node.</span></li><li id="cce_faq_00263__li143311624204318"><span>Create a PV and a VG again. In this example, the following error message is displayed:</span><p><pre class="screen" id="cce_faq_00263__screen1937154794616">root@host1:~# pvcreate /dev/vdb
Device /dev/vdb excluded by a filter</pre>
<div class="p" id="cce_faq_00263__p1891411456466">This is because the added disk is created on another VM and has a partition table. The current VM cannot identify the partition table of the disk. You need to run the <strong id="cce_faq_00263__b7596225796">parted</strong> commands for three times to re-create the partition table.<pre class="screen" id="cce_faq_00263__screen161794404613">root@host1:~# parted /dev/vdb
GNU Parted 3.2
Using /dev/vdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos
Warning: The existing disk label on /dev/vdb will be destroyed and all data on this disk will be lost. Do you want to continue?
Yes/No? yes
(parted) quit
Information: You may need to update /etc/fstab.</pre>
</div>
<p id="cce_faq_00263__p1317544164613">Run <strong id="cce_faq_00263__b221081051015">pvcreate</strong> again. When the system asks you whether to erase the DOS signature, enter <strong id="cce_faq_00263__b157921116191012">y</strong>. The disk is created as a PV.</p>
<pre class="screen" id="cce_faq_00263__screen181716442468">root@host1:~# pvcreate /dev/vdb
WARNING: dos signature detected on /dev/vdb at offset 510. Wipe it? [y/n]: y
Wiping dos signature on /dev/vdb.
Physical volume "/dev/vdb" successfully created</pre>
</p></li><li id="cce_faq_00263__li1188312084218"><span>Create a VG.</span><p><div class="p" id="cce_faq_00263__p106671422114216">Check the Docker disks of the node. If the disks are <strong id="cce_faq_00263__b6876759121012">/dev/vdb</strong> and <strong id="cce_faq_00263__b7881105918108">/dev/vdc</strong>, run the following command:<pre class="screen" id="cce_faq_00263__screen460225891810">root@host1:~# vgcreate vgpaas /dev/vdb /dev/vdc</pre>
</div>
<div class="p" id="cce_faq_00263__p150518231422">If there is only the <strong id="cce_faq_00263__b9205141661110">/dev/vdb</strong> disk, run the following command:<pre class="screen" id="cce_faq_00263__screen10596183381915">root@host1:~# vgcreate vgpaas /dev/vdb</pre>
</div>
<p id="cce_faq_00263__p73311328422">After the creation is complete, reset the node.</p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00281.html">Node Running</a></div>
</div>
</div>