valix

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant Microserver Gen8 (Xeon 1220Lv2) - Additional comment: To avoid custom extra.lzma, I already installed in 2019 an Intel e1000e Dual-Nic (HP NC360T) to go for 6.2, and disabled the onboard NICs in BIOS. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu D3417-B1 C236 Chipset w/ Xeon 1220v5 - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Biostar A10N-8800E (Carizzo), 8 GB DDR4 2133, Inline 76617d 4x SATA controller

@hoppler it worked like a charm on my 918+ config!

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant Microserver Gen8 (Xeon 1220Lv2) - - Additional comment: To avoid custom extra.lzma, I already installed in 2019 an Intel e1000e Dual-Nic (HP NC360T) to go for 6.2, and disabled the onboard NICs in BIOS. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu D3417-B1 C236 Chipset w/ Xeon 1220v5 - Comments: -/- - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Biostar A10N-8800E (Carizzo), 8 GB DDR4 2133, Inline 76617d 4x SATA controller - Comments:-/-

I tested the Power Plan on the HP Powerserver Gen 8 I also have. It worked in a restricted way. It cannot determine between the week days, each day is today for booting up, setting up to boot e.g. only on saturdays results in a boot every day. I assume an issue I have to live with - and I lived with it since 2015 or 2014. A nice to have, but on the other hand, Xpenology is no comercial product.

It didn't work.

Loader version and type: 1.04b DS918+ DSM version in use (including critical update): 6.2.2-24922-4 Using custom modules/ramdisk?: no Hardware details: Biostar A10N-8800E Ver. V6.1 (AMD FX-8800P Carrizo Processor), 4 GB DDR4 2400@2133 LAN: Realtek RTL8111H Gigabit SATA: 2x via SoC and 4x via Inline 76617D Add-In Card (Marvell 88SE9230 Chipset), S.M.A.R.T is supported for both Comments: clean install, used DSM_DS918+_24922.pat, perfect, CPU FAN replaced by Noctua 60 mm 3 Pin Fan, GPU clock reduced to minimum Loader version and type: 1.04b DS918+ DSM version in use (including critical update): 6.2.2-24922-4 Using custom modules/ramdisk?: no Hardware details: Fujitsu D3417-B1 w/ Intel Xeon 1220v5, 8 GB DDR4 ECC 2133 LAN: Intel I219-LM Gigabit SATA: 6x onboard Comments: clean install, used DSM_DS918+_24922.pat, perfect

Thank you, I'll try

This are my test settings for DSM And the device shut down as usual correctly as planned, but even as usual nothing happend at 18:12 - no start up. This are the power settings in BIOS: I could set a wake up date in BIOS but it couldn't be controlled from DSM GUI. DSM 6.2.2 on Biostar A10N-8800. But I hat the same experience with my HPE Microserver Gen8 and a Fujitsu D3417-B1 Board.

Of course I did. As I wrote it works perfectly for shutdown but not for startup. And I tested this with all my current and former Xpenology NAS (AMD Kabini, Intel Haswell, Intel Skylake, Intel Ivy Bridge, AMD Carizzo platforms). It never worked for startup. I give you one task: Set a shutdown time and 30 minutes later a startup time and please let me know if it worked for you.

Hi there, I ask myself if it wouldn't be great if the power schedule would work to boot and shutdown the NAS at a certain time. Shutdown works so far without any change for me at all my NAS but what about booting? Of course I could set a wakeup-timer in the BIOS but it is no very dynamic and has often poor possibilities and since the NAS is running headless I wouldn't always attach and detach a monitor and keyboard to change the BIOS settings - very annoying. Does anybody have a clue how to setup a working startup timer?

Alright, after replacing the currently used usb stick by another one it works fine. Obviously Hardware fault.

Hi there. I need some support to get on with my new NAS build. (This is supposed to be my 5th Xpenology NAS). This time I switched from Intel based systems to an AMD based system. When I install the image (no matter which 6.2.2) image with a 1.04 918+ bootloader, the installation process stops suddenly at 57% or 58 % depending on the 6.2.2 release with the error message " File could not be installed. The file is propably damaged. (13)". I found nothing suitable to this error message. I tested to install the current image from the internet and from a local file - no success. My hardware: Biostar A10N-8800E Ver. 6.1 (Carrizo), Realtek NIC onboard Inline 76617d SATA Controller (Marvell 88SE9230) 1 WD Red 1 TB 2,5" HDD connected to the Biostar MB 1 Seagate Ironwolf 8 TB also connectro to the MB 1 WD Red 3 TB HDD, connected to the Marvell controller all drive are recognized correctly by the controllers (BIOS view) I made no changes on the BIOS except the fan control, and disabled the serial I/O header, because I don't need it. I changed the file grub.cfg of the connected usb drive. The change lines are: VID, PID, changed the last 6 numbers of the SN and MAC section, and changed the SataPortMap to 24 (2x SATA onboard 4x SATA of the controller add-in card) Any ideas? Ps: The Inline Controller Card worked already perfectly on a AMD Kabini NAS build in 2016 with DSM 5.2

Sorry for the late answer. I m still running 6.1.x.... In November I took the latest loader from the link list: And I double checked it again - it was 1.03b That I used - the file is still on my computer. Right, in some kind I was in the wrong sub topic regarding the version - but the fault was the same. Nevertheless I remain sticking to 6.1. as long as possible, perhaps some day a new loader is available. And I am aware that this Xpenology porject is a project of voltuneers ...

Have you solved it? I 'm facing the same issues. Either it is telling me that the file ist corrupted or if I have a working file the server isn't reachable (no dhcp request) after the reboot.

I didn't mean only 918p. The same issue appears when also trying Jun's Bootloader 1.03b for 3615xs + DSM6.2 or Jun's Bootloader 1.03b for 3617xs on Ivy Bridge. I deleted after each test the partitions to show "new" disks to the installations process. After installation of DSM (downloading + exctraction+reboot) the device was always dead, as already described to 918, but I faced this issue with both other loaders... I wouldn't use "any" if I would mean the specific 918, but I did mean "any".