Fault Caused by marking

The Fault Caused by the volume label-general Linux technology-Linux technology and application information. The following is a detailed description. Today, I am very depressed and I am late for work. I didn't expect it to be even more depressing that I had to go to the office and the computer had to go down. The Boot screen was stopped at fsck. ext3: Unable to resolve 'lable =/boot' won't stop, prompting you to enter the administrator password for maintenance or press 'ctrl + d' to restart. Isn't the boot partition broken? Enter the password to enter the repair mode:
# Mount-no remount, rw/
# Mount-
The screen prompts that the/boot volume label cannot be found. No, right? Really bad? I just went to another partition (/enjoy partition, where I put a movie) and checked the content. unexpectedly, I found something in the boot partition. Dizzy, okay. It seems that it's just a problem. I tried the tune2fs command for a long time. I guess I did not mark the volume when I tried it yesterday. I used e2label to check my sda1-8:
# E2lable/dev/sda1
/Enjoy
It is found that sda1 and sda3 are the same LABEL and both are enjoy. Therefore, use e2label to change sda1 to boot.
# E2lable/dev/sda1/boot
Then synchronize the root system and mount it again as read-only:
# Sync
# Mount-no remount, ro/
# Reboot
After restart, everything works normally.

[ This post was last edited by somethingels]