Recommended Posts

Hi all,

 

I just received a new F2-221 (with Hdmi), but the installation of XPEnology fails to complete, because the bios boot order is locked, the HDD is always the 1st priority, so after the initial setup it will boot into HDD ignoring the bootloader on the usb drive.

 

It is possible to boot from Usb, but is always necessary to go into the bios and select the one time boot option.


Wonder if anyone had this problem and if there is a way to unlock the boot order options on the Bios or install the bootloader to HDD (overcoming this problem).

I took some pictures from the bios.
 

I hope i am doing some noob stuff here, because if this situation does not have a fix, the newer Terramaster units cannot be hacked anymore!

 

20201021_182639.jpg

20201021_182717.jpg

20201021_182733.jpg

Link to post
Share on other sites
6 hours ago, IG-88 said:

does not seem to be a general problem

https://forum.terra-master.com/en/viewtopic.php?t=393

 

maybe try to rest bios to default settings

 

Thanks for your reply. 

I already did a bios reset multiple times (tried every option to reenable the boot order menu), but it remains locked. 

 

On a side note, the bios date is posterior to that post you mentioned, so the bios is different from those units for sure.

 

My unit is a newer model without any doubt. I will post some hardware pictures tomorrow, maybe someone who has a later model can compare, because I think there are some hardware changes too. I only have 1 internal USB port and the internal memory is running at 1600....

Link to post
Share on other sites
8 hours ago, Num3 said:

I only have 1 internal USB port and the internal memory is running at 1600....

 

in default mode the unit would need to be booted from that internal usb port, i guess i tried to use that port already when its the only one

a option would be to use exactly that usb flash drive/pcb that the manufacturer delivered, maybe they locked the usb boot to that vid/pid (synology seems to do that with its internal usb)

you could make a copy of the usb with Win32Diskimager (or a similar tool) and then write jun's loader to it (and match usb vid/pid in grub.cfg)

 

a more complicated alternative is to find the rigth usb flash drive and matching oem software to manipulate the usb like done in the factory, you could freely choose the usb vid/pid, i did this 2 years ago to make a usb with synology's vid/pid

you can use the forum search to find that - but be warned that can easily fry a flash drive and some of the sources for such tools have questionable reputations and might contain malware in worst case, also it can be difficult to find the right usb flash drive because when buying the controller used is usually not mentioned, it might set you back ~30 bugs to find the right one and get it working (not mentioning the time)

Link to post
Share on other sites

I have taken pictures of the guts of the F2-221 unit I got.

My board says it's a BOO-J3355-S1_V2.0, can anyone confirm with an older unit if the board is the same?

 

Btw, this board seems to be generic for the F2 and F4 models, the other 2Gb of onboard ram are just unpopulated :P

The SATA riser board is probably the same for the 4xx and 5xx models but with more sata ports on it.

 

20201023_070520.jpg

Edited by Num3
Link to post
Share on other sites
On 10/22/2020 at 12:33 PM, IG-88 said:

 

in default mode the unit would need to be booted from that internal usb port, i guess i tried to use that port already when its the only one

a option would be to use exactly that usb flash drive/pcb that the manufacturer delivered, maybe they locked the usb boot to that vid/pid (synology seems to do that with its internal usb)

you could make a copy of the usb with Win32Diskimager (or a similar tool) and then write jun's loader to it (and match usb vid/pid in grub.cfg)

 

a more complicated alternative is to find the rigth usb flash drive and matching oem software to manipulate the usb like done in the factory, you could freely choose the usb vid/pid, i did this 2 years ago to make a usb with synology's vid/pid

you can use the forum search to find that - but be warned that can easily fry a flash drive and some of the sources for such tools have questionable reputations and might contain malware in worst case, also it can be difficult to find the right usb flash drive because when buying the controller used is usually not mentioned, it might set you back ~30 bugs to find the right one and get it working (not mentioning the time)

 

Yeah, i tried the original USB with XPEnology on it, no cigar :(
I believe the Terramaster bootloader installs to HDD after the initial setup and probably checks if the USB pen is installed when running (or not)...

Fact is, my Bios has the boot order menu locked, so i cannot change it.

I already installed other OS's, but they all boot from HDD. XPEnology requires the pen to boot from and then launch the OS, so it does not work on this version of the hardware...

 

The only option i can see, is if XPEnology bootloader copies it self to a dedicated partition of the HDD to be able to boot and then load the OS from another partition. Leaving the original boot pen inside, so the security checks can be made.

Edited by Num3
Link to post
Share on other sites
1 hour ago, Num3 said:

Yeah, i tried the original USB with XPEnology on it, no cigar :(
I believe the Terramaster bootloader installs to HDD after the initial setup

 

yes but how does a system boot and is seen in network with blank disks

its either PXE from the nic or the usb, at least there must be a way to force the usb boot when nothing its installed on disk

 

 

Link to post
Share on other sites
  • 2 weeks later...

Came across this when trying to fix the same issue I was having with installing TrueNas.

After several changes the one that worked for me was to make the following change in BIOS:

Advanced>CSM Config>

Boot option Filter (UEFI & Legacy) <this is the default>

Storage = UEFI

Other PCI devices = UEFI

 

I then put my os drive in P0 then had the rest of my drives after that, but did did test this with TrueNas installed on a USB and had it in the internal header and it worked as well. 

 

I should  note that I have the F5-221, but BIOs version matches yours.

 

I hope this helps a little. 

 

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.