bearcat

@djwayne1985 You do know there is a search function here?

@lovesky In regards to #3 you said "However, the link you give me, explains how Install XPEnology on a standard computer and not on a NAS" thats why I asked, since the link referred to installing DSM (4.1?) on a Netgear Readynas Ultra Now, what version of bootloader did you use on your stick ? It seems like the Ultra 2 is using an Intel Atom D425, that is an x86, 32bit CPU, that limits your choice of compatible versions. (read= legcay loaders) If you try making a USB boot stick, using the info and links here or here it might work. And yes, untill you are able to connect to your box, using ssh/telnet, and write to your internal usb-boot the USB stick has to be used/mounted for you to be able to boot. In regards to #1 Did you try with more than 1 type of USB stick? I see they claim it to be very "picky" in regards to the stick beeing used. There seems to be an unofficial update, you might want to do some "digging" to see if that might help you out. In regards to #2 Have you tried contacting the previous owner?

Assuming you are the correct owner of the box, and not somone trying to hack I faced a similiar problem with the box of a friend, but that was running DSM 4.3. I was trying many things, including the "Password of the day trick" As can been seen in that thread, there is a way to manually delete the DSM system partitions, letting you reinstall the system from scratch, while keeping the data. It works, but can be dangerous if you make a mistake. What I ended up with, was an update to 5.2, allowing me to reset the config, and keep the files. Since you allready are on 5.2, maybe a forced install, using a new stick, will give you the option to migrate your data, or if your HW is compatible with DSM 6.1, you could try that upgrade. btw: Is your system set up to autoblock IP adresses after Xnumbers of failed logins? That might keep you out, even with the correct password.

There has been posted a guide to be used with x86 (32bit) it might be worth a look btw: As you get an IP from your server, using Windows on the client, confirmes that your HW is working, but it still needs to be compatible with the bootloader/DSM used, and they are Linux based.

If its compatible, your DHCP server should have been getting a request.. Have you tried a different cable or port? Next Q: What bootloader have you been trying?

First 2 things for you to find out as a start: 1 - What networkcard (or chip) is inside your computer? 2 - Is that card/chip compatible with the version of DSM you try to innstall?

@lovesky 1 - So you have tried the recovery procedure Netgear posted with no luck? 2 - What version of DSM has been running on it before, and what version are you trying to install? 3 - Did you follow my link and read how to install DSM on your Netgear? (as you may see, this was posted 2014, so it means OLD version of DSM)

I don't know your hardware, but Google indicate that the "Advent Firefly FP-3104" might be using a H55 based chipset, do you know what the SATA controller is? You might get lucky using a "driver extentsion" and adding a "extra.lzma" to your bootimage as the 6.2 loader might have dropped some older hw support? As to why you have to convert into an .ISO and if that might cause problem, thats another story

Maybe this can help you on the way ? It will be pointing you back here. If you want to restore it to the original Netgear firmware, there is an USB Recovery available.

@MCFLY78 Hi Marty, did you find the link? (it's for the 918+ only).

Ahh, OK. Note that in the BIOS, the drives have to be detected as ACHI not IDE, if it's in IDE it will not been seen in DSM

6.2.1.x ?

Supposedly, this should be supported, but there might not be many users here?

@fa2k Thanks, I will give it a try when I find the time, currently I just added a Intel based nic, to "save the day"

I'm sure you have tried a different cable? Have you tried loading anything else, like a live linux distro, or even Windows, to make sure the nic is working? If you look at this thread. it seems like your board should be compatible.

Having some "free" time, I did a test with one of my Microservers. HP N54L - 16GB RAM, DS3615xs DSM 6.2-23739 Update 2 5 * WD 3TB RED, SHR-1, ext4. Some median values: (variations of: dd if=/dev/zero bs=1M count=256 | md5sum) 268435456 bytes (268 MB) copied, 0.839746 s, 320 MB/s 536870912 bytes (537 MB) copied, 1.71475 s, 313 MB/s 1073741824 bytes (1.1 GB) copied, 3.40958 s, 315 MB/s 2147483648 bytes (2.1 GB) copied, 6.94679 s, 309 MB/s 4294967296 bytes (4.3 GB) copied, 13.5109 s, 318 MB/s 8589934592 bytes (8.6 GB) copied, 28.5729 s, 301 MB/s (variations of: sudo dd bs=1M count=256 if=/dev/zero of=/volume1/test conv=fdatasync) 268435456 bytes (268 MB) copied, 1.34079 s, 200 MB/s 1073741824 bytes (1.1 GB) copied, 3.84433 s, 279 MB/s 2147483648 bytes (2.1 GB) copied, 8.32476 s, 258 MB/s 4294967296 bytes (4.3 GB) copied, 16.427 s, 261 MB/s 8589934592 bytes (8.6 GB) copied, 30.308 s, 283 MB/s To "spice" the numbers, I have a 120GB SSD as read-cache, and I can see it getting good use during this test

@apple3000: try these steps: Activate the SSH service in DSM Connect to your Synology with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh my.nas.ip (replace with the actual IP) Enter your credentials (user: admin) Change folder to root (cd /) Delete the folder (sudo rm -r .xpenoboot) If the SSH service keeps stopping, you have to be quick.

Did you edit the grub.cfg to reflect the new MAC adress, and disabled your internal NIC ?

Can you see any signs of your computer in the log of your DHCP server ? And just to be sure, it HAS been working OK with DSM 5.x, using your internal nic (that suposedly is an Intel) ?

1 important question ... Are you trying to install DSM 6.2.x ? If so, make sure your NIC are compatible before waisting your time

Hello again, hope i did not scare you with my Tarot cards According to this your computer has an onboard Intel NIC: I217LV but here it says Intel 82579V (same chip as on your external PCIe card?). From what I can read here, the Intel 82579V should be all OK with DSM 6.2.1 So if you made your bootstick, with the correct vid/pid/sn//mac, and your are able to boot, and to install the .pat it should have been working after the reboot. Did you install the .pat manually, from a local copy, or was it automaticly downloading the newest DSM from internet? Whats the name/fileversion of the bootloader you downloaded?

If you downloaded and installed the .PAT automaticly, you got the "latest and greatest" DSM, who don't support your NIC. Start over agaim using Jun's loader v1.02b DS3615xs, and manually download the DSM 6.1.7-15284 .pat file, and use it to install. When your up and running, you may update to DSM 6.1.7-15284 Update 2, but disable auto-update. This works very well with ML110 G5.

Same as the admin/password you chose during the install ?

In regards to your question in the first post: I think what you have done wrong, is to not read all the warnings in regards to this problem, and failed to check if your hardware is compatible before updating. Then you made the next fail, assuming other people know what hardware you are using, allways be as specific as possible. I'm a bit psycic, and by reading my Tarot cards 🤓, I can see that you tried using a non-supported nic, even if you did not specify the make/model..... Thats why your old 5.x is working, because of a change in the kernel config that breaks all non official PCIe devices drivers in 6.2.1. Most likely, if Mars is entering the right orbit, an Intel based NIC would work...