Search the Community

Honnêtement pour le N54L, je resterai sur le DS3622XS qui est 100% compatible. Je ne sais plus si à l'époque où je l'avais, le DS920+ était fonctionnel mais de prime abord je dirai que oui et effectivement le transcodage iGPU devrait fonctionner mais bon vu le niveau du CPU ça ne t'apporterai rien du tout! Aujourd'hui la carte réseau de base est gérée nativement, donc l'autre HP NC360T pourrait encore te servir pour avoir une seconde IP ou faire du bonding. Pour les options du loader la seule obligatoire est le directboot, le reste c'est du classique et dépend des choix/besoins de chacun.

Bonjour à tous, Suivant de loin les évolutions de Xpenology, j'aimerai refaire mon loader avec ce dernier loader ARC qui semble au top. Etant sous DS3622xs+ et DSM 7.1.1-42962 Update 1, je me demande quelle version de DSM pourrait le mieux correspondre. J'ai toujours mon bon vieux HPN54L, pile de bios changée et je but déjà au premier choix.... quel DSM utiliser sur mon N54L. - DS920+ ? Pour quelle raison ? il me semble que le seul bénéfice avec ce DS est le décodage ? - DS923+ ? quel bénéfice versus le DS920+ ? - DS3622XS pour rester avec le même DS que celui que j'ai aujourd'hui ? Quel est la réelle différence entre les DS920+ (ou DS923+) et le DS3622XS+ ? J'ai une carte réseau HP NC360T, suite aux vieux souci de port ethernet inutilisable avant. Ré-Utiliser l'éthernet d'origine ou laisser ma NC360T ? Ensuite avez vous quelques infos concernant toutes les options avant de Biuld le loader ? j'ai trouvé le Wiki (https://github.com/AuxXxilium/AuxXxilium/wiki) mais y a t'il quelque chose en FR ou orienté pour nos N54L ? J'ai bcp de questions Merci par avance pour vos lumières.

Bonjour Nicoueron, J'ai préparé la clé pour flasher le bios. Avant de tenter la procédure pour la mise à jour, je ne trouve pas d'info sur l'obligation de changer la carte réseau. Il y a actuellement la carte d'origine du N54L. Dois je commander la NC360T ? Merci pour tes lumières

Hello, i have an hp gen8 HP ProLiant MicroServer Gen8 - Server - Ultra-Micro-Tower - 1-Weg - 1 x Pentium G2020T With DSM 6.2.2-24922 Update 6 with jun loader 1.03 (DS3615xs) and network card HP NC360T Yes i'm late on the upgrade process i didn't take time to do it since years ... I'm trying to prepare my migration and after reading many post and tutorial i'm not sure witch one i have to follow Do you have any tips or recommendation before i start ? should i change some BIOS config ? should i use DSM 7.x with TinyCore RedPill (TCRP) Loader ? should i upgrade first to DSM 6.3 ? What is the Syno model i should use Thanks for your help i plan to follow this video that follow the flyride tuto but it's not the same CPU as mine gen 8

Bonjour, J’ai soupçonné que la carte réseau intégrée à la carte mère était en cause et que la dernière version de rr ne la reconnaissait pas. J’ai créé une nouvelle clé USB avec la dernière version 23.11.10 et j’ai ajouté une nouvelle carte réseau que j’avais en réserve, la HP NC360T, et le NAS a immédiatement été trouvé avec l’assistant Synology en mode recuperation, j'ai aussi testé avec une carte réseau en USB pour l'instant tout fonctionne comme d'habitude

Just a quick guide from my installation of DSM 6.2.1 Update4, before I forget it. The process was much easier than I expected, thanks to all the contributions and sharing in this forum. *** This guide required MODDED BIOS and a HP NC360T NIC *** Hardware Setup Flash kamzata's modded bios, use attached file to burn an USB with the modded bios, boot the server from it and let it complete the bios flashing Install the HP NC360T NIC, I bought a used one in Taobao for 14 bucks Load "Optimal Defaults" from BIOS, then In Advance page, disable C1E Support In Chipset page, disable the onboard NIC Atheros AR8132M NIC DSM Installation Download Jun's Loader v1.03b DS3615xs (Synoboot_3615.zip | 17.3 MB | MD5 = e145097bbff03c767cc59b00e60c4ded) Download PAT file DS31615xs DSM 6.2.1-23824 Update4 (263MB) Prepare the USB boot drive, I followed Polanskiman's tutorial to write the generated SN, USB vid and pid in to grub.cfg boot image then burned it to my USB drive (below steps also come from Polanskiman's tutorial, really recommended to read it through) Boot the USB drive, select the 1st option (or just let it timeout in a sec), wait for 10mins then run Synology Assistant, your Microserver should be found as a "Not Installed" DSM Right click on the found DSM and select install, browse to the download PAT file above. Installation will take some time (30mins for my 8TB drives) Post Installation Enable SSH login Update packages Add SynoCommunity package sources - http://packages.synocommunity.com/ WIP Using Webcam as an IPcam with Surveillance Station Kamzata Modded BIOS - run HPQUSB.rar

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update 3 - Loader version and model: ARPL-i18n 23.9.6 / DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Intel Xeon X5690 - Asus P6T - 24GB 1333mhz ECC DDR3 - NIC HP NC360T PCIe - LSI 9207-8i - Additional comments: Manual update via GUI.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update 2 - Loader version and model: ARPL-i18n 23.8.1 / DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Intel Xeon X5690 - Asus P6T - 24GB 1333mhz ECC DDR3 - NIC HP NC360T PCIe - LSI 9207-8i - Additional comments: Manual update via GUI.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update-1 - Loader version and model: ARPL-i18n 23.7.4 / DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Intel Xeon X5690 - Asus P6T - 24GB 1333mhz ECC DDR3 - NIC HP NC360T PCIe - LSI 9207-8i - Additional comments: Manual update via GUI.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64561 (with Update 1) - Loader version and model: ARPL-i18n 23.7.4 / DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L - NIC: HP NC360T PCI-E - Additional comments: Manual update via GUI

- Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 7.2-64561 (with Update 1) - Loader version and model: ARC Automated RedPill Loader 23.7.33 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L - NIC: HP NC360T PCI-E - Additional comments: Manual update via GUI | Rebuilded loader to 7.2 with direct boot

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 UPDATE 6 - Loader version and model: ARC Automated RedPill Loader 23.7.33 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L - NIC: HP NC360T PCI-E - Additional comments: Manual update via GUI | Rebuilded loader with direct boot

Ciao a tutti Ho appena risistemato il pc che uso come nas. Funziona tutto perfettamente, ma ho una velocita' in scrittura che definire oscena e' dire poco......... Caratteristiche principali HW: CPU Xeon X5690 24 Gb ECC 1333 DDR3 Controller LSI 9207-8i 8 dischi da 4TB scheda di rete HP NC360T (ho anche provato con la Realtek 8111C onboard ma il risultato non cambia) La rete e' cablata in rame CAT6, lo switch e' un Linksys (sottomarca Cisco) 8 porte con management e funziona perfettamente come dimostra lo screenshot con i risultati di iperf3 Nel primo screenshot con il grafico del trasferimento files si vede la velocita' oscena di trasferimento. La versione DSM e' 7.1.1-42962 Update 5 e il loader e' ARPL v1.1-beta2a configurato come 3622 Nel secondo screenshot dove va a piena banda, e' con la stesso PC con FreeNAS............. Avete un'idea del perche' DSM ha una velocita' di trasferimento che fa pena ? Idee ?

Hello all I am trying to stop banging my head against the wall... I have tried just about everthing. I gave up with the internal Nic so got this card can anyone help me as does not find the nas on the network using find.synology etc what loader etc will work with 6.2 Thank you in advance regards Mike

Hi all. Please do help me. I stuck at the very early point for long time already. Thank you all guys in advance. Hardware: HP Gen7 N36L (with mod-bios) HP NC360T NIC (Intel) Bare Metal Environment Software: Jun's loader 1.03b for xs3615 USB grub file has been modified with the VID_PID, SN, Mac1 and Mac2 addresses. Issue: Boot from USB. Screen stays at "Screen will stop updating shortly." (screenshot) Wait 30 minutes. It cannot be discovered in the network. Scanning LAN IPs, using Synology Assistant, or find.synology.com, none of these methods can see my server. Even from the router LAN IP pool, I cannot see any wired node exists. Please, please help. Jerry

Hello everyone I've just set up the pc I use as a nas. Everything works perfectly, but I have a write speed that to call obscene is putting it mildly......... Main features HW: Xeon X5690 CPU 24 Gb ECC 1333 DDR3 LSI 9207-8i controller 8 x 4TB disks HP NC360T network card (I have also tried the Realtek 8111C onboard but the result is the same) The network is wired in copper CAT6, the switch is a Linksys 8 ports with management and it works perfectly as the screenshot with the iperf3 results demonstrates In the first screenshot with the file transfer graph you can see the obscene transfer speed. The DSM version is 7.1.1-42962 Update 5 and the loader is ARPL v1.1-beta2a configured as 3622 In the second screenshot where it's running at full bandwidth, it's with the same PC with FreeNAS............. Do you have any idea why DSM has a transfer speed that sucks? Any ideas ?

