I removed a preinstalled Windows 10 to install Fedora 26 on my Lenovo Yoga 9. Now, the computer doesn't boot. Gets stuck during the booting and
it shows this. Can Someone please tell me what I should do to fix this? I am completely new to Fedora. I indent to remove Windows 10 and keep Fedora 26.
I was able to solve this it. The problem was that while installing Fedora 26, I didn't do the partitioning properly. I left almost all of my hard drive space unpartitioned/free and had little to none for boot, swap etc.
So all I had to do was reinstall Fedora 26 with proper partitioning and the problem was solved. I mainly followed the following two links:
https://www.tecmint.com/fedora-25-installation-guide/
https://docs-old.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/sect-installation-gui-manual-partitioning.html
Proper partition is important!
Related
After an update of my TrueNAS I started getting some strange double beeps.
I thought it might be thermal warning, so I cleaned my NAS PC, put a monitor and keyboard on and booted it up.
I started to see some strange token series popping up, seemingly random: ^[[6~^ ^[[6~^.
I thought nothing of it.
Then more beeps, system froze. I checked the monitor. It was flooded with ^[[6~^ ^[[6~^.
I then rebooted my TrueNAS and went into the shell by pressing 9.
Now I see: ~~ and the same beeps occur when the characters appear. Roughly around every 8 seconds.
What is causing these? I tried unplugging all USB devices, I even tried to google.
I found things like kbdcontrol, jons, crontab. But with my very limited Linux knowledge I could not make anything work.
Hoping someone can help me with this.
Something went wrong with the patching process (I guess)
How I fixed it:
In the GUI I went to System -> Boot
I reverted to the previous patch.
Rebooted the system.
Issue still occurred.
Then I went to Dashboard -> check for updates.
It then went on and installed the update (as before).
Now the issue is resolved.
I just downloaded Linux Mint 18 Cinnamon (64-bit) and burned it to a dvd. I want to partition about 20GB on my G drive for it, then add more later. the goal is to eventually go over from windows 8 (current operating system) to Linux Mint, is this possible? If not, any better sugestions? thanks in advance.
Yes, you can do that. First dual-boot the system with Linux. Once you are comfortable to get rid of Windows, use Gparted to simply delete Windows partitions and extend the Linux partitions.
Environment:
Remote dedicated server
FreeBSD 9.1-release with custom kernel [quota,ipfirewall,ipfirewall_default_to_accept]
SSH access
No easy KVM access (only accessible by my provider)
Goal:
Upgrade to FreeBSD 9.2-release (for a start then... to 10.1...)
Reason:
Freebsd 9.1-release is supported only until Dec 30 2014
Question:
How to upgrade FreeBSD 9.1-RELEASE to 10.1-RELEASE for instance, using freebsd-update or rebuilding the kernel and world, knowing that the server can't be accessed after being rebooted in single user mode because of the remote situation.
I read about kern.securelevel set to 2 to allow installing the world without being in single user mode, what to think about it?
How to upgrade the kernel from 9.2 sources without the 9.1 base system (it breaks, CC header problem)?
How would you proceed?
Yes i did follow these instructions (http://freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html) but as explained, it failed to boot because of an irq16 storm ; there was a problem in the usb support then. Here is the result:
vmstat -i
interrupt total rate
irq1: atkbd0 9 0
irq16: xhci0 ehci0 49440997 716
irq23: ehci1 240726 3
cpu0:timer 10114125 146
irq264: re0 3166270 45
irq265: ahci0 2493196 36
cpu1:timer 4722048 68
cpu6:timer 4767453 69
cpu3:timer 5537583 80
cpu7:timer 5928230 85
cpu2:timer 6624744 96
cpu4:timer 4985019 72
cpu5:timer 5463323 79
Total 103483723 1499
This post from an old thread confirms my suspicion that there no such option because it would not be useful:
> so, how can I make that there is no single user mode?
You need to fix
the problem that's causing it to go into single user mode. For that
you need access to the box (..) Until
you can see where startup is failing you don't know what needs fixing.
David
This assumes that the system only goes down into single user mode if some problem exists (corrupt file system, hardware trouble etc). Asking such to not happen is not possible mostly.
You might modify the system behaviour, after all you can modify it from source, e.g. here one might replace the single-user state single_user with runcom:
init.c:383
But then it is still a matter of luck, if the resulting system is usable or not.
Situation solved (was not easy) by booting on a precompiled kernel of 9.2-RELEASE with the needed kernel options. After a boot failure, in fact it's more because of hard drive file system problem, we managed to boot on this bloody kernel thru IP-KVM access.
So it's possible to keep using a GENERIC kernel and to avoid the firewall to block you right away because you don't have an hand (physically speaking) on the machine and do all that remotely.
The solution is to add these in /boot/loader.conf
net.inet.ip.fw.default_to_accept="1"
ipfw_load="YES"
and in /etc/rc.conf
quota_enable="YES"
No need to compile a new kernel for quota support either, i always thought it was the only way, good thing i was wrong.
First off, sorry for my english, it is not very good.
I have a Toshiba satellite c885d running windows 8.1. I have a lexar 4 gigabyte usb flashdrive. It says on the back: LJDS50-4GB. I used Linuxlive usb creator and backtrack 5 r3 gnome 32 bit. I downloaded the ISO from backtrack-linux.org.
When I put my usb into my computer, hold f12, and power it on, it takes me to the boot menu, where it gives me 4 options to boot from. after each one, there is a little bit of text. except after "usb" is blank. and then at the bottom is two more options, one taking you to the menu that you can also access by pressing f2 durring startup.
If I hit enter when usb is selected, it takes me to a black screen that says two words (something like checking usb, but I forgot. I will put in an edit that will contain a picture and the exact text.) then after 2 seconds, it says failed, and then launches windows. PLEASE PLEASE PLEASE help me out. I tried researching a solution to the problem, none of which worked. I have successfully run backtrack from the VM thingy that linuxlive has with all of the usb stuff, and It works fine, but it is really slow, as I have too many windows processes running at the same time. If anyone can diagnose me with a problem, awesome. If you can give me a solution, stupendous.
edit: it says "checking media" and then "failed"
images:
Ok, after some discussion in question comments I suspect that the problem is in your install image. If you can't see GRUB menu then you are unable to enter bootloader on your USB drive. It might be several things causing your problem with common denominator - UEFI:
You have written your install image incorrectly and UEFI is not recognizing it.
You have written your install image correctly, but that image is not capable to run on UEFI - see discussion here.
Anyway 100% way to make Backtrack like most of current Linux distros to work on UEFI is to turn UEFI to legacy mode (BIOS), though you have to unninstall Windows 8 ;-)
I would not give lot of hopes to that because Backtrack 5 is based on Ubuntu 10.04 which is way too old - earliest Ubuntu supporting UEFI is 12.04.
I can recommend a few things that might help:
Erase your usb flash drive and write Backtrack image to it again, but with UnetBootIn. There is an official tutorial for that.
Do not try to install Backtrack 5 if don't know what GRUB is. You can install latest Ubuntu that can run on UEFI with SecureBoot (not sure it's easy) and enjoy all of the tools from Backtrack repositories.
Good Luck and have a lot of fun!
I figured it out, just had to follow the tutorial from this page: https://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-windows-8-64-bit-system-uefi-supported
I recently installed Linux Mint Debian Edition - it was installed into a logical partition (formatted to ext4) under a 40 GB extended partition that was previously used as a backup/recovery disk in Windows 7.
It works quite well - the only problem is when I boot to Windows, then next time, Linux won't boot. I then need to use a recovery distro and run fsck.ext4 which detects some problems with group descriptors, fixes them and it's all good again.
My feeling is that Windows tries to mount (and fix / defrag / whatever) that partition which messes it up - I suspect that, because 1) it only happens after I boot to Windows, 2) Windows still displays the old recovery/backup disk D: (although you cannot access it and it doesn't show a free/total space etc.).
Any idea how to fix it?
Just a shot in the dark, it could possibly be the listed partition type.
Check the disk with your favorite partition table editor (fdisk, cfdisk, parted, whatever), and check to see if your linux partitions are listed as Windows ones or if they are correctly listed as Linux. If they are listed wrong, you should safely be able to change this, and it could stop Windows from harassing you.