So I booted Parrot OS from an external drive (SanDisk 3.2Gen1) and I gave it 32GB of persistence (I don't know if it really does anything to help). Now I am trying to partition the drive. Everything goes well untill i try to install it to the drive. It just pops this error and I don't know what to do next.
Error image
I have tried to do it with the GParted program but that doesn't work either.
Looks like you are trying to partition the drive the live system runs on?
If so, try booting from another drive than the one you'd like to partition.
Related
guys I have an issue with Linux
I wanna install Linux on flash disk like internal disk
actually I wanna install it with presentation space
I did it but it limited with 4 gig space.
I wanna use all space of flash disk and do my works on it like an internal partition
like a really OS
In the normal installation process, you will be asked to select the partition on which you would like to install Linux.
The option for bootable USB will be visible with a warning sign. In some flavours, it may be hidden however, you can still install it. Simply click on the USB drive partition and Linux can be installed on it.
Make sure you have at least 16GB USB Flash drive to run your Linux smoothly.
I have been trying to install macOS Catalina on virtual box foloowing this tutorial:
https://techsprobe.com/install-macos-catalina-virtualbox-windows/
When getting to the step of having to actually install catalina the virtual machine boots into an EFI shell
The same person who wrote the tutorial wrote a supposed fix:
https://techsprobe.com/how-to-fix-efi-internal-shell-on-macos-catalina-on-virtualbox/
The fix adds an ISO file which contains parts of an apple file system which is loaded via a startup.nsh file which you create in the shell.
The fix itself however does not work either. Now I have no idea about how EFI shells work or how "fs#" relates to loading files from the apfs ISO. Here is the startup.nsh file as well as the error associated with trying to run it:
Now like I said I dont have much of an idea of how EFI works or whats going on here in general, so feel free to educate me.
I was able to fix the UEFI problems as follows (credit to techrechard website):
At UEFI prompt: Type exit
You’ll be brought into an EFI text-mode GUI.
Select Boot Maintenance Manager and click.
Select Boot From File and click
You should see two entries in a list (they are cryptic looking PCI bus paths).
The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. The second PCI path is probably to the recovery partition, the one you need to boot from. If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. If the recovery partition isn’t present and valid, these instructions won’t work.
Click the 2nd entry, you should see (and then click):
macOS Install Data
Then click:
Locked Files
Then (if present), click
Boot Files
And finally click:
boot.efi
Installation will continue, or you will boot into the OS or get the Recovery Utilities menu (where macOS can be reinstalled from or Disk Utilities run). The ambiguity of that last statement is I did that awhile before writing this comment and I don’t recall what I booted into first, only that it worked and was not hard to figure out what to do at that point. If you have a recovery partition, to boot directly into the Recovery Mode turn on the Mac and immediately press and hold (⌘)-R
Apparently if you follow this link how to install catalina, you will get an error like the one you got (This is probably due tu the way virtualbox reads disks--> uefi or legacy). Mine was :‘FSL: \ system/library/coreservices \ boot EFI’ is not recognized as an internal or external command, operable program, or script file?. On another forum I found this command:
> Install.nsh
If you write it in the command line of your virtualbox MAC environment it should proceed. It worked fine when I typed it.
Long story short, windows 10 is utterly broken on my laptop after it automatically installed some updates. It's now stuck in a loop which always ends up saying "Undoing changes made to your computer"
I can't get into the BIOS.
I can't get into the Windows Recovery Environment.
Been talking to MS support for far too long so far, so I'm wondering if it's possible to add it as a secondary disk drive to another machine that does work, and manually remove any updates that were installed directly through the filesystem?
The only solution MS were willing to offer was to format the whole drive and re-install windows.
When I moved the HDD into a working windows 7 machine it actually prompted a chkdsk to run over the disk.
It found a whole load of orphaned files, not sure if that was really the cause, but after backing up as many files as I had access to, I put the drive back into the other machine and now it boots.
tl;dr, chkdsk fixed it.
I was stuck in this loop last night
machine configuration : Dell Inspiron
windows 10 (original)
What the one thing you can do is to use an application name Dell usb recovery tool. You will have to format you whole computer be it c:// or any other. You will need an extra hard drive to make a backup.
the process goes like this.
You will have to install the above application on other computer and open it and fill your service tag and make that pen drive bootable with that application.
Now plug in that pen drive to the laptop.
Go for troubleshoot.
Repair.
Install new original os.
It will ask for backup make a backup to other HDD.
Install and recover your backup.
I installed linux debian as a 2nd system and it works fine, however when I choose Windows in loader(lilo) to boot, it stops on a windows logo.
I tried to boot in safe mode, and it stops on classpnp.sys driver.
I'm not sure whether the problem is in classpnp or in some other driver which is failed to load after it.
I also tried to boot with bootlog (ntbtlog), however it is not created (I check C:\Windows).
It seems like smth is wrong with hard drive configuration with several partitions.
I've googled a lot of similiar issues with classpnp.sys, but none of the solutions helped:
-I tried to change bios SATA coniguration from IDE to AHCI,
-restore backup configuration files (SAM, DEFAULT, SECURITY etc).
If anyone knows what else can I do with this, please help.
This belongs on super user, but you need to press F8 and select safe mode. There you can fix your problems
I have both linux and windows installed on my pc. when I make some programs in lex and yacc (when working on linux)and store all the files in a folder ,they are corrupted If I use windows for some time. for example 3 days back after storing all the files( xyz.l , a.out ) I switched to windows for some other work after rebooting my pc. after 3 days when I again open that folder(while using linux) a.out was converted into an image and when I double clicked on it, an image opened. the image was same which I downloaded 2 days back while working on windows but I stored in some other folder. so does the memory space used for storage for linux and windows overlap? if not what could be the reasons? It has happened 2 times. and really I have to recode all my programs . I am not able to understand why?
It is not supposed to overlap.This sounds like a configuration problem , where windows and linux are configured to mount the same partition.
Check the file /etc/fstab (under linux) and find out whether this is true.You can try making files in various places and observe if they can be found on the other os.
I don't know how your partitioning looks like, but I guess that it is set up in a way that both OS have read/write access to all partitions, or at least windows has read/write access to the Linux partition.
Is your linux partition a FAT32 partition? You should set it to read only in windows, but I'm not sure how to do this.
Do you use hibernate on the windows side? Windows can get confused if data changes while it is asleep, and this might be the cause of the problems.