Apfelbomber

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.

The issue was resolved thanks to another post in the Updates section - I simply had to delete the DNS entry and re-enter it. That fixed it. Many thanks anyways!

Update: Or not. Sporadically, the package manager has a connection, but it seems to be completely random and unpredictable.

Update: Disabling the Intel NIC seems to have resolved the problem. Maybe the four ports were too many?

I recently updated my Microserver Gen8 which is running on Jun´s loader v1.03b as a 3615xs to DSM version 6.2.3-25426 (it was running on 6.2.3-25426 before, with the only issue being that I couldn´t shut it down or restart it via DSM) and since that update, the server can´t connect to any services. The package center is unavailable, as are Plex and TeamViewer. I can access the Server just fine, as long as I´m within the network. There´s no data loss and no other issues so far. It´s not a router problem either, the settings there are the same as always and I don´t see anything that could cause this problem. I´m using an Intel NIC because the onboard ports wouldn´t be recognized by DSM after update 6.2.3. However, after the latest update, the onboard ports were visible again in DSM. Using these ports instead of the ports on the NIC doesn´t resolve the issue either. I changed the serial number of the loader because I had another Gen8 with the same settings in the network. I don´t have that one anymore. I also listed all four mac addresses in the loader, just in case they started working again after another update (which they obviously did), but maybe the four ports may cause the issue too, so I´ll try to remove the NIC and boot again, just to see if anything changes. If there´s any Gen8 user out there who has it working on 6.2.3-25426 I´d really appreciate any help whatsoever. The specs of my Gen8 are the following: 12Gigs of HP ECC RAM Intel Xeon E3 1230 Intel 2-Slot 1Gbit NIC Many thanks in advance!

- Outcome of the update: SUCCESSFUL-ISH - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun´s Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen8 with additional Intel Network Card - Additional comments: The Update itself was succesful as in no data loss or connectivity issues TO the server - as long as you´re within the network. The server seems to have no connection whatsoever to the package manager and apps like Plex or TeamViewer don´t have connection either. VMs on the server, however, don´t have any issues. I´ll update this post in case I find a fix, but for all Micro Gen8 users: be really careful about updating!