Linux enter emergency mode on boot due to corrupted USB disk mounted by fstab
# Welcome to emergency mode!
That's the end of the world.
My `journalctl -xb` output (the red parts):
```
systemd-udevd: Error calling EVIOCSKEYCODE on device node
timeout wating for device dev-sdb1.device
mountd could not create listeners
nfs-server.service: Job nfs-server.service/start failed with result
w1: model license "MIXED/Proprietary" taints kernel.
PNFS blkmaping enablement. is not active
```
# Try fix
It maybe caused by a corrupted USB or disk device (that you configure auto-mount before).
```bash
# remove the device that's suspicious:
nano /etc/fstab
# restart computer:
reboot
```
Now my computer boots successfully.
# How
After some googling, I think it maybe related to `mount` `fstab` `nfs`. So I go check my `/etc/fstab` and try delete the U-disk mount point. And it fixed my issue!
# What
I use U-disk and `rsync` for my `Desktop` folder backup.
Auto mount point also created in case I'm on CLI.
U-disk corrupted and my laptop couldn't boot into the system.
~~Now I have to recover my U-disk (exfat format)~~.
Update: I was able to open it under Windows. And by using the `Windows error checking tool` I can read it under Linux without any file loss. (Maybe caused by moving 3G movie (split xaa x 10M) from Linux to Windows.)
That's the end of the world.
My `journalctl -xb` output (the red parts):
```
systemd-udevd: Error calling EVIOCSKEYCODE on device node
timeout wating for device dev-sdb1.device
mountd could not create listeners
nfs-server.service: Job nfs-server.service/start failed with result
w1: model license "MIXED/Proprietary" taints kernel.
PNFS blkmaping enablement. is not active
```
# Try fix
It maybe caused by a corrupted USB or disk device (that you configure auto-mount before).
```bash
# remove the device that's suspicious:
nano /etc/fstab
# restart computer:
reboot
```
Now my computer boots successfully.
# How
After some googling, I think it maybe related to `mount` `fstab` `nfs`. So I go check my `/etc/fstab` and try delete the U-disk mount point. And it fixed my issue!
# What
I use U-disk and `rsync` for my `Desktop` folder backup.
Auto mount point also created in case I'm on CLI.
U-disk corrupted and my laptop couldn't boot into the system.
~~Now I have to recover my U-disk (exfat format)~~.
Update: I was able to open it under Windows. And by using the `Windows error checking tool` I can read it under Linux without any file loss. (Maybe caused by moving 3G movie (split xaa x 10M) from Linux to Windows.)
评论
发表评论