Jump to content
XPEnology Community

sounds2k

Rookie
  • Posts

    4
  • Joined

  • Last visited

Everything posted by sounds2k

  1. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 - 25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 7 N54L - Additional comment: Reboot required - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 - 25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: yes - extra3615_v0.11_test - Installation type: BAREMETAL - HP Microserver Gen 8 (Intel Xeon E3-1220L V2 with 8GB RAM and Asus NIC: ASUS XG-C100C 10Gb) - Additional comment: Reboot required
  2. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: YES, v0.5 for 6.2.2 (before upgrade - see additional comments) - Installation type: BAREMETAL - HP MicroServer Gen7 N36L, using built-in NIC (HP NC107i / Broadcom BCM5723) - Additional comments: upgrade within DSM GUI - no response on network after reboot. Had to switch off server manually and recreate the USB loader stick as a completely standard Jun's Loader v1.03b (no modifications to second partition). Server then booted, completed upgrade and rebooted again after which it was all working. NIC does not support jumbo frames.
  3. I have a N36L - so the same motherboard but with a slower processor. I was initially unable to get DSM 6.2.2 working (with the extra.lzma file) - the network card only responded prior to installing DSM, after the initial reboot it stopped responding. So I reverted back to 6.1.7, which worked on the first attempt (and the NIC responded on the first reboot). However, a few days ago when trying this again I noticed that on the first reboot after installing DSM (although the NIC wasn't responding) the hard drive was quite busy, doing what I presume is rebuilding/updating the kernel using the additional drivers ... because after a couple of minutes, it rebooted again by itself, this time the network card did start responding - and it worked fine. But ... as mentioned above, Synology seem to have reverted the driver changes again for v6.2.3, meaning you can use the v1.03b loader without needing to add the "extra.lzma" file and the network card will work on the first boot after installing the DSM software ... which is even better 😀 Oh and auto hibernate (after HDD power down) worked on v6.1.7, it doesn't work on 6.2.2 or 6.2.3. However, a scheduled shutdown and/or startup works fine, which is what I use now because I found that the auto hibernate was too inconsistent.
×
×
  • Create New...