smileyworld

I found a software, which checks most of my requirements -> wisemapping If you want to try it out in docker you can have a look here

I am looking for a self hosted mind map tool. I don't mind if it runs in DSM as package or in docker as container, but it should have similar features like coggle. Does anyone have recommendations?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 - Loader version and model: PeterSuh's tcrp v0.9.4.3-2 JOT DS3622xs+ - Using custom extra.lzma: NO - Installation type: Baremetal - Additional comments: + Unplugged the X540-T2 NIC before upgrading + built new loader + upgrade existing DSM via Synology Assistant

@AbuMoosa it also works if the host is xpenology and the recording server is virtualized DSM. @Yuriy Pelekh depends where you add your camera. If you add all cameras to NAS1, then all resources (CPU/RAM/STORAGE) will be used from NAS1. However if you add the cameras not only to NAS1, then the resources will be shared.

Habe es gerade getestet und es ist möglich mit nur einem Xpenology System auszukommen. Habe am Host (Xpenology 7.2-64561) 2 Gratislizenzen + 1 Lizenz aus VDSM (7.2-64570) die mittels CMS geteilt wird. Die VDSM Lizenz ist gekauft und musste in VDSM aktiviert werden, weil man die Lizenz am Xpenology Host nicht aktivieren kann. Man könnte aber auch gleich einfach einen anderen Loader, der mehr Gratislizenzen bietet, verwenden -> DVA1622 CPU mit 4 physischen Kernen / 4 virtuellen Kernen DVA3221 CPU mit 4 physischen Kernen / 4 virtuellen Kernen Quellen: CPU physische / virtuelle Kerne Tutorial für Lizenzen zwischen Synology / Xpenology / VDSM teilen

I just stumbled across this categorized list for Docker containers. If anyone is interested, take a look -> https://mariushosting.com/docker/

Hey argate7, I personally would try it with this guide: https://www.digitalocean.com/community/tutorials/how-to-install-and-set-up-laravel-with-docker-compose-on-ubuntu-22-04

Found the answer on synology's website for my original problem. You need the pro version for nested VMs. If anyone needs it, here is the documentation.

Expansion unit No I do not have an original expansion unit. But it would be nice to be able to see the 10 remaining disks via expansion unit(s). PCIe cards Thanks for the hint. I will have a look and report back if I find anything interesting.

Is it possible to display expansion units (Synology DX1222) or pci-cards (intel X540-t2) in DSM7-TCRP like this? I am asking because it would be nice if I could see all my (22) drives and for example instantly know which drive I have to replace. For now it looks like this. My guess is, DSM only displays 12 drives in use because the DS3622xs+ has only 12 slots.

