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 want your help to find how can i recover my parrot os system. I use parrot os alongwith windows. I have 4gb of ram so i tried to make a swap file in parrot os . I created the swap file and put swappiness=10 in system.conf . But when i tried to reboot. I shows an error. enter image description here
I tried many times to start it nut i failed.
Here is the error when i try to start it
Reloading system manager configuration Starting default target
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.
Press Enter to continue.
When i go to recovery mode it show failed to load /swap
image of error recovery error
enter image description here
Get a Linux live-CD USB stick.
Boot up with live CD, mount your system root path(should be somewhere at /dev/) to /mnt, then you need to check /etc/fstab file, remove /swap item inside.
After that follow Arch - swap to set-up swap partition properly.
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 1 year ago.
Improve this question
I have an Ubuntu 20.04 'VMWare Workstation 16' Virtual Machine on an Ubuntu 20.04 laptop. When I try boot my VM, I see this output:
SMBus Host Controller not enabled!
Assuming drive cache: write through
/dev/sda5: clean 519701/1933312 files, 7505521/7732480 blocks
Failed to start Load AppArmor profiles
Failed to start Load AppArmor profiles managed internally by snapd
The VM then crashes and does not boot, immediately after the last message above. The first message is also new.
I don't think that I can access the terminal in the VM before the VM crashes. So not sure how I can fix this?
I have information in the VM that I'd like to access.
Milan
When launching the VM, try pressing shift when the VMWare logo comes to enter the manual setup.
After pressing F2, select 'Advanced Options for Ubuntu' and boot in recovery mode. When offered a list of options about what to do, go onto the root terminal. Enter sudo apt purge snapd and add blacklist i2c-piix4 to the bottom of the file /etc/modprobe.d/blacklist.conf
Then resume the boot and both are resolved.
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 4 years ago.
Improve this question
My question is about Ubuntu-16.04.
It's showing error -
Error mounting /dev/sda5 at /media/***/New Volume: Command-line `mount
-t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sda5" "/media/harshit/New Volume"' 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/sda5':
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.
To fix that problem you can run from Linux
ntfsfix /dev/sda5
By any chance did you created that partition by Clonzila?
If yes there some issue with it you must use partclone.ntfs for Microsoft partition.
That usually happens because since W8, when you turn off Windows, it is really doing some kind of a hibernation (it keeps information of the status of processes from the last session ), this for giving the user a faster Windows start experience. This is why you have this error. All you have to do to avoid this is just hit "restart" instead of "turn off" from within Windows.
If you want to know more of this Windows feature, read here
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
Apart from the main disk, I used to have another disk attached to the host which is /dev/vdb. In order to mount it automatically, I made changes in the /etc/fstab file.
While after I removed /dev/vdb, my CentOS 6.7 fails to start, and always stops with an error saying /dev/vdb is unavailable.
At this point, I can type the root password to enter into the command prompt, while when I trying to edit /etc/fstab file, it shows it is in read-only mode. I can't understand why it's read-only since I'm already the "root".
I'm sure removing the problematic line from fstab file would resolve my problem, but no idea of how to override the file. Can somebody help me out?
Use a live-cd or -dvd to boot up your system (I find puppy linux works well for this task). Locate your /etc/fstab file on the hard drive and edit it manually.
Exit from the live-cd session, remove the disk and reboot normally. If /etc/fstab has been rewritten correctly you should start normally.
An alternative of course, is to reinstall the /dev/vdb device if possible and edit /etc/fstab if doing that boots correctly.
If it is a Virtual machine than you can mount the fs and make changes in /etc/fstab umount it and boot vm. or you can chroot into vm as well with
sudo chroot /path
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 have installed flashrom software. When i try to run sudo flashrom command it gives me "Could not get I/O privileges (Operation not permitted). You need to be root" error. Also I tried su command to switch root and run again. I also tried sudo -i command to login as root. However any of them did not work
#if defined (__OpenBSD__)
msg_perr("If you are root already please set securelevel=-1 in /etc/rc.securelevel and\n"
"reboot, or reboot into single user mode.\n");
#elif defined(__NetBSD__)
msg_perr("If you are root already please reboot into single user mode or make sure\n"
"that your kernel configuration has the option INSECURE enabled.\n");
#endif
Reading this from the FlashRom.org pastebin site should give some insight.
This is the only file in Flashrom that contains the line, "You must be root"
Therefore, in my opinion, this is the only place the error can be coming from.
I changed secure boot option in bios settings as disabled. So I can run the flashrom program. But it gives this output.
WARNING! You seem to be running flashrom on an unsupported laptop.
Laptops, notebooks and netbooks are difficult to support and we
recommend to use the vendor flashing utility. The embedded controller
(EC) in these machines often interacts badly with flashing. See the
manpage and http://www.flashrom.org/Laptops for details.
If flash is shared with the EC, erase is guaranteed to brick your
laptop and write may brick your laptop. Read and probe may irritate
your EC and cause fan failure, backlight failure and sudden poweroff.
You have been warned.
So there is nothing to do. I have to search another tool to flash my bios
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 am trying to install ubuntu 14.04.2 LTE. I have a lunovo ideapad with windows 8. I have followed all necessary steps flawlessly, and even factory reset my laptop to make this smoother. I get this error when trying to boot and install ubuntu. I also get it if i try to run ubuntu without installing. Also I tried re-downloading ubuntu, and remounting on my usb with the universal usb installer.
Is this error due to my computer, or the ubs/unbuntu? There was another option in the boot menu. It was check disk for error. I do not know if it was checking disk as in the iso disk or my hard drive, but a ubuntu lunch screen appeared and it was looking into some ubuntu files (on the usb), when it was done it said there was 2 errors. It did not say what kind or if it repaired it , or how to repair it. It only gave me the option to exit, then lunovo boot screen appeared and it stayed in a attempting to repair loop for quite a awhile so I gave up on that and shut down.
I would ask this in ask ubuntu, but I do not have enough "respect points" to upload an image.
Major respect to anyone who can help me out, I have been to get ubuntu for 2 days now, and I hit a dead end.
This error message can appears in those cases:
1. Your hardware it not compatible, usually ACPI issue. Try to boot with additional options: "noapic" and/or "acpi=off". You should be able to set parameters in "Other options" [F6 key].
2. Your RAM is broken. Check it in "Test memory" option.