Leaderboard

So far, I can´t see anything out of the ordinary. My best bet would be to get a cheap Intel NIC (I bought one for not even 25€, 2-port, 1gbit) and try it with that. I´m currently working on a couple of Dell servers and I´m having a similar issue as you do, though it´s not even working with my Intel NIC. Just try a couple of different configurations, loaders and whatnot, there´s always something that you need to figure out before it works... If you have a spare HDD, try that out too. Especially with your case 3. Usually, it doesn´t matter whether it´s an SSD or an HDD, but you never know. Good luck!

Hi there! In my experience, HP Servers usually function the best as a 3615xs with the 1.03b loader by Jun. However, be aware that on some versions, the onboard NICs will stop working since some versions apparently only support Intel NICs. Are you certain that pid and vid of the stick and the mac address(es) are correct and that you saved the grub before dismounting? I know that might seem like a dumb question, but things like that were the most common mistakes that both me and a couple of friends of mine did because we were too impatient. And last but not least, I´d recommend deleting all data on the HDDs in between installations. In case 2, DSM could be partially installed or just be corrupt and case 3 could see the data on the HDDs as an already existing DSM and therefore just try to recover the data, which fails because said data is corrupt. I hope you get what I mean... Anyways, best of luck with your installation. If it fails again, you could try installing a virtualization OS and try it there, maybe that works.

min. 4th gen intel cpu for 918+ it's documented here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ you would need to use 3615 or 3617 for a 3rd gen cpu, and when using 3615/17 you need csm/legacy mode in the uefi bios and need to choose the non uefi usb boot device

The first thing coming to my mind during reading your text is: "check speed and duplex settings!". Sometimes there is a mismatch between the NIC and the connected network switch regarding these settings which results exactly into the issues you are describing. The default setting in DSM is "auto" but maybe it helps if you to set speed/duplex fix to "1000mbit/full duplex". You can find the setting in the NIC settings of DSM. Before testing this I would suggest that you configure the second NIC as a fallback with a own fixed IP if the change doesn't work and you lost completely your connection. You can also check your network switch (if your have a manageable one) and check if the speed/duplex settings from this side is matching what DSM sees and set them fix to 1000 mbit/full duplex.

Hola, pues yo seguiría aconsejándote la versión DSM 6.1.7. Que es la que mayor compatibilidad tiene, más actualizada está con menos problemas de drivers. El bootloader sino me equivoco no se puede instalar en dispositivos tipo disco duro (sean SATA o m.2) ya que necesita de cierto parámetros que no pueden "extraerse" (o emularse) de esos dispositivos. Lo del dual boot pues simplemente seleccionando si arrancas desde USB con el bootloader o desde el disco duro donde tengas el sistema podrías hacerlo. Ahora bien cuidado con como "tratas" los discos en cada uno de los sistemas porque podrías romper o el sistema Xpenology o el OS desde Xpenology. Es decir no trates de montarlos en el otro sistema o seguramente los corromperás.