make linux machine grub bootable using bootable disk [closed] - linux

Closed. This question is not about programming or software development. 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 3 months ago.
Improve this question
I am not familiar to grub, and very less to linux.
What i currently have is the recovered linux machine disk.
Which has grub bootable source machine, but for booting on other platform (hypervisor/cloud)
My team used an extlinux to make it bootable by overwriting its boot code and make that machine bootable on other platform like cloud/hypervisor.
Did something like in this link
I want to make that machine grub bootable so i tried and came up with something below:
Created 1 gb disk.
installed grub using command on fat32 partition using below link
Content of grub.cfg
menuentry 'usbboot ubuntu' {
set root (hd0,1)
linux (hd1,3)/boot/vmlinuz.efi root=/dev/sdb3
initrd (hd1,3)/boot/initrd.lz
}
After that i created vm. Attached 1GB disk first then recovered disk second.
please help me to resolve issue

I was able to solve the issue, Issue is their was no such device like /dev/sdb3,It may be due to hypervisor type. So i was trying mount command in BusyBox and i found it their as /dev/vdb3.

Related

Parallels error: "Image BSS overlaps adjacent EFI memory region" [closed]

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 11 months ago.
Improve this question
I'm using parallels an an m1 macbook pro and the virtualization of ubuntu 20.04 worked perfectly fine until today. I can't launch it and it tells me that "Image BSS overlaps adjacent EFI memory region".
Does someone know how to fix it ?
I also can't create a new virtual machine since it prints the same error when I try to launch the new one.
Booting into an older version of the Kernel allowed me to safely access the VM after this happened to me. Although I also was running out of disk and needed to increase the amount of disk space allocated to the virtual machine.
I believe the latest version of the Ubuntu 20.04 kernel may not work on Parallels for now. Specifically linux-image-5.13.0-35-generic gave me trouble and booting into linux-image-5.13.0-30-generic worked fine.
The steps I took were
Attempt to boot into VM. It should hang at Parallels error: "Image BSS overlaps adjacent EFI memory region"
Go to Actions > Stop
Attempt to boot into the VM once again, at this point it should allow you to select Advanced options for Ubuntu. Select this.
In this screen select an older kernel version to boot into. I didn't have to boot into Recovery Mode.
Uninstall the breaking kernel. I just did sudo apt-get purge linux-image-5.13.0-35-generic.
It should be noted that I had older kernel versions available. If you've also deleted older kernel version preemptively, then I'm not sure what can be done.

Windows 10 Boot Linux without BIOS menu or USB stick [closed]

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 6 years ago.
Improve this question
I have Linux both command line linux, and Ubuntu, but my computer is Windows 10 based. Also the hardware is not what it used to be. I.e... No working USB port, No DVD slot (But I do have a Micro SD slot if I can boot it from there) but I was wondering if I can install and boot linux directly in Windows? And I was wondering if Windows 10 would be active still, and if I an switch in between the two? I have never worked with Linux or booted it. How can I boot linux in windows without anything but a micro sd card?
you can not boot linux on windows. you can make Bootable USB and use live linux or use virtual machine like VMWare
Use a virtual machine. They allow you to run multiple operating systems at once, and as long as your machine supports virtualization, they work perfectly for the situation you are describing.
My preferred virtualization software include:
VMWare
and
VirtualBox
From there, download and install the Linux .iso file of your choice to be able to open and switch between operating systems at will. Also, make sure to enable virtualization in your BIOS settings.

VirtualBox doesn't have enough space left on Device [closed]

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 6 years ago.
Improve this question
I have a problem on Oracle VirtualBox : it regularly tells me that I don't have enough space left on device, when updating or installing.
In the VB settings, I have set my Motherboard base memory at 3370MB.
My HD IDE Primary Master has an actual size of 2MB and virtual size of 20GB, and my Optical Drive IDE Secondary Master is 1,46GB.
The Linux distribution is 1.534G.
When I run df -h in the VB, it tells me that the full filesystems are :
/dev/sr0, 1.5G, mounted on /cdrom
/dev/loop0, 1.5G, mounted on /rofs
/cow, 1.7G and 72k available, mounted on /
I am running it from a Windows 7, and the distribution I use inside the box is the latest Linux Mint.
I don't know if this is the relevant information you need, please ask me if you need anything else.
Thank you in advance for your help
Ok, I found the solution. The problem is that if you don't install Mint inside of the virtual machine, the only space available is your memory, so it is used as drive space. The solution was to first boot it via the live CD version, then install it inside of the virtual machine, and then reboot it using the version of Mint you just installed on the virtual hard disk you have in the virtual machine.

VirtualBox. Fedora 11 freezes when boot [closed]

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 have Fedora 11 installed on VirtualBox. By accident some files in /var directory were damaged or removed(I don't know what exactly). Now when trying to run Fedora, it goes untill choosing the user and freezes. No reaction at mouse and keyboard clicks. Does anyone have any suppositions how to run it, or at least how to retrieve files from virtual machine? I booted it to the terminal where I updated all what is possible - gnome, etc...But still no result.
It's impossible to know what happened without knowing what got removed. However, a great way to get your files out is using scp. Good examples for this can be found here.
Alternatively, if you've installed the Virtualbox Guest Additions you can use a USB drive to retrieve your files. There's a pretty good tutorial on how to get your USB drive working on VBox here.
If you want my best guess as to what's wrong, something in your /var relating to your GUI got removed, as from what I understand you can still boot to your command line. My suggestion would be to get what you need off the machine using the above tools and get a fresh install.

Copy pre-configured OS image to slave local drive with PXE [closed]

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
I have a handful of servers and would like to configure them as close as possible to a standard HPC cluster, currently focusing on automated node provisioning. My requirements for this are:
All nodes are identical, so I'd like to use a pre-configured install I have set up on one of the nodes
I have created an image of this install, which I would like to use to boot all nodes (this is a copy of the filesystem on the configured node)
The software image should be installed on the local disk of each node (not mounted over NFS)
I've been playing around with PXE and managed load Ubuntu 14.04 on a slave node, with the software image provided through NFS.
Is it possible to tell PXE to copy the contents of the NFS-mounted directory to a local disk partition and then make it boot/run linux from there?
Is it possible to tell PXE to copy the contents of the NFS-mounted
directory to a local disk partition and then make it boot/run linux
from there?
PXE is just a mechanism for booting a system over the network. Since you have complete control over what you feed your systems via PXE, you can do pretty much anything you want.
Four your scenario, you would want to boot into some sort of minimal Linux environment that is able to:
Mount NFS filesystems
Copy files
Configure the bootloader locally
That's a pretty short shell script. Once it completes, you would reboot the system, which ideally would be configured to prefer booting from the local disk (so that once you have configured the local boot loader, the system will not attempt to PXE boot during subsequent boots).
You may want to take a look at the Clonzezilla project, which does some of what you want.

Resources