Emergency mode after adding partitions and installing another Linux distribution












0















I had Linux Debian installed onto my computer. My partition table was as follows:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda4: __________________________________________________________________________

File system: ext4


On /dev/sda1 I had EFI boot partition, /dev/sda2 was my root (/), and /dev/sda4 was mounted as /home. To install Manjaro Linux, I resized partitions (by GParted) and arrived at the following partition table:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda3: __________________________________________________________________________

File system: swap

sda4: __________________________________________________________________________

File system: ext4

sda5: __________________________________________________________________________

File system: ext4
Operating System: Manjaro


As you can see, I added /dev/sda3 as swap partition and /dev/sda5 as a partition where I installed Manjaro. During the installation, I formatted /dev/sda1 (where I booted Debian from) and Manjaro installed its boot files there. After installation, I have two options in GRUB: boot Debian and boot Manjaro. Booting Manjaro is working fine, but booting Debian leads to the Welcome to emergency mode! problem. I am asked to give the root password but after I enter it nothing seems to happen (perhaps I've forgotten the password but there is no message indicating that it is wrong). After some googling, I have come to conclusion that Debian's fstab may be incorrect. Please have a look at it:



# / was on /dev/sda2 during installation
UUID=de26f007-befa-4524-b1c8-059e115aa36c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=B1D2-AC43 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=5c273b54-01ad-4186-9821-1e90980a8913 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
#UUID=9da48f63-2583-4e29-8997-3c6474e4bcbc none swap sw 0 0
UUID=ECA5-260F /boot/efi vfat defaults 0 1


What should I do to have my Debian working?










share|improve this question

























  • You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

    – A.B
    yesterday













  • yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

    – thrig
    yesterday











  • Why not provide the journalctl -xb as that error message mentions?

    – jdwolf
    15 hours ago











  • @jdwolf I will do in a couple of hours when I get home.

    – menteith
    14 hours ago
















0















I had Linux Debian installed onto my computer. My partition table was as follows:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda4: __________________________________________________________________________

File system: ext4


On /dev/sda1 I had EFI boot partition, /dev/sda2 was my root (/), and /dev/sda4 was mounted as /home. To install Manjaro Linux, I resized partitions (by GParted) and arrived at the following partition table:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda3: __________________________________________________________________________

File system: swap

sda4: __________________________________________________________________________

File system: ext4

sda5: __________________________________________________________________________

File system: ext4
Operating System: Manjaro


As you can see, I added /dev/sda3 as swap partition and /dev/sda5 as a partition where I installed Manjaro. During the installation, I formatted /dev/sda1 (where I booted Debian from) and Manjaro installed its boot files there. After installation, I have two options in GRUB: boot Debian and boot Manjaro. Booting Manjaro is working fine, but booting Debian leads to the Welcome to emergency mode! problem. I am asked to give the root password but after I enter it nothing seems to happen (perhaps I've forgotten the password but there is no message indicating that it is wrong). After some googling, I have come to conclusion that Debian's fstab may be incorrect. Please have a look at it:



# / was on /dev/sda2 during installation
UUID=de26f007-befa-4524-b1c8-059e115aa36c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=B1D2-AC43 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=5c273b54-01ad-4186-9821-1e90980a8913 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
#UUID=9da48f63-2583-4e29-8997-3c6474e4bcbc none swap sw 0 0
UUID=ECA5-260F /boot/efi vfat defaults 0 1


What should I do to have my Debian working?










share|improve this question

























  • You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

    – A.B
    yesterday













  • yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

    – thrig
    yesterday











  • Why not provide the journalctl -xb as that error message mentions?

    – jdwolf
    15 hours ago











  • @jdwolf I will do in a couple of hours when I get home.

    – menteith
    14 hours ago














0












0








0








I had Linux Debian installed onto my computer. My partition table was as follows:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda4: __________________________________________________________________________

File system: ext4


On /dev/sda1 I had EFI boot partition, /dev/sda2 was my root (/), and /dev/sda4 was mounted as /home. To install Manjaro Linux, I resized partitions (by GParted) and arrived at the following partition table:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda3: __________________________________________________________________________

File system: swap

sda4: __________________________________________________________________________

File system: ext4

sda5: __________________________________________________________________________

File system: ext4
Operating System: Manjaro


As you can see, I added /dev/sda3 as swap partition and /dev/sda5 as a partition where I installed Manjaro. During the installation, I formatted /dev/sda1 (where I booted Debian from) and Manjaro installed its boot files there. After installation, I have two options in GRUB: boot Debian and boot Manjaro. Booting Manjaro is working fine, but booting Debian leads to the Welcome to emergency mode! problem. I am asked to give the root password but after I enter it nothing seems to happen (perhaps I've forgotten the password but there is no message indicating that it is wrong). After some googling, I have come to conclusion that Debian's fstab may be incorrect. Please have a look at it:



# / was on /dev/sda2 during installation
UUID=de26f007-befa-4524-b1c8-059e115aa36c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=B1D2-AC43 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=5c273b54-01ad-4186-9821-1e90980a8913 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
#UUID=9da48f63-2583-4e29-8997-3c6474e4bcbc none swap sw 0 0
UUID=ECA5-260F /boot/efi vfat defaults 0 1


What should I do to have my Debian working?










share|improve this question
















I had Linux Debian installed onto my computer. My partition table was as follows:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda4: __________________________________________________________________________

File system: ext4


On /dev/sda1 I had EFI boot partition, /dev/sda2 was my root (/), and /dev/sda4 was mounted as /home. To install Manjaro Linux, I resized partitions (by GParted) and arrived at the following partition table:



sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32

sda2: __________________________________________________________________________

File system: ext4
Operating System: Debian GNU/Linux buster/sid

sda3: __________________________________________________________________________

File system: swap

sda4: __________________________________________________________________________

File system: ext4

sda5: __________________________________________________________________________

File system: ext4
Operating System: Manjaro


As you can see, I added /dev/sda3 as swap partition and /dev/sda5 as a partition where I installed Manjaro. During the installation, I formatted /dev/sda1 (where I booted Debian from) and Manjaro installed its boot files there. After installation, I have two options in GRUB: boot Debian and boot Manjaro. Booting Manjaro is working fine, but booting Debian leads to the Welcome to emergency mode! problem. I am asked to give the root password but after I enter it nothing seems to happen (perhaps I've forgotten the password but there is no message indicating that it is wrong). After some googling, I have come to conclusion that Debian's fstab may be incorrect. Please have a look at it:



# / was on /dev/sda2 during installation
UUID=de26f007-befa-4524-b1c8-059e115aa36c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
#UUID=B1D2-AC43 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=5c273b54-01ad-4186-9821-1e90980a8913 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
#UUID=9da48f63-2583-4e29-8997-3c6474e4bcbc none swap sw 0 0
UUID=ECA5-260F /boot/efi vfat defaults 0 1


What should I do to have my Debian working?







debian boot grub2 dual-boot manjaro






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 14 hours ago







menteith

















asked yesterday









menteithmenteith

1819




1819













  • You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

    – A.B
    yesterday













  • yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

    – thrig
    yesterday











  • Why not provide the journalctl -xb as that error message mentions?

    – jdwolf
    15 hours ago











  • @jdwolf I will do in a couple of hours when I get home.

    – menteith
    14 hours ago



















  • You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

    – A.B
    yesterday













  • yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

    – thrig
    yesterday











  • Why not provide the journalctl -xb as that error message mentions?

    – jdwolf
    15 hours ago











  • @jdwolf I will do in a couple of hours when I get home.

    – menteith
    14 hours ago

















You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

– A.B
yesterday







You could try editing (at boot time) the grub boot prompt and add or replace root=/dev/sda2 to the command line just before actually booting Debian. If this works, then well I don't know what else (grub issue?). Also if you did this just at the wrong time when having on Debian udev 240-2 or 240-3 (and not -4) then you hit a systemd/udev bug

– A.B
yesterday















yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

– thrig
yesterday





yeah try commenting things out of fstab, I've seen stray entries therein send Ubuntu boots to sudden systemd emergency mode

– thrig
yesterday













Why not provide the journalctl -xb as that error message mentions?

– jdwolf
15 hours ago





Why not provide the journalctl -xb as that error message mentions?

– jdwolf
15 hours ago













@jdwolf I will do in a couple of hours when I get home.

– menteith
14 hours ago





@jdwolf I will do in a couple of hours when I get home.

– menteith
14 hours ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494902%2femergency-mode-after-adding-partitions-and-installing-another-linux-distribution%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494902%2femergency-mode-after-adding-partitions-and-installing-another-linux-distribution%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux