When working with Linux<\/mark><\/a> servers, especially cloud-based systems, you may sometimes encounter the message:<\/p>\n\n\n\n This usually happens when the system cannot mount one or more filesystems during boot a common situation seen in Emergency Mode Linux.<\/p>\n\n\n\n A common cause is an incorrect entry inside \/etc\/fstab, which can break the boot process and force the server into emergency mode.<\/p>\n\n\n\n In this blog, we will walk through a real-world scenario where the server failed to boot because \/etc\/fstab attempted to mount the wrong device on \/var\/www.<\/p>\n\n\n\n You\u2019ll learn how to identify the issue, correct the fstab file, and safely restore the system to normal operation.<\/p>\n\n\n\n After logging into emergency mode, running:<\/p>\n\n\n\n shows:<\/p>\n\n\n\n This indicates that the system could not mount the \/var\/www directory during boot.<\/p>\n\n\n\n To determine why, check the \/etc\/fstab file:<\/p>\n\n\n\n Inside it, you may see an entry like:<\/p>\n\n\n\n At first glance, this looks correct.<\/p>\n\n\n\n However, upon deeper inspection, it becomes clear that \/dev\/sdc is not a filesystem \u2014 it is a disk with an MBR table.<\/p>\n\n\n\n Checking the disk with:<\/p>\n\n\n\n returns:<\/p>\n\n\n\n And the actual filesystem is located on the partition:<\/p>\n\n\n\n Verified using:<\/p>\n\n\n\n which shows:<\/p>\n\n\n\n This means the system was trying to mount the entire disk instead of the partition that actually contains the filesystem.<\/p>\n\n\n\n Because \/dev\/sdc had no filesystem, the mount failed \u2014 causing the emergency mode boot issue.<\/p>\n\n\n\n To fix this, edit the fstab file inside emergency mode:<\/p>\n\n\n\n Locate the incorrect line:<\/p>\n\n\n\n Comment it out:<\/p>\n\n\n\n Save the file and reboot:<\/p>\n\n\n\n The system should now boot normally without dropping into emergency mode.<\/p>\n\n\n\n Running Filesystem Check (Optional but Recommended)<\/p>\n\n\n\n Because \/dev\/sdc1 showed:<\/p>\n\n\n\n it is recommended to run an fsck to ensure the filesystem is clean.<\/p>\n\n\n\n However, never run fsck on a mounted root filesystem.<\/p>\n\n\n\n Option 1: Force fsck on next boot<\/p>\n\n\n\n Option 2: Boot into recovery mode and manually run:<\/p>\n\n\n\n This safely repairs any pending journal issues.<\/p>\n\n\n\n Emergency mode in Linux often points to problems related to the filesystem, and incorrect fstab entries are one of the most common triggers.<\/p>\n\n\n\n In this scenario, the system failed to boot because \/etc\/fstab attempted to mount the entire \/dev\/sdc disk instead of the actual partition \/dev\/sdc1.<\/p>\n\n\n\n By identifying the failed mount, correcting the fstab entry, and rebooting, the system returned to normal operation.<\/p>\n\n\n\n Always ensure that fstab entries point to valid filesystems \u2014 not raw disks \u2014 to prevent similar boot failures.<\/p>\n\n\n\n If you encounter this issue in the future, you now have a clear, step-by-step process to diagnose and fix it quickly.<\/p>\n\n\n\n If you\u2019re still stuck in Emergency Mode Linux or facing recurring \/var\/www mount issues, our experts can help. Skynats offers reliable Linux Server Management Services<\/a> and 24\/7 Server Management Services<\/a> to diagnose, repair, and fully secure your server. Contact us anytime for instant support and get your system back online quickly.<\/p>\n","protected":false},"excerpt":{"rendered":" Introduction When working with Linux servers, especially cloud-based systems, you may sometimes encounter the message: This usually happens when the system cannot mount one or more filesystems during boot a common situation seen in Emergency Mode Linux. A common cause is an incorrect entry inside \/etc\/fstab, which can break the boot process and force the […]<\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[1180,1182,1179,1010,1181,302],"class_list":["post-17073","post","type-post","status-publish","format-standard","hentry","category-blog","tag-var-www-mount-in-linux","tag-24-7-server-management-services","tag-emergency-mode-linux","tag-linux-server-management-services","tag-linux-servers","tag-server-management-services"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17073","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=17073"}],"version-history":[{"count":3,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17073\/revisions"}],"predecessor-version":[{"id":17086,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17073\/revisions\/17086"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=17073"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=17073"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=17073"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}You are in emergency mode. \nAfter logging in, type \"journalctl -xb\" to view system logs.<\/code><\/pre>\n\n\n\nIdentifying the Issue<\/h3>\n\n\n\n
systemctl --failed<\/code><\/pre>\n\n\n\nvar-www.mount loaded failed failed \/var\/www<\/code><\/pre>\n\n\n\ncat \/etc\/fstab<\/code><\/pre>\n\n\n\n\/dev\/sdc \/var\/www ext4 defaults 0 0<\/code><\/pre>\n\n\n\nfile -s \/dev\/sdc<\/code><\/pre>\n\n\n\nDOS\/MBR boot sector, extended partition table<\/code><\/pre>\n\n\n\n\/dev\/sdc1<\/code><\/pre>\n\n\n\nfile -s \/dev\/sdc1<\/code><\/pre>\n\n\n\nLinux rev 1.0 ext4 filesystem data ...<\/code><\/pre>\n\n\n\nCorrecting the fstab Entry<\/h2>\n\n\n\n
vim \/etc\/fstab<\/code><\/pre>\n\n\n\n\/dev\/sdc \/var\/www ext4 defaults 0 0<\/code><\/pre>\n\n\n\n#\/dev\/sdc \/var\/www ext4 defaults 0 0<\/code><\/pre>\n\n\n\nreboot<\/code><\/pre>\n\n\n\n(needs journal recovery)<\/code><\/pre>\n\n\n\ntouch \/forcefsck\nreboot<\/code><\/pre>\n\n\n\nfsck -fy \/dev\/sdc1<\/code><\/pre>\n\n\n\nConclusion<\/h3>\n\n\n\n