Ubuntu / Manjaro Dual Boot Power Cut while on

P1000 · October 21, 2020, 10:03pm

I have been using Manjaro as my main distro in dual boot for the last couple of days. Rather new to this as a computing student but I was understanding how to use it fine.

I needed to move the desktop computer upstairs and I believe it only went into suspend mode rather than shut down before the power was unplugged.

Then when I go back onto the computer when it’s setup upstairs I can log into Ubuntu fine with internet connection but when I get to manjaro KDE login screen, I can put in my password but then it freezes when I press login (Mouse continues to work but can’t click on anything, the login button looks pressed but just freezes)

I’m struggling to work out how to fix it from many articles on the internet. I know this one is arch but hoped it might be similar: [attached [bbs . archlinux . org / viewtopic.php?id=152284]
I don’t think I understnad the steps that were made to fix this?

Thank you very much for the help,
Peter

"

Finished File System Check on /dev/disk/by-uuid/…
Mounting /boot/efi…
Unrecognised mount option “umask=077” or missing value
[FAILED] Failed to mount /boot/efi
See ‘systemctl status boot-efi.mount’ for details.
[DEPEND] Dependence failed for Local File Systems.

"

adelpozoman · October 21, 2020, 11:00pm

Do you have other users in Manjaro to try? If you can you know its a problem with your main account.
If not, in the login screen use CTRL+Alt+F2 to go to tty2, then try to log in from there.

P1000 · October 21, 2020, 11:02pm

Ah okay I’ll try that in tty2 when start work tomorrow morning and see what happens. Is there something I’d need to do if I get into tty2 to debug the problem more? Thank you very much

adelpozoman · October 21, 2020, 11:04pm

We will see from there, but a good first step is moving all your config files from your /home/username/ folder elsewhere (like a backup), so the next time you log in it will generate all of them from scratch.

megavolt · October 22, 2020, 8:59am

This have to be umask=0077 … there is a zero missing.

stephane · October 22, 2020, 7:57pm

boot on USB iso manjaro
open a terminal and a browser on this topic
and report

sudo manjaro-chroot -a
cat /etc/fstab
exit ( end-chroot )

P1000 · October 26, 2020, 6:30pm

Thanks everyone for the advice. I’ve only just had a chance to look at this again. It now can’t get to the login screen:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.8.16-2-MANJARO #x1
Hardware name : Gigabyte Technology … BIOS F3 GK
Call Trace:
dump_stack+0x6b/0x88
panic+0x112/0x2e8
mount_block_root+0x317/0x165
? reset_init+0xbf/0xbf
kernel_init+0xa/0x111
ret_from_form+0x22/0x30
Kernetl Offset: * from & (relocation range: …)
—[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]----

And then it freezes and doesn’t take me to login.

megavolt - It is now saying umask=0077

I’ll see if I can work out how to boot from a memory stick next and see if that helps

P1000 · October 26, 2020, 7:09pm

I unfortunately can’t send the screenshot but this is what I get:

/dev/nvme0n1p1 fat32
/dev/nvme0n1p2 ext4
/dev/nvme1n1p1 ext4 /mnt/noot/efi Manjaro_20.1.1
/dev/nvme1n1p2 ext4 /mnt

[manjaro@manjaro ~]$ sudo manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> Detected systems:
–> 0) ManjaroLinux
–> 1) ManjaroLinux1
–> 2) Ubuntu
==> Select system to mount [0-2] :
0
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
–> mount: [/mnt]
–> mount: [/mnt/boot/efi]
[manjaro /]# cat /etc/fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a device; this may

be used with UUID= as a more robust way to name devices that works even if

disks are added and removed. See fstab(5).

