Tone

Does anyone can recommend a network card with a compatibility driver that had no problemas with IP assignation and continue with installation? I've been considering to buy this one for example that has a r8125 built-in chipset: https://www.amazon.es/Ziyituod-RTL8125-Chip-Accesorios-computadora-domésticos/dp/B0B1WNCPZ6/ref=sr_1_12?__mk_es_ES=ÅMÅŽÕÑ&crid=3DJ5YCWK8V0NE&keywords=rtl8125&qid=1666188635&qu=eyJxc2MiOiIwLjAwIiwicXNhIjoiMC4wMCIsInFzcCI6IjAuMDAifQ%3D%3D&sprefix=rtl8125%2Caps%2C102&sr=8-12

I've been experiencing issues too with the same setup. I tried with every different builds and the most compatible for me it's DS3622xs+ which at least allows me to proceed with the wizard installation but always get stuck at 70% and then reboot and it's prompted to start over again the installation...

I'm running into the same problem but in my case I got the real mac address assign but immediately I boot the loader, the NAS is lost. No dhcp entry in the router, only when I enter again in the config loader...

Hello again, Do you know what could it be the issue? I think bnx modules are part of modules already and my mac address matches with the onboard NICs.

Yep, and the mac is correct. I added the second one just in case and modify the net_if number but still won't assign IP. In any case how should I added them manually? Which would be the repo?

To clarify: network card is an Embedded Broadcom BCM5720 Dual Port Gbe LOM. Didn't have problems building the booloader with pocopico (but got issues with installation pat) but here I'm not even able to get an IP....

Hello there, First thanks for the automated solution. I'm having the following issue, when I choose de build (DS3622xs+) and build it and when I boot the loader, I lose the IP assignation immediately and I'm unable to init synology assistant to start the installation and when I reboot and loader it's booted I get an ERROR on ip assignation. Do I miss some specific network driver or something like this? I'm using an HP Proliant Microserver Gen10 (AMD opteron X3126) Thanks!

No worries, after all I think it's not really the problem at all changing the build. I just followed a big variety of methods and all of them results in the same results: there's no problems building, serializing, setting de VID/PID of the usb and so on but something that really annoys me is when I execute satamap, it's not able apparently to find any drives although the DSM setup runs smoothly being able to detect the HDD, it's this normal?

Which build is DVA11621+? The only one I see here is DS1621+ here which Indeed has support for AMD but Ryzen models... I don't know if that could have an impact no harm to try it.

bromolow-7.1.0-42661 (DS3615xs)

Hello there, I'm experiencing the same issue, whenever I load and build the bootloader, I'm prompted with the installation wizard, select the pat file, reach 72%-73% and then reboot and prompted again with the installation wizard in an endless loop. I tried everything and when I mean by everything... EVERYTHING, tried every different builds, usbs, spare disks, changing sata mode from Legacy to UEFI and viceversa, removed any possible RAID configuration... My setup is an HP Proliant Microserver Gen10 AMD Opteron X3216 PD: Just to mention that I'm parting from a clean installation, neither migration nor recovery.

I’ll take a look. Probably the answer is managing the options under system utilities instead of bios. Thanks!

Thanks for the tip but apparently there's no option in bios to disable the onboard SATA. Bios is Megatrends ZA10A280 just if its of any help...

Hello and good afternoon, A week ago I posted in this thread an issue trying to do a fresh install in an spare disk before moving my RAID from 6.2.3 to 7.0, didn't get any answer so far, you can see more details in here: In short, whenever the system boots, a "install" screen is always displayed, no matter how many time I select the manual .pat, it always reach 70% and then reboot and "install" screen is shown over and over again... Any ideas? No errors are displayed at all Regards!

Hi guys, Don't know if this is the proper place to ask for it so here we go: I'm trying to do a clean installation to DSM 7.1.0-42661 but with no success... I always get stuck at 73% of installation and then reboots with a 10 min counter, once is rebooted the installation prompt is shown again. I used broadwellnk architecture to build the loader so the model version used is DS3622xs+, just in case I used the default choice for satamap assignation which is in the image attached, something weird to me since I got 4 SATA ports, not 8 and It states as 0 drives which I don't know if its correct or not. This is my user_config: { "extra_cmdline": { "pid": "0x6545", "vid": "0x0930", "sn": "2030SQRMN5HWZ", "mac1": "70106FCA609E", "SataPortMap": "18", "DiskIdxMap": "0001" }, "synoinfo": { "internalportcfg": "0xffff", "maxdisks": "16", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no" }, "ramdisk_copy": {} } My setup is a HPE ProLiant Microserver Gen10 with a CPU: AMD Opteron X3216 which I think it's a pretty common setup in XPE world. Regards

