Search the Community

Hi all My hardware is a hp n40l and on it I have DSM version 7.2 installed to it I am connecting a UPS by APC model Smart 750i after activating the power menu in my DSM under the UPS tab it does not detect the UPS.

I revived my old N40L Microserver again. Put in the power cord and booted her up. Running well. It's running with the below version, June's loader. I'm not sure what version loader. I wanted to try and update the DSM with a more recent version but not sure where to go first. The microserver is stock. It does not contain a extra NIC. I think I have changed BIOS years ago. To add extra SATA port capabilities? Anyway, what are my options? There is a serious amount of family photographs on it. I got those backed up on a external drive but I rather not do a total reinstall. Can I update to new DSM 6.2.3? 6.2.1 needed an extra Intel NIC to function. At some point there was a seperate Broadcom driver available. Does 6.2.3 still need the extra Intel NIC or is it possible to work with the broadcom driver?

Hi, Im running DSM 6 for over a few solid years on my old server and i was wondering if i can update to DSM 7? I checked the other forum posts but i could not find the right answers based on my current setup. Its running pretty good with Radarr, Sonarr, Jackett, Pi-hole, Plex and Transmission in docker so i still don't think i need to update the hardware. Current setup: AMD Turion II Neo N40L, DS3615xs 4bay, DSM 6.2.3-25426 Update 6. TIA

Hi My hardware is HP Proliant N40L. I want to install from scratch DSM 7.1.1 , DS3622XS+. From what I have read on the forum I need to proceed as follows: 1) Update the bios TheBay_Microserver_Bios_041.rar 2) Change BIOS settings according to Ludo 34's guide 3) Successively follow the tutorial . Is this the only effective method? Will the built-in network card work? I'm not comfortable with the command line. Does it work stably, or is it better with this hardware to use version 6.2? Please help me and suggest.

I have a Baremetal HP N40L that had been running for nearly 4 years flawlessly but had a bootloader USB stick die. I've got a new one in there; I restored Jun's Loader synoboot3617.zip so it's 6.2. I've put the chassis' MAC address in there, which I copied from the HP BIOS, used the XPEnolgy Serial Generator, to get a fresh SN, used lsusb to get the VID and PID, double checked that I got them around the right way (fell for that one way too many times!). I restored Jun's Loader onto that USB stick, then mounted the first FAT partition on a Linux system to navigate to the grub.cfg file in /grub/ . Saved it. Unmounted the USB stick, remounted it, checked that it all stuck and it did. I then inserted it into the system and booted. Now, here's where things get weird. DSM emailed me to say that it was shut down incorrectly, Transmission is working, Plex server is working, but I cannot access the DSM desktop, mount any of the shared partitions, and if I scan for open ports, I can only see the Transmission 9091 one as being open. Does anyone have any ideas? This is really very confusing. Synology Assistant can't see it (I've tried two different Win10 PC's and a Linux PC). I re-flashed the bootloader with a PC instead of using image restore on Ubuntu. Now find.synology.com finds it, I select Repair, it restarts it and it's lost again. Plex server is working like before, all the content, which is stored on the Volume1 of this NAS is available to Plex and plays perfectly. I can't mount any of the partitions over SMB. Transmission is also there. Now when I use find.synology.com, it finds it with the correct IP, but the MAC address listing is blank, as is the Server Name and Serial Number. Status shows "Not installed". Synology Assistant application can't see it. What am I doing wrong? I've tried a myriad of different html ports in case that somehow the ports got changed... I've run out of ideas. This system has four years of painstaking curation of very hard to find content on there, and although we can still access it and play it through the Plex service, we can no longer use the NAS as a NAS. It's been ages since I've first installed Xpenology on this system, and fear that I may not be doing the bootloader right. For instance, I'm not sure how to force SSH to be enabled with an option in the bootloader. I've googled but can't seem to find instruction for this. I'm thinking that forcing a DSM software installation / recovery might be a way to right whatever wrongs happened to the server when we lost the first bootloader. Can someone please point me to the instructions on how to do this?

Now i had installed DSM 7.2-64570 Update 3 , my microserver is HP N40L 7gen , bios system was an original at the moment of instalation. Yesterday i was up to date my bios mos The Bay for runnig all empty HDD interfaces. Everything works perfect.