Anyone else experienced this? I've got an HP Microserver gen10, an HP NC360T NIC and DSM 6.2.2-24922. Ever since the upgrade from 6.1 to 6.2 the system will drop of off the network about once a week. Sometimes when adding large torrents to the download station (but maybe that's only coincidence). Is there any way to diagnose this? Any system logs besides the Log Center? The only abnormality I'm able to see in the Log Center is that LAN 1 goes down and receives a 169.254.xxx.xxx IP, like the cable was disconnected. It stays like that indefinely.

Bonjour, Ma config actuelle est une installation Barmetal 3615xs - DSM 6.1.7-15284 J'ai acheter une carte HP NC360T dans le but de migré avec le loader 1.03b dans une version de DSM 6.2 La nouvelle carte est bien fonctionnel sous l'installation actuel de DSM Lorsque je lance le loader 1.03b 3615xs ou 3617xs, je ne trouve aucun serveur dans Synology assistant, par contre avec le loader 1.04b pour DS918+ je vois bien le serveur dispo dans Synology assistant mais une fois arrivé dans DSM j'ai un sablier infini lorsque je souhaite voir les interface réseau et les config comme les port DSM etc ne reste pas mémorisé Mes essai on était bien entendu réaliser en ayant retirer les disques en production j'avait juste mis un vieux disque de 1To Si vous avait une idée pour me venir en aide je vous remercie par avance

Я как раз воткнул карту HP NC360T 2-port, запретил встроенную, создал загрузчик для 1621, переехал с 6 на 7.1.1 - загрузилась все норм, и теперь у меня слетает биос, система грузится через раз (не получает ip, полагаю из-за конфликта со встроенной сетевой), но не видит 2 винта и орёт (это следствие слетающего биоса). Батарейку менял. Попробую тогда биос запаролить как предложили. Ну и ещё попробую на базе 3615 собрать загрузчик. Может в 7 и vvm там работает. Но это видимо в выходные уже.

Hello, I have a HP Gen 8 with DSM 6.2 update 2 installed in a microSD card with the boot loader 1.03b 3617xs Today I have install a new NIC PCIe HP NC360T, and disable the intenal NIC. I have start the Gen 8 and he boot OK and work correctly. So, after reading the post, thinking that the NIC HP NC360T was compatible, I made the upgrade to 6.2.2 directly from the system. Now I cannot enter and I cannot find it with Synology Assistant. Can anybody help me?... I not an expert on this.

i used HP N54L + HP NC360T , upgraded to 6.2.2 24922 , it's working fine in the synology system , but i found that i cant reboot or shutdown , reboot/shutdown is not working when i try to reboot or shutdown , no response from N54L How to solve thie problem ? i had used the modded bios and disable C1E and internal NIC . 1.03b loader + 6.2.2 24922 PAT

Hi to all, To update me DSM to the last system 6.2.2-24922 I bought a Network Card HP NC360T with intel NIC. But when I created the bond (link aggregation) when I upload, download or use the bandwidth of this bond, my DSM crash, the connection is off and restart with the issue message system. First question: How I can find the system log to check where the problem is ? Second Question: I think that the problem come from this card. Because before I use Internal NIC + TpLink Card to create the Bond and I never HAd a problem Thanks a lot.

I have been using my xpenology v 5.x on Baremetal HP Microserver GEN8 for the last 2 years with no problem.... I haven't been able to update the plex app for several months, so I decided to update it to v6.x given ALL the feedback + on DSM update reporting.... I made a complete backup and starting from DSM 5.2-5967 Update9 (latest) and I made the boot key following the tutorial and directly with the DSM DSM 6.2.2 Update 3 (latest) Everything good! Xpenology has been reborn as upgradable. I performed the migration operation successfully (it is also in the logs) Problems begin If I click on the control panel i get the error in attach If clik ok i go on but try to configure the network cards i get the no response for infinite time In DHCP mode all (network share by example) working fine. App not tested i replicate the procedure by replacing the network card with another one of the same type (HP NC360T) and I have also rebuilt, changing the boot key, wit no success Any idea please? Many Thanks in advance.

Alors personnellement, j'ai récemment migré mon N54L, je me suis pas pris la tête, j'ai utilisé ARPL beta 2, avec le bios correctement configuré. J'ai également la cartre NC360T et ça a fonctionné "plug & play" ... Il faut juste penser à cocher le "direct boot" dans les conf du loader ARPL avant de reboot.

Normalement la carte NC360T n'est pas nécessaire avec Redpill, la carte réseau intégrée suffit. Est-elle bien activée dans le bios ? As-tu testé avec seulement 1 dd de 4To ou à minima tes 4disques sans le SSD ? As-tu testé avec une autre clé USB ? Quelle est exactement la commande que tu lances lors du build ?