Ubuntu sudo not available switch to root7/27/2023 Imagine forgetting to lock your computer while logged in as a root user. Using the root user instead of the regular account with the sudo command brings additional security risks. This is the safest solution for working in Linux with root rights. During this time you won't be prompted again for your password. The password is remembered for 15 minutes. I am so pleased that you stuck with me to help me out amac777 (and the rest of you, too)! I hope to find you around the forums again.The root user’s password is then requested before the command is actually executed. I simply dismissed these as side effects of the 'sudo' issue. and an update was attempted and I kept receiving messages about broken packages and 'crash reports' in my upper right-hand side of the screen. Indeed the disk (root) had been full (as described earlier in this thread) due to a backup gone awry. If yhou decline this option you will need to manage your system's authentication configuration by hand. Please indicate whether these local changes should be overridden using system-provided configuration. One or more of the files /etc/pam.d/common have been locally modified. It ran for a little bit, and said the following: In fact, there was an option in the recovery mode menu to fix or repair broken packages (I think something to that effect - which I never even noticed before). Well, it wasn't 'exactly that', but it lead me to the place where I found my solution. It is fixed, and what you told me to do, fixed it. Sir, you're quite amazing and I commend you. Wow! Such an easy fix to a very complex problem. Can anyone refute this?Īll things aside - while I appreciate your help, I will continue to try each and every one of your solutions until this weekend, at which point I throw in the towel, and reinstall Linux from scratch, and restore my backed up files to where they were. Agree? I'm thinking that it will only see each disk individually, and hence may not be seeing my LVM Partitions correctly. I think the reason I can't mount the proper device is because a LIVECD will not detect the idea that my 2 hard disk drives are configured in a RAID 0. I gotta tell ya - all this mounting is making me crazy. I hate to say it again - it's the perverbial chicken and the egg - you asked me to run a sudo command. Sudo chroot /media/disk /bin/bashAnyway, are you sure it's /dev/sda1?.if not check the output of Su and type in the password that you previously set in the chrooted environment, you will have root access. Sudo reboot and reboot into your installed ubuntu. Or in that case whichever partition is marked as boot is most probably your root partition (most probably cause you might have made a separate boot partition).Īnother way is, to mount that device (which you think is root) and see it's contents.there should be the sbin and tmp folders there.Īfter you've confirmed that it's the root partion, chroot with (assuming you've mounted it in /media/disk). Sudo fdisk -l.it should be marked as boot. Are they encrypted in some way? Or could it be that because I'm running a RAID array that it is unable to find the RAID (instead maybe sees the drives individually, rather than as a whole?)?Īnyway, are you sure it's /dev/sda1?.if not check the output of I couldn't seem to find these when I was in the live mode cd. I'm guessing that the partition 'root' is mounted on is /dev/mainvg/root or dev/mapper/mainvg-root. I created a volume group called 'mainvg'. I created manual partitions and used LVM. I did not let Ubuntu automatically partition my drives. I don't know if it's /dev/sda1 or what - or, as you said - /media/disk. I have a hunch that I'm doing something wrong when I'm mounting my root partition (where I have installed Ubuntu). Sudo chroot /mnt/ubuntu and I get a message stating 'chroot: cannot run command `/bin/bash': No such file or directory'. I did as you stated, and attempted this before: Sudo: 3 incorrect password sudo sudo -iĭE_logics - thank you for your detailed explanation - I'm still fairly new to this. So, how to I get root privileges back sudo rm -R FreeAgent So I try to SUDO the same command, and it tells me 3 times in a row, "Sorry, try again", followed by "sudo: 3 incorrect password attempts". So, I went into /media and tried to delete the backup directory and file(s) that were in that directory, but it tells me that permission is denied. I discovered that the root directory was full when the machine tried to get updates, and couldn't. I finally established why - that my /media directory had filled up due to the USB-attached device having been unmounted for whatever reason, and SimpleBackup tried backing up without the mount in place - thereby filling up the filesystem.
0 Comments
Leave a Reply. |