Can't boot DragonOS_FocalX_R37.1.iso from USB (General UDrive)
Brought to you by:
cemaxecuter
Menu
▾
▴
Hi,
It says in the READ.ME that it won't boot from a DVD and to burn it to a thumb drive. I made a bootable image on an 8GB drive. It loads GRUB and spins for awhile, then gets to the LUBUNTU loading screen & the wheel spins until it fails with the console error message "No media on /dev/sr0." Of course there isn't media on /dev/sr0. There isn't a DVD in the drive. I burned the image on a USB drive. Looks like the image needs some tweaking for booting from a thumb drive.
Cheers,
Randy
Randy,
Burn the iso with ether to a thumb drive is your best bet, but also check the hash on your and make sure it’s good. There’s Rufus and some Linux capable tools, but etcher is one of the better ones.
If after those two things are completed and you still have an issue - I’d have to think more. But that’s generally what everyone does, no other tweaks needed unless there’s issues with Nvidia hardware and such.
Sent from Proton Mail for iOS
On Mon, Jan 13, 2025 at 7:15 PM, Randy Winchester <ranwinchester@users.sourceforge.net> wrote:
Hi,
I finally figured out what the problem was. I think it's pretty obscure. I have never seen anything like this, and Google didn't turn up much.
I did the SHA256 check on the download file and it was fine. I ended up doing multipe downloads and burning multiple copies on thumb drives, including one with Balena Etcher, and none of them would finish booting.
It seems that one of the difficult things about trying to figure out what went wrong with a thumb drive not booting is that there isn't a lot of information preserved. It starts to boot, it fails to boot, you never get a recovery prompt, and you shutdown and reboot the computer. There aren't any logs to look at.
When I was booting, everything would hang and I'd the get console message:
It finally occur ed to me that that might not be the actual error message. I removed "quiet splash" from the grub boot line, and I got an interesting bios message. I couldn't capture it, but it essentially said that would not allow the boot to't complete because the Windows EFI file indicated that Windows had not shut down cleanly. Then, the init: line above would repeat until I hit CRTL-c.
The solution was simple. It's a dual boot machine. I booted Windows, then shut it down. Then I powered on the computer and selected the Udrive and edited the grub command line again so that I could see what was happening. Everything booted fine.
This looks like a fun live drive to play with. I tried GQRX and I after I selected my dongle, I was tuning FM radio stations without and other configuration. I'm looking forward to check out all the rest of the great apps, and so happy I don't have to install every one of them.
Cheers!
Wow that’s a good catch, never once had that happen but now I wonder how many others may have experienced that when not being able to boot. Good find!!
Sent from Proton Mail for iOS
On Mon, Jan 20, 2025 at 11:00 PM, Randy Winchester <ranwinchester@users.sourceforge.net> wrote:
Its also a general good idea to use Ventoy on usb drives. To my experience that is adding a great compatibility layer and make it possible to boot images that did not start without Ventoy.
With Ventoy you can also use memdrive and other usefull additions without the need of the ISO-developer to have to implement that.