Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 01/24/2022 in all areas

  1. Hi all, A while ago I've started experimenting with a solution that would not require docker and/or a system running linux, but just a simple image that you can boot on your physical/virtual system and create the loader from there. I started with the plain disk image of 200MB size and tried to fit all in this image. As always first partition of the image is the synoboot1, second synoboot2 and third one (synoboot3) is tinycore. Tinycore is a simple linux distribution that can boot to a GUI so you can start creating the loader. Most network modules are included so you can verify also the extensions required on your system. A script will take care most of the actions that you would manually perform and just copy the loader contents to the 1st and 2nd partition. The loader is created from a pre-compiled redpill extension (should work) or you can compile it yourself (still testing). You can bring over and use the rp-helper configuration files so you dont have to do that again. To connect using ssh you will need first to reset the tc user password by typing # passwd tc The image can be found here: https://github.com/pocopico/tinycore-redpill Before starting the loader creation just run # ./rploader.sh update now and answer y I would appreciate any findings to improve the image.
    1 point
  2. Hi, I'm completely new to XPenology concept, so apologies in advance. Please guide me even if I am in the wrong forum. We had a RS815RP+ running DSM 5.2-5967 (update 6, I think) which served as common storage of 3 VMware ESXi servers. The connection between ESXi and NAS was via iSCSI/LUN. Unfortunately, the device broke down and now I am looking for a straightforward way to recover my VMs. Since the HDDs are in good health, I managed to mount them on a PC but the content is not what I expected to see. Below is a very short list from its root file system: [root@recoverypc synology]# ls -l total 3380 drwxrwxrwx 6 root root 4096 Apr 27 2018 @appstore -rw------- 1 root root 10240 Sep 16 2020 aquota.group -rw------- 1 root root 13312 Sep 16 2020 aquota.user drwx------ 2 root root 4096 Sep 14 2016 @autoupdate drwxr-xr-x 6 1024 users 4096 Nov 17 2016 @database drwx------ 2 root root 4096 Dec 25 22:22 @EP drwx------ 2 root root 4096 Jun 11 2016 @iSCSITrg drwx------ 2 root root 16384 May 8 2015 lost+found drwxr-xr-x 2 root root 4096 May 8 2015 @S2S -rw------- 1 root root 3649536 Nov 1 2016 @smbd.core -rw------- 1 root root 5120 May 15 2015 synoquota.db drwxrwxrwt 3 root root 4096 Sep 29 12:27 @tmp -rw-r--r-- 1 root root 28672 Jul 6 2015 winbindd_cache.tdb [root@recoverypc synology]# ls -lh \@EP total 11430513168 -rw-r--r-- 1 root root 4.1T Sep 29 12:28 EP_BUF -rw-r--r-- 1 root root 4.1T Sep 29 12:28 EP_DAT_00000 -rw------- 1 root root 4.1T Sep 29 12:28 EP_DAT_00001 -rw------- 1 root root 2.7T Sep 29 12:28 EP_DAT_00002 -rw-r--r-- 1 root root 4.1T Sep 29 12:28 EP_FRI -rw-r--r-- 1 root root 4.1T Sep 29 12:28 EP_ROD -rw-r--r-- 1 root root 4.1T Sep 29 12:28 EP_TBL From Synology Support they said that the recovery will be possible only if a new Synology NAS is used to replace the old one. Since I'm not going for a new Synology again, I would highly appreciate some instructions on how to use XPenology in order to access my VMs (vmdk, vmx, etc)? Thanks in advance.
    1 point
  3. 1 point
  4. this is the same as the one i offer under additional drivers for 3617, just sr_mod and cdrom added https://clicknupload.cc/bteubeic2y0k
    1 point
  5. The weird thing is that adamadam has a 1000:0072. So i think he can be helped with ds3615xs and mpt2sas. I can be mistaken too.
    1 point
  6. ./rploader.sh ext bromolow-7.0.1-42218 add *url* for 3615xs replace „bromolow-…“ With matching device Type and Version so you’re fine. Add *url* of your choice of Repo at Github, mostly recommended Pocopico‘s ones.
    1 point
  7. No problem, glad you’re up & running. Do not update beyond 6.2.3u3 with loader 1.03b, later versions of DSM require a different boot loader.
    1 point
  8. That’s as it should be, you need to access it from another machine’s web browser
    1 point
  9. Did you try find.synology.com?
    1 point
  10. Sorry i didn't notice his disk was on port 3, i suggested sataportmap = 1 as he only has one disk and that worked for me when testing. I'm still learning myself
    1 point
  11. That was by design, and part of ThorGroup's effort to limit Synology's telemetry monitoring.
    1 point
  12. SSD, если и ставят, то для КЭШ_а. Особого прикладного значения в нём нет, если только в единичных, для нашего с вами применения, случаях. Если собираетесь создавать весь массив из SSD, то возможно прирост скорости и будет, но опять таки, по задачам нужен ли он ? Поставьте его на по-Играться, потом замените на основные харды.
    1 point
  13. Yes it works without any Problems, the Solution did you find here ........read buggy25200 information!
    1 point
  14. 918 не взлетит на этом проце. 3615 или 3617.
    1 point
  15. Hello everyone, today finally after some failed attempts (because I was wrong with the procedure) I was able to install a new diskstation 918+ vers. DSM 7.0.1 in vm mode on virtualbox to test it (I need to install it in baremetal mode on a special server) with an image downloaded from the network, unfortunately I am not able to build it myself and everything is ok, it seems to work correctly and I will test it for a few days with installation tests of the applications I need. I needed to know something for those who have already done it or are aware of it and it is this; having the need to install DSM 7.0.1 on a special machine in baremetal mode where a DSM 6.2.3 up3 version already runs, must a new installation be made or can you do a migration? The migration obviously (as long as everything goes well) is much faster and less expensive in terms of time, obviously for safety I would back up the whole machine but if it were possible to do the migration it would be much better. Does anyone know if it is possible and possibly how ??? Thank you
    1 point
  16. Тогда зачем цепляться за 1151 и проц с 610 ядром?
    1 point
  17. Да...... Поставьте 3615 и посмотрите вдумчиво. Особо файлами не забивайте. А через время придёт понимание необходимого и тогда создадите финальный штрих Я когда был в начале славных дел, трижды перестанавливал, пока моя конфигурация не родилась
    1 point
  18. Hi, @dodo-dk Exact ! Be carreful do not update ds3617xs to DSM 7.0.1-42218 Update 1 or 2 without reading this more, There is a new zimage and rd, you can see the pat size is more weight than ds3615xs or 918+ synology_broadwell_3617xs.pat 26.98MB synology_bromolow_3615xs.pat 10.10MB synology_apollolake_918+.pat 10.53MB And there is a problem (a problem for futur ?!) A priori, the new pat file on synology download site are no longer gz type archive! And so they are no longer usable by our current scripts. It is possible that all pat files will be distributed in this new format. I have prepared the bsp for update 2, you can up to update 2 without going through update 1. But to be able to use it, you will have to produce a PAT file yourself! WHAT ?! 😢 And this as long as we do not have a tool allowing extraction of these pat files with a script. I cannot provide you the PAT file i made, because it contains proprietary data. In order to produce your PAT file, here is a procedure to follow: Prerequisites You must have a machine with a ds3617xs 701 already install, on the LAN, and with a serial connection capability. (A virtual machine is the best choice) And another machine to receive the PAT file (with ssh server un this procedure). Launch a manual migration to update 2 from GUI DSM 7.0.1. After the reboot which will fail! Connect to the serial port You can see why it didn't work... DiskStation> cat /var/log/junior_reason Exit on error [7] root not matched with junior... Which means that your bootloader is no longer usable with the current version. DiskStation> mkdir /root/tmproot DiskStation> mount /dev/md0 /root/tmproot/ DiskStation> mount /dev /root/tmproot/dev DiskStation> chroot /root/tmproot /bin/bash DiskStation> chroot /root/tmproot /bin/bash bash-4.4# cd /.syno/patch bash-4.4# tar -zcvf mypat.pat * bash-4.4# scp mypat.pat yourlogin@ipremotemachine:~ Here you have your PAT file ! In this tutorial I work with the rp-helper tool but you can use what you prefer. Put your PAT file in the cache download directory so that it can be used without downloading synology's one, or host your file on a server and modify the pat_url! Add in your global_config.json ... { "id": "broadwell-7.0.1-42218u2-test", "platform_version": "broadwell-7.0.1-42218u2", "user_config_json": "USERCONFIG.json", "docker_base_image": "debian:9-slim", "redpill_lkm_make_target": "test-v7", "compile_with": "toolkit_dev", "downloads": { "kernel": { "url": "https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.180.tar.gz", "sha256": "519ff74ceaa52462d6b9a8452d90ba5cd009807830134de5e1df269b44dd380b" }, "toolkit_dev": { "url": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwell-7.0.dev.txz/download", "sha256": "e050987fbbab0c246aff2af935b1d8a4140ce490915aa4c92f3c8d163eea970c" } }, "redpill_lkm": { "source_url": "https://github.com/jimmyGALLAND/redpill-lkm.git", "branch": "develop" }, "redpill_load": { "source_url": "https://github.com/jimmyGALLAND/redpill-load.git", "branch": "develop" } } .... I advise you to clone develop branch https://github.com/jimmyGALLAND/redpill-lkm.git in a directory and modify global_config.json to set "local_rp_load_use" to true in order to be able to use a modify config.json file ... "docker": { "use_buildkit": "true", "image_name": "redpill-tool-chain", "download_folder": "docker/downloads", "local_rp_lkm_use": "false", "local_rp_lkm_path": "./redpill-lkm", "local_rp_load_use": "true", "local_rp_load_path": "./redpill-load", ... In redpill-load edit config.json file under config/DS3617xs/7.0.1-42218u2/config.json ... { "os": { "id": "ds3617xs_42218u2", "pat_url": "https://global.download.synology.com/download/DSM/criticalupdate/update_pack/42218-2/synology_broadwell_3617xs.pat", "sha256": "XXXXXXXXXXXXXXXXXXX" put here the sha256sum of your PAT file }, .... In order to use virtio or redpill-boot-wait for ds3617xs_42218u2 You can use https://github.com/jimmyGALLAND/redpill-ext I will update the @pocopico ext repo coming days. Good night people
    1 point
  19. Для определения VID/PID исторически пользуюсь USB Device View входящим в XPENOLOGY TOOL 1.4.2 И в конфете вроде все так же... любят, очень любят! с загрузчиком от Jun's версия 6.2.3-25426 встает и работает как родная!
    1 point
  20. Just a new Xpen user... Very cool! My question is do most home users need the newest update? I humbly suggest no. I just use mine to save family photos, movies, music. The fact that we can take an old desktop and make a super fast NAS is incredible. Thanks to ALL of you that created and help to improve this project. Often makes me wonder if we channeled your brain power and ingenuity to solving cancer we could make inroads THANKS!!!
    1 point
  21. Here is how you can edit grub after dsm6 install (if using esxi make sure the boot drive is NOT non-persistent for this to work): SSH into dsm and type echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt /mnt/grub/grub.cfg umount /mnt or for using winscp to edit the file with notepad++ (vi editor is not that hard, but...): 1. Login using putty or any other ssh client with administrator account (usually "admin") 2. You will be asked for a password. Enter the one for the administrator account 3. You will get a command prompt 4. Enter: sudo su - 5. You will be asked for a password. Enter again the one for the administrator account 6. You will get a command prompt root@... 7. Enter command: synouser --setpw root your_new_root_password For "your_new_root_password" please use the desired password for root account. Nou you can SSH into dsm and type echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt start winscp and connect to your dsm (user root and the password you set before) an go to /mnt/grub/ and edit grub.cfg Save and close editor when finished. Get back to the ssh sesion and do umount /mnt It is easier to edit the cfg before install, in win10 just write on the usb stick (after writing it using winimage or rufus); for older windows you have to mount the image and edit the cfg before writing to usb stick. You can try to create a new usb and switch the one you have working on the current install to avoid using ssh, if it's not working just plug the old one in again. For esxi users: use osfmount or vmware workstation to mount the vmdk boot image and edit the cfg.
    1 point
×
×
  • Create New...