Eldritch Horror
New Member
Hello everybody!
Since it might be seen as a little rude, if I'd just stumble onto this platform with nothing but a technical problem, I thought, that it might be appropriate to give a little backstory, what lead me here:
First of all I have to admit, that I am not at all well-versed, when it comes to Linux. Shame on me! I am mainly using Linux Mint on my Netbook, because that device has VEEERY little disk space. And the countless updates of the pre-installed Windows OS have slowly but surely littered the hard drive so full, that there was barely 1 GB left for me to work with. With Linux Mint I've had 20 GB free and it runs a lot smoother. (I've even thought about getting Knoppix instead of Mint, but that's a different Story.)
Unfortunately yesterday I totally messed up by trying to correct the time and date ... It would be too embarrassing to go into detail, what went wrong there. Suffice to say: The Linux OS has been destroyed and I need to reinstall it using a USB-Stick, that I've made bootable with UNetbootin. (Luckily I didn't have any important data on the device, that might get lost now due to my foolishness. I just want to get my sweet little netbook to work again.)
The problem now is, that the damn thing refused to let me boot from that stick, even though I set the USB-port to the very first position of the boot order in the BIOS. No matter, what I do, I always end up in the grub menu. So, I need to manually boot from there, which should not be too difficult - or so I thought.
Using "ls" showed me, that my netbook recognizes the USB-stick as (hd0,msdos1). I've verified that through:
ls (hd0,msdos1)
which gave me the UUID of the stick: 349B-50B3. I then proceeded like this:
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --set=root 349B-50B3
chainloader /EFI/BOOT/bootx64.efi
boot
(Side-note: The File-Names of "EFI" and "BOOT" are indeed capitalized like that.)
Anyways... All of that only resulted in an error-message shortly being shown on screen, that read:
Failed to find fs: Unsupported
Failed to load image \EFI\BOOT\bootx64.efi: Unsupported start_image() returned Unsupported
And that's pretty much, where I give u, because I have no idea, what this means or how I could proceed. I'd be very grateful, if someone could help me getting my netbook to work again.
Greetings
A.
Since it might be seen as a little rude, if I'd just stumble onto this platform with nothing but a technical problem, I thought, that it might be appropriate to give a little backstory, what lead me here:
First of all I have to admit, that I am not at all well-versed, when it comes to Linux. Shame on me! I am mainly using Linux Mint on my Netbook, because that device has VEEERY little disk space. And the countless updates of the pre-installed Windows OS have slowly but surely littered the hard drive so full, that there was barely 1 GB left for me to work with. With Linux Mint I've had 20 GB free and it runs a lot smoother. (I've even thought about getting Knoppix instead of Mint, but that's a different Story.)
Unfortunately yesterday I totally messed up by trying to correct the time and date ... It would be too embarrassing to go into detail, what went wrong there. Suffice to say: The Linux OS has been destroyed and I need to reinstall it using a USB-Stick, that I've made bootable with UNetbootin. (Luckily I didn't have any important data on the device, that might get lost now due to my foolishness. I just want to get my sweet little netbook to work again.)
The problem now is, that the damn thing refused to let me boot from that stick, even though I set the USB-port to the very first position of the boot order in the BIOS. No matter, what I do, I always end up in the grub menu. So, I need to manually boot from there, which should not be too difficult - or so I thought.
Using "ls" showed me, that my netbook recognizes the USB-stick as (hd0,msdos1). I've verified that through:
ls (hd0,msdos1)
which gave me the UUID of the stick: 349B-50B3. I then proceeded like this:
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --set=root 349B-50B3
chainloader /EFI/BOOT/bootx64.efi
boot
(Side-note: The File-Names of "EFI" and "BOOT" are indeed capitalized like that.)
Anyways... All of that only resulted in an error-message shortly being shown on screen, that read:
Failed to find fs: Unsupported
Failed to load image \EFI\BOOT\bootx64.efi: Unsupported start_image() returned Unsupported
And that's pretty much, where I give u, because I have no idea, what this means or how I could proceed. I'd be very grateful, if someone could help me getting my netbook to work again.
Greetings
A.
Last edited: