billat29

You want 6.2.3. v1.03b ds3615xs. Turn off c1e in the bios of the n36l

I will send you here: For N54L read N36L

And did you ever get to the root cause of your earlier disk problems? Error 13 is a very vague message which can be a problem preparing for, or writing the new system to disk. If you are having problems with the hardware, that might explain all this weird behaviour. If @flyride stops by, they might also have some thoughts.

What I can say is that 6.1.7 is the version that supports the widest range of hardware and that there isn't anything magical in 6.2.3. It could be that the 1.03b loader doesn't have the driver for the nic on your PC. I did a search on the forum and found these. I don't know whether it is worth reviewing the second link as I think he says that he got it to work.

If the fixed IP was set up by DSM and DSM doesn't start, you will get a dynamic IP. But then DSM should have restarted, complaining bitterly about the system volume having crashed and any apps that were still on volume1 would be broken. So there's something else going on here. One question: What version of DSM were you running before the crash? The same?

If its running DSM then info center>network or if windows in settings>network Or you could look at your router's list of devices or it should be listed in the BIOS of the machine

The MAC of the target machine - i.e. the one you will install DSM on

An update to 6.2.3 should be possible with the 1.03b DS3615xs loader. You need to prepare a new USB stick and download 6.2.3 .pat file to your PC and run a manual upgrade. There isn't a current tutorial, but this method is still valid. There is a tool to help create the USB stick which can be found here:

The onboard nic works with 1.03b DS3615xs (and '17xs) and 6.2.3. At the moment, that's the "latest" it will do

It's been a long time since I used the 5.2 loader. But it sounds like the boot process may have completed. What happens when you open find.synology.com from a PC on the same LAN?

First is to check this thread to select the correct bootloader and DSM version. 6.2.3 is the last release that works with the current loaders. If that doesn't help, Start a new thread in the noob lounge. Post the details of your hardware what bootloader version you are trying and what the last message you saw was.

What's the last message you get on the screen?

As you will have found when you came here, 6.2.4 is NOT supported by the current loaders (There is a new one in development but it's not ready yet). You will need to do this....

I think if you have got to this point then you can either say "It works!" and move on to something else or if you are keen to understand a little more, then it is time to look for some network primer articles which will do a much better job of explaining all this than I could.

First of all it is definitely working. You also turned IPV6 off on your NAS so we can feel confident that any network access your NAS makes is going through your VPN using IPV4. In the posts above, the external IP of the NAS is 194.127.172.80 which if you look up on one the" find my IP" sites turns out to be in the NL. You leave the download entry in DS permanently. It never downloads anything and when you look at the tracker entry it will give the then current external IP address of the NAS. This may change slightly. But if it changes to look like the address that your ISP gives you (86.241.144.201 in this case) then there is something wrong with the VPN connection. All the information on IP addresses that you have found while browsing from your PC say great things about the external address of your PC (or rather your router) - not the NAS. As your PC is not connected via the VPN it will always show your local connection to your ISP as that is what it is using. And 2a01:cb1c:8072:fc00:d5:b227:724d:61a9 is "real" as it is the address of your PC (not your router) on the external internet.

I am pretty sure that it is working as you want. When you say "If I go to https://blah blah" don't you mean that you did this on a browser on your PC? And unless you think you have routed your PC through DSM acting as a gateway, it will show your public, non-VPN IP address because that is the route the PC will take. I went to those addresses and that is what I found too. However, when I copied the magnet link to create a download task for DS, then I got the correct VPN address shown.

If you check Control Panel>General, the address under "Default Gateway" should not be one on your local network. It may say (VPN) after it. Preferred DNS server should also be an address on the VPN network above not on your LAN. When you go to Network Interface you see an entry for the VPN with connected time, IP address on the VPN network and values for both bytes sent and received. If you are not getting that, then the connection is either not being established with the VPN server (not logging in?) and/or you have some parameters wrong. I use another VPN and it was a long long time ago, but I think I just used the Create>create VPN profile under Network Interface to set up my connection and it just worked.

This post gives you recommendations for the loader you want : https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ If you are getting an option to migrate, then the loader is finding a system on the disk. You need to erase the disk (or at least the approx 2GB partition at the start of the disk The USB drive contains the bootloader and must be present. The system must be set to boot from the drive. It will load and start the DSM system it finds on disk Useful links are contained in this post : https://xpenology.com/forum/topic/36294-dell-r510-12bay-baremetal-requirments/?tab=comments#comment-174827

a) Good advice is: DON'T. See all the messages at the top of the forum page. The latest release that is currently supported is the one I suggested. 6.2.3 is the latest release that works. b)You will need a new loader to go to 6.2.4 or 7.x. This is currently being developed (see the "redpill" thread in the developer section). In general you need to refer to the forum before you attempt any new release. In the meantime, make sure that automatic updates are disabled in Control Panel. For now, stick with 6.2.3

Good news! There is also an internal USB but lets stick with the one that works 25426 is the one you want

I can eliminate some of the possibilities: DS918 won't work. It's for a later Intel processor. extra.lzma is not required. N54L will work with integrated nic without. For the initial boot of the loader, it doesn't matter about VID, PID and MAC. You can't install without VID and PID set, but it should appear on the network. SO, do you get any messages on the screen after the BIOS starts the bootloader? and, are you sure that the box is physically connected the network (no cable problems etc_

OK. I am missing something here. I do not understand why you wouldn't go back to the source files you used to create the bootloader in the first place, make changes and write to USB anew. I am happy to work through the steps to get you to install DSM on your N54L but I would take you back to the beginning and go through what you have done, step by step. It sounds like that would just annoy you at this point. But if it is not booting - have you disabled C1E in the BIOS?

Once the bootloader gets to "Screen will stop updating shortly", it really means it. The next step is to open a browser on a PC connected to the network and type in find.synology.com - or alternatively download Synology Assistant to your PC and run that. From this point on, neither monitor or keyboard do anything - after all a real Synology has neither.

You will need to create a new bootloader if you want to upgrade. See here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

1. Probably not. But see below 2. See the IG-88's post in the link below for useful links 3. It needs to be there for the box to boot