All Activity

This stream auto-updates     

  1. Past hour
  2. Скорее всего да, но теоретически, надо проверять )
  3. Today
  4. Works Perfectly I installed DS3617 on VMware ESXi after instal conform the above guide. After that I increased CPU to 4 and memory to 16gb without problems. After that I also tried to upgrade to 6.2.2-24922 Update 2 Also without problems! Just a happy user
  5. svens

    DSM 6.1.x Loader

    Hi all, I'm running "DSM 6.1.4-15217 Update 2" inside a (VMware ESXi 6.7.0) virtual machine on a HP Microserver gen 8. What is the best option for me to upgrade to 6.2? I have to specify that right now, after each reboot/restart/power loss, I have to always recover my installation. Thanks.
  6. - Outcome of the update: FAILED 😭 - DSM version prior to update: DSM 6.2.1-23824 Update 6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J5005-ITX (motherboard network card disable) with Intel Gigabit PRO/1000 CT - Additional comments: No network at boot
  7. Quickconnect only works with original serials & macs from real boxes which you should own. If you intend to access your Xpenology‘s shares with SMB/CIFS from outside your local network you should use a VPN solution which is available from the package center.
  8. I have a problem and I do not know what it is. someone can help me with the subject, apparently it is the connection. thanks from colombia
  9. My my xpeno is running under 6.1.5 15047 juns loader v1.03b , on my Intel Core i3-4130 2.4ghz dual core 8192Mo i get issue xhen i want to make the update to 6.1.5-15284
  10. Берете новую флешку, записываете на нее загрузчик 1.03b, берете чистый тестовый винт и пробуете установить систему с нуля на новом железе, желательно сразу воткнуть lan и raid контроллеры, которые планируете использовать в новой сборке и проверить их работоспособность. Если все взлетело, то перезаписываете флешку заново, втыкаете свои рабочие винты в новую сборку и спокойно мигрируете на новую версию дсм на новом железе.
  11. True brand new 🙂.. thanks for the patience ...👍
  12. Hello everyone, I'm a bit desperate here! My xpenolgy VM crashed after I copied all my data. I got a nasty Volume 1:crashed. I can get the results from cat /proc/mdstat and everything seems ok: ash-4.3# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md3 : active raid1 sdb3[0] 6249933824 blocks super 1.2 [1/1] md2 : active raid1 sda3[0] 16149504 blocks super 1.2 [1/1] md1 : active raid1 sda2[0] sdb2[1] 2097088 blocks [12/2] [UU__________] md0 : active raid1 sda1[0] sdb1[1] 2490176 blocks [12/2] [UU__________] and: ash-4.3# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Fri Jun 21 19:08:00 2019 Raid Level : raid1 Array Size : 6249933824 (5960.40 GiB 6399.93 GB) Used Dev Size : 6249933824 (5960.40 GiB 6399.93 GB) Raid Devices : 1 Total Devices : 1 Persistence : Superblock is persistent Update Time : Mon Jul 15 06:50:55 2019 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : LM_Server:3 (local to host LM_Server) UUID : 538bbadf:b8e76d4a:ae1e786d:6ae773a7 Events : 167 Number Major Minor RaidDevice State 0 8 19 0 active sync /dev/sdb3 ... but I can't get any return from vgdisplay: ash-4.3# lvm vgscan Reading all physical volumes. This may take a while... and I don't get anything else. I also tried: ash-4.3# mdadm --assemble --scan -v mdadm: looking for devices for further assembly mdadm: no recogniseable superblock on /dev/md3 mdadm: no recogniseable superblock on /dev/md2 mdadm: no recogniseable superblock on /dev/zram1 mdadm: no recogniseable superblock on /dev/zram0 mdadm: no recogniseable superblock on /dev/md1 mdadm: no recogniseable superblock on /dev/md0 mdadm: no recogniseable superblock on /dev/sdm3 mdadm: Cannot assemble mbr metadata on /dev/synoboot2 mdadm: Cannot assemble mbr metadata on /dev/synoboot1 mdadm: Cannot assemble mbr metadata on /dev/synoboot mdadm: /dev/sdb3 is busy - skipping mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdb1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sdb mdadm: /dev/sda3 is busy - skipping mdadm: /dev/sda2 is busy - skipping mdadm: /dev/sda1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sda mdadm: No arrays found in config file or automatically And finaly: ash-4.3# btrfs check /dev/md3 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 bytenr mismatch, want=2953562390528, have=0 Couldn't read tree root Couldn't open file system But I don't know how to interpret it ... Anyone willing to give me a hand? I don't know what to do after this ...
  13. Hello and welcome. Clearly you are new to the forum. First I would recommend you to read the FAQs of the forum. Also please post in the correct section. You posted in the French section. Your topic is in English so I am moving it over there.
  14. Hab dir ne PM gesendet[emoji4] Gesendet von meinem LYA-L29 mit Tapatalk
  15. Всем здрасти! Давненько не виделись ) Разжился я тут комплектом на 1155 сокете и решил по такому случаю обновить свой NAS. Что имеем в данный момент, по железу: Q6600, D975XBX2, 8Gb RAM, LSI 9211-8i, Intel EXPI9402PT. По софту: DS3617xs DSM 6.1.7-15284 / Jun's v1.02b_MBR_Genesys Loader Что хочется поставить: i3-3220, Asus P8Z68-V Pro, 8 Gb RAM, теми же останутся raid и lan контроллеры. А так как проц будет другой, то DSM хочется современной версии 6.2.2, а для этого нужно менять загрузчик на 1.03b. Ну и желательно конечно же сделать все это с сохранением инфы. Какой должен быть порядок моих действий?
  16. Loaded DSM 6.22 - worked like a charm...😀 Now how do I get external access? Unable to get Quick connect or network the drives ... HELP! 🤯
  17. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Intel Desktop Board DQ77MK - i5-3330 - Additional comments: None
  18. Les disques n'auraient -ils pas été assemblés en raid via le contrôleur intégré au Gen8 (création d'un volume) ? Si c'est le cas, il est normal de ne pas voir de disque, le pilote de la carte n'étant pas présent dans le DSM. En supprimant ce volume (tous les disques en mode indépendant), ça devrait régler le problème (si c'est la configuration supposée qui est activée). Bien entendu, si des données sont sur les disques, ne pas oublier de les sauvegarder avant la suppression du volume raid ! Jacques
  19. Tout à fait d'accord avec Evotk. La course à la version n'est pas forcément une bonne chose, ça pousse d'ailleurs à la consommation. Le service apporté (avec sa sécurité nécessaire en ce monde) est la vraie raison d'être d'un serveur. J'ai un Gen8, mon slot PCIe est occupé par une carte SATA, donc je reste en 6.1.7. Si un jour je veux passer à autre chose, alors je virtualiserai le tout via ESXi. Jacques
  20. Guys, a short update: I was able to fix the problem! I don't know how, but I did a reboot from the menu and the NAS rebooted with 6.1.4 (unlike earlier tries, where the system was not found by the Syno Assistent). I wiped the 4th WD RED and reattached it, not found. I did another reboot with the disk connected and the disk was found, and I was able to repair the volume. I did a full backup of all my data before the wipe, just to be safe, but all the data is still in place. However, all my programs are gone. I restored a settings-backup so I have most of my settings like before, but still need to reinstall al lot of stuff. But at the end of the day, nothing that can't be repaired, so nothing is lost. Thanks ever so much for all your help guys, much appreciated! Cheers, Frank
  21. Ben oui partagez avec la communauté ce que vous avez fait. Cela pourra servir à plus d'un!
  22. Oui et d'ailleurs vous allez vous calmer rapidement même. @JacquesF a poster pour vous aidez alors qu'il en avait aucune obligation. Si sa réponse ne vous convient pas ou alors qu'elle ne répond pas à votre problématique, la moindre des choses serait d'avoir un peu de courtoisie et de reconnaissance au lieu d'avoir une attitude agressive est désagréable envers un member respecté par la communauté. Vous ferez bien de relire les règles du forum et de faire en sorte que ce type d'attitude ne resurgissent plus. Merci d'avance.
  23. Buenas quisiera si me podéis decir si estas memorias son compatibles con el Gen 8. https://www.ebay.es/itm/16GB-2X-8GB-DDR3-PC3-12800U-1600MHz-CL11-DIMM-Desktop-Memory-For-AMD-Chipset-New/152363814223?_trkparms=aid%3D555018%26algo%3DPL.SIM%26ao%3D1%26asc%3D20170831090034%26meid%3Dbdea397f067f4a448028249668516962%26pid%3D100005%26rk%3D1%26rkt%3D12%26mehot%3Dpp%26sd%3D273432026691%26itm%3D152363814223%26pg%3D2047675&_trksid=p2047675.c100005.m1851 https://www.ebay.es/itm/DDR3-1x-8GB-PC3-12800U-1600MHz-CL11-240Pin-DIMM-SDRAM-KVR16N11-8SP-Memoria-RAM/273432026691?_trkparms=aid%3D555018%26algo%3DPL.SIM%26ao%3D1%26asc%3D20190212102350%26meid%3D65be7009f8cb4c1f83c45c1ffc042437%26pid%3D100012%26rk%3D1%26rkt%3D12%26sd%3D222485652156%26itm%3D273432026691%26pg%3D2047675&_trksid=p2047675.c100012.m1985 Y si no decirme donde las puedo comprar Muchas Gracias
  24. Meaning DSM does not accept your user password? Please be a bit more specific or if you get any errors.
  1. Load more activity