Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I 've got an issue with my UEFI boot values.
In the past I installed Ubuntu 14.10 LTS as a dual-boot system.
It was working ok, until I decited to remove it.
I deleted the Ubuntu partitions and merged them with my Windows partition.
Everything is working fine, except when I check the Boot Menu inside the BIOS, there is still a value considering Ubuntu.
http://i.imgur.com/xo9tF82.jpg
I followed this guide: https://askubuntu.com/questions/63610/how-do-i-remove-ubuntu-in-the-bios-boot-menu-uefi but the value is still remaining there. Is there a way to completeley remove it without loosing the values that point to my Windwows system.
My Laptop is a Lenovo G50-70
Thank you in advance!
Boot a live Linux cd using legacy, have a USB stick with you.
Run lsblk to find out where your efi partition is
$ lsblk
Mount that efi partition and your USB stick to 2 separate folders (replace sda1 with the path of your efi partition and sdb1 with the path of your USB.
$ mkdir /mnt/usb
$ mkdir /mnt/efi
$ mount /dev/sda1 /mnt/efi
$ mount /dev/sdb1 /mnt/usb
Cd into the EFI folder of the efi partition
$ cd /mnt/efi/EFI
Move the folder "ubuntu" into the USB so you can restore it if something goes wrong
$ mv ubuntu /mnt/usb
Done!
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 12 months ago.
Improve this question
I've got a problem on Debian 10.11 (but I think it's not only Debian related) with onboot mounting Windows share.
cifs-utils 2:6.8-2 amd64 Common Internet File System utilities
cat /etc/fstab | grep share2
gives
//10.100.0.204/share2 /home/share2 cifs auto,vers=default,rw,file_mode=0775,dir_mode=0775,noperm,gid=100,username=user1,password=passwordhard 0 0
When I type:
command mount /home/share2 Works as expected.
dmesg gives me an errors:
[ 5.045482] CIFS VFS: Error connecting to socket. Aborting operation.
[ 5.046471] CIFS VFS: cifs_mount failed w/return code = -101
I think that linux tries too early to mount samba shares.
What can I do about it?
I know that I can use crontab and:
#reboot root sleep 15; mount /home/share2
as workaround but I like resolving problems at source.
If the problem is indeed samba service is loading too fast.
It is possible to edit samba service file.
Add Requires=<a service-name that need to be loaded prior to samba>
This trick is the official pattern to control/manage/order systemd service loading.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am on termux with root permission.
My phone has aarch64 cpu architecture.
I'm trying to chroot a ubuntu filesystem with amd64 architecture
i've seen and this https://unix.stackexchange.com/a/222981
here's my command
sudo chroot ubuntu /bin/qemu-x86_64-static /bin/bash --login
i logged in successfully but when i run command
ls or any
it's give an error like Exec format error
then i tried that command with qemu-x86_64-static like qemu-x86_64-static /bin/ls it's execute successfully
any idea for this???
i think i can add alias for all command for starts with qemu-x86_64-static but that's not good idea...
You need to tell the kernel that when it sees an arm64 binary it should run it by launching QEMU. The mechanism for this is called "binfmt-misc", and to configure it you need to write data in the correct format to special files in the host system's /proc/sys/fs/binfmt_misc/ directory. Most Linux distros will do this for you automatically when you install their QEMU packages, but obviously Android won't do this for you.
First check that your phone's kernel has binfmt-misc support compiled in at all: there should be a file /proc/sys/fs/binfmt_misc/status and if you cat its contents it should read enabled. If not, try modprobe binfmt_misc. If after that the status file is still not there then you won't be able to get this working unless you can somehow build a new kernel for your phone.
If the support is present in your phone's kernel, you can try the qemu-binfmt-conf.sh script that upstream QEMU ships as a mechanism for registering QEMU with the binfmt-misc machinery:
https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh
(This is just a script which writes the correct lines of data to /proc/sys/fs/binfmt_misc/register.)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
After kernel update, the version of kernel in uname is not updated itself.
It is a problem because all the modules are loaded through it, so I had to rename the folder with new modules to the old version (as a temporary solution) but I would like to solve this problem properly.
~: pacman -Q linux
linux 4.9.11-1
~: uname -r
4.9.8-1-ARCH
Have you replace the kernel image (bzImage or vmlinuz)?. If yes then there is some issue with your grub conf parameter. Otherwise you need to replace the kernel image as well as.
Below are the steps which you need to update the kernel:
1) Replace your kernel image (vmlinuz or bzImage you can check the name from your grub conf parameters) with the existing kernel image..
2) Copy the new module folder (containing all new modules) into the /lib/modules folder..
3) Sometimes there may be issue during module loading. So you can run the depmod -a command inside your new module folder.
4) Reboot the board and check the kernel version and your kernel image details (like kernel version and date of compiled kernel image) though uname -a command.*
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
(Accidental) Action
Hi, I am not very well versed in Linux but using Ubuntu for more than a year.
Couple of days back I accidentally changed the ownership of my root folder while changing ownership of another non-root directory. I am not sure but as far as I remember, I executed sudo chown -R root:root /bin accidentally.
The Consequences
Now I am unable to do anything that requires sudo. This is the error I am getting while performing any such task:
max#max-ThinkPad-T430:~/Desktop$ sudo chown -R root:root /bin
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
Question
What's the solution to bring back the sudo working exactly as it was before the incident.
I would recommend creating a bootable disk (CD, DVD or USB Drive) using the "Startup Disk Creator" (/usr/bin/usb-creator-gtk) and a recent Ubuntu Desktop .iso file, available from http://www.ubuntu.com/download/desktop/.
Once you have created the startup disk, reboot your computer and ensure that you boot from the startup disk. I assume you know how to do that given that you have installed Ubuntu before.
Don't choose the "Install Ubuntu" mode, just use the "Try It Out" mode to get to a desktop environment. From there you should be able to mount your existing Ubuntu setup and chown root /etc/sudoers so that your sudo command will work again.
Reboot to your real Ubuntu installation and try sudo ls, it should work now.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I've installed both windows 8 and Linux 3.8.0-35-generic on my Laptop.
I'm unable to access the other drives other than one in which Linux has been installed.
It is showing following error. Casket is name of the partition.
Error mounting /dev/sda4 at /media/rancher/Casket: Command-line `mount -t "ntfs" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sda4" "/media/rancher/Casket"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
I thought shutting down windows properly would solve the problem ,but no change.
Is there any other way to shut down windows properly. Or any other way to access the contents of the drives.
Did you try the suggestion at the bottom of that error message - mounting the filesystem read-only?
sudo mount -o ro -t auto /dev/sda4 /media/rancher/Casket
Or just add the -o ro to your /etc/fstab file for the /dev/sda4.