Linux

54947 readers

550 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Sudden emergency (lemm.ee)

submitted 1 day ago* (last edited 1 day ago) by Rubanski@lemm.ee to c/linux@lemmy.ml

13 comments fedilink hide all child comments

I am a Linux beginner but I really enjoyed it so far. So far. Since yesterday, my Linux (pop OS) only wants to boot into emergency mode. I have a suspicion, even though my Linux and Windows are located on different physical disks, somehow Windows does it's toxic ex lover things and somehow broke my Linux I assume. It's there a terminal command to somehow reorganise my boot files?

you are viewing a single comment's thread
view the rest of the comments

[–] BananaTrifleViolin@lemmy.world 10 points 1 day ago* (last edited 1 day ago) (1 children)

Do you have any drives/ partitions set up to load at boot other than the main linux partition?

A common issue can be if linux is trying to mount a partition specified in fstab (the config file that lists all the hard drives to be loaded) and it can't mount it, it will go into emergency mode. It does this as it assumes the drives are critically important and to prevent any damage to your system. You can mark non essential partitions as "nofail" in the fstab file so that linux continues to boot even if those partitions are unavailable.

If you'd added a USB drive or another hard drive to auto mount at start up and its not available to linux then that might be the issue. Reinsert those drives and linux should boot. Alternatively you can login using emergency mode and edit the fstab file yourself if you know what youre doing. The offending drive can be removed/commented outthe fstab file or the nofail option added.

If your linux install is set to mount your windows C: partition (for file access in linux for example) then its important to know the drive can be locked out by windows. Windows "fast startup" is a very common cause - it basically means windows doesnt shut down fully, it does a fake shutdown (hibernates), and doing this locks down the drive, preventing any access to the C: drive including in linux. If this scenario applies to you, boot into wndows, disable fast startup in the control panel and then try to reboot into linux.

It this works it is still worth using the "nofail" option in fstab for any non essential drives. I personally dont auto mount my windows drive at all anymore; I have it visible in my file manager but manually mount it (just clikcing on it does it) when I need it.

[–] cmc@lemmy.cleberg.net 1 points 1 day ago

Agreed, it’s usually fstab. I wrote a blog post once to remind myself how to fix it, which may be helpful here: Procedure to Correct /etc/fstab File for Resolving Ubuntu Emergency Mode.