Popular Content

Showing content with the highest reputation since 11/04/2019 in all areas

  1. 1 point
    Надеюсь не до одури кнопку жали, чтобы он аварийно выключался? Какой кнопкой? Если ресетом, то никогда этого не делайте. Теперь по поводу восстановления, попробуйте сделать флешку от 3615, мигрировать на нее, если устроит, то на ней и остаться, если больше 3617 по душе, то аналогично с 3615 мигрировать на 3617. P.S. делайте ручную установку, подкладывая файл прошивки версии 6.1.6 или 6.1.7, на 6.2 амд может не взлететь. Или возьмите чистый винт и проэкспериментируйте с крайней версией.
  2. 1 point
    After upgraded to DSM 6.2.2 and moments 1.3.2, the face recognition is empty , and concept category only has child. I found thus shoud be a bug of photo detection plugin. So, there is the way to fix it: 1. enable SSH, and disable Moments. 2. replace /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so with my attachment. 3. enable Moments. (maybe need to reindex.) everything is fine. Enjoy~ libsynophoto-plugin-detection.so
  3. 1 point
    this is the first (experiential?) test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2 packages for 1.03b and 3615/3617 are coming (need to get a "older" hardware tor testing, my new B360M/G5400 testsystem did seem to freeze when loading the kernel with 1.03b, even no serial console output after starting loading the kernel) tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used (i guess also normal updates - jun left no notes about that so i had to find out and guess) hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas the rest of the drivers just loads without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2 v0.6_test http://s000.tinyupload.com/?file_id=29784352988385987676 !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) if there are more then 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation you can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) i might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17) i will extend here to what is in the old thread for 6.2 had but atm i'm more willing to add 3615/17 support basically what is on the old page is valid, so no sata_*, pata_* drivers here the driver in the test version listed as kernel modules the old thread as reference !!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!!
  4. 1 point
  5. 1 point
    There is a better way^^ Just activate it: In your browser open the following urls one after another: Replace the following: URL, PORT, USER, PASS, SERIALNUMBER (dont replace any other symbols like : oder ") https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" To get the current activation status call the 1. query above and then https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 ------------------------------ Example for url: server, port: 5001, user: admin, pass: admin, serialnumber: 123400 link here:
  6. 1 point
    As a strong advocate of 10Gbe networking on XPenology, I am happy to finally see an affordable, passively-cooled switch on the market (even though many folks don't even need a switch - a direct-connected multi-port NIC will often suffice). To use it, you'll have to familiarize yourself with DACs and/or optical SFP's but this is a major step forward for the price. https://www.servethehome.com/mikrotik-crs305-1g-4sin-review-4-port-must-have-10gbe-switch/
  7. 1 point
    lol thanks. To me that was a USB 3.0 port though. Didn't know that option was in bios. One would think that would be enabled by default. But im a big boy, i can take it :) Thanks for sticking with me though. Truly appreciated!
  8. 1 point
    Merci beaucoup @kaktuss77 pour ta réponse. Bon, ce soir je viens de faire la mise a jour de DSM en 6.2.2-24622 update 3, ça a l'air nickel (a part le "reboot" et "shutdown" non fonctionnel. Le logiciel ok, mais pas le serveur physique. Bon, pas bien grave, en théorie, je devrai pas redemarrer souvent le serveur, et il est branché sur un gros onduleur donc....). J'ai reçu ma carte Lsi 9211-8i IT aujourd'hui. Je devrai l'installer ce weekend. Pourrais-tu juste me confirmer une information : avec cette carte en mode IT, le branchement des disques durs peux ce faire a chaud? Enfin, ce que je veux dire c'est que si je branche mon disque dur il deviens directement disponible dans Synology, ou il y a quand même des manips a faire (redemarrage? ajout sur carte (bios)? Etc...) Je reviendrais ici une fois la carte installée, ça pourra toujours être utile pour d'autres utilisateurs.
  9. 1 point
    I'm embarrassed to say that while I was editing grub.cfg to get rid of the serial console, I just realized that the NIC light on the far end of my server to the switch went out (I was only looking at the server end). Plugged the far end into another port, lights went on, and it works. Sigh. Thanks for all your help. I can see that without LAN access the Gen7 are really hard to debug, since there's no console, but there's no excuse for user error on my part...
  10. 1 point
    @deesnow Ok, since I have lost my magic crystal-ball I will ask you a few questions, for someone to be able to help you: 1 - What version of DSM and bootloader did you upgrade from? 2 - Do you use DS3615 / 3617 / 916 / 918? Did you change this during your upgrade? 3 - What type of NIC do you have, and what driver is it using? 4 - Do you have any additional packages installed? (if so, did you install them before or after the upgrade?) 5 - next Q will follow later
  11. 1 point
    Когда то страдал Хардоманией и на прошлых версиях Хрени, с Raid контроллером HP P410, подвешивал 10 хардов. Эксперимента ради и пробы на крепость сервака. Правил конфиг под количество дисков. Биос не трогал точно, кроме настройки самого Raid контроллера. Все десять определялись и крутились. Правда потом пришёл к истине, что такая гирлянда мне ни к чему и остановился на пяти хардах
  12. 1 point
    @radga 918 не взлетит на вашем проце, нужен 4 го поколения и выше.
  13. 1 point
    serial output is just normal for xpenology, does not depend on the hardware type (server/desktop) but you need a null modem cable, the usb2serial is the equivalent of a normal serial cable i use a usb2serial adapter and connected to it a null modem cable A null modem cable is a RS-232 serial cable where the transmit and receive lines are crosslinked. https://en.wikipedia.org/wiki/Null_modem
  14. 1 point
    This first method seems to have worked perfectly! Uploading a bunch of data now to fill the increased space to test if volume remains stable. I did not find that tutorial in a forum search, so thank you!
  15. 1 point
    Hi guys, For some of you who wish to expand btrfs Syno volume after disk space increased. Before: df -Th btrfs fi show mdadm --detail /dev/md2 SSH commands: syno_poweroff_task -d mdadm --stop /dev/md2 parted /dev/sda resizepart 3 100% mdadm --assemble --update=devicesize /dev/md2 /dev/sda3 mdadm --grow /dev/md2 --size=max reboot btrfs filesystem resize max /dev/md2 After: df -Th btrfs fi show mdadm --detail /dev/md2 Voila Kall
  16. 1 point
    ok so i checked bios. For some reason USB 3.0 Controller was unchecked. @IG-88 A huge thank you! Tried to transfer the same 1GB file and Im getting speeds of 108 again.
  17. 1 point
    Hey all, I have an old HP Elite 8100 CMT convertible minitower with 2x 1 TB drives. I am trying to decide if i should invest in new WD Red drives or buy a synology NAS. I have a synology router with cloud server installed connected to an external 500 GB SSD drive. Synology Drive is not available for SRM only DS Cloud / Cloud drive. I want to use the NAS to replace google drive and one drive on my families Android phones for backup of internal storage AND SD Card (DS Cloud does not backup SD Cards) as well as PCs. QUESTIONS: Does Xpenology support the HP 8100 CMT? Is there a guide in the forumns to get started? What are tge gotchas? Thanks team!
  18. 1 point
    Hello, My name is Mike and i stumbled upon this forum when i was looking for a synology like os to place on my (old) pc. but to be honest I'm more confused after reading the forum than before . this is the noob section but where can i find the beginners guide or do i have it wrong that this is ment to run on pc's ?
  19. 1 point
    Hi all, Chris here, working in IT as an enterprise architect, but on the side I'm also an enthusiast and hands-on with many DYI projects. Including Xpenology... been using it for 2 years now, mostly on HP Microservers (also on top of ESXi), with SAS controllers and drives (for durability) and also on other systems for friends and family. Greatly appreciate all the work you guys do, including the contributions posted here from users! Best regards!
  20. 1 point
    it does not have to be that old 5.2 loader when you have a 3615, updated to 6.2.2 and want to downgrade its also possible to use loader 1.02b for 3617 and on migrate select the 2nd option to keep only data (loose settings), install "DSM_DS3617xs_15266" and from there you can decide to migrate to 3615 dsm 6.1 or updgrade to 6.2.(0) 3615 or 3617 but that 6.2.2. downgrade is history in a few days i already have a working extra.lzma for 3615 DSM 6.2.2 that contains all drivers the version for loader 1.02b had, it only needs some documentation and testing
  21. 1 point
    Hi all, After upgrading to Ryzen, I had a spare i5 i could use to replace my first "server": first gen i3 with linux (I use Arch BTW 🙂) and virtualbox. I have been working professionally with Vmware for a while now, so that seemed the logical choice. Still, it was not easy getting into XPenology. After trying bare metal for a while with VMM, I used Jun's 1.02b and DSM 6.1.7 on ESXi 6.7 and passed through the SATA controller. I'm copying data over now and will see where it takes me. I'm still looking for backup advice though. I have been using a combination of filesync and borgbackup previously.
  22. 1 point
    Hi, I'm Dan WHAT I HAVE/HAD : ds107 that I managed to upgrade to newer DSM that a DS109 could run. Everything looks like it was running fine. After about 6 month working, it turns out my system is failing to reboot after a few power failures. My drive work ok as tested in in a USB adapter with extre EXT3 drivers so it can be read from windows. NOW I'd like to try to build myself a system. HARDWARE I HAVE without spending: Unsure how to get info to describe my system by the important components XPEnology and DSM needs to run. Dell 7050 series micro computer with a built in SSD and a 500gb 2.5" hdd built-in. Very limited SATA interface and expansion possibilities. Hoping I can add drives via USB interface. I have 2 x 1.0TB and 1x 2.0TB 3.5" sata drive I could use once I get the new system working with the built in HDD. It would also be great to use the 1.0TB drive from my DS107/DS109 without erasing the data! Maybe re-install OS/DSM and make my old hardware work again While I build my new system and then add the drive to it!
  23. 1 point
    Hi. My name's Max and I'm a software developer. Stumbled upon Xpenology project while researching DSM on bare metal. I've had a DS411slim for the past 5 years and was curious about DIY alternatives to 918+. After a few days of tinkering and reading various posts I managed to successfully install DSM 6.2.1 Update 3 on HP Z230 workstation. DSM 6.2.2 wouldn't take on it. Not sure if I'm going to put this box in production yet, but it's definitely nice to know we can build DIY Synology boxes.
  24. 1 point
    Nice! Any idea about when you'll be able to release the 3617 version? Also, could you please enable the virtio_* drivers? This would be helpful for promox/kvm etc. users
  25. 1 point
    I915 driver loop KP started at [ 72.061444] Download the extra here below. Change of this extra.lzma > - removed drivers i915.ko drm_kms_helper.ko drm.ko in usr/lib/modules - removed reference of this drivers in etc/rc.modules - removed the i915 folder in /usr/lib/firmware and edit/removed the i915 EXTRA_FIRMWARE in the /etc/rc.modules Installation > sudo -i echo 1 > /proc/sys/kernel/syno_install_flag mkdir -p /mnt/synoboot1 mkdir -p /mnt/synoboot2 mount /dev/synoboot1 /mnt/synoboot1 mount /dev/synoboot2 /mnt/synoboot2 Remove extra2.lzma and replace extra.lzma by the one in my sign in /mnt/synoboot2 Important > clean /usr/lib/modules/update/* - Be careful with the rm ! rm -rf /usr/lib/modules/update/* And reboot extra.lzma
  26. 1 point
    I've spent the past couple days messing with this, and I've mostly got it working, though there are still a few bugs. The HP AMS code assumes a lot of things exist on the system that obviously aren't there with DSM, and that means it segfaults non stop. I finally got a build to work, and the main bug I notice is that in iLO only the first HDD is listed. This is in AHCI mode, it's possible the drive details show up OK in RAID mode. Also, I didn't really see any fan speed changes once I got this working, it was 10% before, and 9% after. Here's a dump of what I've been testing. No idea how correct any of it is, haven't done any development in a long time This was built against the latest bromolow DSM source and is running on 5.2-5592 Update 3, I dunno if it works on other versions of DSM. Use at you own risk, though I can't imagine there's much risk involved with something that is basically just an SNMP wrapper. Kernel Module - Steps mostly from here: http://xpenology.com/wiki/en/building_xpenology Download DSM 5.2 source and toolchain: http://sourceforge.net/projects/dsgpl/f ... z/download http://sourceforge.net/projects/dsgpl/f ... z/download Extract toolchain to /usr/local, extract source somewhere cd source/linux-3.10.x cp synoconfigs/bromolow .config make ARCH=x86_64 CROSS_COMPILE=/usr/local/x86_64-linux-gnu/bin/x86_64-linux-gnu- menuconfig Go into Device Drivers -> Misc Devices, hit M at "Channel interface driver for the HP iLO processor" to build the kernel module Save and Exit make ARCH=x86_64 CROSS_COMPILE=/usr/local/x86_64-linux-gnu/bin/x86_64-linux-gnu- modules copy drivers/misc/hpilo.ko to /usr/lib/modules/3.10.35 on NAS vi /usr/lib/modules/3.10.35/modules.dep and add this line: /lib/modules/3.10.35/hpilo.ko: modprobe hpilo should work with no errors lsmod | grep hpilo should show that hpilo is loaded HP AMS I couldn't get any of the executables provided in the debs or rpms to run without segfaulting. So I searched around, and found some source on github: https://github.com/marker55/hp-ams It's not the absolutely latest from what I can tell (seems to be 2.1), but it's close, as 2.2 is the most recent rpm I could find. What's important is it has the new command line args that 2.0 and below don't have, which let use chose which MIBs to query So git clone that repo, or just download the source zip. Download http://sourceforge.net/projects/net-snm ... z/download and copy it to the hp-ams-master folder Run make From what I can tell, it's not too important what compilers are used to build. I wasted a day adding cross compile support into all the Makefiles so I could build with the Synology toolchain to see if that would fix the numerous segfaults, but it doesn't seem to be necessary. After build is complete, copy the hpHelper executable to /sbin/hpHelper on the NAS chmod +x /sbin/hpHelper Test it Assuming you've already modprobed hpilo, run this as root to test if AMS works /sbin/hpHelper -f -L -I0 -M1,5,14,16,18,23,99 Should see a message like 'NET-SNMP version 5.7.2 AgentX subagent connected' Give it a minute or so, and see if things start showing up in iLO. There are two other MIBs, 0 and 11, but including either of those just causes it to segfault. Might be fixable, but I haven't dug into the code. Run at start Ctrl-C your test run to stop it, then create a startup script. vi /usr/local/etc/rc.d/S99HP-AMS.sh #!/bin/sh modprobe hpilo /sbin/hpHelper -I0 -M1,5,14,16,18,23,99 chmod +x /usr/local/etc/rc.d/S99HP-AMS.sh /usr/local/etc/rc.d/S99HP-AMS.sh ps | grep hpHelper Should show it is running, and iLO should still report correctly. Download 5.2 - hp-ams.tar.gz 6.0 (thanks to ema) - https://mega.nz/#!gt0HTCJZ!PeXq-qutvb6mZT7ZuP3Htfi-abkEdOYNZ_HcCVTd-6Y 6.1 (thanks to ema) - https://mega.nz/#!R8dUhDJb!dyYEVSsrWSohPfU5O7Uxo-GisuMKZPZbG4HbeiIeHk0 Note the modules.dep.hpilo file, that's so you don't extract blindly and overwrite say the modules.dep file for VirtualBox. Rename to modules.dep if you don't have one, or copy the contents into your existing modules.dep. Unfortunately, I really don't have a lot of time to work on this, so I doubt I'll ever have a proper package available or keep things up to date. But I figured I could at least dump what I had, so anyone else that wants to mess around with it can.
  27. 0 points
    ben si, mais de toute façon je pense que tu as déjà perdu tes données en qq sorte 😕