bearcat

@smidra (and others), you should have read the posted Warning! and thread to save yourself some problems.

@Baskedk Hello First off, I hope you have read this. Second, you are on the right track, download the 1.03b bootimage, and prepare your USB stick, with the correct vid/pid/sn/MAC. Download a local copy of the .PAT file you are going to install, to avoid getting "The Latest and Greatest" as it will most likely brake your system. Shut down you NAS, swap the USB stick, reboot and follow "standard procedure". When it's up and running, make sure you disable automatic updates! If (or when) it explodes, you may want to do some reading here and here. Third, make sure you have bacakup of any important data before you start. btw: For real? Did you actually do some reading before posting your 2.post above? Since none of the users (that I know of) are mindreaders, how can anyone tell what hardware you are using and what may/may not work with that?

@dragosl : To bad that adding a supported NIC is an option to you, it would save you for some work now, and down the road if it happens again. As you might expect, you are not alone in getting 1 update too much... If you would care to read some here or here, you will see some work that can be done to downgrade. Since you seem to enjoy to do some "dirty work" (ref. your mention above), I tested a "Quick and Dirty" solution earlier today, by "UnFixing" my "HotFix". I shut down the system, running with JUN'S LOADER v1.03b - DS3615xs, and removed the extra NIC. Then I deleted the USB stick, and made a new one, with JUN'S LOADER v1.03b - DS3617xs. I booted the system with the new image, and when asked for the .PAT, I used a local copy of the DSM_DS3617xs_23739.pat file. I was greeted with a migration option, and choosed to do a "Reinstall", keeping my Data and deleting/resetting all settings and apps. Seeing that all this worked out OK, I rebooted and was running 6.2 with no update installed, but I was later given the choice to innstall Update 2. Now ... to get back to where I one was, I did the same thing once more, but this time with the 3615 Still, I have an annoying update alert, nagging about Update 2....

1 - Fast and dirty fix: install a supported NIC.(HP NC360T is one I can recommend). 2 - Good question, I see my server informs me about the update being available, but I still have to press the update button.

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - MSI B85M-E45 + HP NC360T (based on the Intel 82571EB chipset) - Additional comments: Due to my expected failure (the post just above), I made a "HotFix", by adding an external NIC, and booted up OK. BTW: you might need to edit the MAC in grub.cfg after adding a NIC..

Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - MSI B85M-E45 - Additional comments: No network access (as expected).

@artyom : Try to turn off Secure Boot under Advanced > Boot options or the bios will skip any Legacy bootable device and only boot from UEFI devices.

Is your NAS connected to internet? Since it's complaining about the network settings and connection, it seems like it might try to do some verification. Might this be a function limited to original Synology hardware, with valid serialnumber? If you know your way around logging/debugging network traffic, you can have a look at what's going out of your NAS while you try to add the cache.

Try realoding your 2. pendrive, that allmost worked, with it's correct VID/PID, and the MAC for the NIC's you will be using. Remember you have more then 1 NIC

Ok, it's written in plain text just in front of you.... The rest of the boot process is "hidden", no more output to the screen will come after that message.

@Biaggi051 you may find your original MAC adress in the BIOS of your mainboard, and use that in the grub.cfg. There is some reference, in German, to the NIC I think is used on your mainboard: Realtek RTL8111GR, you might check it out (and search the forum).

This is not how it works with DSM... The system will be installed on ALL drives, the drives will be partitioned with 3 partitions 1 - System, 2 - Swap, 3 - Datastorage. and the first 2 will be identical on all drives. Dfds was asking you of what files you tried to use for your install, any pictures of your hardware, bios, car or girlfriend will not answer him or other who might want to help Unless you know what file you downloaded, it might be hard for us to guess. Start with reading: Read it all, but when you try to follow it, skip the part about migrating, and follow the installation of 6.1.x If you get this to work, you might try to update to 6.2 later.

This might be the problem, maybe you where installing a 6.2.x file ?

@Biaggi051 and @dedligamer You "might" need to do some reading over here. Short version, the file you MUST edit, is part of the bootloader file, (synoboot.img) and you have to do the edit before writing it to your USB stick.

@trek102 This is running on one of my a HP Microserver N54L, using Jun's Loader v1.03b DS3615xs, DSM 6.2-23739 Update 2.

1 - Wich BIOS do you have? 2 - Wich port is your SSD connected to? 3 - Is your port set to ACHI ? Edit: I'm betting your HP is not custom buildt, so your question might fit better in this section.

So, you get NO boot indication on screen, NO messages? (and then ofcource, no DHCP reguest to your DHCP server?) If so, your boot USB is not working at all I guess, try booting any other computer from it. So, you want to run your NAS in an actual production environment? I was under the impression that you where trying to "recycle" an old server no longer in productional use, in such case the free ESXi host running DSM, would not be limiting you in any way. Next things to try: 0 - Read the manual for your server, make sure it can boot from USB, doublecheck all settings in BIOS (primary boot device/legacy etc.). 1 - Find yourself a NIC, verified to work with DSM. 2 - Make a DSM 5.2 based USB bootloader, and verify it's working (by booting any computer). 3 - Test DSM 5.2 on your server, with original and new NIC, verify what's working or not. 4 - Make a DSM 6.0.x based USB bootloader, and verify it's working (by booting any computer).. 5 - Test DSM 6.0.x on your server, with original and new NIC, verify what's working or not. 6 - Make a DSM 6.0.x based USB bootloader, and verify it's working (by booting any computer).. 7 - Test DSM 6.1.x on your server, with original and new NIC, verify what's working or not. 8 - Get drunk, it's Friday

Unless your controller is a "Official" Synology device, with original drives supplied from them, I cant see how you had it working after your update to DSM 6.2.1 ? But anyways... Have a look at this thread:

Have you tried to downgrade your DSM? ref: https://xpenology.com/forum/announcement/17-dsm-621-23824-warning/

OK, first thing, your NIC seems to be BroadCom based, BCM5709. Here I found: So it seems that NIC needs some "help" to work with DSM versions higher than 6.0.2. Let's see if that is correct: Go here and first download and try Jun's loader v1.01 DS3615xs Make sure you read and follow the related info/tutorial. If the above refuses to boot, try the Jun's loader v1.01 DS3615xs with MBR partition found on the same page. btw: do you have any spare NIC's, known to work with 6.x to try if averything else fails? btw2: You can use a free ESXi license on your NAS, no cost.

Hello, and welcome The secret language might be: Read all the FAQ's, and then post all the info you have on your hardware and be specific in what you have allready tried. Before thinking of a CD-ISO, let's start with a USB boot stick. (do you know your VID/PID?) What bootloader did you allready try? What NIC do you have? (make/model)?

The safest choise would be OpenVPN according to this.

@florinpoe It looks like your USB is not bootable, try to boot it on a different computer. btw: is there an UEFI / secure boot setting on that HP, of so you must disable it and select legacy boot from USB.

Was your NAS using static or dynamic IP? If DHCP was in use, do you see the adress it gets from you router, and can you ping that adress? Have you checked your cable?

Disable any "Secure Boot" setting in BIOS, select Legacy boot if the choice is available.