Ubuntu 16.04 啓動長時間停留在紫屏狀態 - Loading Initial Ramdisk
1. Ubuntu 16.04 啓動長時間停留在紫屏狀態
2. Advanced options for Ubuntu
3. Loading Initial Ramdisk
選擇以下內核：
Ubuntu, with Linux 4.15.0-42-generic 默認內核
Ubuntu, with Linux 4.15.0-39-generic 內核
Ubuntu, with Linux 4.15.0-29-generic 內核
然後按鍵 Enter 啓動，全部都無法正常啓動，停留在 Loading Initial Ramdisk...
4. Recovery Mode - 恢復模式
重啓系統 -> Advanced options for Ubuntu (高級選項) -> Ubuntu, with Linux 4.15.0-42-generic (recovery mode)
Ubuntu 操作系統帶有恢復模式，通過 Recovery Mode，用戶可以訪問損壞系統的命令行，修復錯誤配置的文件，測試系統內存是否工作等等。
要在 Ubuntu 上訪問恢復模式，必須運行 GRUB 引導加載程序，如果你正在使用其他引導加載程序，則可能無法訪問此功能。
5. Recovery Mode - fsck
恢復模式下的 fsck 功能可以通過掃描損壞的硬盤並刪除它們來快速修復損壞的硬盤。
要使用 fsck，請使用向下箭頭在 Recovery Mode 菜單中突出顯示它，然後按 Enter 鍵啓動，讓它自動刪除損壞的數據。
根據系統啓動報告 Checking filesystems 失敗提示，可以看出 Ubuntu 系統不能啓動的真正原因是 /etc/fstab 項掛載失敗。
6. Ubuntu 系統開機自動掛載失敗導致系統無法啓動
cat /etc/fstab
yongqiang@famu-sys:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=53a5a063-1ea4-434d-ad98-6cdaefff158a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ed619771-4748-4f5a-86a5-355c8c22a290 none swap sw 0 0
/dev/disk/by-uuid/6d76a02c-8296-4aac-8b0b-5ac1d667a6a9 /mnt/6d76a02c-8296-4aac-8b0b-5ac1d667a6a9 auto nosuid,nodev,nofail ,x-gvfs-show 0 0
/dev/disk/by-uuid/79dd189b-b1b6-48c4-9c90-560934f420f5 /mnt/79dd189b-b1b6-48c4-9c90-560934f420f5 auto nosuid,nodev,nofail ,x-gvfs-show 0 0
# foreverstrong
/dev/sda /media/famu/DISK_DATA ext4 defaults 0 0
yongqiang@famu-sys:~$
vim /etc/fstab 修改文件，將掛載失效的行註釋，reboot 重啓進入正常啓動。
yongqiang@famu-sys:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=53a5a063-1ea4-434d-ad98-6cdaefff158a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ed619771-4748-4f5a-86a5-355c8c22a290 none swap sw 0 0
/dev/disk/by-uuid/6d76a02c-8296-4aac-8b0b-5ac1d667a6a9 /mnt/6d76a02c-8296-4aac-8b0b-5ac1d667a6a9 auto nosuid,nodev,nofail ,x-gvfs-show 0 0
/dev/disk/by-uuid/79dd189b-b1b6-48c4-9c90-560934f420f5 /mnt/79dd189b-b1b6-48c4-9c90-560934f420f5 auto nosuid,nodev,nofail ,x-gvfs-show 0 0
# foreverstrong
# /dev/sda /media/famu/DISK_DATA ext4 defaults 0 0
yongqiang@famu-sys:~$