Leaderboard

NOTE: This problem is consistently manifested when running as a virtual machine, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3 and under certain conditions, other 6.2.x versions. The fix can be implemented safely on baremetal installs. You can verify if you have the issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If these files are not present, your Synoboot devices are not being configured correctly, and you should install the fix script. If synoboot3 exists that is ok

И вам вечер добрый Пропала вечерняя развлекуха.... Поздравляю, удачное приобретение Работает только Валидная пара Серийник + МАК и то, если эта пара прошла регу на сайте Синолоджи и там виден ваш девайс 2.0 вполне достаточно. Скорости загрузки хватит за глаза. Загрузчик работает только в момент загрузки и всё..... До следующей перегрузки или отключения. DSM инсталлируется на каждый хард стоящий в Хрени. Системные разделы на каждом харде. Будет и пять дисков, а можно и больше настроить. В N54L влезает шесть хардов без каких либо серьёзных манипул

DS1812+ has earlier version Atom chip (Cedarview D2700) than the chips that had the boot clock problem (C25xx). So that probably won't apply. PSU is usually the culprit there, but you already tried that...

Hey there, today was an interesting day. I finally got all parts together and decided to upgrade my server to support more drives. 5 hours later, and two heart attacks, I finally got everything running. But lets start from the beginning. (I am not mentioning my self-made problems of updating my BIOS which I shared here (3 posts total): So I ahave currently 10 disk plus two SSDs in my setup and want to expand my storage. Case has 24 hot-swap ports, so all fine. Already have 6 (4 usable via SAS cable atm) internal ports and am using an LSI SAS 9220-8i for 8 more ports. Of

When setting up an XPEnology system, you must first determine which DSM platform is needed. Platforms support hardware and software features. The platform, combined with the version of the DSM software desired, informs the selection of a loader. This table and decision point example should help navigate the DSM options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 11-Aug-2020 DSM

J'ai gagné 4Ko .

11 Mb/s = ~100mbps The cable, port and router are gigabit: i replaced, in the same place with same cable and same router, the old nas (that worked in gigabit mode) with this one! The router recognizes the hp port as gigabit! The cable is gigabit, only in synology i read 100mbps (under Control Panel -> Network -> Network inteface -> LAN 1 -> Network Status) and, obviously, the maximum speed reached is 11/12 mb/s Before, during installation, I was in another place NEWS I SOLVED WITH SSH: ethtool -s eth0 speed 1000 or ethtool -s eth0 autoneg off speed 100

if the loader 1.03b came up with the single test disk its not a problem with csm, tho loader would not boot in this case this older unit might take while when updating 1/2h is not unusual from what i've seen here one thing with the recorey is odd, loader 1.02b is dsm 6.1 not 6.0 edit: that can't be right, the version 25426 is dsm 6.2.3 imho atm there are two "simple" options 1. use the 1.03b again and make a migration, wait at least 1h and then hard reboot if needed the system may come up than as 6.2.3 (doing a migration to a

Конечно.

you would need a 2.5G capable nic on/in the Mac too and both need to be connected directly or by a switch supporting that speed/connection in your case the Mac (and your switch between them) is now limiting the speed as it only allows 1Gbit max

Here are some snapshots of vDSM 7 Preview.

Hi all, in an effort to simplify the process, I've done some work towards that, but i think there is a lot of room for improovement. So far what i've done : - Translated about 100% all disk, kept original and translated original on a separate folder - Cleaned up the firmware process and kept as much many as i could from initial scripts - Added an automated process to figure out as many devices as i could during model.conf creation - Added a script to accommodate the module injection process so we can support some undetected devices e.g. vmxnet3, e1000 etc - Adde

- Outcome of the update: SUCCESSFUL DS3615xs DSM v6.2.3-25426-Release-final - DSM version prior update: DSM v6.2.3-25426 - Loader version and model: JUN'S Loader V1.03b - Installation type: WorkStation 15 Pro Win10x64 - Using custom extra.lzma: NO - Additional comments: Requires reboot No DOWNLOAD DS3615xs DSM v6.2.3-25426-Release-final

This affects users who have their NAS exposed to the internet (NAT, open ports). It‘s fixed in DSM 6.2.3-25426-3 . Description Multiple vulnerabilities allow remote attackers to execute arbitrary code via a susceptible version of DiskStation Manager (DSM). https://www.synology.com/en-global/security/advisory/Synology_SA_20_26

Пробуете, должно помочь по аналогии с ESXI и Workstation.

If referring to the 3.3v power line used as a reset line on many shucked disks, it can be taped over or just removed entirely.

Hi, When I purchased it I checked for CMR "WD Red 6TB NAS 3.5 Inch Internal Hard Drive - 5400 RPM Class, SATA 6 Gb/s, CMR, 64 MB Cache - WD60EFRX" Thanks for you post BTW HEADRAT

Be sure to take out your loader USB with the drives and burn another one for the test, then when you restore your old drives, put your old loader back at the same time.

Yes I'm using btfrs, no snapshots. I'm making backups with rsync on another xpenology nas, weekly, I've already formatted my infected nas and after checking integrity of storage pool I'l start copying files back from backup, which will take three days but, it is what it is

generell lohnt auch ein blick in die logs um zu sehen was dort an meldugen steht wenn es schon mehrfach vor kam dann lohnt auch eine statistische betrachtung die strom und sas versorgung ist in 2 x 4 geteilt, wenn das problem immer auf einer 4er seite ist dann sind es ziemlich sicher kabel probleme, wenn es sich verteilt dann kann man aber leider nicht viel sagen, es könnte dann auch noch an den kabeln liegen oder am netzteil (selbst unverträglichkeiten platte/controller sind nicht auszuschließen) ganz allgemein ziehen 2.5" platten nicht so viel strom aber es kann trotzdem am ne

Da Fallen mir zwei mögliche Ursachen ein: Unterversorgung der Platten mit Strom oder defekte Kabel Im Storage Manager im Bereich HDD/SSD, lohnt es sich bei jeder Platte mal "Health Info" anzusehen und dort den "Drive Reconnection Count". Sobald da bei auch nur einem Laufwerk die Zahl > 0 ist (und sich evtl. auch noch weiter erhöht) würde ich dringend die Verkabelung wechseln und/oder ein größerees Netzteil einbauen. Achte darauf das die Sata-Stromkabel von unterschiedlichen "Hauptsträngen" vom Netzteil abgehen. Minderwertige Verlängerungskabel können zu Problemen führen. Defekt

with 6.2.2 you would need to use jun's i915 driver by using "0.8_std ds918+" with 6.2.3 there is a newer i915 driver from synology on the same level is jun's diver was, supporting up to geminilake and lower tier 9th gen cpus ootb, only thing to do is to use my extra.lzma to remove jun's old driver (not working with 6.2.3 because of kernel changes by synology) and make the new one from synology active there is nothing special, it works with 6.2.2 it will with 6.2.3 the 1st post in this thread is also about updating from 6.2.2

Oui, puis quand tu rajoute des disque, il install DSM sur les disque que tu rajoute de manière transparente. Avec la commande : fdisk -l | grep '/dev/[sh]d\|sata[[0-9]\|[a-z]]' Tu peu lister les disques présent dans/sur DSM ( SATA et USB ) Voici un exemple chez moi : On peut voir que tout les disques présents en interne, on 3 partitions ( DSM / SWAP / DONNÉES ) et pourtant, il n'ont pas tous était placé en même temps. On peut voir que sdq et sqr ont 1 seule partition, cela s'explique car ce sont des disques externe ( USB ).

synology is not writing the whole code, they would use the kernel driver if present and then ffmpeg so if you want a to estimate you would need to check it that Xe functionality is supported by ffmpeg and if there is a driver already in the kernel

Bonsoir, J’ai suivi les conseils de [mention]EVOTk [/mention]. Test à blanc ; aucun souci Migration : aucun souci A noter que la carte réseau pci fonctionne ainsi que la carte réseau intégrée. Merci encore Envoyé de mon iPhone en utilisant Tapatalk

sata might be more often used for the connector, the mode it operates can be old ide one and the newer ahci now days you usually only see ahci, the old ide mode was just on older systems and for compatibility to older os the ahci driver is natively used by synology an all models and is part of the kernel, so whatever happens to driver support, this should always work i point out at the 6.2.2 compatibility problems (longer time no compatible drivers) or the still existing scsi/sas problems with 918+ i did not wanted to say you should have read this before updat

i did read that here in the thread and it worked on my 3617 test system mod the following file /etc.defaults/syslog-ng/patterndb.d/scemd.conf destination d_scemd { file("/var/log/scemd.log"); }; -> #destination d_scemd { file("/var/log/scemd.log"); }; destination d_scemd { file("/dev/null"); }; so you comment out the original line with a "#" and add a new one that will move the log data of scemd to /dev/null instead of writing them to disk

Bonjour, J'ai utilisé les fichiers de cette discussion : Cela à fonctionné sans soucis.

maybe you downloaded the wrong version, extra2.lzma only exists in 918+ driver pack (loader 1.04b), 3615/17 only have one extra.lzma if you expect a specific answer you might want to be more specific about the hardware, like usb vid:pid or the chip used if its the adapter from this thread (0bda:8156) https://xpenology.com/forum/topic/36454-adding-an-255-gb-net-adapter-on-xpenology-nas/?do=findComment&comment=176526 then yes, the id's are in it driver is v2.12 r8152.ko (latest is v2.14, so no major number that might indicate bigger changes)

try the forum search, i wrote a bout that, its not yet available and is only planned for 3615/17 as these two don't have hw transcoding and i already tested the driver with that kernel 3.10.105 (its likely the nvidia driver will also compile with the the 4.4.59 kernel of 918+)

Hello. Après avoir fait le nécessaire niveau driver sur le syno, la carte nvme fonctionne très bien. Cependant, j'ai opté pour un système simple ssd avec un max de stockage possible. Alors voici ce que j'ai acheté (pj) J'ai mis 2 ssd sur la carte mere pour le cache 2 hdd sur la carte 2 port sata pci 1 5 hdd sur la carte 6 port sata pci 4x 1 ssd (pour le systeme) sur la carte 6 port pci 4x Donc, 1 ssd système 2 ssd cache 7 hdd raid 5 pour le stockage. Tout est up. Parfaitement fonctionnel.

Hola, si puede ser un problema o no tanto, hazte un nuevo pendrive con el boot adecuado y reinstala la versión la misma versión que tenías o una un poco superior, no deberías tener problema, creo recordar que el bootloader 1.03b es el compatible con las versiones posteriores a la 6.0.2 de DSM. Seguramente por eso dejó de arrancar correctamente, y recuerda desactivar las actualizaciones para que no vuelva a ocurrirte lo mismo.

https://xpenology.com/forum/topic/7341-tutorial-compile-xpenology-drivers-in-windows-10/ https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/ https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/6.0/enu/DSM_Developer_Guide_6_0.pdf

I believe your i5 10400 has 6 cores and 12 threads? I have the dated version, 8400, 6 cores 6 threads. 918+ afaik supports 8c16t so your processor will be in full use without a hitch.

I suggest doing 1. and writing down all the steps and recording what happens - or doesn't happen. As @IG-88 says, if it gets stuck in the middle of the installation, then leave it for a while. I also now remember one of my steps to upgrade to 6.2 required a couple of hard boots and a wait to make sure the disk light had stopped. If it all stops, post what you did and what messages you did (or didn't) get.

Did you remember change your boot mode to Legacy/CSM when you upgraded to 1.03b? That is the common error.

Если вы его не делали- нисколько.

btw that kind of language might be seen off putting (or even insulting) from some people its signaling you are normal and the other is weird and abnormal (i think it was not your concise intention but it has a sub context you should be aware of) - it might be a little like this? (a snipped from zootopia) https://www.youtube.com/watch?v=oXpTBt2iNbg

imho you should not need that spk when using my extra.lzma also the most common reason seems to be wrong usb port or speed degradation of a 3.0/3.1 gen 1 or 3.1 gen2 port use "lsusb" to see how fast the device is connected with usb ash-4.3# lsusb |__usb1 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (xhci_hcd 0000:00:14.0) hub |__1-5 051d:0002:0106 00 1.10 12MBit/s 24mA 1IF (American Power Conversion Back-UPS XS 800CI FW:920.T2 .I USB FW:T3 3B1409X17540 ) |__1-7 f400:f400:0100 00 2.10 480MBit/s 224mA 1IF (SanDisk Ultra Fit 4C53100164121

ben, à chaque changement de disque la taille augmentera légèrement si DSM le permet au pire il reste sur la meme taille qu'actuel et te dira qu'il y a de la place inutilisé mais c'est pas grave. Au bout du dernier disque la taille devrait arriver à son maximum. et donc tu devrais être en mesure de pouvoir étendre le volume à sa capacité maximale

El mejor lugar para saber si encontrarás problemas es el reporte de usuarios sobre las actualizaciones, algunos incluso detallan como solucionaron el upgrade si es que les dio problemas:

hi thank you for everyone soon I will announce my DESKTOP vDSM with Quickconnecte still functional on appliance.ova IN DSM.EXE version HERE IS A DEMO. BETA SHARING YOU DSM APPLIANCE 6.2.3 UPDATE.2 ??

Hi, on DSM 6.2.2 I got this: sed: -e expression #1, char 40: unterminated `s' command sed: -e expression #1, char 94: unterminated `s' command Any idea? Thanks!

HP N54L Gen7 microservers are definitely old now - I've been using 2x of them for the last 8yrs - one configured as a Linux server, the other as a XPEnology backup NAS, originally 5.2.5644 then just recently 6.1.7.15284 after I'd bought a Synology DS918+ as I needed a dual backup system (live backup and additional archive) solution. They are old boxes now I agree - they work really well though, relatively cheap on auction sites - with spares and upgrade options being cheap due to hardware age (memory upgrades etc). After BIOS upgrades the rack drives are also hot-pluggable. As IG-8

It seems to me a strange thing, mystifying… Try attached .so. libsynonvme.so.1

Minor changes. Dev Guys now do some more strict PHYSDEV parsing. Nothing special. libNVMEpatch.sh

ALL of 2 XPENOLOGY Videos where deleted by YouTube from my tiny channel . Copy of Video stored here for now. https://mega.nz/#!0AZwXKjb!0e1ZajS_0rDIynsKbGVRJO-gmFUeSjfpnXziiZkQDgU

Yeah, the only thing in that whole long terminal session that did anything was the copy file above. You're lucky the random shell action didn't do any damage as root. Now you need to make the script executable: Then reboot and your drive should show up in Storage Manager. Please do yourself a favor and only use R/O cache mode, not R/W ...

Записываем загрузочную флешку. Редактируем grub.cfg программой OSFMount Начальная стадия установки DSM, это создание загрузочной флешки. После определения Хардового конфига (железо, его конфигурация) и дальнейших потребностей для себя от DSM, определяем версию DSM загрузчика под неё. На данный момент, имеется три версии загрузчика под разные эмуляции DSM , это : ds3615 , ds3617, ds918+ Под ds3615 , ds3617 - последний загрузчик v1.03 b Под ds918+ - последний загрузчик v1.04b Имеются и более ранние версии, всё зависит от вашей конфигурации и желаемого результата.

Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 1. Ссылка на загрузчики от 5.0 до 6.2 2. Как установить на примере загрузчика 1.04b для DSM 6.2 (918+) 3. Совместимость загрузчиков 6.0-6.2 и железа 4. Тестирование и как проверить работает ли транскодинг на примере Asrock J4105-itx, там же сборка extra.lzma с гибернацией дисков 5. Как отредактировать grub.cfg и заменить extra.lzma на работающей хрени 6. Пакет для активации железной кнопки Power off на корпусе хрени (крайняя версия 6.2-0002, на нее и ссылка) 7. Корректное отоб