UUID=CBDE-CFF6 /boot/efi vfat umask=0077 0 2
UUID=66af1964-b40f-4dd6-9bac-01537e684675 / ext4 defaults,noatime 0 1
[manjaro /]# exit ( end-chroot )
bash: syntax error near unexpected token `end-chroot’
[manjaro /]# exit
exit
–> umount: [/mnt/boot/efi]
–> umount: [/mnt]
[manjaro@manjaro ~]$

[manjaro@manjaro ~]$ sudo manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> Detected systems:
–> 0) ManjaroLinux
–> 1) ManjaroLinux1
–> 2) Ubuntu
==> Select system to mount [0-2] :
1
==> Mounting (ManjaroLinux1) [/dev/nvme1n1p2]
–> mount: [/mnt]
–> mount: [/mnt/boot/efi]
[root@manjaro /]# cat /etc/fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a device; this may

be used with UUID= as a more robust way to name devices that works even if

disks are added and removed. See fstab(5).

UUID=e7b022e9-4e79-4ab1-ab02-a17e032ffcf1 /boot/efi ext4 umask=0077 0 2
UUID=90e88015-b3b9-4570-92a8-09b362681e92 / ext4 defaults,noatime 0 1
[root@manjaro /]#

Thank you very much!

P1000 · October 26, 2020, 7:15pm

My nvme0n1p1 says it’s type is fat32 whereas the other nvme sections all say ext4. Is that alright for them to be different?

chomsky · October 26, 2020, 7:42pm

Yes that would be /boot/efi and is supposedd to be FAT32

stephane · October 26, 2020, 7:56pm

case 1 : UUID is false , /boot/efi is short in UUID for Fat32 (vfat )
you can check with USB iso manjaro

sudo lsblk -fs

P1000 · October 27, 2020, 10:31am

Thank you, it comes up with this:

manjaro@manjaro ~]$ sudo lsblk -fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0
squash 4.0 0 100% /run/miso/
loop1
squash 4.0 0 100% /run/miso/
loop2
squash 4.0 0 100% /run/miso/
loop3
squash 4.0 0 100% /run/miso/
sda1 iso966 Jolie MANJARO_KDE_2011
│ 2020-10-01-14-09-49-00
└─sda
iso966 Jolie MANJARO_KDE_2011
2020-10-01-14-09-49-00 0 100% /run/miso/
sda2 vfat FAT12 MISO_EFI
│ 1AFD-57C6
└─sda
iso966 Jolie MANJARO_KDE_2011
2020-10-01-14-09-49-00 0 100% /run/miso/
nvme0n1p1
│ vfat FAT32 CBDE-CFF6
└─nvme0n1

nvme0n1p2
│ ext4 1.0 Manjaro 20.1.2
│ 66af1964-b40f-4dd6-9bac-01537e684675
└─nvme0n1

nvme1n1p1
│ ext4 1.0 Manjaro 20.1.1
│ e7b022e9-4e79-4ab1-ab02-a17e032ffcf1
└─nvme1n1

nvme1n1p2
│ ext4 1.0 90e88015-b3b9-4570-92a8-09b362681e92
└─nvme1n1

nvme1n1p3
│ ext4 1.0 7ebcfccb-171e-4ba3-9909-5a8d0c347c6d
└─nvme1n1

[manjaro@manjaro ~]$

stephane · October 27, 2020, 4:35pm

correct to mount 1 ( manjarolinux1 )
/etc/fstab for /boot for UUID CBDE-CFF6

sudo manjaro-chroot -a 
nano /etc/fstab
efibootmgr -v
exit

P1000 · November 1, 2020, 10:01pm

Okay, so I eventually managed to backup everything and re-install but my configuration backup copied over and come up with a similar problem again.
I managed to get into tty2 and move the configuration files I think? I re-started the computer and it did the same thing with the login button freezing.

When I get into tty2 and do ls -a, it looks like it has re-generated .config which looks good.

So, I assume it’s another file in my home/user folder. What shall I do to work out which file is causing the problem? I have a backup of the user home directory so loosing things shouldn’t be a problem. I assume .cache is deleted automatically?

.bash_history
.bash_logout
.bash_profile
.bashrc
.bashrc_functions
.bashrc_system
.cache
.config
Desktop
.dir_colors
Documents
Downloads
.face
.face.icon
.fonts.cong
.gnome
.gtkrc-2.0
.kde4
.local
Music
.nv
Pictures
pkglist_aur.txt
pkglist.txt
.pki
psrc
Public
.python_history
Templates
Videos
.vscode-oss
.Xauthority
.Xclients
.xinitrc
.zshrc

P1000 · November 1, 2020, 10:04pm

Would it be worth some sort of file related to login GUI if that’s to do with it freezing at all?

linux-aarhus · February 9, 2022, 6:30pm