Hello guys, I don't know if this section is the most appropiate for this question. I got a failed migration (I rather say a big mistake from my side) when I was running the assistant dialog to go from 6.2 to 7.0. I didn't realize until the very end that I was running a clean installation so when the progress was starting I immediately interrupted it. Fearing the worst I switched loaders from redpill to jun's so now it's non-accesible, fair enough, since I think is in the limbo between 6.2 and 7.0 and it has lost all the configuration as it's prompted in the assistant. I removed the RAID 5, compound of three drives and mounted apart and launched GParted crossing fingers that although synology is not accessible, the data is still there. Just mounted and this is the result (see attachment) So "Archivos", "photo", "docker" and so on are the main folders where my data lives and whenever I try to access them I get what states there: `cannot access ***: Input/output error` Doing so surfing around the web I found the command `btfrs scrub` and tried it. Apparently other filesystem like `ext` allows you to access the folders even though it could be corrupted, non the case for btfrs since this holds some metadata checksum in order to preserve non-corruption problems, so if there's no validation, you're not able to access the data. After running this command, I get no errors but I still not being able to access these folders. I know I know, great mistake but there's no possible way to retrieve the data at least and copy them to a spare disk? I was reading about running `btfrs repair` or another options such as `fsck` but these options are discouraged in terms that they work as a last resort... so just asking, any advices? Should I say good-bye to all my data? 🥲

Thank you for the answer! I think I'll go for the last option: buy 3x4tb, create the RAID5 and copy all the data from the 3tb and discard it.

Hello there, I don't know if this is the correct section to ask this but I was trying to find a specific solution to my question and didn't find anything. I got the current situation. I'm currently mounting a 3tb NAS HDD and I have 3 more slots to extend. I want to create a RAID 5 and I want each one to be 4tb. I was thinking to buy a 4tb one and replicate (which I don't know really how to do it) from the 3tb. Another choice is to buy two 4tb and create a RAID 5 so in the long-term I'd replace the 3tb one for a 4tb and I was wondering if this could lead to parity problems since they have different sizes? Which choice do you think is the more easiest and manageable?

Hello there, I don't know if you read my previous post but seems to be a similar problem. I replaced the extra.lzma but only after run the new bootloader and running the wizard to looking for the NAS and restore it. After this you only need to unplug the USB, and running "Ext2 Volume Manager" as @IG-88 stated in the previous post to replace the extra.lzma in the existing bootloader and plug in and boot again and now your NAS should be shown again to continue with the migration.

Thank you very much! Finally worked! It was a very painful process since I cannot edit the bootloader usb directly and I had to make an image of the booteable usb and replace the extra.lzma through osfmounter but anyway... now it's working flawlessly! Thank you again and I will try to update to 6.2.3 althought I cannot see any updates in the upgrade panel... should be do it via manually? Regards.

Hello and thank you for the quick answer, Yes I read something about the extra.lzma but I thought it was only for cases the NIC wasn't able to be detected at all but now that you mention, it disappears at second boot so I'll try this. Now I'll put the specs of my machine: CPU: AMD Opteron X3216 / 1.6 GHz NIC: Broadcom 5720 And I'd say that's the most relevant, the machine is an HP Proliant Microserver GEN10. You can find more information here: https://cdn.cnetcontent.com/ac/34/ac34857c-5b7d-4bc0-a7b4-e981390c37eb.pdf

Hello there, I've been running DSM 6.1.7-15284 for a while thanks to Jun loader 1.02b for over two years with no problems, however I was thinking that it was time to do some update and since Jun's loader for 6.2 has been released for a while so... I encouraged to update the xpenology. I did through the system packager to upgrade to the most recent version pointing to 6.2.2-24922 and reflash the usb with the Jun's loader 1.03b for 3615xs. Following again the tutorial for the migration from 5.2 to 6.0.2 I just configure the grub file matching my mac addresses, pid, vendor and the sn pointing to 1130LWN015135 as states here for 3615xs: https://xpenogen.github.io/serial_generator/index.html I found it through http://find.synology.com/# and prompted the diskstation and click on recovering. When the progress loader began to start, it showed 1% percent to recover the system and suddenly prompted that was in the process to restarting... suspicious. I did again the process to find my synology but this time wasn't unable to find any. There was no ip listed in my router for the xpenology. I repeated this process burning the loader again, plug in, and so on... I don't know if I am missing something... I hope there's nothing corrupted or sort of... anyone that could know what's going on?