ironic 裸金属启动失败了

 

               

 

[centos@  boot]$ cat /etc/fstab 
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=MKFS_ESP /boot/efi vfat defaults 0 1
[centos@  boot]$ 

 

 

 

swap 
swaplabel -L "new label" /dev/XXX using util-linux
ext2/3/4 
e2label /dev/XXX "new label" using e2fsprogs
btrfs 
btrfs filesystem label /dev/XXX "new label" using btrfs-progs
reiserfs 
reiserfstune -l "new label" /dev/XXX using reiserfsprogs
jfs 
jfs_tune -L "new label" /dev/XXX using jfsutils
xfs 
xfs_admin -L "new label" /dev/XXX using xfsprogs
fat/vfat 
fatlabel /dev/XXX "new label" using dosfstools
mlabel -i /dev/XXX ::"new label" using mtools
exfat 
tune.exfat -L "new label" /dev/XXX using exfatprogsAUR
exfatlabel /dev/XXX "new label" using exfat-utils
ntfs 
ntfslabel /dev/XXX "new label" using ntfs-3g
udf 
udflabel /dev/XXX "new label" using udftools
yum install mtools

   不需要对/boot/efi分区打label

 

 

 

e2label /dev/sda3 cloudXXX

 

The label of a device can be obtained with lsblk:

$ lsblk -dno LABEL /dev/sda2
Arch Linux
Or with blkid:

# blkid -s LABEL -o value /dev/sda2
Arch Linux

 

 

[  193.370770] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  193.930763] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  194.500780] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  195.070775] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  195.630757] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  196.190777] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  196.750755] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  197.310793] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  197.870763] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  198.430763] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  198.990775] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  199.560772] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  200.120777] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  200.680754] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  201.250752] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  201.820765] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  202.380766] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  202.940781] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  203.520776] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  204.080762] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  204.640772] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  205.200764] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  205.770785] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  206.340763] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  206.900770] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  207.460779] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  208.030776] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  208.600771] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  209.160790] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  209.720768] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  210.280776] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  210.850762] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  211.410759] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  211.970787] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  212.540771] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  213.100774] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  213.660770] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  214.220771] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  214.220Warning: /dev/disk/by-label/cloudimg-rootfs does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.


dracut:/# 

 

 

To check the UUID of the original volume, use the following command
blkid
This command prints the characteristic attributes of the block devices on the system. The output would look something like this
/dev/xvda1: 
LABEL=”cloudimg-rootfs” 
UUID=”263dc91a-fc69–2314-cdaf-23cabc336a24" 
TYPE=”ext4" PTTYPE=”dos”
Copy the UUID from the original volume (/dev/xvda1), and use tune2fs command to replace the UUID of the new volume with that of the original volume.
sudo tune2fs -U UUID_OF_ORIGINAL_VOLUME /dev/xvdf;
The final step here is to set the system label of the new volume to what is present in the original volume. You can find out the system label of the original volume via the following command
sudo e2label /dev/xvda1
The output would look something like
"cloudimg-rootfs"
If there is no system label for the original volume (usually present only in Ubuntu and similar flavors), you can skip this step. Else set the system label for the old-volume using the following command
sudo e2label /dev/xvdf cloudimg-rootfs
This is it for the composition step. We can now log out of the instance via SSH.

 

[  214.220771] dracut-initqueue[3186]: Warning: dracut-initqueue timeout - starting timeout scripts
[  214.220Warning: /dev/disk/by-label/cloudimg-rootfs does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.


dracut:/# blkid
dracut:/# ls /dev/
autofs           mapper              tty0   tty24  tty4   tty55  urandom
bus              memory_bandwidth    tty1   tty25  tty40  tty56  usbmon0
char             network_latency     tty10  tty26  tty41  tty57  usbmon1
console          network_throughput  tty11  tty27  tty42  tty58  usbmon2
core             null                tty12  tty28  tty43  tty59  usbmon3
cpu_dma_latency  ptmx                tty13  tty29  tty44  tty6   usbmon4
fb0              pts                 tty14  tty3   tty45  tty60  usbmon5
fd               random              tty15  tty30  tty46  tty61  usbmon6
full             raw                 tty16  tty31  tty47  tty62  usbmon7
hidraw0          rtc                 tty17  tty32  tty48  tty63  usbmon8
hidraw1          rtc0                tty18  tty33  tty49  tty7   vcs
hwrng            shm                 tty19  tty34  tty5   tty8   vcs1
input            snapshot            tty2   tty35  tty50  tty9   vcsa
kmsg             stderr              tty20  tty36  tty51  ttyS0  vcsa1
kvm              stdin               tty21  tty37  tty52  ttyS1  vga_arbiter
log              stdout              tty22  tty38  tty53  ttyS2  zero
loop-control     tty                 tty23  tty39  tty54  ttyS3
dracut:/# ls /dev/disk
dracut:/# ls /dev/disk
ls: cannot access /dev/disk: No such file or directory
dracut:/# 

  最后发现原来是ramdisk中缺少华为对应raid卡的驱动

posted on 2020-07-06 16:43  tycoon3  阅读(489)  评论(0编辑  收藏  举报

导航