Hi, need your help please. I am new in linux and was trying things in my Centos 7. When i boot my system, i got the error below


" Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): "

ive got, 2 hdd and 1 hdd is sda1 and second hdd is sdb. To better understand, here is the clearer view of my partition.

Thanks a lot..

Attached Thumbnails

 

Did you try "journalctl -xb" to see the system logs to get an idea of what went wrong?

Hello There,

I have encounter this as wel a few times.
But you have to read the journal to find you're problem indeed.

For me it was some folder location's and disk mount issue a couple of times.
Those startup mount location needs to be correct and can be modified with fstab.

Its mostly so simple in my experience but finding it without knowledge is difficult.

Regards,

Wouter

When you have found the error messages, post them here and someone should be able to show you how to fix the problem.

thanks for all your help..

i attached here the error which i think is causing, not sure if this is the right one.

before i got the error, i was testing on LUKS on backup-databckup (is it called LVM or what is the proper term for that)

this was the command i run, then i shutdown. Maybe there is still some commands i need to run after the last command below which is the mount command. Just wanted to know, if i did some mistakes on the commands below.

- sudo umount /backup/data
- sudo shred -v iterations=1 /dev/backup/databckup
- sudo cryptsetup -v luksFormat /dev/backup/databckup
- sudo cryptsetup luksOpen /dev/backup/datackup databackup
- sudo mkfs.ext4 /dev/mapper/databackup
- sudo mount /dev/mapper/databckup /backup/data/

Attached Thumbnails

   

Those commands look ok - I'd guess you have specified XFS as the filesystem type in /etc/fstab.

1 members found this post helpful.

From what i read is that the mount folder is this in fstab and you change a drive or after a reboot the drive name changed from sdb to sda.
If you want start the server again al you have to do is use command sudo vi /etc/fstab and remove that specific mount line or adjust disk name or uuid number to the specific new disk name or dev name.

I encountered the same issue and to fix this for the next time use the harddisk specific uuid number. I dont know the commands exactly but I do have it written somewhere if you need it.

Regards

Wouter

edit /etc/fstab by adding a # at the beginning of the line that has /backup/data.

1 members found this post helpful.

Thank you so much colorpurple21859, you really saved my pc/work. I was trying different options, steps for the past one week. By just adding the #, my linux booted as normal. Thanks a lot really.

I have question though, if you dont mind?

By adding the #, what is the purpose of it or what does it do?
This is the line i have in fstab
/dev/backup/databckup /backup/data xfs defaults, usrquota 0 0

If i removed or delete that line in fstab, that would also solve the issue?
May i know what causes the boot issue by the way?

Putting a # in front of many config files in Linux indicates that the stuff after it is a comment for human readability and not to be executed by the program reading the config. It is a handy way to remove a config option but keep it around if you need to put it back.
Since the system is working it should be safe to remove that line now.

1 members found this post helpful.

Thanks a lot uteck for the info. i will take note of that.

As I suggested, you have XFS specified in that fstab entry. However you did a mkfs for ext4 - merely changing the entry from xfs to ext4 will maintain the automatic mount. Commenting it out (using #) or deleting the line will mean you will have to manually mount it after each boot.

You need to spend some time understanding your linux system and what changes may affect - for example "man fstab" would be an easy start. Historically fstab has listed essential filesystems for the system and any errors indicate the system won't work, so the boot fails.

1 members found this post helpful.