所以我有双启动（win + ubuntu），我缩小了 Ubuntu 分区，并将这些 GB 添加到我的 Win 分区（通过 Windows 磁盘管理），现在它显示 busybox。Gparted 成功完成所有操作，没有任何错误，系统运行良好，但今天当我尝试启动它时 - BusyBox。请不要将其标记为重复，因为这个令人沮丧的事情没有明确的答案。
尝试过启动修复，没有任何效果。
一些输出：
ubuntu@ubuntu:~$ sudo parted -l
Model: ATA WDC WD10EZEX-08M (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 630GB 630GB primary ext4
2 630GB 842GB 212GB extended lba
5 630GB 842GB 212GB logical ntfs
3 842GB 842GB 105MB primary ntfs
4 842GB 1000GB 158GB primary ntfs boot
Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 4005MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 4005MB 4003MB primary fat32 boot, lb
A
/var/log/boot.log文件
stdin: Not a typewriter
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Generating locales (this might take a while)...
Generation complete.
pwconv: failed to change the mode of /etc/passwd- to 0600
Using CD-ROM mount point /cdrom/
Identifying... [f8a7462a6e6017e4f995aa3cfc2ac6a9-2]
Scanning disc for index files...
Found 2 package indexes, 0 source indexes, 0 translation indexes and 1 signatures
Found label 'Ubuntu 17.04 _Zesty Zapus_ - Release amd64 (20170412)'
This disc is called:
'Ubuntu 17.04 _Zesty Zapus_ - Release amd64 (20170412)'
Copying package lists...gpgv: Signature made Wed Apr 12 03:43:31 2017 UTC
gpgv: using RSA key
gpgv: Good signature from "Ubuntu CD Image Automatic Signing Key (2012) <[email protected]>"
Reading Package Indexes... 0%
Reading Package Indexes... Done
Writing new source list
Source list entries for this disc are:
deb cdrom:[Ubuntu 17.04 _Zesty Zapus_ - Release amd64 (20170412)]/ zesty main restricted
Repeat this process for the rest of the CDs in your set.
[9;0]
文件系统检查
ubuntu@ubuntu:~$ fsck
fsck from util-linux 2.29
ubuntu@ubuntu:~$
启动错误：
ubuntu@ubuntu:~$ fsck -a /dev/sda1
fsck from util-linux 2.29
fsck.ext2: Permission denied while trying to open /dev/sda1
You must have r/w access to the filesystem or be root
ubuntu@ubuntu:~$ su -
Password:
su: Authentication failure
ubuntu@ubuntu:~$ sudo fsck -a /dev/sda1
fsck from util-linux 2.29
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
ubuntu@ubuntu:~$ fsck /dev/sda1
fsck from util-linux 2.29
e2fsck 1.43.4 (31-Jan-2017)
fsck.ext2: Permission denied while trying to open /dev/sda1
You must have r/w access to the filesystem or be root
ubuntu@ubuntu:~$ sudo fsck /dev/sda1
fsck from util-linux 2.29
e2fsck 1.43.4 (31-Jan-2017)
/dev/sda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 258 was part of the orphaned inode list. FIXED.
Inode 611 extent block passes checks, but checksum does not match extent
(logical block 512, physical block 40361984, len 529)
Fix<y>? yes
Inode 784 extent block passes checks, but checksum does not match extent
(logical block 13, physical block 1748389, len 465)
Fix<y>? yes
Deleted inode 1680 has zero dtime. Fix<y>? yes
Inode 23341766 extent tree (at level 2) could be narrower. Fix<y>? yes
Inode 23342389 extent tree (at level 2) could be narrower. Fix<y>? yes
Inode 23469229 extent tree (at level 2) could be narrower. Fix<y>? yes
Deleted inode 25952265 has zero dtime. Fix<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -9780 -9793 -(40407568--40407570) -(40511114--40511129) -(40511131--40511145) -(40511147--40511163) -(40511165--40511178) -(40511180--40511199) -(40511201--40511214) -(40511216--40511233) -(40511235--40511250) -(40511252--40511274) -(40511276--40511289) -(40511291--40511308) -(40511310--40511323) -(40511325--40511344) -(40511346--40511360) -(40511362--40511379) -(40511381--40511394) -(40511396--40511408) -(40679424--40681471) -(40685568--40687615) -(40691712--40693759) -(40697856--40699903) -(40704000--40706047) -(40710144--40711067)
Fix<y>? yes
Free blocks count wrong for group #0 (95, counted=97).
Fix<y>? yes
Free blocks count wrong for group #1233 (1433, counted=1436).
Fix<y>? yes
Free blocks count wrong for group #1236 (10240, counted=10519).
Fix<y>? yes
Free blocks count wrong for group #1241 (0, counted=6144).
Fix<y>? yes
Free blocks count wrong for group #1242 (0, counted=5020).
Fix<y>? yes
Free blocks count wrong (99499195, counted=99510643).
Fix<y>? yes
Inode bitmap differences: -258 -1680 -25952265
Fix<y>? yes
Free inodes count wrong for group #0 (22, counted=24).
Fix<y>? yes
Free inodes count wrong for group #3168 (8142, counted=8143).
Fix<y>? yes
Free inodes count wrong (38097865, counted=38097868).
Fix<y>? yes
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 355380/38453248 files (0.3% non-contiguous), 54284173/153794816 blocks
ubuntu@ubuntu:~$
答案1
所以我尝试了所有方法，最终有一个人找到了解决方案（至少对我有用）
看起来最近的 ext 文件系统出现了一些问题...因为这是我在过去两周内第四次收到这个问题。（来自朋友，现在来自这里）。
我猜测你的文件系统可能以某种方式被损坏或破坏了，但这很容易修复，不用担心 ;-)
一切都可以通过 Ubuntu Live CD 完成。从那里启动，并检查哪个分区是安装 Ubuntu 的分区（sda1、sda5……）。您可以使用 Gparted 轻松完成此操作。即使从那里，您也可以右键单击分区并选择“验证”。
如果您想从命令行执行此操作，只需输入：
fsck /dev/sda1（sda1 是安装 ubuntu 的分区）。它将修复 ext4 文件系统问题。如果您在使用过程中遇到太多问题，请向其中添加“-a”开关：
fsck -a /dev/sda1我必须告诉你，使用这个要谨慎。如果数据在那里很敏感，请先从 livecd 备份到其他地方（如果可以的话）。
文件系统修复后，您应该能够再次在 ubuntu 中正常启动。
希望这对你有帮助。
- 大卫·兰多
原始答案：启动时 Busybox 出现错误 谢谢！