lol, those are the exception. SystemRescue is a good live system?
another way to access your system to try and fix it is:
at the grub prompt (hit ESC after the Bios POST to see it)
press E for edit
and add a 1 to the end of the grub command line
(the line starts with “linux” and usually ends with loglevel=3 or udev_log_priority=3)
add a space and a 1 to the end
then F10 or CTRL-X
to boot
This should land you in a root shell.
I don’t have much confidence to use the Bios, I will first try to solve the problem with live system. And again, thanks for the help
You would not be using/accessing the Bios - but the Grub prompt
which is usually hidden - you don’t get to see it normally.
Only when you press “Esc” at the right moment.
But this will not work when you have no root password set.
… I guess …
The usb live system is probably better.
SystemRescue is a good option?
not familiar with it
Is it a linux system?
then: yes
literally any linux live cd will do
one with a graphical user interface may make things easier to navigate
all you want to do is mount the / filesystem of your disk and
chmod u+s ...
the sudo binary
I already boot the system with live system, but how do I access /filesystem from the console? or the graphical user is better?
mount the / filesystem of your installed system!
Are you root in your live system?
whoami
tells you
lsblk -f
shows you your disk and partitions on it
note the name of the partition with the / filesystem on it
get root if you are not yet
sudo su -
mount the partition your root filesystem is on (the name you noted)
to /mnt
mount /dev/xyz /mnt
ls -al /mnt/usr/bin/sudo
to verify that you are indeed “above target”
it should list the file and permissions just as before in this thread
If that is the case, proceed:
chmod u+s /mnt/usr/bin/sudo
verify once again - the output should now show an “s” where there was an “x” before
ls -al /mnt/usr/bin/sudo
if that is so, you are done
umount /mnt
reboot
1 Like
I don’t understand this part [quote=“Nachlese, post:31, topic:131972”]
mount the partition your root filesystem is on (the name you noted)
to /mnt
mount /dev/xyz /mnt
[/quote]
i am already root, and i put “lsblk -f” so i get
“NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/archiso/sfs/airootfs
sda
-sda1
vfat FAT32 something
-sda2
ext4 1.0 somthing
-sda3
swap 1 somthing
sdb
sdb1
vfat FAT32 RESCUE804
sr0”
as root:
fdisk -l
maybe that output is more clear to you
/dev/xyz stands for whatever the name of your device is - I can’t know that, but you can see …
It is likely that this is /dev/sda3
so:
mount /dev/sda3 /mnt
… format your output - it’s hard to read like that
Welcome to Manjaro! 
- Please read the information behind this link. It will help you to post necessary information. [HowTo] Provide System Information
- Please press the three dots … below your post and then press the
- If you give us information about your system, we can see what we’re talking about and make better suggestions.
- You can do this by using
inxiin a terminal or in console.
inxi --admin --verbosity=7 --filter --no-host --width
- Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
- Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
- Copy the output from inxi (including the command) and paste it into your post.
- To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.
(Wisdom lies in reading
)
with “fdisk -l” i get 3 devices and its type “file swap”, “linux filesystem” and “efi system”. so i guess is the /dev/xxx with the filesystem type
the one with linux filesystem
not “swap”, obviously - and not “efi system” either
so it should be:
mount /dev/sda2 /mnt
when /dev/sda2 is the linux filesystem
I managed to return the root permissions. Thanks
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.