Got it

Failed to Start VRM

Latest reply: Jul 26, 2022 16:26:09 192 11 3 0 0

Hello everyone!


After FusionSphere is upgraded to 6.5.1SPC10, the VRM fails to be started and the message 'Could not find /dev/vda1' is displayed. Please have a read below for more details.


ISSUE DESCRIPTION


After FusionSphere OpenStack is upgraded to 6.5.1SPC10, the local VRM VM fails to be started. The message 'Could not find /dev/vda1' is displayed. Enter Y to log in to the system and run blkid. In the result, /dev/sda1 is returned:


blkid


ISSUE ANALYSIS


1. Log in to the host where the VM is located and import the environment variables.


2. Run the following command to check the instance of the VMnova show VM id | grep instance_name


instance name


3. Run the following command to check the instance IDvirsh list --all


virsh list


4. Run the virsh dumpxml Id command to view the VM XML file information:


xml


5. As shown in the following figure, the boot disk whose boot order is 1 is the boot disk and the disk type is ide:


boot disk =1


The following figure shows the query result of a normal VRM VM:


bootdisk


6. Query the active GaussDB node: cps template-instance-list --service gaussdb gaussdb


gaussdb


7. Log in to the active GaussDB node and access the database:


su gaussdba

gsql nova -W password

\x


gsql nova -W


Run the below command and record the execution result:


select * from instances where uuid='VM ID';

select * from BLOCK_DEVICE_MAPPING where instance_uuid='VM ID';


As shown in the below figure, if RECORD 1 is returned, refer to the solution in this case. If the returned RECORD is not 1, contact our Huawei technical support.


RECORD


8. The type of the disk whose drive letter is vda is virtio, while the type of the disk whose drive letter is sda is ide. The environment is upgraded from 2.x. After the local disk management VM (such as VRM and FSM) is upgraded, the disk type of the system disk changes. When the system starts, the system cannot find the disk corresponding to the disk name. As a result, the system fails to start.


SOLUTION


Change the boot disk format to virtio. Ensure that the system disk name recognized by the system is vda after the system is started. The procedure is as follows.


1. Download the attachment 'Modifying Disk Mounting Method Script' and upload the decompressed script to the /home/fsp directory on the controller node.


2. Run the following commands to grant permission to the script and change the VM disk format to virtio:


cd /home/fsp

chmod 755 nova_refresh_bdm_bus_v2.py

python nova_refresh_bdm_bus_v2.py set_virtio VM ID


chmod 755


3. Log in to the active GaussDB node and access the database:


su  gaussdba

gsql nova -W password

\x


gaussdba


Run the below command and back up the returned result to the TXT file:


select * from instances where uuid='VM ID';

select * from BLOCK_DEVICE_MAPPING where instance_uuid='VM ID';


Run the below command to change the value:


update BLOCK_DEVICE_MAPPING set DISK_BUS=ide 'where INSTANCE_UUID='VM ID';

update BLOCK_DEVICE_MAPPING set DEVICE_NAME= '/dev/hda' where uuid='VM ID';

update instances set ROOT_DEVICE_NAME='/dev/hda' where uuid='VM ID';

\q

exit


Exit the database.


4. Hard restart the VM: nova reboot VM id –hard


5. Log in to the VM using VNC and check whether the VM is started properly.


6. Repeat steps 1 to 5 to perform the preceding operations on all local disk management VMs (such as VRM, FSM, and allinonefm) where the problem occurs.


This is my solution, how about yours? Go ahead and share it with us!

The post is synchronized to: Huawei Cloud Computing Case

  • x
  • convention:

xianxian
Created Jul 26, 2022 08:47:21

Thanks for your sharing!
A good case about VRM.
View more
  • x
  • convention:

olive.zhao
olive.zhao Created Jul 28, 2022 01:16:21 (0) (0)
Thanks!  
user_3915171
Created Jul 26, 2022 15:15:13

thanks
View more
  • x
  • convention:

olive.zhao
olive.zhao Created Jul 28, 2022 01:16:27 (0) (0)
 
harisaliehsan
Created Jul 26, 2022 16:25:24

Good post
View more
  • x
  • convention:

olive.zhao
olive.zhao Created Jul 28, 2022 01:16:38 (0) (0)
Thanks!  
harisaliehsan
Created Jul 26, 2022 16:25:32

Thanks for Sharing
View more
  • x
  • convention:

olive.zhao
olive.zhao Created Jul 28, 2022 01:16:45 (0) (0)
 
azkasaqib
Created Jul 26, 2022 16:26:00

Good post
View more
  • x
  • convention:

olive.zhao
olive.zhao Created Jul 28, 2022 01:16:58 (0) (0)
Thanks friend!  
azkasaqib
Created Jul 26, 2022 16:26:09

Thanks for Sharing
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.
Information Protection Guide
Thanks for using Huawei Enterprise Support Community! We will help you learn how we collect, use, store and share your personal information and the rights you have in accordance with Privacy Policy and User Agreement.