Hi,

I was running red hat Linux 7 on my vmware. Initially there was only hard disk (sda).For learning Fdisk, I added a second hard disk (sdb), format it partprobe, than mkfs.ext4, mount it with a mount point on my desktop , but after restart , Now I am not able to boot up its throwing error " Welcome to emergency mode!After logging in type journalctl -xb .......give root password for maintenance.

same thing happned with my second machine as well.



Please help.

What did you add to /etc/fstab ?

As far I remember, I added full path than than /dev/sdb1 than deault, 0, 0

There are several possible errors

1 - typographic error in the fstab file
2 - the mount point doesn't exist (and may be due to a typeographic error)
3 - the device sdb may not have a partition table (since you are learning fdisk, you might have forgotten to save it).
4 - the mkfs may have been done on /dev/sdb and not /dev/sdb1 - which would have wiped out the partition table

The easiest thing is to comment out the fstab entry and reboot.

Experiment with fdisk/mkfs/fsck... and manually mount the filesystems you expect.

You borked something, likely in fstab. Comment out the line and reboot to get back into your OS. Once there, verify the drive partitioning looks correct, edit your fstab so it's correct, and then use "mount -a" to attempt to mount all disks in fstab to their proper places. If you get an error, investigate and fix it, and only reboot once it's working correctly.

SElinux might be stopping a boot ( security check )
/home/YourUserName/Desktop/MountPoint

is owned by "your user name"

also the "Desktop" folder is more decoration than a real folder

try using the already existing

/mnt/YourPartition

Hi memebers,

Same problem again.

Please find the /etc/fstab file below edited by me:
#
# /etc/fstab
# Created by anaconda on Wed Jul 20 00:02:57 2016
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=4b2cd685-b9d0-4fc4-8cb1-a2985932a501 / ext4 defaults 1 1
UUID=276d1a6b-86d4-4597-b60a-92fb81588a69 /boot ext4 defaults 1 2
UUID=b75f38b1-bd64-43c9-8680-b09e6a65a431 swap swap defaults 0 0
/dev/sdb1 /mnt/test ext4 default 0 0


Only the last entry was made by me to add sdb1.
It was working even after I mount it.
I was able to see it in df -h.
than I make entries in /etc/fstab and rebooted, it didnt work.

Does /mnt/test exist after boot?

You might do a "ls -l /dev/disk/by-uuid" show after a boot (with the /dev/sdb1 commented out of the fstab).

Also seeing the output of "cat /proc/partitions" wouldn't hurt either.

These will confirm the existence of the partition tables.

Again, after you make the change in /etc/fstab, you should unmount it and then run "mount -a" to test the actual fstab entry before rebooting. This will protect you against typos and other formatting errors.

Your line needs to say "defaults", not "default". I'm not sure if that's enough to cause it to barf on boot, but testing it with "mount -a" before rebooting would verify.

changing to "defaults", from "default" solved the issue.
Uhhff, Never though Such a small mistake can make system fail to boot up.

Thanks a lot to everyone.
Being new to Linux, It give me a lot of confident to have guys like you!