No boot device found after installing SSD on Travelmate B117M

Hi from a Newbie

I'm trying to resurrect my wife's beloved Travelmate B117M after the HDD failed. Simples - I thought - fit a nice new 240Gb SSD and reload Linux Mint - as it was before, no dual boot, just Mint, or Ubuntu over the last 6 years.

Wrong!

Everything works as it should for the install, Secure Boot disabled, F12 enabled, in goes Mint, restart - and nothing beyond the Acer splash screen other than 'NO BOOT DEVICE' (unless I put the USB loader drive back in)

The SSD is on HDD1 (not HDD0???) and even if I reset the boot order to make it the first, nothing.

This the output of 'sudo efibootmgr'

which, I hasten to add, I dug out on the advice of 'another website' whilst trying to work out what's wrong, not because I know what I'm doing.

The BIOS is an Insyde H2O, Rev 5, updated to 1.7 (probably the original?)

Anyone any idea of a way forward, please

[Edited the thread to add the Title ]

Accepted answers

All comments

Willumn

Doh! Looks like my first effort got posted in the wrong part of the forum. Can someone move it for me, please - or should I just re-post?

StevenGen

https://community.acer.com/en/discussion/comment/1175270#Comment_1175270

There are allot of guides on how to install Linux on a new SSD drive so follow those as you must have done somthing wrong for the laptop not to boot into the OS, also I advise you to choose a more "standard" version of Linux like Ubuntu instead of Mint. Remember that all current distributions of Linux can be installed in UEFi mode on this laptop.

Make sure that your Travelmate B117-M is in good order and there are no other issues with the laptops hardware, as for starters having an early bios like the version 1.07 (not 1.7 as there is no such bios for this laptop) is a problem as this laptop has had 6 bios updates from the 1.07 and the last bios version is the version 1.24. Make sure that you prepare the laptop properly for a new SSD boot drive and that everything functions on this laprop, as by what you have said above, there is definitely some issues with this laptop.

Leostat

One of the admins is able to move if you really want :D although it doesn't matter tooooo much

This has happened on a a few Acer models, where for some reason grub doesn't write the efi boot stuff properly, no clue why!

It looks like 0005 does have the boot mgr on though, so it may be as easy as setting it with

sudo efibootmgr -o 0005,0001,2001,2002,2003

Did you also try to install Ubuntu? I'm confused on why there is a boot entry for that, and 7nsure if it's that mint just hasn't changed stuff

Willumn

Hi StevenGen and thanks for the response.

Just to complete the picture: It's a Travelmate B117-M-C9UR

I've read the equivalent of War and Peace regarding resolving problems loading Mint - and followed the diagnostics. I've also tried to load Ubuntu with the exact same result.

- and you're quite right, my typo, it's 1.07, not 1.7. I would happily upgrade the BIOS but the only upgrade I saw was one that seemed to require Windows of some description to function as the loading method.

I don't have Windows.

Both OSs (Mint and Ubuntu) have been on there in the past and functioning properly with the old, now deceased, mechanical HDD.

Not wishing to encourage answers, I didn't mention my suspicions that the BIOS is the problem - but you seem to hint that it may well be so. I have even dug around in the BIOS EFI file permissions and this is what I found:

under 'Select EFI file as trusted for execution' it only shows HDD1 (the SSD) and under that:

<EFI>

<.>

<..>

<BOOT>

Under ubuntu (which is what I understand Mint shows as)

<.>

<..>

grubx64.efi

shimx64.efi

mmx64.efi

From what I read, the hierarchy down to 'shimx64.efi' is the right file to see to get it trusted and loading?

The BIOS looks as if it will allow me to add detail to that area. Is there something else that should be there?

Will

ps to save my blushes, could one of the Moderators bump this to the correct area of the Forum, please?

Willumn

https://community.acer.com/en/discussion/comment/1175296#Comment_1175296

Hi Leostat.

Thanks for the response, apologies, yours came in after I had pressed 'POST COMMENT' to reply to StevenGen.

Responding to your comments in reverse order:

From my understanding, Mint reports as Ubuntu in some instances. I believed it is largely derived from Ubuntu.

As a (slightly fearful) novice, how should I go about editing the boot order to the sequence you described above?

nb: to quote a message I saw recently 'elsewhere': "Please tell me how to do it as if you were trying to teach a 3rd-Grader" 🤔

Leostat

Its odd that it worked before and not now with the SSD . And you are right that you need windows to update the BIOS, it may be worth chucking windows on there just to update it, and see if that allows it to boot . And it may also fix the boot issue if its some weird boot bug!

Also there arnt any rules about cross linking other forums or anything :) so dont worry about anything like that!

Could we grab the full output of efibootmgr -v?

Willumn

This is what I get:

-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-

mint@mint:~$ efibootmgr -v

BootCurrent: 0001

Timeout: 0 seconds

BootOrder: 2001,2002,2003

Boot0000* Unknown Device: HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC

Boot0001* USB HDD: TOSHIBA TransMemory PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,7d7473ea-fce2-4e11-b099-a49d0a25ce4c,0x48dd90,0x2130)RC

Boot0002* Unknown Device: FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)RC...0

Boot0003* Unknown Device: FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)RC...0

Boot0004* ubuntu HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)

Boot0005* Linux Mint HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\efi\ubuntu\grubx64.efi)

