Unetbootin no mountable file systems12/21/2023 The 40 GB hard drive even thinks it only has a 143.2MB capacity with 0 KB free. I used dd to copy the entire disk image to the drive, and it acknowledges itself to be a Live CD. I changed the device within the nf file to ultra0: as it is for that drive. Within the /boot/nf file, the root is by default: root=/dev/ram0. The shell won't really help me, if I try: dev/hda (the only thing I can find in /dev that looks like the second internal harddrive I am booting from), I only get the nice warning No mountable filesystems!. Then it can't find /newroot in /etc/SOMETHING (I can't remember). Q to skip doesn't work, but it prints a nice warning > Skipping. It then gives me the options: shell to get into a shell, q to skip, enter to try the same again. I have reached the point where I can boot the Live CD (I have no functional CD Drive, so it is from a spare Hard Drive), but after the kernel is loaded, I get a message "No root found at /dev/hda. It would be great if anyone could help.I am attempting to install Gentoo on my PowerPC Mac. This raised doubts in my mind, like "Is it considered bad practise to use Unetbootin?" I last used Unbootin several years ago so I don't know if it's considered a bad idea to use it nowadays. So, what went wrong? Is it something dumb like Linux Mint being incompatible with my AMD processor? Or should I try to install 19.0 instead of 19.1? Maybe try Debian? Interestingly, while I was searching for Unetbootin one of the autocomplete results was "unetbootin alternative". exe) to uninstall my virtual media, and then I wrote this post. My windows installation wasn't affected though, so I started it back up (It loaded suspiciously quickly, but seems to have forgotten to start up the audio service), ran Unetbootin (the. I gave Unetbootin another go, and got the same result. Interestingly there was an option to hit enter to go back to the media selection menu, and I did that with no problems. Perhaps Windows's logic was that if windows didn't start then it had failed to start, but I will not discuss amusing coincidences here. A recent hardware or software change might be the cause." I picked "Unetbootin" from the select media screen and. After waiting for Windows to start so I could shut it back down, I made sure my laptop was plugged in this time and started my computer again. I plugged it back in before it could shut down though (The battery on my laptop is a bit weird, it always thinks it's "01 min to full charge"), but by this time Windows decided that it would just boot up Windows 10. When I plugged my laptop in, I turned it on, but the power cable fell out and the screen went black on the "select media" screen. My laptop's battery was low so I decided to shut down my computer until I could get to a power source. I waited for it to finish, and it did so with no errors. But this isn't r/choosemydistro, so I'll describe the problem.Īfter downloading the latest ISO of Linux Mint MATE 19.1 (Performance is one of my main aims) I used Unetbootin to create the "virtual" installation media on drive /C. I decided on Linux Mint because it seems to be fast and easy to use, which is important as I don't plan to mess around in the command line for anything other than apt-get-ing programs, and plan to use my laptop for mostly just word processing. My laptop used to run Windows 8 but I upgraded it to windows 10. I previously used Unetbootin to install Ubuntu onto an netbook (But never learned the command line) so I'm not a total noob. I don't have a USB stick bigger than 1 GB so I decided that I'd use Unetbootin to install it. I'm a Windows 10 user with a 64-Bit AMD E1-6010 (1.35GHz) and 4GB of RAM looking for something a bit faster on my laptop so I looked to dual-boot Linux Mint with plans to possibly single-boot it.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |