问题原文
原帖链接 · cawecoy · CC BY-SA 4.0
My setup:
- My OS is Ubuntu 18.04
- Vagrant 2.0.0
- VirtualBox 5.2.18 r124319
- Ubuntu installed into vagrant/virtualbox (version uknown)
sudo vagrant up was always working, suddenly it has stopped working... it gets stuck on SSH auth method: private key until reach timeout.
So I run sudo vagrant up with GUI enabled to check for errors, and what I found:
Scanning for Btrfs filesystems
/dev/mapper/vagrant--vg-root: contains a file system with errors, check forced.
/dev/mapper/vagrant--vg-root: Inodes that were part of a corrupted orphan linked list found.
/dev/mapper/vagrant--vg-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/mapper/vagrant--vg-root requires manual fsck
How to proceed?
已采纳解答
原帖链接 · cawecoy · CC BY-SA 4.0
I've solved the issue. Here is how:
vagrant upwith GUI enabled- As soon as GUI open, keep pressing Right Shift, select "Advanced Options for Ubuntu" and then select "Ubuntu in Recovery mode"
- After "/dev/mapper/vagrant--vg-root: UNEXPECTED INCONSISTENCY" appears, run
fsck /dev/mapper/vagrant--vg-rootpressing Enter everytime the proccess ask to fix an issue vagrant upagain with GUI disabled, problem solved
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
