vCenter宕機,重啟出現fsck failed無法啟動
阿新 • • 發佈:2019-01-30
現象
突然發現VC無響應,控制檯看結果如圖:
網上查資料
主要參考其中的
Option 2:
- Press Control+D or reboot the vCSA using the vSphere Client.
- When the GRUB bootloader appears, press Spacebar to disable autoboot.
- Select p and enter the root password
- Type e to edit the boot commands.
- Scroll to the second line displaying the kernel boot parameters.
You see this line:
kernel /vmlinuz-3.0.101-0.35-default - Type e to edit the boot command.
- Append init=/bin/bash to the kernel boot options.
- Press Enter. The GRUB menu re-appears.
- Type b to start the boot process. The system boots to a temporary BASH shell.
- Set the default shell to BASH by running this command:
chsh -s /bin/bash root - Reboot the vCSA using the vSphere Client.
- Enter the root password.
- At the repair filesystem prompt, type this command:
fsck /dev/mapper/log_vg-logEnabling BASH shell in vCenter Server Appliance 6.0
-
vCenter Server Appliance 6.0 does not boot to the BASH shell by default.
To enable the BASH shell:
- In the GRUB boot loader press p.
- Enter the root credentials when prompted.
- Select VMware vCenter Server Appliance and press e.
- Select the line that begins with kernel and press e.
- Add init=/bin/bash to the end of the line and press Enter. This line should start with <nousb audit=1</font>.
- Press b.
解決過程
1.模式按照上述20個步驟操作
2.其中13步替換成我故障的路徑進行修復:分別為:fsck /dev/mapper/core_vg-core 和 fsck /dev/mapper/seat_vg-seat
3.修復成功
注意事項
1.修復過程中各階段的重啟可以用冷啟動的方式
2.第7步新增init=/bin/bash前面要加一個空格。如: