#Wont boot entering rescue mode
1099 messages · Page 2 of 2 (latest)
press Ctrl-L
make note of that path.
then put that path in second line.
plus the file name of dat file
@bronze raven i guess i have to wait until the copying progress is finsihed
yep
you could also rename the file to mint22.1-4GB.dat
and reference it accordingly
ready?
Well now both files are on the Ventoy partition should i hit "OK"?
yes, it does indeed
i guess it needed a vlink if putting on another partition.
so dont worry about vlink
now tick "autosel"
I do not know what a "v link " is
it's another tool in ventoy installer folder
u can make special links with it that ventoy can find iso's or persistence on any other device
interesting
and those vlinks get put in the lines u were editing.
but dont worry about it for now.
so where is the "autosel" button?
autosel makes the live boot with persistence, without u having to tell it to.
it does not show up on my current screen
as step 39 mentions
did u hit ok button? show it
u should see a new line and on left or right is tickbox
@rich patio
No i cant find it ):
ok, tanks, i found it
u can have multiple persistence files for same ISO, default should be 1
the value holds 1
ok step 40, 41
I do not understand the last step right, do i have to reboot and let my pc boot from the SSD or from the WD HDD?
reboot to external WD
alright
all normal default boot options.
when u get to the live desktop, change the wallpaper.
and right click desktop, and make any text file and save it there.
you may also connect to Wifi in it.
and do just sudo apt update once in terminal after connecting Wifi
then reboot again to this same drive. should have kept all change.
That screen popt up after booting
Yes
No
sigh
that drive is fucked.
you were SUPPOSED to SEE ventoy white screen on the WD external drive when u booted it.
just the same way like the other day with ventoy flash stick usb
Could it be the problem that I always also disconnect the power cable before I disconnect my drives?
idk
u should do a safe shutdown on computer always.
or do safe-eject, then it doesnt matter , usb plug or power plug
I do, I disconnect th power after it has shutdown safely
it could also just be the firmware on that drive doesnt let it be bootable
because this ventoy method should 100% work. just like it did on ur flash drive the other day
Can be at least it can be used to store some files and maybe let it run some programs
i mean, u can take this exact drive now, to modern computer and test
But if the firmware does not support the "booting process" why did it show up as a bootable drive on my Mainbord setting?
if it doesnt work there, then 100% for sure it's the drive, not the BIOS of ur old pc
And the other drives on that pc are safe?
yes
There are a couple ones in with some important data
ur not installing anything. ur just running this new ventoy WD .
which now has persistence too.
if it doesnt work, forget about that drive for booting anything forever.
u can boot the WD external hard drive as uefi. ventoy should support it
So I should boot as normal and ignore it for now?
well obviously make that exact device boot up
not the internal hdd
if it fails with same message, it's just no good. the firmware for WD GAME DRIVE is just not right for being bootable.
It just booted in windows from a other drive, maybe I failed to save the changes
instead of saving changes, just use the boot-menu key for that brand of computer
Well the WD drive has some files at least
i know it does. that's not the issue
Trie to boot again
Responsable
did it fail again on new pc?
Well i had to slide it in the first spot, I didn't knew that I had to do it
It still boots in windows
ok that means that external drive isn't bootable
you can do a "clear ventoy" like u did before and just delete all those files.
u can use ur ventoy flash usb for experimenting with linux mint 22.1 you can even vlink the dat file on ur SSD, and reference it in the plugson setup . eg: first make vlink, then copy/paste vlink file to the flash usb ventoy, and run the plugson thing again, and make new persistence
ABANDONED (Reason attached above)