Messenger

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 - 25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen7 N54L - Additional comments: Reboot required

so just updated everything worked like expected. Thank you very much.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: Jun's Loader v1.03b 3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer N54L - Additional comment: onboard nic, update pat file with control panel

Hello all, i am on hp n54l microserver gen7 and have no additional nic. I am on dsm 6.2-23739 update 2 and now i read its possible to update out of the box with old 6.2 drivers to new dsm 6.2.3??? For this old version (6.2), i don´t use additional lzma - just junes DS3615xs out of the box. For 6.2.2 i remembered must need an additinoal nic or custom lzma - but now just update in control panel, reboot and all fine and finished? Greetings messenger

someone migrated successfull n54l without data, settings loss?

so semi-brick better preferred way of installation (without losing apps) then migration (losing apps) i think?

hello did someone migrated hp n54l without additional nic?

Think many got a HP N54l like me, possible to integrate the Nic (Network Controller: Embedded NC107i PCI Express Gigabit Ethernet Server Adapter) think from Broadcom?

Is there someone here to make onboard nic compatible in next loader fo HP N54L?

Is it possible to integrate in next loader driver for onboard nic for hp N54l / N40L in ds918? Or build similar loader for 3615xs (3617xs)? people buy additional nic for there systems but maybe possible to integrate?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7 15284 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L - Additional comments: must delete .xpenoboot folder to get access to network and filesystem in dsm

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 1 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen7 N54L - Additional comments: REBOOT REQUIRED

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - N54L G7 - Additional comments: REBOOT REQUIRED

Update done. No problems - can access shares.

then i think there will no timebomb in this patch

i´ve got 5 hdd´s in a raid and one single hdd. Just jun´s loader (modified with my mac, sn, vid, pid) with custom bios. no problems ´till now.

on n54l you didn´t have to modify.

ok i´ve got wol working: start putty login as admin sudo -i cd /usr/local/etc/rc.d vi S99ZZZ_Shutdown.sh paste the commands from the scipt with copy and paste: #!/bin/sh case $1 in start) if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then /var/packages/shutdown_script/DSShutdown.sh & fi ;; stop) if [ -f /var/tmp/shut.down ]; then rm /var/tmp/shut.down fi ifconfig eth0 down ;; *) echo "Usage: $0 [start|stop]" ;; esac then save with: wq! chmod 755 S99ZZZ_Shutdown.sh the wol is working again

can u explain how u exactly did it? with winscp i cannot verify with root and with admin i ve got permission denied to copy in this share. with putty i can login with admin and switch to root with "sudo -i" but i don´t know how to copy.

found it my fault thx will test it later

rc.d not existing is it the same like rc.sysv?

Migration done successfully. But someone got wol working?

does one of these steps activate wol? http://xpenology.me/how-to-activate-wol/ or is it because of disabling C1E in Bios?

with the modified 1.02 from june with all drivers for hp n54l from this topic or just native 1.02

@netrider and @djvas335 upgrade with clean install and founding your data or just migrate to the higher version with assistent?