Leaderboard

In diesem Bereich bitte einmal lesen. dort wird das Probleme was du mit deinem RAM hast beschrieben und gezeigt, wie du es lösen kannst. Lg,

OK so this is just an informative post from a N00B take the information herin with a grain of salt. I tried to follow the instructions to a T it didn't work.... but I was a moron, here's the story, I did everything requested... but then when it got to (the system is rebooting it will take 10 minutes) I figured I would speed it up and reboot it myself. BIG MISTAKE. when it came back up it wouldn't accept any PAT files, or anything. I thought something went wrong with the USB drive. after trying everything I could think of to get this working. I finally took all the hard drives and mounted them with a windows system. deleted all the partitions. and created a new boot drive (On USB) I would still get to the point where I needed to upload the file, then it would blank out and go back to showing me that it's corrupt. it took me a while to realize what was actually happening. the different systems (619, 3615,3617) has different hardware I'm using a base intel board. and nothing seems to be working 619 wouldn't boot, and 3617 wouldn't load the rom. so. I started from scratch. loaded 619, expecting it not to boot. - it behaved as expected loaded 3615xs -- following the instructions perfectly. it booted, downloaded the PAT from Synology didn't work. had to use the one in the forum post. but that loaded so here's the takeaway, because there's not compatable hardware list. and no real guidance on which Synology bootloader to use. (Thanks Jun I LOVE IT) you need to find the one that is the most compatable with your systems. I was under the impression that the bigger number is better, and that I'd be happier with 3617. but I found that THAT is the reason I couldn't load the PAT file. I hope this is helpful to someone just starting out with this. because it was a 3 day ordeal of frustration and failure for me. HAPPY NASing

not if you follow the steps in the 2nd link, the new driver package contains a new drivers for the microservers broadcom onboard nic that works with 6.2.2 but for starting you can update to 6.1 and just follow the normal 6.1 tutorial (and update later to 6.2 when understanding the process better) for "practicing" you might disconnect your disks and put your usual usb flash drive aside and use a fresh usb together with a empty disk (any old disk will be ok as long as its sata) if you are done testing you can just connect all your old stuff and everything is as before when being able to successful installing dsm 6.1 (fresh install) you might use that new usb flash drive (loader 1.02b) to upgrade (migrate) your old disks with that to 6.1 from 6.1 to 6.2 its pretty much the same way, new loader needed (1.03b) and you can practice with a new usb and a empty disk until you have a way to do a fresh install of 6.2 its more complicated with 6.2 as version 6.2.1/6.2.2 are like a new DSM version compared to the initial version 6.2.(0), you cant user loader 1.03b for 6.2.2 without "modding" it (like in the 2nd link above) so if new to the thing keep to the tutorial until you get more familiar with the process of installing (a hacked) version of dsm and then start doing things that build on the normal install tutorial (like the 6.2.2 thing)

Just to comment about Quicknick's loader. I actually helped Quicknick debugging his loader for several months but he decided at the last minute not to release it for fear of legal reprisal. The person hosting that page with Quicknick's loader was supposed to provide a secondary/mirror hosting platform for him, as Quicknick and I were working on the main hosting solution. Unfortunately as mentioned above Quickinick decided against releasing the loader and that mirror hosting never removed the links, which in my opinion is wrong.

Here is a working ams as above for "loader 1.03b with 3517 DSM 6.2.2" please extract into /volume1/Downloads/ as above My previous zip contains some excess directories and duplicate library files; I have added the hpilo.ko for 918 / 3157 as labeled (thanks IG-88) this is tested on my Microserver g8 running 2.70 ilo To start, execute: insmod /volume1/Downloads/hp-ams/hpilo.ko sudo LD_LIBRARY_PATH=/volume1/Downloads/hp-ams/lib /volume1/Downloads/hp-ams/sbin/amsHelper -f -I0 -M1,5,14,16,18,23,99 script something like: more /usr/local/etc/rc.d/S99HP-AMS.sh #!/bin/sh modprobe /volume1/Downloads/hp-ams/hpilo.ko sudo LD_LIBRARY_PATH=/volume1/Downloads/hp-ams/lib /volume1/Downloads/hp-ams/sbin/amsHelper -f -I0 -M1,5,14,16,18,23,99 You'll see the below messages on both platforms if it is working, safe to ignore... NET-SNMP version 5.7.3 AgentX subagent connected error: Unable to open /usr/lib/rpm/rpmrc for reading: No such file or directory. Can't find directory of RPM packages System used: Microserver G8 HP Ethernet 1Gb 2-port 361T Adapter1.52, 0x80000fc5, 1.1752.0Slot 1 iLO2.70 May 07 2019System Board Intelligent Platform Abstraction Data0.00System Board Intelligent ProvisioningN/ASystem Board Redundant System ROMJ06 05/21/2018System Board Server Platform Services (SPS) Firmware2.2.0.31.2System Board System Programmable Logic DeviceVersion 0x06System Board System ROMJ06 04/04/2019System Board System ROM Bootblock02/04/2012 hp-ams3517.zip