Bonjour, [EDIT] @nicoueron05/05/2023 : révélation de la section BIOS [EDIT] @nicoueron24/11/2022 : ajout section "mise à jour" [EDIT] @nicoueron19/11/2022 : version DSM7.1.1 minimum + adaptations commande suite aux changements du loader >v0.9.2.9 [EDIT] @nicoueron07/10/2022 : fin support <DSM7.1 [EDIT] @nicoueron26/09/2022 : Ajout capture écran paramètre IDE pour avoir les disques 5 et 6 de visible [EDIT] @nicoueron27/06/2022 : support DS3622XS+ et note sur l'incompatibilité de l'USB avec DSM7.1 [EDIT] @nicoueron28/04/2022 : prise en charge de l'USB [EDIT] @nicoueron22/03/2022 : précision sur la pile du bios [EDIT] @nicoueron16/03/2022 : ajout de DSM 7 [EDIT] @nicoueron08/05/2020 : adaptation du tuto pour DSM 6.2.3 sans aucun matos nécessaire en plus. Pré-requis 1 : Vérifier la pile du BIOS Avant tout de chose, le serveur HP N54L gen7 étant maintenant très ancien, je conseille fortement de procéder au remplacement de la pile du BIOS, pour info la référence est CR2032. N'hésitez pas à faire des captures d'écrans des options de votre BIOS avant son remplacement, à défaut les options ci-dessous devraient pouvoir vous aider Pré-requis 2 : Flashé le BIOS avec cette version correctement configurée Celui de 2011 (V041 - 2011): TheBay_Microserver_Bios_041.rar Le Bios Mod: o41072911mod.rom Il suffit de supprimer celui présent sur la clé, de copier/coller le fichier mod.rom et de le renommer comme l'ancien. Vous pouvez suivre ce Tuto qui est très explicite : How to flash Bios HP Proliant (c'est le même Bios pour les 3 servers N36L; N40L et N54L). Une fois le BIOS flashé faites les réglages suivants : Onglet Main: Onglet Main > Boot Setting Configuration : Onglet Advanced > CE1 Support = Disabled Onglet Advanced > IDE Configuration > SATA Controller Mode AHCI Onglet Advanced > Advanced ACPI Configurtation > ACPI v2.0 Onglet Advanced > AHCI Settings > ici il faut vous assurer que TOUS les disques sont bien détectés et que le paramètre AHCI BIOS Support est sur Enabled Onglet Boot > Hard Disk Drives > ici positionner la clé USB en premier Onglet Chipset > ici positionner l'option onChip IDE Type sur IDE 0. Un service DHCP doit être actif sur votre réseau. De même, lors de la construction du loader (point 8), le serveur doit avoir accès à Internet. 1. Création de la clé USB Bootable : Télécharger puis décompresser le fichier tinycore-redpill.vXXX.img.gz depuis le repo github de Pocopico. Dézipper-le avec 7zip par exemple et à l'aide de l'outil BalenaEtcher "graver" le fichier img correspondant sur votre clé USB (2Go - 4Go suffisent). 2. Connecter la clé USB au serveur et booter dessus pour démarrer sur TinyOS (cf. capture d'écran du BIOS pour forcer le boot sur USB en premier). 3. Ouvrir le terminal une fois que vous êtes sur Tiny et entrer ifconfig pour connaitre l'adresse IP attribuée par le DHCP. ifconfig 4. Depuis un autre ordinateur, connectez-vous en SSH via Putty par exemple car beaucoup plus simple pour les commandes à moins que vous soyez à l'aise avec un clavier QWERTY. ssh tc@[IP] Exemple : ssh tc@192.168.0.80 Entrer le mot de passe suivant : P@ssw0rd 5. Le loader est maintenant compatible avec le DS3622XS+, à votre convenance vous pouvez rester en DS3615XS ou passer au DS3622XS+ qui offrira un support à plus long terme. ./rploader.sh serialgen DS3622xs+ et appuyez sur Y pour valider 6. Pour relever le VID:PID de votre clé USB, entrer la commande. ./rploader.sh identifyusb now Et appuyez sur Y pour valider 7. Pour trouver le bon SataportMap et DiskDxMap ./rploader.sh satamap now Et appuyez <Enter> puis sur Y pour valider Ce qui donne par exemple : 8. Compiler votre loader pour votre HP N54L selon le type de Syno choisi et la version de DSM correspondante : ./rploader.sh build ds3622xsp-7.1.1-42962 9. Redémarrer le serveur : sudo reboot 10. Normalement le serveur doit redémarrer par défaut sur la clé USB. Laissez le faire... 11. A l'aide de Synology Assistant ou depuis le navigateur (http://[IP]:5000) se connecter et finir la configuration de DSM. Prévoir d'importer le fichier pat DS3622XS+). enjoy 🥳🥳🥳🥳🥳🥳Votre serveur XPEnology est opérationnel !🥳🥳🥳🥳🥳🥳 ################################################################### ################# FAIRE UNE MISE A JOUR ###################### ################################################################### Pour effectuer une mise à jour (->Update 2 par exemple) : 1. Rebooter le serveur sur TinyCoreOS (dernier choix lors de l'affichage du grub) 2. Lancer les commandes suivantes dans cet ordre : ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh backup sudo su ./rploader.sh postupdate ds3622xsp-7.1.1-42962 Le script doit détecter la mise à jour et proposer de l'utiliser, il faut confirmer avec 'Y' La commande postupdate doit être faite en root, d'où le sudo su juste avant 3. On reboot le serveur de nouveau : reboot 4. Vérifier que l'option de démarrage sélectionnée est bien USB lors du grub. 5. L'écran affiche les instructions suivantes (il n'y a plus rien à faire d'autre de ce coté, c'est normal) : 6. Connectez-vous à l'interface de DSM de manière classique, sinon passez par SynoAssitant !

Да, у меня N40L/N54L,но и на Gen8 так же несложно

Я так понял, у вас N40L/N54L, да? А на Gen8 с Ксеоном кто-то ставил? И еще вопрос - Актив Бекап ставится (ломается ли стандартнім способом)?

Добрый. Предыдущая версия ОС также DS1621+ была? У меня тоже N40L, стоит 7.1.1 update 6, DS3615xs. Для 3615xs нет образов для 7.2. Как можно обновиться на 7.2? Обновиться хочу также по причине периодического зависания сети. Сеть просто отваливается в рандомной периодичностью.

I had builded with friend mode. After them instaled 7.1.1 and update to actual version 7.2. Everything works very well. Bios in my N40L is not updated,as factory made.

Получилось установить 7.2 на HP microserver N40L Версия DS1621+, загрузчик ARC-23.9.0. Ссылка на файлы: https://disk.yandex.ru/d/KccqPx6PfbasBw

Hello all. After struggling for days with trying to replace that broken Jun's Loader, we've successfully used this guide on youtube ... along with all the links to @flyride 's guides etc, and upgraded that RAID set to 7.1.1. I tried going up to 7.2, but that failed. The trick was to remove the failed dataset drives, put in a blank drive, install a new TCRP following these guides, set it up and get it working, then shutting down and installing as per this guy and FlyRide's instructions verbatim. Don't miss any of the steps, note that the list of images has changed and now shows actual model numbers. I used ds3622xsp-7.1.1-42962 for my N40L with C1 disabled and the Russian BIOS hack to get all 6 SATA ports working. Many thanks to you, Mr CloudAutomation, @flyride and @pocopico for all your hard work and help with this process.

Доброго времени суток всем. Возникла проблема с вентилятором на N40L. Купил Aero Cool 12V-DC 0.15A (120 x 120 мм, 4 pin, 500 об/мин - 1500 об/мин, 18.2 дБ - 27.5 дБ), кто подскажет распиновку HP?

Hi I try to install xpnology on my old N40L I have follow thi guide step by step [Tuto] - HP N40L et HP N54L gen7 (DSM 7.1.1) But after the reboot tinycore is presnet and the nas os do not start I can log into tinycore whit putty but no more How I can solve the problem ? Here the commands login as: tc tc@192.168.0.82's password: ( '>') /) TC (\ Core is distributed with ABSOLUTELY NO WARRANTY. (/-_--_-\) www.tinycorelinux.net tc@box:~$ ./rploader.sh serialgen DS3622xs+ Serial Number for Model = 20C0SQRPG0B3H Mac Address for Model DS3622xs+ = 00:11:32:59:2B:30 Should i update the user_config.json with these values ? [Yy/Nn] y tc@box:~$ ./rploader.sh identifyusb now Found USB Flash SerialNumber: FBI1402187000076 Vendor ID : 0x090c Product ID : 0x1000 Should i update the user_config.json with these values ? [Yy/Nn] y tc@box:~$ ./rploader.sh satamap now Found "00:11.0 Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)" Detected 6 ports/3 drives. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=6 DiskIdxMap=00 Should i update the user_config.json with these values ? [Yy/Nn] y Done. tc@box:~$ ./rploader.sh build ds3622xsp-7.1.1-42962 bspatch does not exist, bringing over from repo % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 10232 100 10232 0 0 48723 0 --:--:-- --:--:-- --:--:-- 48723 Rploader Version : 0.9.4.6 Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master Extensions : all-modules eudev disks misc Extensions URL : "https://github.com/pocopico/tcrp-addons/raw/main/all-modules/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/eudev/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/disks/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/misc/rpext-index.json" TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwellnk-7.0.dev.txz/download TOOLKIT_SHA : 0d9edca67d9e7e14c2529bbb58341b623936124d5264f71f1e4acbacf3ea202d SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/broadwellnk-source/linux-4.4.x.txz/download SYNOKERNEL_SHA : d3e85eb80f16a83244fcae6016ab6783cd8ac55e3af2b4240455261396e1e1be COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : ds3622xsp TARGET_VERSION : 7.1.1 TARGET_REVISION : 42962 REDPILL_LKM_MAKE_TARGET : dev-v7 KERNEL_MAJOR : 4 MODULE_ALIAS_FILE : modules.alias.4.json SYNOMODEL : ds3622xsp_42962 MODEL : DS3622xs+ Local Cache Folder : /mnt/sdd3/auxfiles DATE Internet : 27052023 Local : 27052023 Checking Internet Access -> OK Checking if a newer version exists on the main repo -> Version is current Cloning into 'redpill-lkm'... remote: Enumerating objects: 1649, done. remote: Counting objects: 100% (1649/1649), done. remote: Compressing objects: 100% (620/620), done. remote: Total 1649 (delta 1016), reused 1579 (delta 996), pack-reused 0 Receiving objects: 100% (1649/1649), 5.81 MiB | 3.19 MiB/s, done. Resolving deltas: 100% (1016/1016), done. Cloning into 'redpill-load'... remote: Enumerating objects: 4166, done. remote: Counting objects: 100% (998/998), done. remote: Compressing objects: 100% (540/540), done. remote: Total 4166 (delta 519), reused 922 (delta 449), pack-reused 3168 Receiving objects: 100% (4166/4166), 123.43 MiB | 21.21 MiB/s, done. Resolving deltas: 100% (2083/2083), done. No extra build option or static specified, using default <static> Using static compiled redpill extension Removing any old redpill.ko modules Looking for redpill for : ds3622xsp_42962 Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/releases/redpill-4.4.180plus-broadwellnk.tgz Extracting module Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/src/check-redpill.sh Got redpill-linux-v4.4.180+.ko Starting loader creation Found tinycore cache folder, linking to home/tc/custom-module Checking user_config.json : Done Entering redpill-load directory Removing bundled exts directories Cache directory OK Found build request for revision greater than 42218 Downloading extractor v2 Extractor already cached Copying to local directory Creating temp folder /tmp/pat Checking for cached pat file Found tinycore cache folder, linking to home/tc/custom-module Found locally cached pat file /home/tc/custom-module/ds3622xsp_42962.pat File /home/tc/custom-module/ds3622xsp_42962.pat, is encrypted Extracting encrypted pat file : /home/tc/custom-module/ds3622xsp_42962.pat to /tmp/pat option -f with value `/home/tc/custom-module/ds3622xsp_42962.pat' option -C with value `/tmp/pat' 0 Creating unecrypted pat file ds3622xsp_42962.pat to /home/tc/redpill-load/cache folder VERSION Pat file sha256sum is : 0d22091bc3f1f707f581839bfd6ec72193a90e16729bf637b7787e23aad42c74 Checking config file existence -> OK Editing config file -> Verifying config file -> config file, os sha256 verify FAILED, check /home/tc/redpill-load/config/DS3622xs+/7.1.1-42962/config.json tc@box:~$

You can check the log later. It seems that there is a peculiarity of the Intel 13th generation. I don't know if you can check the following contents in Korean with a translator, This is the success story of the only 13th generation motherboard in this forum. (TCRP FRIEND Fail) https://svrforum.com/case/684586 (TCRP Jot Success) https://svrforum.com/case/684652 It seems that 13th generation CPUs are not supported by ARPL or TCP FRIEND's latest GNU kernel. Because the case of intentionally changing to JOT mode instead of FRIEND mode is due to CPU compatibility. In general, when old AMD CPUs such as HP N40L and N54L are used, JOT is used because GNU kernel does not support it. JOT mode of TCRP corresponds to Direct Boot of ARPL. The above success story also failed with FRIEND, but this is a successful case by switching to JOT. Older CPUs are not supported by GNU, but I think it is a case where too new CPUs are not supported. M SHELL for TCRP also supports JOT. For the loader build method, DDSML is recommended rather than EUDEV. And try JOT, not FRIEND.

have just done my gen 8 using the i18n and the same settings as the n40l and its booted 1st time and running great

Hi a little help please a few days ago i used the i18n loader with an n40l server and to get it to work i had to go into advanced then development tools and use switch direct boot to true i have just tried to do the same with a new usb drive after i click on development tools it loads then goes back to the previous menu but the option for switch direct boot is no longer there am i missing something? answered my own question i had to make the bootloader then go back into advanced and the option was there

Just wanted to say thanks you all for the help just in case any one is trying to do the same thing with the HP n40l think it will also work with the n54l i installed ULANSEN PCI-E to USB 3.0 Type C +3 Type A Expansion Card - Interface USB 3.0 4-Port Express Card and the UPS was seen starlight away i am still on the arpl loader but i take it with this card as its a lot faster than the onboard USB Peter Sue s loader should work

Hi i hope some one can help me i have installed DS3622xs+ on a N40L using ARPL the server has started up fine but when i add my UPS Cyber power VP1200ELCD via usb it dose not see it checking on the synology web site the VP1200ELCD is compatible with the DS3622xs+ i have a second server running the old jun loader running DS3615xs and the UPS is picked up straight away i am hoping to also bring this server over to DS3622xs+ with the ARPL loader and would like to know how to get the UPS working any suggestions would be greatly appreciated

no the server is up and running plugging the ups in and its not seen by the server at first i was thinking it may be due to the boot loader and how it works thats why i asked the question but it now looks like synology removed the drivers for the usb ports that the n40l has

its to get the ups to work only from what i understand the after DSM7 there are no native drivers installed for the usb sockets on the n40l that is why the ups is not working

Hallo Gemeinde, habe meinen alten HP ProLiant Microserver N40L ausgegraben und versuche mit Hilfe von xpenology ein "Synlogogy" NAS zu basteln. Habe nach den Anleitungen schon einige Images auf USB Stick gemacht welches auch bis:...... bootet Kernel ....... durchgelaufen ist. aber es konnte nichts im Netzwerk gefunen werden, weder an der Onboard LAN Karte, noch an der extra verbauten Gbit Karte. Habe verschiedene Loader und Geräte versucht, wobei die 918+ mit 1.04 nicht bis zum Punkt: .... bootet Jernel ..... voran kommt. Ich hatte vor auf eine 120 GB SSD die Software DSM zu installieren und die 4 HDD als Speicher zu nutzen. Ich hoffe es funktioniert so mit der Hardware und meinen Gedankengängen. Warum funktioniert es bei mir nicht wie beschrieben? Kann man in der grub.cfg auch neben der MAC Adresse der Netzwerkkarte auch die IP gleich mit vorgeben? Weitere Fragen beantworte ich gerne. LG aus Sachsen

Only the REDPILL bootloader should be connected to the USB port of the PC used for XPE. If two or more bootloaders are connected or if another USB stick is co-attached, it will affect kernel booting. It was the first time I knew that it affected even the UPS using the USB port. I have to ask N40L / N54L users who use UPS in the Korean community where I am active.

N40L Bios settings C1E disabled and AHCI set IDE Combined mode dose not exist on my bios and the switch direct boot to true ds3622xs+ dsm 7.2-64570 update 1 is running fine will your installer now work the same? Do you want me to test your installer now to see if it works before i start to put things back on my server?