Forums

Bonjour,   J'ai un N40L tournant sous ARC en directboot (obligatoire sur ce HP Proliant Microserveur). J'étais en version DSM 7.2.1-69057 Update 3. Tout était bien fonctionnel. Le 24/04 j'ai reçu un courriel m'informant de la disponibilité d'une nouvelle version de DSM. (DSM 7.2.1-69057 Update 5). J'ai donc été dans Panneau de configuration, Mise à jour et restauration pour télécharger l'update 5. Une fois téléchargé, je l'ai installé. DSM a rebooté et depuis, ça boucle : 1. "Récupération" proposée (image 1). Clique sur "Récupérer" 2. Installation en cours de DSM (image 2) 3. Installation terminé (image 3) 4. Redémarrage (image 4) Puis retour au point 1. J'ai déjà eu ce problème lorsque je suis passé de DSM 7.2.1-69057 Update 1 à DSM 7.2.1-69057 Update 3. J'ai dû réinitialiser mon DSM. Je n'ai pas perdu mes données, mais toute la configuration a été effacée. Savez-vous comment je dois procéder pour redémarrer correctement mon DSM sans rien perdre ?   Merci

I can also confirm full USB functionality and advanced speed via TCRP. My systems are not only used for testing purposes. As of a year ago, ARPL didn't work.   It's also super easy and quick to migrate from internal RAID0 using a single Linux mdadm-command. If you have an external single drive, you should ideally place the parity disk of a RAID4 there. If you have a dual(or more)-case, it makes sense to place the mirror drives of the RAID10 there.    In general, the slow hard drive performance when writing in RAID 5/6 scenarios, with only 3-5 drives, is out of the question for me anyway. I can also imagine the long recovery times with the associated collapse in performance. We're not talking about a data center-sized installation where the penalty is almost negligible.

no, there is no such thing that tricks dsm (xpenology or original) into accepting a "normal" sata (or sas) enclosure as one of there original expansion units afaik there is some tinkering in specific drivers kernel code and firmware checks for the external unit involved (was introduced ~2012/2013 before that any eSATA unit that presented every disks as single disk worked) also worth mentioning is that technically its a simple sata multiplier and you use the amount of disk in that external unit through that one 6Mbit sata connection, all drives involved (external unit) sharing this bandwidth) as long a you just have to handle a 1Gbit nic you wont see much difference but if you want to max out what lets say 4 + 4 10TB drives can do and use a 10G nic you will see some differences and raid rebuild might speed might also suffer in eSATA connection scenarios   also a general problem with that kind of scenario is reliability as when accidentally cutting power to the external unit there will be massive raid problems afterwards usually resulting in loss of the raid volume and when manually forcing repairs its about how much data is lost and hot to know what data (files) is involved i dont know if synology has any code in place to "soften" that for there own external units (like caching to ram or system partition when sensing that "loss" by a heartbeat from external and bringing the raid to a read only mode to keep the mdadm raid in working condition)   as you can use internal up to 24 drives with xpenology and only your hardware is the limit (like having room internal for disks and enough sata ports) there is only limited need for even connecting drives external and some people doing this hat seen raid problems if you dont have backup from you main nas then don't do that kind of stuff, its way better to sink some money in hardware then learning all about lvm and mdadm data recovery to make things work again (external company for recovery is most often out of question because of pricing)   maybe a scenario with a raid1 with one internal and one external disk might be some carefree thing bat anything that goes above the used raid's spec's for loosing disks is very dangerous and not suggested   and to bridge to the answer from above, in theory usb and esata externel drives are handled the same, so it should be possible to configure esata ports in the same way as usb ports to work as internel ports, as esata is old technology and mostly in the way when it comes to  xpenology config files it's most often set to 0 and not in use, i used one esata port as internal port years back with dsm 6.x - but as a ootb solution is the thing then externel usb as internel drives is the common thing now and with 5 or 10 Gbits usb is just as capable as esata for a single disk (and you will have a good amount of usb ports on most systems where esata is usually, if there as any, is just one   if you want to use usb drives as "intrnal" drives then you can look here (arc loader wiki) https://github.com/AuxXxilium/AuxXxilium/wiki/Arc:-Choose-a-Model-|-Platform its listed specifically that its usable that way    

Bonjour,   J'ai actuellement un N40L avec 8 Go configuré avec un groupe de stockage en RAID6 composé de 4 disques de 6 To (soit 1 volume en ext4 de 10.8 To dispo). J'envisage de passer à un Dell PowerEdge T110 II (Xeon E3-1220 V2 3.11Ghz / 24 Go de Ram). L'idée est de donner plus de répondants à mon NAS.   Mon N40L émule actuellement un DS3622xs+ (DSM 7.2.1-69057 Update5). J'ai plusieurs questions. 1. Est-ce que la migration hardware en restant avec un boot ARC ne va pas faire perdre mes données ? 2. Est-ce que je vais y gagner à basculer sur le T110 en termes de performance ? 3. Faut-il rester sur un DS3622xs+ ou un autre modèle est plus adapté ?   Ça sera peut-être l'occasion de passer à la virtualisation au passage à ce T110 II. Avec la fin de la version gratuite de l'hyperviseur bare metal ESXi, il vaut mieux s'orienter vers proxmox sur ce matériel ? Si je mets en place un hyperviseur, concernant la VM dédié à DSM , même questions que précédemment : 1. Est-ce que je ne vais pas perdre mes données ? 2. Est-ce que je vais y gagner en termes de performances ? 3. Faut-il rester sur un DS3622xs+ ou un autre modèle est plus adapté ?   Merci.  

на ArcLoader 23.11.20 все обновилось!