I can finally report that I fixed it. What I did to resolve my issue tried to determine if it is a hardware/software failure connected 8 disks to 1 HBA (HBA2 was not installed at that time) and checked if every disk was listed (computer management in windows server 2016, another OS would probably work as well) unplugged HBA1 and connected HBA2 -> also checked if 8 disks were listed -> one disk was missing, so I checked all connectors and one was loose. flashed firmware of my second HBA. connected both HBAs, installed 22 disks and all were listed in WIN server 2016 unplugged my X540-T2 10Gbit NIC installed Xpenology as follows ran command by command ./rploader.sh clean ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh identifyusb ./rploader.sh serialgen DS3622xs+ vi user_config.json adapted my user_config.json to my environment { "extra_cmdline": { "pid": "0x1000", "vid": "0x090c", "sn": "xxxxxxxxxxxxx", "mac1": "xxxxxxxxxxxxx", "mac2": "xxxxxxxxxxxxx", "mac3": "xxxxxxxxxxxxx", "SataPortMap": "", "DiskIdxMap": "" }, "synoinfo": { "esataportcfg" : "0x00", "usbportcfg" : "0xc00000", "internalportcfg" : "0x3fffff", "maxdisks": "22", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no" }, "ramdisk_copy": {} ran these commands to finish the tcrp loader ./rploader.sh build broadwellnk-7.1.0-42661 ./rploader.sh backup ./rploader.sh backuploader exitcheck.sh reboot plugged my x540 in connected my LAN cable to one of the LAN ports booted from USB and installed the appropriate DSM_DS3622xs+_42661.pat Special thanks to @Peter Suh @IG-88 @flyride for your support.

@Peter Suh Yes that's true. It looks like it's a firmware issue after all. I connected my NAS to a display and was wondering why only one of the HBAs was displaying in BIOS (ctrl +c). Now 2 hours later I learned that I have 2 different controller cards even though they were sold both as LSI 9211-8i (IT-mode). It seems there was so much rebranding and the companies used same or similar chips (sas2008) but different BIOSes. At least someone mentioned this here -------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------- MegaRAID is however able to see both HBAs and collects the following data from both cards. I thought it would make troubleshooting easier when I simplify things (install same Firmware/BIOS) but oh boy it keeps getting more and more complex😅 HBA SGX-SAS6-INT-Z has BIOS version 07.39.02.00_07.24.01.00 is working but I cannot enter the BIOS at all It wont let me "update" the BIOS with 07.39.02.00 probably because downgrading firmware is not allowed windows server 2016 cant find a suitable driver for this card HBA SAS9211-8i has BIOS version 07.39.02.00 has a working BIOS which I can enter with Ctrl + C. windows server 2016 installs the best driver for this card on its own. So at this point I do not know where to find either a firmware newer than 07.39.02.00_07.24.01.00 with a working BIOS or a way to downgrade the SGX-SAS6-INT-Z HBA to 07.39.02.00. Furthermore I am not sure if this would fix my/our problem. Do both of your HBAs have the same BIOS version?

There also seems to be a known issue with duplicate drives which is documented even by broadcom itself. Interestingly this is also a bad firmware problem. https://www.broadcom.com/support/knowledgebase/1211161495925/flash-upgrading-firmware-on-lsi-sas-hbas-upgraded-firmware-on-92

@Peter Suh I am not so sure anymore that it has solely to do with tcrp or DSM7. I tried plugging in 22 drives and even in mint only 20 are recognized. Maybe there is also an issue with the HBA or a cable. I also saw during boot that there my two HBAs are on different BIOSes. My plan is to identify the missing drives first and then changing the drives to different slots, so I can be sure all drives are ok. Next thing will be to upgrade firmware of my HBAs. If that doesnt help, than i really dont know where to look even further.

Yes that was me and I checked it. I will report back tomorrow. Maybe I found something which would explain the behavior, but I want to double check first.

@Peter SuhLooks like only drives in slot 11-13 are recognised by tc even though the scsi-5.10.3-tinycore64.tcz was saved and I got an OK message. lrwxrwxrwx 1 root root 0 Jul 2 03:52 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jul 2 03:52 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jul 2 03:52 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc

I can tell you only my point of view why I decided to go for more power. There are two main reasons for my beefy hardware. I wanted to use my NAS for a LAN-Cache and for VMs Even though my NAS does so much more. It is like a server dedicated to many tasks. For me there was a sweet spot to choose for buying hardware. My variables were: compatible hardware price availability electrical power consumption raw performance in DSM (CPU + RAM + read and write for my volume) That's for example why I use 5 SSDs for a single Volume in RAID 0 and have a 10 Gbit NIC in use. However, I don't care about how much performance DSM itself needs to run basic NAS OS tasks. If you want to know more about this topic I can recommend you this Video.

@IG-88Thanks for correcting my mistake. Nonetheless, when I try it with the DS3617xs loader the outcome unfortunately still the same.

I am currently switching from DSM 6.2 to 7.1 and my setup is as follows: How to expand drive number in DSM7? Now my problem is, that it is not possible to do the same trick in DSM 7 to expand beyond x drives like it was in 6.2. (My setup would allow 22 in total from which 14 are used for now) I already chattet with @Peter Suhabout this topic but unfortunetly we could not solve my problem. Things I tried: Building the loader as described by @Peter Suh (Guide) installed the latest tcrp image with rufus on usb booted in tc & connected via ssh ./rploader.sh update ./my.sh ./rploader.sh clean ./my.sh DS3622xs+J poco noclean Building the loader as described by @flyride (Guide) installed the latest tcrp image with rufus on usb booted in tc & connected via ssh ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh identifyusb ./rploader.sh serialgen DS3622xs+ #I tried building the loader with and without this command ./rploader.sh satamap vi user_config.json # adding those lines: "maxdisks" : "22", "esataportcfg" : "0x00", "usbportcfg" : "0xc000000", "internalportcfg" : "0x3fffff", ./rploader.sh build broadwellnk-7.1.0-42661 ./rploader.sh backup ./rploader.sh backuploader exitcheck.sh reboot Seutp & outcome VM or BareMetal : BareMetal Hardware (Motherboard/CPU) : MSI MPG Z390 / Intel 9900T Storage-Controller: 2x LSI SAS 9211-8i (HBA in IT mode) Hot Plug Applied : Yes Network Interface 1 : Intel i217v (e1000e) Network Interface 2 : Intel X540-T2 (10 Gbit) Network Interface 3 : Intel X540-T2 (10 Gbit) Loader : TCRP 0.4.6 version of rploader.sh : 0.8.3 Platform : 3622xs+ Platform Version : 7.1 Platform Revision : 42661-U1 GRUB Boot selection : USB Unfortunetly both methods resulted in the same outcome which is the following: My NAS looks physically like this. I numbered the drive slots from 1 - 22 to have an easier time explaining my issue. So slotnumber 1-8 are connected to HBA 2 9,10 and 17-22 are connected to HBA 1 11-16 are connected to the mainboard SATA ports I have 3 PCIx16 Slots on my mainboard First one is used for Intel X540 T2 10 GBit NIC Second one is used for HBA1 Third one is used for HBA2 Currently the slots below are occupied: 1-4 = 4 HDDs 6-9 = 4 HDDs 11-13 = 3 SSDs 17-19 = 3 SSDs = 14 drives in total. Now in this config either slot 6 or 7 isnt recognised in DSM, every other drive works. When I put the drive from slot 6 into slot 5 it is reconised, BUT unfortunately one drive from slots 1-4 is missing then. I tried this with multiple combinations. The outcome was always that 1 drive was missing (not a specific HDD/SSD or SLOT). As soon as I add more than 13 drives it keeps getting weird. Since my setup worked in DSM6 my guess is that either I am missing something or TCRP is missing something. Troubleshooting: TinyCore sd list lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop10 -> ../devices/virtual/block/loop10 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop11 -> ../devices/virtual/block/loop11 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop12 -> ../devices/virtual/block/loop12 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop13 -> ../devices/virtual/block/loop13 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop14 -> ../devices/virtual/block/loop14 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop15 -> ../devices/virtual/block/loop15 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop16 -> ../devices/virtual/block/loop16 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop17 -> ../devices/virtual/block/loop17 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop18 -> ../devices/virtual/block/loop18 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop19 -> ../devices/virtual/block/loop19 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop20 -> ../devices/virtual/block/loop20 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop21 -> ../devices/virtual/block/loop21 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop22 -> ../devices/virtual/block/loop22 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop23 -> ../devices/virtual/block/loop23 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop24 -> ../devices/virtual/block/loop24 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop25 -> ../devices/virtual/block/loop25 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop26 -> ../devices/virtual/block/loop26 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop27 -> ../devices/virtual/block/loop27 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop28 -> ../devices/virtual/block/loop28 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop29 -> ../devices/virtual/block/loop29 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop30 -> ../devices/virtual/block/loop30 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop31 -> ../devices/virtual/block/loop31 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop32 -> ../devices/virtual/block/loop32 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop33 -> ../devices/virtual/block/loop33 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop34 -> ../devices/virtual/block/loop34 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop35 -> ../devices/virtual/block/loop35 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop36 -> ../devices/virtual/block/loop36 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop37 -> ../devices/virtual/block/loop37 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop38 -> ../devices/virtual/block/loop38 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop39 -> ../devices/virtual/block/loop39 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop40 -> ../devices/virtual/block/loop40 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop41 -> ../devices/virtual/block/loop41 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop42 -> ../devices/virtual/block/loop42 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop43 -> ../devices/virtual/block/loop43 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop44 -> ../devices/virtual/block/loop44 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop45 -> ../devices/virtual/block/loop45 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop46 -> ../devices/virtual/block/loop46 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop47 -> ../devices/virtual/block/loop47 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop48 -> ../devices/virtual/block/loop48 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop49 -> ../devices/virtual/block/loop49 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop50 -> ../devices/virtual/block/loop50 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop51 -> ../devices/virtual/block/loop51 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop8 -> ../devices/virtual/block/loop8 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop9 -> ../devices/virtual/block/loop9 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 26 09:08 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdd -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host6/target6:0:0/6:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jun 26 09:08 zram0 -> ../devices/virtual/block/zram0 Synology sd list dummy@NAS:~$ ll /sys/block total 0 drwxr-xr-x 2 root root 0 Jun 26 11:00 . dr-xr-xr-x 12 root root 0 Jun 26 11:00 .. lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-0 -> ../devices/virtual/block/dm-0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-1 -> ../devices/virtual/block/dm-1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-2 -> ../devices/virtual/block/dm-2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-3 -> ../devices/virtual/block/dm-3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-4 -> ../devices/virtual/block/dm-4 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-5 -> ../devices/virtual/block/dm-5 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-6 -> ../devices/virtual/block/dm-6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md2 -> ../devices/virtual/block/md2 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md3 -> ../devices/virtual/block/md3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md5 -> ../devices/virtual/block/md5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 26 11:00 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 26 11:00 sde -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdg -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sdg lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdh -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:1/end_device-6:1/target6:0:1/6:0:1:0/block/sdh lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdi -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:2/end_device-6:2/target6:0:2/6:0:2:0/block/sdi lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdj -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:3/end_device-6:3/target6:0:3/6:0:3:0/block/sdj lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdk -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:0/end_device-8:0/target8:0:0/8:0:0:0/block/sdk lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdl -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:1/end_device-8:1/target8:0:1/8:0:1:0/block/sdl lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdm -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0/block/sdm lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdn -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:3/end_device-8:3/target8:0:3/8:0:3:0/block/sdn lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdo -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:4/end_device-8:4/target8:0:4/8:0:4:0/block/sdo lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdp -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:5/end_device-8:5/target8:0:5/8:0:5:0/block/sdp lrwxrwxrwx 1 root root 0 Jun 26 11:00 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host7/target7:0:0/7:0:0:0/block/synoboot lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram0 -> ../devices/virtual/block/zram0 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram1 -> ../devices/virtual/block/zram1 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram2 -> ../devices/virtual/block/zram2 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram3 -> ../devices/virtual/block/zram3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram4 -> ../devices/virtual/block/zram4 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram5 -> ../devices/virtual/block/zram5 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram6 -> ../devices/virtual/block/zram6 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram7 -> ../devices/virtual/block/zram7 Ubuntu tryout sd list root@ubuntu:~# ll /sys/block total 0 drwxr-xr-x 2 root root 0 Jun 26 09:24 ./ dr-xr-xr-x 13 root root 0 Jun 26 09:24 ../ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop0 -> ../devices/virtual/block/loop0/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop1 -> ../devices/virtual/block/loop1/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop2 -> ../devices/virtual/block/loop2/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop3 -> ../devices/virtual/block/loop3/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop4 -> ../devices/virtual/block/loop4/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop5 -> ../devices/virtual/block/loop5/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop6 -> ../devices/virtual/block/loop6/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop7 -> ../devices/virtual/block/loop7/ lrwxrwxrwx 1 root root 0 Jun 26 09:25 loop8 -> ../devices/virtual/block/loop8/ lrwxrwxrwx 1 root root 0 Jun 26 09:27 loop9 -> ../devices/virtual/block/loop9/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sda -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdb -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdc -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdd -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sde -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sde/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdf -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:1/end_device-7:1/target7:0:1/7:0:1:0/block/sdf/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdg -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:2/end_device-7:2/target7:0:2/7:0:2:0/block/sdg/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdh -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:3/end_device-7:3/target7:0:3/7:0:3:0/block/sdh/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdi -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:4/end_device-7:4/target7:0:4/7:0:4:0/block/sdi/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdj -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:5/end_device-7:5/target7:0:5/7:0:5:0/block/sdj/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdk -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdk/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdl -> ../devices/pci0000:00/0000:00:17.0/ata1/host1/target1:0:0/1:0:0:0/block/sdl/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdm -> ../devices/pci0000:00/0000:00:17.0/ata2/host2/target2:0:0/2:0:0:0/block/sdm/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdn -> ../devices/pci0000:00/0000:00:17.0/ata5/host5/target5:0:0/5:0:0:0/block/sdn/ I would appreciate any hints🙂

I face a similar problem however my setup is a bit different. VM or BareMetal : BareMetal Hardware (Motherboard/CPU) : MSI MPG Z390 / Intel 9900T Storage-Controller: 2x LSI SAS 9211-8i (HBA in IT mode) Hot Plug/Hot Swap Applied : Yes Network Interface 1 : Intel i217v (e1000e Not working for me in xpenology) Network Interface 2 : Intel X540-T2 (10 Gbit) Network Interface 3 : Intel X540-T2 (10 Gbit) version of rploader.sh : 0.8.3 Platform (DS3622xsp/DS918+/DS920+/DVA3221/DS1621+/DS3615xs/DS3617xs) : 3622xs+ Platform Version (6.2.4/7.0.1/7.1) : 7.1 Platform Revision (42218/42661/42661-U1) : 42661 GRUB Boot selection : USB Current Status : Boots to kernel Both of my LSI SAS 9211 are recognised but I cant add more than 13 drives. As soon as I add the 14th drive to one of my SAS controllers another HDD/SDD isn't recognised any more. I tried editing the user.conf according to this tutorial (this worked for me in DSM 6) but DSM7 keeps behaving weird.

Maybe I didn't read every post in this thread carefully enough but do we have a loader for DS3617xs on DSM7? I am asking cause my CPU has 16 threads and as far as I know DS3615xs only supports 8 threads. The screenshot is from flyride's post on October 19, 2018

Do we have some community members who are capable of what @ThorGroupwas intending to do? And if so, are they willing to do it? No pressure from my side, but I really want this project to grow

I'd be looking forward to be one of the first users to use DSM 7 in my production enviornment as soon as the redpill loader hits a release candidate state. @ThorGroupLet me know if there is anything I can support you with.

Follow up question on VMM and AMD CPUs. Since Synology is using the AMD Ryzen Embedded V1500B in their product line up (where VMM is working), shouldn't it be possible to work with VMM in xpenology as well? I'm asking cause I am thinking of switching my Intel i3-8100 to an AMD Ryzen 7 3700X and I'd like to use VMM.

I changed my RAID configuration. For anyone interested: 4x WD RED 3TB HDDs in RAID 5 dd if=/dev/zero of=/volume1/homes/lan/testx bs=4096M count=1 conv=fdatasync oflag=direct 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB) copied, 19.9718 s, 108 MB/s