Let me start out by saying I’m a fan of Synology. I have owned a DS216Play in the past and have upgraded to a DS918+ in recent years. In my view Synology DSM is one of the more user friendly interfaces for NAS type devices and so I decided to revisit the XPEnology project when I came across my old HP N54L.
While I found several other posts of people already running XPEnology on their N54Ls I did not find a detailed installation post specific to my needs. I decided to visit the installation FAQ and from there the DSM7x loaders and platforms page. I remember feeling a little overwhelmed at first but after a while figured that I needed the DS3622xs+ loader (broadwellnk) as the DS918+ loader requires a newer CPU and all the other DS36XXxs+ are marked obsolete.
The installation proces is well documented and not worth repeating here. Instead I will share the options I used during installation that resulted in a working XPEnology system. After booting into TinyCore some configuration is needed before building the image. Important to note here is that the USB you use to boot TinyCore from will need to stay connected to the system even after installation so keep that in mind when selecting your USB device. I used the following commands and settings for my install:
./rploader.sh update
./rploader.sh fullupgrade
./rploader.sh identifyusb
./rploader.sh serialgen DS3622xs+ realmac
./rploader.sh satamap
./rploader.sh build ds3622xsp-7.1.1-42962
./rploader.sh backup
./rploader.sh backuploaderAfter running these commands and rebooting the system you should be able to find you XPEnology system with the Synology Assistant. However I found that my system never came back online even though the it seemed to be running fine. A quick google search showed me that I had to disable the C1E option, under the Advanced CPU settings, in the BIOS for the internal NICs to start working. After the change I was able to find my new system and continue with the DSM installation.
Now that the installation is finished I will do some more testing before deciding if I will place this system into “production” at one of my relatives. I think they can benefit from a system like this but I need to be sure it will run without issues.
Upgrading DSM
I had some time this week to look into upgrading to newer versions of DSM starting from 7.1.1-42962. After several failed attempts I can share that I have version 7.2.1-69057 Update 4 running on my N54L. The path I took to get there was from: 7.1.1-42962-1–>7.1.1-42962-6–>7.2-64570-1–>7.2-64570-3–>7.2.1-69057. Updates were applied via the DSM update function and after each update I booted the TinyCore friend to update the loader. The TinyCore friend does not boot DSM on my N54L so I interrupted the boot attempt and just rebooted and chose the normal loader USB option.
References:
- https://xpenology.com/forum/topic/9394-installation-faq/
- https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/
- https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/
- https://xpenology.com/forum/forum/78-dsm-updates-reporting/
- https://github.com/pocopico/tinycore-redpill
- https://mega.nz/folder/rBMGVCxB#h5jdbzv7tfPliyUhnqqEDQ
- https://www.synology.com/en-us/support/download/DS3622xs+?version=7.1#system
Hi Tom,
Did you apply any bios mods? Or are you running a vanilla n54l?
As a matter of fact I did apply a bios mod! It allowed full sata speed for all sata ports including the dvd/cd rom and hotswapping of drives. I will add the link if I can find it again.
EDIT: I’m pretty sure its this one from user kamzata: https://www.bios-mods.com/forum/showthread.php?pid=75965#pid75965
Awesome! Thank you!
One last question: did you use the bios or the uefi usb image?
I’m pretty sure I used the bios one!
Thank you so much! I tried setting it up but the device never appeared in the assistant. After flashing the custom bios and disabling C1E it works like a charm!
the backup command in tcrp does not work somehow, seems like the sde3 partition is filled up to the brim
Thanks for letting me know and enjoy your hacknology!
Hello losing my esata drive. Can u help? Only have 5 from 6 HDDs
Hi Stefan,
It depends. Could you share some more details on your setup?
Regards
Tom
I migrated from DS3615xs 42218 to DS3622+.
I have a SHR Raid with 5 HDDs – one of them on the esata port. One Standalone HDD.
After migration i lost the esata HDD in Raid. Under tcrpl all 6 HDDs are displayed so in Bios too. C1E is disabled and AHCI is enabled.
All fine migration but under new DS3622+ only 4 HDDs from RAID and Standalone are online.RAID now critical.
Maybe some configuration to bring back the esata HDD on this OS?
And this is with the N54L? If so I assume four disks in normal spot, one in the dvd drives place and one 1 esata?
yes something like that. DVD drive offers space for 2 drives. A normal RAID disk and a small SSD. One of the RAID disks is connected to the esata. The SSD is standalone.
I see. As the older version did recognize your 6 drives wouldn’t it be a better idea to downgrade to the known working version?
Worked now 🙂
had to modify DiskIdxMap=0001 and SataPortMap=9 to get all my 6 HDDs to work.
Your Guide was a perfect help.
You can change your Topic to 2023 now. 😀
That sounds like a success to me! I will think about changing the year to 2023 hahaha.
following this, i got an Error on the backup steps (filled up the 1gb image)
to get around this, i had to do:
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh
backup now;
I see! How much storage does your usb have and could that be the reason for this error?
Hi, i’ve just inherited a N54L microserver with 2x 3tb (WD Red) hdd’s, i’m trying to get DSM installed, i’ve flashed the modded bios to it you linked above and using a 32gb sandisk usb 3 key to boot redpill. I went with the automated redpill loader and set it up as the ds3266xs+ same as yourself, it builds the bootloader and i get an ip address followed by “Loading DSM Kernel” then “Booting” but i cannot find the device in synology assistant nor does navigating to the ip address itself do anything. I have tried disabling the C1E option in the bios as you said but no change. I’m stuck here, any tips would be appreciated 🙂
Got it working using Tinycore Redpill instead of the automated redpill script which i figured out was freezing on boot. Applied the modified bios and got added another 2 WD Reds in there. Also figured out how to enable SHR raid modes, not sure if shr is needed but thats what i use on my real synology DS418 and DS920 boxes so figured i’d stick to what i knew.
Congrats on getting it working! Enabling SHR was a setting you need to enable after installing DSM if I recall correctly. I believe I have done the same on mine but I would have to turn it on to check.
Hi Mike, I have a HP 54L since 2013 but I never upgraded and since few years I was not using it. I would like to upgrade the system but I am newbee since I am lost if I want to redo it now ! Could you tell me first how to upgrade the bios step by step ? Then apparently if we wnat to continue to upgrade to DSM 7.2 or upper we need to use something different than AFAIK ? How could help me step by step ? I was also with Esxi and I do not know if I can still have it as I would like to have VM in Linux and W11. Do you know if it is possibvle to add to the 54L a graphic card for the VM in Windows ?
Not Mike but I can add the instructions to updating the bios to the post if you want.
I am trying to install on a N54L with the custom Bios installed and the default settings. I have downloaded TCRP loader v0.9.4.0 and I can successfully do all the steps and reboot. However, synology finds no drives. Not on the 5th sata or any of the bays. Individually or all installed. I can see them in the BIOS and the boot, but not in TCRP. Even if I boot in the setup to make changes, in the screen that shows the hardware information, the disks do not appear.
The setting in BIOS is AHCI, so that is not the issue.
Any ideas?
Trying to install to N54l with mobbed BIOS and all the steps successfully followed as indicated above. Using v0.9.4.5 TCRP loader but when i load find synology, once I click to accept and start installing, it either gives me a not found network error or when I do succeed, it finds no disks at all to install. I have a single 250GB WD empty disk, that I am trying with. Any ideas?
I would recommend starting fresh and follow the steps detailed on my blogpost. You mentioned you are using a different loader or newer version, maybe that is part of the issue? From the installation page I get this:
“NOT ALL HARDWARE IS SUITABLE:
DSM 7 has a new requirement for the initial installation. If drive hotplug is supported by the motherboard or controller, all AHCI SATA ports visible to DSM must either be configured for hotplug or have an attached drive during initial install. Additionally, if the motherboard or controller chipset supports more ports than are physically implemented, DSM installation will fail unless they are mapped out of visibility. On some hardware, it may be impossible to install (particularly on baremetal) while retaining access to the physical ports. The installation tutorial has more detail on the causes of this problem, and possible workarounds.”
Regards,
Tom
The loader is the only one available. There is no way to find the 0.8.0 anywhere anymore.
I think version 0.9.3.0 of TinyCore is what I used for my N54L. It can be downloaded here: https://github.com/pocopico/tinycore-redpill/releases/tag/v0.9.3.0
That did the trick, thank you my friend.
Happy to hear that helped.
Any idea what is the maximum 7.1.1-42962 version we can install? Can we go up to update 5 for example?
That I do not know. Maybe the xpenology forum https://xpenology.com/forum/ has the answer you seek.
I managed to upgrade to the last version , update 5 whitout issues.
Hp N54l , bare metal instalation
How do you apply the additional updates?
I cannot see any update in DSM after 42962 Update 1?
DSM reports that I am fully up to date?
Thanks!
You download them from the Synology website. Your system will tell you there are no updates if it thinks the system is running well and there is no reason to update.
Someone tried the new 7.2 Version?
Hi There !
Thanks for this post , I’ve decided to switch from proxmox to bare metal on my N54L , I face an issue which I can’t solve
using TC 0.9.4.8 with model DS3622xs , I can see the 6 disks BUT one DSM has booted I don’t have any network
using other loaders (ARC & ARPL) , I have network once DSM has booted BUT it does not see the 5th & 6th disks those not on the 4 bays 🙁
Any idea guyz ?
Thanks !
Have you disabled the C1E option in the bios?
Yes , it’s disabled
I don’t mind purchase a NIC if need be
(BTW , any recommendation for a good CG which can transcode popular format ?)
Thanks
XT
to get all hdds working for me i had to modify
DiskIdxMap=0001 and SataPortMap=9 to get all my 6 HDDs to work.
All good ! after tweaking BIOS , the missing disks are seen under AHCI and now DSM see all of them
forgot to say that I got no luck with TCRP but with this one
https://xpenology.com/forum/topic/60130-redpill-tinycore-loader-installation-guide-for-dsm-71-baremetal/page/34/#comment-445094
so I don’t understand how you guyz can run Xpen with TCRP unlike me 🙂
I’ve used this version of TCRP and others have reported success with this version as well: https://github.com/pocopico/tinycore-redpill/releases/tag/v0.9.3.0
I tried “arpl i18n”, “ARC redpill loader” and TCRP… all failed…until this one (Peter Suh’s loader)…
But other than the 4 regular harddrives, my other drive won’t be recognized even I added below statement…. any help?? thx.
“DiskIdxMap=0001 and SataPortMap=9 to get all my 6 HDDs to work. “
Could you tell a bit more about the versions of loaders you used? Other information that could help with debugging is welcome.
I guess you are in DSM 7.1 right ?
AFAIK 0.9.3.0 is not compatible with DSM 7.2 so you’ll get same issue as me the day you’ll want to upgrade to DSM 7.2
I can share my experience if need be
I think so. Its not my main NAS so I havent looked into upgrading to 7.2.
For me it works with Red-Pill from https://github.com/fbelavenuto/arpl Version: v1.1-beta2a. Steps to do: Upgrade your Bios with mod bios file. Disable C1E in bios CPU settings. Get fast USB Stick and flash it with ARPL Bootloader. Put Usb Stick inside HP N54L. Follow install instructions from github ARP Loader. Choose DS3622xs+ broadwellnk and machine type: 46962. Important: After create bootloader go to Advanced Menu and before boot select the “Switch direct boot” option to activate it and boot. The last setting did the trick to get running DSM on N54L HP Microserver.
Sadly I’m having no luck with this. Tried many times. Using finds.synology.com finds it and takes me through two pages of terms and then won’t progress any further. I’ve done the C1E and direct boot things too. I’m at a loss! It’s so frustrating as you are not the only one who has success. I would love to have a eurika moment!
Hi,
Thanks for commenting. Could you maybe walk us through what steps you have taken so that we may be able to help you?
Regards,
Tom
Have installed as per above guide using Tiny core v0.9.3.0, installed 7.1.1-42962 (with Update 1), and then used the update function to update to 7.1.1-42962 Update 6. Can the N36L support 7.2?
Thanks.
I’m not sure the N36L can support 7.2 but if it supports 7.1 I would suspect it can support 7.2. I see the new version of the tinycore-redpill:https://github.com/pocopico/tinycore-redpill/releases/tag/v0.9.4.9c loader has support for 7.2.
Hi Denis, did you use a modded BIOS on your N36L?
well my issue is when i manually updated to 7.1.1 update 6 through the web UI, i ma now stuck in recovery and when i recover it just starts again like a loop. Do you know how to fix this i am trying as im new Xpenology i usually use OMV but i do like the simplicity of this, i am trying to build for a friend as it would be easy to swap disks then doing it the SNAPRAID way.
thanks.
I did a search on the update and xpenology and found the folowing: https://xpenology.com/forum/topic/64619-dsm-711-42962/. It seems the update does not work with this version of the Tinycore loader. Have you tried using a newer version? Before updating DSM it is advised to check the updates forum to ensure compatability with the the current setup: https://xpenology.com/forum/forum/78-dsm-updates-reporting/. As installing a non compatible update results in a broken system.
Yeah i figured. It looks like that max supported version is 7.1.1-42962. as i tried to load 7.2 and it does the same. Update 6 of 7.1.1-42962 didnt work did not matter what i tried would not come back online. Is there any downside staying on 71.1-4262. Will all apps and docker work as normal.
Thanks
The only downside I can imagine is missing out on security updates and/or features. Just don’t expose it directly to the outside (the internet) and you should be fine. All apps should function without issues including docker. Also I see new releases of the loader that should support 7.2 you could try that and let me (and others) know the results?
Regards,
Tom
Anyone had any luck with Xpenology 7.2 on HP Microserver Gen 7 ?
Would love to update, because i wanna use the immutable snapshot feature…
update: got 7.2 working now on my N40L with 4x 16TB HDDs
even migration vom 7.1.1-42962 to 7.2.1-69057 worked like a breeze (no loss of settings + data)
i used arc loader 23.10.3 (https://github.com/AuxXxilium/arc)
key to success was setting “Direct Boot” to “true” (https://github.com/AuxXxilium/AuxXxilium/wiki/Arc:-Direct-Boot-Option)
Model: DS3622xs+
Pat file: DSM_DS3622xs+_69057.pat
Maybe this helps someone.
best regards
Thanks for the feedback! I’m sure this will help the people wanting to test out 7.2.
THank you – just commenting to say this worked for me to get 7.2.1 installed on my N54L.
Steps in OP wouldn’t boot for me.
Most confusing part was the VGA interface of ARC loader didnt load but accessing via web did. No issues from there, can see all 6 drives – thanks for the tip of using ARC
I have 16G memory installed, but 12.3G memory is set as reserved part, any idea to fix that?
I tried to add “disable_mtrr_trim” in grub.cfg but it caused system hang.
I haven’t encountered this before but does it say why its reserved? This might be relevant to your issue: https://www.reddit.com/r/synology/comments/jxfwki/1621_with_32gb_ram_50_reserved/
Can anyone share how they got this working on a N36L? I’m having issues after the friend boots. No network connectivity after the message “nothing will be displayed here anymore”. I have disabled C1E option.
Update.. Actually got it to work using the installer mentioned by Denis. However it only sees 4 drives. I was hoping to utilize the internal CD port as a 5th drive.
maybe see my comment from 5th of june. 😉
Hi.
I followed this guide to install DSM 7.2.0-64570 on my N40L microserver.
I used Tinycore version 10.
All seems to be ok. When it boots I see dhcp assigned an ip but I can’t ping and Synology assisntant doesn’t detect the device.
C1E state is disabled.
I’ll try with original BIOS and hacked one with same results.
Any clue?
Thanks.
Have you checked DSM 7.2.0-64570 is compatible with your machine or Tinycore? Furthermore if you see an ip has been assigned can you go to that ip in a web browser? It should redirect you to port 5000. If you have more information you can share with me let me know!
Hi.
No I can’t go to the assigned ip through the web browser. Even through port 5000. Time out.
No ping. But I can see the ip because I connect a monitor to the microserver.
Initially I tried to mount DSM 7.2.0-69057 but it said not compatible. Then I installed 7.2.0-64570 (I see this version when I upgraded the loader) with success. I boot the loader and I see the ip but I can’t reach it.
I don`t know what I’m doing bad.
Thanks.
Does the ip start with 169.? If so there was no actually ip assigned via dhcp but rather the machine gave itself an ip. You are using Tiny Core V10 and DSM 7.2.0-64570 on a N40L right?
I have an installation error when installing on N54L.
The pat file available to download from your posted link is 7.1.42661 while the command I have used, by following your advice above, is “rploader.sh build ds3622xsp-7.1.1-42962”
When I try to install the pat file, the installation fails at 57%, the exact error message is “you have to use an installation file of 7.1.1-42962 or later”.
There are so many files to download on Synology website, can you help?
Thanks
Derrick
Hi Derrick,
For the DSM version I used you go here: https://www.synology.com/en-us/support/download/DS3622xs+?version=7.1#system
Download the file and give it a try!
Regards,
Tom
Someone who installed latest Version on HP N54L? If yes which loader and which settings?
N40L must noch be the same like N54L.
I’m thinking about updating the post with known working configs people have shared in the comments per software version i.e. 7.2. What is the latest version you are referring to?
TCRP v0.9.4.3 DS3622xs+ on DSM 7.1.1-42962 Update 1
But I´m interessted in the ARC loader.too from https://auxxxilium.tech/redpill/ to change from TCRP.
Hi all,
I have tried and tried and tried the BIOS MODS website to download the approparite bios firmware. However, I can not get the links to start a download, and none of the moderators seem to be replying to my messages. Is anyone able to email them over to me directly?
I’ve uploaded the files I used here: https://mega.nz/folder/rBMGVCxB#h5jdbzv7tfPliyUhnqqEDQ
Thank you very much!
Thank you for taking the time to leave a comment!
Unbelievably helpyful. Thank you so much.
Ok… Next drama. Followed instructions to the letter… And I can now find the NAS using synology Assistant. However, It states that DSM is not installed. So, I attempted to install DSM but it gives error “FAILED TO INSTALL THE FILE. THE FILE IS PROBABLY CORRUPTED”. Any ideas???
CANCEL THAT. I was using the wrong PAT file!
So it is working now? 🙂
Hi,
First of all, amazing tutorial. I couldn’t believe my luck when I stumbled onto this page explaining how to do exactly what I was trying to do.
I have an N54L that was setup by a friend with xpenology running DSM5.0, which I used to serve my music via Plex, but Plex aged out of DSM5.0 so I’m trying to upgrade it to DSM7.1 as per your instructions.
I’m a noob to all of this but read everything I could find and successfully got through the entire upgrade right after rebooting and changing the C1E setting in the boot menu without issue. But, when I rebooted the GRUB menu doesn’t show the options for Redpill, only the Tinycore option. Do you have any advice on why this might be happening?
Congratulations on upgrading your xpenology! I haven’t ran into this issue before but I’m thinking you could just re run Tinycore?
Thanks for the lighting fast reply. No idea what I did the first time but it has worked the second time around and was able to select redpill from the GRUB menu. Only now it’s stopped at ‘booting the kernel’ which I understand is normal but i can’t find it using Synology Assistant. It’s not connected to my router (no IP assigned) so I assume it’s a network issue. I’ll have a poke around online and see if I can find out what’s going on. If you have any advice on first things to look at please let me know.
Appreciate the help so far!
Is this likely part of the problem?:
Loading initramfs…
error: file ‘/custom.gz’ not found
I would take a breather and look at whats working and what is not. Is the only problem not having network now?
Hi Tom,
Ok, so I’ve tried a few more times and I’m still having the same problem. I noticed the BIOS clock was incorrect so that has been fixed. Synology Assistant is still unable to find it and my router can’t see it so it’s not assigning it an IP address. It’s not a router issue as the router see’s it when it’s booted into Tinycore.
The inconsistencies I’m noticing between what I’m getting and what I’m seeing on successful install logs online are:
-the GRUB menu doesn’t display Tinycore as an option once the command sequence has been run and server rebooted, only Redpill options.
-after selecting Redpill USB from the GRUB menu I get an error saying file ‘./custom.gz’ not found (though I can see it being copied during the build command).
I don’t want to keep taking your time and filling your page with troubleshooting so I’ll ask one last question before I take it the the xpenology forums. Do you know if custom.gz stores the detected hardware information? If it’s not aware of the NIC, that would explain why the router can’t see it.
So you are getting an IP when booted into the tinycore image builder but not when you boot the image? I’ve spend some time during the weekend setting my system up again and found that my grub entries have the image and the tiny core option. If the loader complains about a file not being present that would explain the issue you are facing. How are you confirming the system boots fully without network being present? Also, I don’t mind us debugging it in the comments but enlisting the help of the forum is not a bad idea!
That’s correct, I’m getting an IP when booted into TinyCore. I actually made a post in the forum yesterday that has more detail:
https://xpenology.com/forum/topic/70202-issues-installing-dsm71-on-hp-n54l-microserver/
It includes a section of the build command output where some errors are occuring that are likely related to not being able to find ‘custom.gz’, including issues with grub.cfg, but I don’t know enough to be able to interpret them towards a solution. I expect the system isn’t booting fully with RedPill due to all these issues, hence no IP.
Thanks again for the help!
I’ve read the forum post and would suggest adding the actual commands you used to get to this result.
Added, thanks.
I found something cool! When booted into the image builder there is a web interface available on the ip of your xpenology box. If you go there you might see some more information although you might need a newer version of redpill. I used the most recent version and seems to work for me.
That web interface saved me! I went with the latest image of TinyCore RedPill (v0.10.0.0) and navigated to the web interface as you suggested. I was surprised to find it was prefilled with all the correct loader information you outlined above, does it determine what is required from scanning the hardware?
The number of ports was different to what the earlier version was finding so I went with what was suggested. Build went off without a hitch, booted into RedPill without issue, router found it no problem, was able to load DS3622xs 7.1.1-42962 Update 1 pat file and migrate all my original files and settings. Seems to be stable and working without issue
Not certain if the TC loader version or different number of ports I was giving it was causing my original dramas but all seems to be solved (touch wood).
I owe you a lot of gratitude for your help and patience. Thank you. Props also for the original blog post, super helpful.
Good to hear, stuff like this makes my day! Could very well be that it tries to identify the system it is running on. If you interested in learning more about docker and containerisation, it is possible to run Plex and other apps as containers on your xpenology box.
Definitely made my day too! Always happy to learn more. What is the advantage to running Plex as a container as opposed to just installing it as a package in Synology?
The main advantage I see is that you are no longer depending on the maintainer of the Plex app. Containers do not depend on the OS but rather if Docker is present which also makes them highly portable. Lets say you add some more apps like Sonarr and Radarr, you could then automate the deployment with a docker compose file. This allows you to run your setup on any machine with Docker installed just with a single command!
There are probably more advantages depending how you look at it and who you ask. The learning curve can be quite steep but the experience you gain will make it worth while. I use portainer to make management a bit more user friendly see here: https://mariushosting.com/how-to-install-portainer-on-your-synology-nas/
anyone tried the arc loader ideally with 6 hdds on n54l?
https://auxxxilium.tech/redpill/
A quick google search showed me that I had to disable the C1E option, under the Advanced CPU settings, in the BIOS for the internal NICs to start working.
crazy… i am going through a lot of different options with a supermicro board, and this one had not come up once. my nics die(d) on boot of DSM.
Tom,
Thank you for publishing this guide. I found it enormously helpful in getting XPEnology running on my N54L. I have a question about updating. You wrote “…after each update I booted the TinyCore friend to update the loader” How redpill provides boot loader functionality for XPEnology is not at all clear to me. Would you mind sharing which specific commands you ran to update the loader?
Hi,
So after installing an update you reboot and select the TinyCore Friend option at the boot select menu. In turn it will update the loader to match what you updated to. Does that make sense?
Regards,
Tom
Yes, it made sense after I did it. Thank you.
Hi guys,
I also managed to install the newest 7.2.x with the archloader, modded bios flashed,C1E disabled and direct boot…
I’m just wondering if someone has experience in disk encryption with the n54l? If I’m not wrong, the cup does not support AES encryption in HW?…
@Haris do you have to modity DiskIdxMapand SataPortMap for the arc loader especially the esata Port? Or just auto-install?
Maybe your can explain the upgrade steps
thx
Open link for example in edge and autotranslate in a language of your choice.
https://xpenology.com/forum/topic/18601-tuto-dsm-7-pour-hp-n40l-et-hp-n54l-gen7/
After all the commands, I get to the DSM installation page. After installing and rebooting, I get to the DSM installation page again. What am I doing wrong? HP N54L
Some more information would be helpful. If you followed the blog to the letter you should have a working system. So take me through your process.
1. Change BIOS
2. Put in port 5 SSD
3. Download and install (tinycore-redpill.vX.X.X.img.gz (for BIOS/CSM/Legacy boot from USB flash drive))
4. Start my NAS with the USB and TinyCore is booting.
5. Run command:
./rploader.sh update
./rploader.sh fullupgrade
./rploader.sh identifyusb
./rploader.sh serialgen DS3622xs+ realmac
./rploader.sh satamap (try change value from 6 to 8)
value 8 i see over web interface
./rploader.sh build ds3622xsp-7.1.1-42962
./rploader.sh backup
./rploader.sh backuploader
6. Load DSM installation page and install DSM, reboot
7. Load DSM installation page, manual reboot
8. Load DSM installation page, manual reboot
…..
I assume by port 5 you mean the port where the DVD drive used to connect? Why are you touching the satamap as its not required when using 4 drives in the regular spots. Does it work when following the post to the letter?
You mean i can skip the command: ./rploader.sh satamap
After command ./rploader.sh satamap, it shows me 6 ports for default.
I would suggest go with the default so you can confirm that works before making changes. Let me know if that solved your issue.
No, it doesn’t work. I tried this it first time. i tried to change sata port from 5 (DVD) to sata 1.
I tried to use TCRP 0.9.3.0, it nothing helpful.
In finally i used this link:
https://xpenology.com/forum/topic/18601-tuto-dsm-7-pour-hp-n40l-et-hp-n54l-gen7/
So you got it to work?
Yes? but not over TCRP
Interesting! Good to hear you got it running.
Hi Tom,
May I know what will happen if N54L with the BIOS moded (latest BIOS 01/10/13) long time ago and the battery drained out? The reason I asked is because I found the machine’s usually with the wrong date and time when I checked it on BIOS. Also, on the AHCI setting page, it only showed 4 hard drive. The other hard drive that I connectted to the dvd drive can only be found as a IDE drive… I am not sure if it causes the failure the xpenology setup. Thanks.
I assume the BIOS settings will be lost and reverted to the default when the battery is drained completely. But I haven’t tested this on a N54L per se. Replace the battery let me know haha.
Many thanks for the reply.
So, it that mean I have to apply the Mod BIOS again? I haven’t buy the battery yet and I will definitely let you know if I replace it. Thanks again.
The bios will not reset to a previous version. Its only the settings that will reset to the default. So if you flashed the modded bios it will still be there when the battery runs dry.
My hacked 041 BIOS had date 1/10/2013. from the BIOS “AHCI Setting” page, I can only find 4 harddrives which put on the normal bay… the one drive that I attached on the DVD rom can’t be seen in here. It is recognized as a IDE drive… Any suggestion? thanks.
Many thanks for your reply.
I replaced the new battery and everything run great now. I am using Peter Suh’s loader (v1.0.4.0) with the DSM version 7.2.1 – 69057 u5. All 5 drives are recognized.
thanks again.
Hi,
can anybody tell me wich latest DSM Version is running on HP N54L with the Loder TCRP in V10.
I have installed DSM 7.2.1-69057 Update 5 only with this Tutorial.
Thanks Tom!
Hi Tom and community – just wanted to say thanks for the guide. I used it with my N54L to go from DSM 5.0 to about 7.1.1. I got stuck and couldnt go any further and obviously quickconnect wasnt working due to being a non official synology device. I have since found the following video and used ARC Loader to build a later DSM (7.2.2-72806) using the DS 3622XS+ software. I followed the following youtube video for anyone interested. I have no affiliation, but was impressed with what I have got now. Thanks again.
https://www.youtube.com/watch?v=gC102SqxQ1Q&t=433s
Hi Dan,
Thanks for leaving a comment. How exactly did you get stuck? Good to hear you got it working in the end though!
Kind regards
Tom
Not sure mate – tried to follow your path “7.1.1-42962-1–>7.1.1-42962-6–>7.2-64570-1–>7.2-64570-3–>7.2.1-69057” but it just wouldn’t go past 7.1.1.
On another note – was considering now going to place a couple of big drives in there. I see that someone mentioned above that they have 4 x 16TB in theirs. Have you had any luck with these larger drives? Just want to make sure before I buy some.
Thanks
Dan
From my understanding it should handle bigger disks just fine. I read somewhere that if the server is powerful enough there is no real size limitation but I could be wrong.
Hello together,
Really great sharing, but for me and my N36L, still not work. No matter ARC or RR, all facing the same problem — No NIC found, even the ethernet lights works. So i can even not config the loader. Wired! And i have flashed the Bios, and keep the C1E disabled.
Have searched around, no idea for me.
Any idea from you guys ?
Thanks!
Hi!
I found the following thread regarding the N36L: https://xpenology.com/forum/topic/54118-hp-microserver-n36l/ . I gather the internal NIC will work with specific versions of DSM but not all. A network card would be the only option of the DSM version does not support the internal NIC.
I think i will never figure this out as it seems to be an Hardware problem. I can only find 1 similar case from the internet.
https://forums.overclockers.com.au/posts/15863895/
One of the comment from Hyram :
” I didn’t get that far yet, I just discovered that the BIOS sees a drasically different MAC address for NIC#1 tan what’s printed on the board itself.
The sticker says it should be 98-4B-E1-08-81-75 but the BIOS reads it as F0-00-EE-00-EE-F3.
Now that looks just plain wrong.”
Hyram was facing the same problem as i do. As the MAC Address in Bios is not the correct one from the sticker on motherboard — even the same as mine.
Luck him that he has already found a “solution” — from my point of view, maybe a coincidence:
“It lives! It lives again and hope shines forth with a blue glow!
Found out what the problem was. It seems lovable ol’ Bazza took to the innards of this particular N36L with an industrial-strength air compressor every few months to clear out the dust. I lifted off both of the removable heatsinks and underneath the larger, more central one I find not only a healthy brick of dust under the lip of the green silicon carrier board, but he’s managed to blow most of the silver thermal paste out along one side where it’s shorting the on-carrier decoupling SMD capacitors.
Clean both exposed chips, clean very very carefully around the carrier lip, apply a fresh drop of IC to each, and clip the sinks back on. Slider ‘er in, hook ‘er up, press the button and I get red-black-red-BLUUUEEE from the status light, woohoo!! Hooked up some vid, dropped one of the other install drives in, reboot and we have Win7 with *working* internet.
DON’t clean yer kit with compressed air, ya nongs!”
Doesn’t work for me. Also it does not make sense i think.
I am a little bit tired of keep trying. i am think additional NIC. — Hope it will work.
Thanks Tom and all of you guys!
Hello Tom,
is your N54L still in Hardware Delivery Condition. Im thinking about expanding memory to 16GB but i found the notice about the memory reserved problem.
Ist the modded N54l with new bios and Exnology still fast enough?
Greez
Hi,
Would I still run the N54L at the moment probably not. There are so many cheaper and more powerful alternatives available that it doesn’t make sense to put money towards keeping it running or upgrading the RAM. I recently installed a K1200 in mine just because it was cool.
However if the goal is to run only xpenology it should be fine. I also upgraded mine to 16 gb.
Kind regards,
Tom
My N54L is running as data grab bit modded to use all sata/esata ports for hdds. Boot with USB Stick and Windows Server.
As i found your Instruction i was woundering i should also do it.
Can you recommend a better cheaper alternative?
Thx
Greetz
AW
Depending of what you require of the system the cheapest alternative could be using what you already have. The N54L is now eleven years old and newer models have been released by HP that might have hit the secondary market. That would be a good way to get more bang for your buck. Would be worth checking the xpenology forums to see what others have chosen to run DSM on. Let yourself get inspired, I’ve even seen people that virtualize xpenology within proxmox making it possible to run it on nearly any machine.
Kind regards,
Tom
I want to upgrade the RAM from 4GB to 16GB. Can anybody tell me what is the right for my N54L?
Greetings
I will try and find the exact memory I bought for this system.
I just upgraded to 16 gb. Bought from this listing on eBay -https://www.ebay.com/itm/153427743468
The boot up recognized 16gb as did the Synology info center.
I recently got memory from this listing https://www.ebay.com/itm/153427743468
The boot up recognized 16gb as did the Synology info center.
2x8GB PC3-10600E (DDR3 1333MHz). You can find it cheap in ebay.
Be aware that it must be ECC RAM (10600E, not 10600U!!!)
Thanks for this great post with such clear instructions. I just updated my n54l from 6.23 all the way to 7.2.1-69057 without any issues or loss of data! Fairly releived to be running a more current version.
One question – I see that the DSM update is telling me thatere is a new version available – DSM 7.2.2-72806 update 2. Where can I check, what research should I do to make sure this would be compatible?
Thanks for commenting! Happy to hear my post allowed to update/upgrade your system and without issues. For any future updates I would ask around the xpenology forums to see if anyone tried the update with this system before. Alternatively you could set up a test system and perform the upgrade there.
Thx for your experience upgrading from 6.2 to 7.2
Can you tell me, which way you took? Do I have to reinstall from scratch, or is it possible to do some kinde of updates in a row?
Just updated via the update feature in DSM. I don’t know if you can skip ahead to the latest or apply multiple.
Hi Richtw,
Can you share how you did the upgrade from 6.23 to 7.2.1-69057 ?
I assume that for 6.23 you need to use Jun’s loader 1.03b but 6.2.4 already won’t work anymore with this loader because the N54l disappears from the network then.
I already have issues to install 7.1.1-42962 as described by Tom. I cannot succeed the setup with the message “The DSM setup failed Cannot install the file. The file is possibly damaged.”
Is it possible to switch loaders during updating and if so how did you do it?
Did you just download the updates automaticly or a manual upload?
Should be great if you could share it.
Many thanks in advance
Kind regards,
André
Hi Tom,
I followed Your instructions (disabled C1E in the BIOS) and executed all the commands with Tinycore Redpill v0.10.0.0 with a PuTTy SSH connection. Tinycore assignes a correct IP Address. All commands were completed succesfully and after reboot for the first time I see all text onto the boot screen is normal with some green text (before I saw yello and red text).
After rebooting the HP Microserver is still not visible because there’s no IP Address assigned to the internal (onboard) NIC.
DSM 4.3 was always running OK for years.
The machine is a HP Proliant Microserver N36L with 8192 MB RAM and dual core processor operating at 1300 MHz
I also tried to build the loader with the webpage withTinycore version 0.10.0.0 which failed with DSM7.x.x as also with DSM 6.2.4.
Any idea why there’s no IP Address assigned after reboot?
Regards,
André
Hi André,
There should be a Tinycore boot selection screen where you can select different options like start from USB, SATA or start the Tinycore friend. You describe you are seeing text both green yellow and red. This makes me believe that you are actually booting the Tinycore friend. If you could confirm my suspicion that would be great.
If that is what is happening you could try and switch boot options and see what happens.
Regards,
Tom
Hi Tom,
Also see this during the configuration:
tc@box:~$ ./rploader.sh identifyusb
Found more than one USB disk devices, please select which one is your loader on
1) Silicon
#? 1
Selected Device : Silicon , with VendorID: 0x090c and ProductID: 0x1000
Sorry, no usb disk could be identified
Is this also a problem? There’s only one USB drive connected but there are 5 USB slots on the HP Proliant Microserver N36L (one onboard which I normally use and four outside).
By using ESC during start after reboot Tinycore build I can catch a boot menu to start from USB, SATA, Tiny Core Image Build and Tiny Core Friend.
After I choosed this option the NAS was visible with a assigned IP Address and I’ve got the NAS visible in the Synology Web Assistant.
I used the latest version of Synology Assistant and also tested find.synology.com in Google Chrome. Both worked correct.
Installing DSM ds3622xsp-7.1.1-42962 through Google Chrome:
First I’ve selected migrate and option reset system configuration (only keep files), NEXT, and select the DSM_7.1.1-42962_DS3622xs.pat file.
The migration failed!
Second installation with option keep systemconfiguration (keep files and settings), NEXT, and select the DSM_7.1.1-42962_DS3622xs.pat file.
The migration failed also!
The latest Synology Assistant automaticly opens your browser for instal the pat file.
So the last test was with the old Synology Assistant 2.3-1157.
In this assistant I could directly select the pat file but also here the installation failed.
– Cannot setup Synology Server (Errorcode: 5)
– An error occured during the installation. The Telnetprotocol of Diskstaion is enabled to find the errors.
I’ve tried to install DSM with booting:
RedPill DS3622xs+ 7.1.1-42962 (USB, Verbose)
RedPill DS3622xs+ 7.1.1-42962 (SATA, Verbose)
The last selection in the boot menu stays active after a next boot.
Both options fails while installing DSM_7.1.1-42962_DS3622xs.
I don’t think the results of identifyusb matter in this case. Your system seems to successfully boot DSM as you are able to see it over the network. I’m reading different things related to failed installations and one thing could be the network. Try updating the NAS from a direct connection or as close as a direct connection as possible. Lastly I read that error code 5 could have to do with the disks (see https://community.synology.com/enu/forum/17/post/6603). I hope its just network issue and not actually a disk issue.
Did you follow the instructions in the blog precisely?
EDIT: Also be very careful when messing with disks and be sure to have a backup before continuing.
Hi Tom,
This week I bought a HP Microserver N54L with 8192 MB memory on board.
I disabled the C1E option in the BIOS.
Followed exactly your procedure for configuring the bootloader by using TinyCore-Redpill.v0.10.0.0. After reboot the NAS is visible on the network so Synology Assistant will find the NAS with the message configuration lost at version 7.1.1-42962
I use the Google Chrome Browser to install the DSM image (pat file) downloaded from the original Synology archive. For the DS3622xs+ I can only find version 7.1.1-42962 (with update 1).
In the browser (which I used also for installing older versions with success on other HP Microservers) I see the welcome screen and choose the Migrate button (the only option) and in the following menu “Reset System Configuration (only keep files)”, then Next and on the screen that follows the option to select the DMS image. The image is correctly uploaded but at ca. 56% the installation is failing again with the message:
The DSM setup failed
Cannot install the file. The file is possibly damaged,
I also tried the other option “Keep System Configuration (keep files and settings)”
Same result
The HP Microserver N54L has also two extra network cards, one in a normal PCI slot and one in a PCI-e port. Also by using these ports at another IP address the setup fails.
Last option was again with Synology Assistant version 2.3-1157, This is an older version where you can directly install the DSM image without a browser.
The process:
1. Applying network settings
2. Format disk – format systempartition
3. Install the firmware to the hard disk
4. Write configurations
Step 1 takes a lot of time. It seems that the network settings are not correctly applied. It doesn’t matter which port I use. I have four ports. One onto the mainboard, a PCI card with two ports and a PCI-e card with one port.
Message: the fast configuration could not be finished because of a connection time-out.
What I also have test:
Installed succesfully DSM_6.2-23739_DS3615xs on another HP Microserver N36L with 8192 MB memory. But after updating to DSM_6.2.4-25556_DS3615xs the NAS didn’t show up anymore in the network (booted with Jun’s boot loader 1.03b)
So I don’t understand how you succeeded to install DSM 7 at your HP Microserver.
The reason I want to use this version is that Let’s Encrypt isn’t working anymore at DSM 6.2.1
The Let’s Encrypt DST Root CA X3 certificate has been expired since September 30, 2021. For DSM 6.2.3 and below, you must update to at least DSM 6.2.4 Update 2 to obtain a Let’s Encrypt certificate.
Well even DSM 6.2.4 I cannot run.
I’m lost…
I also tried the web interface of Tinycore Redpill to build the image but that will also not work, After reboot and selecting start from USB nothing happens because the zImage file is missing.
And I tried the Automated Redpill Loader (ARPL). The loader was build and after reboot everything seems to work normal and I even got an IP address assigned but after 5 seconds it rebooted by itself and stayed into a boot loop after every start.
I don’t know what to do anymore.
Any suggestions?
I’ll wait for your respionse.
Wit h kind regards,
André
Hi André,
After reading what you shared my suggestion would be to start over with the N54L. Put in a hard disk you can use for testing (one that is not important and can be formatted if need be). Reset the BIOS of the N54L to optimal defaults. If you have multiple network cards you can do without disabling C1E. Now follow the steps in my post and share the results, we can take it from there.
If you have other information about the network environment your N54L lives in I would like to know but we might have to switch to another form of communication. I’m active on bluesky and discord.
Kind regards,
Tom
Hi Tom,
I already used a single HDD which may be formatted.
BIOS load optimal settings I already did by default. (BIOS is the latest firmware)
When I enable C1E the NAS is not found anymore in the network.
Tried again with Automated Redpill Loader (ARPL) several versions but the NAS was not visible in my network,
So again with Tinycore Redpill without any success. Also tried the DS3615xs because this setting I’ve used to run DSM 6.2.1 successfully.
./rploader.sh fullupgrade
./rploader.sh identifyusb
./rploader.sh serialgen DS3615xs realmac
./rploader.sh build ds3615xs-7.1.1-42962
./rploader.sh backup
./rploader.sh backuploader
exitcheck.sh reboot
After reboot and used ESC to catch the boot loader selected boot from USB.
The NAS came up in my network. Setup in Google Chrome was not a migration now but seen as a fresh installation by Synology.
Selected DSM_7.1.1-42962_DS3615xs.pat image.
Same result as I reported before.
I don’t know how the setup a DSM 7 station anymore.
P.S.: I couldn’t find your account on bluesky and discord.
Kind regards,
André
I see! Well I can be found on bsky here: https://bsky.app/profile/tomvanveen.bsky.social . Lets chat there 🙂
Kind regards,
Tom
Hi Tom,
Just registrated an account at Blueskyand found your profile. I cannot sent you a private message because you have disabled this into your settings?
My account: https://bsky.app/profile/andre7968.bsky.social
Kind regards,
André
Well I tested with Arc Loader version 1.5.5. and did a full automatic build for the DS3622xs+ which succeeded on my HP Microserver N54L. The webportal was loaded correctly and I could install DSM_7.2.2-72806_DS3622xs.pat
Finally it works!
https://auxxxilium.tech/redpill/
Last week I installed DSM 7.2.2 on a HP Microserver N36L (1300Mhz-8GB RAM). Updated from the old version Xpenology 4.3. Works like a charm and all data was migrated. Just prepared an USB stick with ARC Loader and started. Update 3 was automaticly installed during the setup. Only minor of ARC Loader is the long boot time. Another thing is when you do the setup with just one HDD it will not detect HDD 2, 3 and 4 anymore when installed after setup DSM. Then you need to use ESC during startup and reconfigure the loader. There’s a extended menu where you finally find an option to select a tower model with 4 HDD’s. By selecting this option and rebuild the loader it will detect the other HDD’s at next boot. When at first configuration of the loader four HDD’s are installed, DSM directly finds all the disks. Means that ARC loader doesn’t detect inactive SATA ports during the automatic configuration.
Kind regards,
André
I installed my N40L today with latest Arc Build v 1.6.5 with automated mode and model DS3622xs+. Works like a charm. No special config needs to be done anymore.
Finished from Rufus2USB till final DSM Boot within 20 minutes :o)