leopold

I did this in the end - works pretty nicely as it happens!

I've got one: I picked up an old Datto four drive chassis into which I'm going to put a mini-ITX board. Said board doesn't have an internal USB port (not that it could be easily accessed anyway) and I'd rather not have the USB key sticking out of the chassis as it's easier to knock/break. Also, the OCD part of me doesn't find it aesthetically pleasing.

Thank you so much for this guide! I tried it three times without success, before properly reading it and realising my silly mistake! To anyone else struggling, PLEASE make sure you do this after doing the 7.0.1 build. I found that the first time running the build didn't actually create this redirect in 100% of cases - okay, so that was twice to my knowledge and most likely three times prior to that, but I digress. Running the build a second time did the trick.

I've asked the question about reserved RAM a fair few times, on here and on other places, and have been met with radio silence. So I'm well pleased that someone else with the same issue was able to get a response as it means I can now move forwards. Thanks for this, it worked on my N54L too!

What does this line do? Does this do the same as the "disable_mtrr_trim" from Jun's loader, by any chance?

Okay, so it's been up a while now and everything seemed to be fine, until I noticed my memory usage seemed pretty high (given I've got 16GB of RAM in this box), so I had a look and all but about 4GB is "reserved". I tried removing a module, taking the box down to 8GB, but the same scenario. I tried all kinds of configurations and the only one that gave an even remotely sane reserved memory count was going down to 4GB. I'm guessing that this is something to do with a 32 bit limit somewhere, but I'll be damned if I can figure it out. Has anyone else experienced this issue and, if so, how do I go about releasing all that lovely memory that I've got in there?

I've finally decided to bite the bullet and try this loader, largely because I've just checked the energy usage of my Proxmox home lab and almost died of shock! So I've stuck this onto one of my ancient HP N54L boxes. And, frankly, it all seems far too easy... I'm waiting for the server to freeze or reboot or burst into flames or summon the evil pixies of Beelzebub or something. If this doesn't keel over in the next 48 hours, I'll be a very happy bunny indeed! Thanks to @pocopico et al for all your sterling work so far on this. If I can slash my home lab electricity costs enough, I might even be able to make a dent in the huge amount of cash I already owe the energy company

Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver N54L - Notes: Loader appears to boot normally, but there is no response to PING or find.synology. Rollback to previous DSM version was successful, thankfully!

It was my own fault. I completely forgot everything I know about change management and hit update on my live servers, only to watch both of them get bricked. Damn! In my defence, I was still suffering from a rather nasty bout of gastric flu, but it does make me question whether I should turn in my ITIL certification... Anyway, massive thanks to you @IG-88, I followed your process on both servers and they are now happily whirring away again. I'll keep an eye on them to make sure nothing untoward happens, but so far, so good. In my local parlance, you, sir, are a flippin' legend!

Thanks, I intend to keep coming back to see about updates. I had found an option which would be useful (I think it was to do with casting from Apple devices, but I could be wrong) which needs DSM 6.2, but I'm not about to buy hardware for this, so it'll be interesting to see if I can get this release with the internal card in the microserver.

After years of contemplating what to use as a replacement for my ageing Windows Home Server and failing miserably with the hassle of trying to force something to work, someone put me onto XPEnology and said it worked fine on the old Gen 7 Microservers. As I have two N54Ls kicking around doing not very much, I found these instructions and gave it a go. After maybe fifteen minutes of prep work and a few minutes of installation, I've got a full system which will replace that creaking old environment, including a functioning DLNA that will serve up my music in more or less the exact same way the TwonkyMedia service did. And to think of all that wasted time faffing about with Linux! The only issue I came up against was hitting the big green "Install" button, which dropped the latest PAT onto my server and scuppered it. Use the "Manual Install" link instead and this gives the download option as mentioned in the instructions. One of the servers is currently having several terabytes of data being copied to it. The other I used as a test rig for upgrading to the latest version of 6.1.x. I was able to take it all the way up to 6.1.7 release 3, with only one forced reboot to get to 6.1.7, so when the master server has got all the data on it, I can give that a whirl, safe in the knowledge I won't break it. Many thanks to Jun for all the hard work on the installer and to Polanskiman for the very clear instructions. You've both saved me a lot of pain!