Boot2001* EFI USB Device RC

Boot2002* EFI DVD/CDROM RC

Boot2003* EFI Network RC

mint@mint:~$

-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-

If there's a better way to post the output other than 'Copy/Paste', I'm all ears, noting the fact that I'm doing this running Mint live on the Travelmate

Will

Leostat

It looks like acer have removed the {pre} tag so nope thats the best way aha

Thanks for that, it does just look like its not setting the boot order so this may make it work

sudo efibootmgr -o 0005,0001,2001,2002,2003

Given there is an ubuntu book thing there and three weird ones ( boot 0000, 0002,0003) though I would say re install and whipe the drive fully, after that, get the boot number and set it using efibootmgr

Willumn

Thanks, Leostat.

First I'll apologise for the numpty questions - and remembering the - "Please tell me how to do it as if you were trying to teach a 3rd-Grader" quote:

I assume I open a terminal and enter the command:

sudo efibootmgr -o 0005,0001,2001,2002,2003

.... press return and leave it to come back to the command prompt, then shut down and restart to see what happens.

If that fails to cure it, do I then try a fresh install of Mint, allowing it to format and install, removing any other items on the drive (Erase disc and install Linux Mint)?

After I do that, do I still need to use Terminal to enter the command exactly as you suggest, or something different?

Will

billsey

Yes, you are trying to change that BootCurrent: 0001 line to point at the Mint EFI section. BTW Mint is a skin on Ubuntu, not a separate distribution.

Willumn

Thanks, billsey.

I'll try it and post the results - but it will be in the morning.

Past my bedtime. 😊

Willumn

It's morning, still dark o'clock and I tried the command you gave me. This is the output of 'efibootmgr -v' which I've taken and posted before restarting the computer:

Imint@mint:~$ efibootmgr -v

BootCurrent: 0001

Timeout: 0 seconds

BootOrder: 0005,0001,2001,2002,2003

Boot0000* Unknown Device: HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC

Boot0001* USB HDD: TOSHIBA TransMemory PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,7d7473ea-fce2-4e11-b099-a49d0a25ce4c,0x48dd90,0x2130)RC

Boot0002* Unknown Device: FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)RC...0

Boot0003* Unknown Device: FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)RC...0

Boot0004* ubuntu HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)

Boot0005* Linux Mint HD(1,GPT,1061a717-6906-47df-9660-744eff00e943,0x800,0x100000)/File(\efi\ubuntu\grubx64.efi)

Boot2001* EFI USB Device RC

Boot2002* EFI DVD/CDROM RC

mint@mint:~$

Will

Willumn

Didn't make any difference, sadly.

I have booted from the Installer again and formatted the SSD to GPT, then reinstalled Mint. After reinstalling, I continued the session as 'Test' and this a screenshot from 'Disks' after the installation.

This is what GParted shows:

and this is the output of the Terminal:

I will try another restart and see what happens, then report.

Thank you all for your patience and anything you can come up with will be much appreciated.

Will

billsey

OK, go into the BIOS to the Security tab and use the Select an UEFI file as trusted for executing option to add the EFI file in that first partition. Navigate to the EFI/ubuntu folder and select shimx64.efi. Turn Secure Boot back on and save and exit. That should allow things to proceed normally.

Willumn

Thanks, billsey.

Before I got your reply - and whilst no one was looking ..............

I used the 'Disc Sanitizer' in the BIOS to completely wipe the SSD, swapped it to Legacy mode and reloaded Mint, choosing 'Something Else' and partitioned the SSD with /, /HOME and Swap Area. I really didn't think I had anything to lose and I've done it so often I can almost install it with my eyes shut.

Anyway, it whinged about not having an EFI partition (in Legacy mode?) and said the installation may fail but I ignored it but away it went and completed the installation.

I restarted it - and **** nearly fell off my chair when it booted straight into Mint 😮

I know it hasn't necessarily resolved the issues but if you don't see any problems laying in wait for me, I'll leave well alone for now. During the boot sequence it flashes up a couple of notices too quickly to read and oddly the first line of text to appear in the boot process is blurred and corrupted.

As a backup I've done a cut and paste on the instructions you gave, so if it plays silly Bs in Legacy mode I can swap it back to UEFI and still refer back to what I need to do, even if I have no internet access.

This is how the SSD looks now

Do you think the problem stems from the BIOS, or from the SSD - or perhaps a simple incompatibility?

Second: is it worth updating the BIOS and is it possible without Windows installed somewhere?

Part of the reason for asking the first question is that early on I contacted the SSD supplier and asked if they knew of a solution. They suggested formatting the SSD to EXFAT, or NTFS and trying again - which I did to no avail. They then offered to inspect the SSD if I sent it back but the problem seems to have been resolved without wasting postage on that exercise, so I have kept it and hope all behaves itself from here on in.

Will

billsey

The biggest issue with using legacy mode is that it leaves you wide open to rootkit viruses. At least you have ti working and there should be reasonably good detection tools for Linux... I wouldn't bother with a BIOS update unless you see something in the notes that means it's got security fixes, and you likely do have to boot into Windows to install them.

Quick Links

Top Members

Weekly

Jack22 30

Puraw 20

Kno63 15

marceljoyce 12

Adi3003 10

Swift Series Intel^® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel^® Evo™