[TerraMaster F2-220]

On 11/18/2020 at 3:06 AM, autumnhasfall3n said:

Hi, I've been troubleshooting for a while now and i've come to a dead end.

So i gave up like 2 years ago, but i had a long weekend so i took another crack at moving from 5.1.7 to 6.2.3

and i did it!!!!

On 11/29/2020 at 7:39 PM, rcached said:

So, a couple of suggestions:

1. Double check you entered the correct MAC address in your GRUB file.
2. If you're using a previously assigned IP address for the old install and you think the new install is using the same IP, make sure you add the port number when you're connecting via the browser; example: http//:youripaddresshere:5000
3. If you have some sort of connected client status page on your router control panel, check there for any active possible IP addresses by process of elimination of known clients
4. Try using an IP/port scanner instead of arp.  Use same process of elimination as mentioned above.
5. There have been some reports on this forum and others that sometimes a router or network device reboot is required to be able to connect to a new Xpenology install for the first time.  YMMV, but that's a simple thing to try at least.
6. Instead of using DHCP, assign a static IP for the MAC address of the 220 at your router/networking device level.  This is how I personally avoid situations like this!

This was actually really helpful. My bastard of a router at the time still decided to hide the thing, but hey i learned something about arp thats neat. Ended up using some network scanning utility, all worked out great.

On 11/3/2021 at 11:57 PM, Hipsi said:

Did you end up getting to the bottom of this?  I'm in exactly the same situation here however I'm installing from scratch rather than upgrading.  Once it's done the 10 minute DSM install, I can no longer see it on the network.  If I start again from the bootloader menu when I get to the Synology screen it detects a previous install and thinks I've moved the drive from another NAS. 

 

I note that (once it's finished apparently installing) when I boot with the USB removed, I just get "GRUB" on the screen.  Is that right or is that indicative of some other issue?

for the record you and i were having different problems. What happened to you was you accidentally downloaded the dsm update from the internet instead of manually installing it (in your defence i did this while trying to update). The internet versions are now beyond the bootloader, so if this does happen you can either wipe your storage disks, reset your usb and try again. OR  follow this handy guide.

 

Also for the people asking about 2.3.4, it doesnt work.

 

 

[how to undo a unfinished update 6.2.3 to 6.2.4 (no boot after 1st step of update)]

If you happen to be trying to do this now using a recent version of system rescue cd. The Update files are all marked as hidden, you will only be able to see them with ls -a and more importantly deleting them requires a slightly different command

rm -rf /mnt/SynoUpgradePackages
becomes 
rm -rf /mnt/.SynoUpgradePackages

they all get little dots. no idea why this is but hopefully i can save someone the half an hour it took me to figure out where the hell they were hiding.

[TerraMaster F2-220]

Hi, I've been troubleshooting for a while now and i've come to a dead end.

I have had 6.1.7 running on an f2-220 for a good few years now, and figured i'd make the effort to update it to 6.2.x or whatever is newest and compatible.

I was running a 1.02b loader i think.

I have done a clean install following the processes described by both delavegagr and rcached

using the 1.03b bios and the appropriate extra.lzma and the files from the .pat using the vid+pid+nic from my previous working config as well as both a fresh and reused serial

i have reconfigured the bios to boot in legacy mode, as well as setting the boot os to "windows 7"

From the screen it appears to be booting into the loader just fine, yet despite my best efforts i still cant detect my server on the network either through synology assistant, the web page, or arp -a and its ip.

 

If there is something completely obvious I have overlooked pointing it out would be appreciated,

thanks and regards