Leaderboard

dsm installs to all hdd's, in the system, thats how it works and as long as at least one disks is working you have a dsm system the usb is just the bootloader with the kernel, if you want to "kill" a dsm system you need to remove the 1st partition of all disks or just wipe the partition table of all disks as long as the loader still finds a system on disks it will try to update and keep settings, its supposed to be like that and needs to be seen from the perspective of a original syno system, if a hardware fails you can insert you disk in a replacement unit and will end up with a system exactly like it was before, the original unit has a usb DOM, same as our usb flash drives for xpenology, if the dom of the new system has a older kernel you can "repair" and the newer kernel from the disk will end on the usb dom and if the usb dom is newer you install the matching *.pat file (or newer) to the disks and updating the system and the result is supposed to behave the same as before, same ip, user, shares, packages (if possible) everything in jun's and rp loader is still around that base system from synology, jun's loader had a option to "reset" to factory defaults and there is a option like that on original systems, meant to be used when you screw up the config in a way its not supposed to be what makes up a dsm system, its the serial and mac in the (usb) loader and the config files of the dsm system partitons on disk, if you want to get rid of the system config you need to get rid of these config's and one way is to just remove the whole system partition on disk (i usually kill all partitions because dsm might behave different if it finds partitions an a disk that is supposed to be empty - that makes sense to prevent users using a "wrong" disk as replacement

Lately, I have been working on some issues you have mentioned. So whats new : - USB disk identification and update user_config.json option - SataPortMap and DiskIdxMap identification and update user_config.json option - Serial number and Mac address generation and update user_config.json option - user_config.json format validation - Image files have been updated to 1GB size and all files in /home/tc have been updated. - Added the backup option to backup /home/tc changes to local image for file repurposing if required in the future - Fixed included custom_config.json to point to Jumkey develop repo instead, as i see many have issues with unknown0 repo. - The default passwd of user tc is now P@ssw0rd (no need to set password for ssh) As always, rploader.sh file might be silently updated, so keep watching for updates. A normal build process would start with : 1. Image burn a. For physical gunzip and burn img file to usb stick b. For virtual gunzip and use the provided vmdk file 2. ssh to your booted loader or just open the desktop terminal 3. Bring over your json files (global_config.json,custom_config.json, user_config.json ) 4. Check the contents of user_config.json, if satisfied keep or else run : a. Change you serial and mac address by running ./rploader.sh serialgen DS3615xs b. Update user_config.json with your VID:PID of your usb stick by running ./rploader.sh identifyusb now c. Update user_config.json with your SataPortMap and DiskIdxMap by running ./rploader.sh satamap now (needs testing) d. Backup your changes to local loader disk by running ./rploader.sh backup now 5. ./rploader.sh build bromolow-7.0.1-42218

Has anyone else experienced synology being installed directly to the hdd? I noticed it the other when I went to build again, reboot, expecting to use find.synology.com to locate it, but was able to still use the ip address to get to the login screen like it nothing happened. I would have figured it would show up as a migrate or something in the reinstall. I ended up reflashing the usb and tried again and got the same result. It wasn't until I formatted the hdd when I was able to do a fresh install. If you look at my previous post, you can see that it seems to install it to the my smallest hdd.

Фу ..... А то я уже испугался )))) Разные проги, разное назначение.... AOMEI Partition Assistant - полный комплект инструментов по хардам. AOMEI Backupper - чисто Бэкапер и я сказал бы лучший. На Винде только им клонирую системные харды

Собрал последнюю версию .112 под DSM 6 TorrServer-6.0-MatriX.112-amd64.spk

I just installed tinycore redpill on a baremetal nas box, with two lan ports (realtek), and only one is showing up after dsm7.0.1 install. They showed up before in Jun's 1.0.4b dsm 6.2.3 they were both on and working. But now after editing user_config.json file with both mac1 and mac2 (different addresses) only mac1 shows up in dsm. Everything else from user_config.json worked including the serial. Just only have the one nic, cant find the other. Any advice?

right at this moment.. im creating new boot usb stick and starting from scratch... Ill let you guys know if it works

i can try, let me some time to prepare and compile

Hi to all, Finally, I've configured SSD Cache in DSM 7.0.1 using virtual disks configured in ESXi. Here the disk configuration of the Virtual Machine (that hosts the DSM): - redpill bootdevice: SATA disk. - volume disks: configured as SATA disks. - cache disks: configured as SCSI over paravirtual SCSI controller, and with the VMX config file edited to add scsi0:0.virtualSSD = "TRUE" for each cache disk. Then I installed redpill tinycore for DS3622xs+ with DSM 7.0.1 42218. So, as the "volume" disks are configured as SATA, and the "cache" disks as SCSI over the pvscsi driver (you need to configure redpill tinycore to add this driver and the vmxnet3), then all in the UI will work. The volume disks are detected in the range sda to sdl (disks 1-12) and the cache disks from sdm. And all of them present correct (fake) SMART values. Therefore, you can create all volumes that you want, and attach to them (using the UI) the cache disks that you want. I advise that I've configured the cache disks only for READ. If you want to enable READ-WRITE, then I recommend to put the host vmdk files in different devices. Be aware!!

SD3622xs+ with DSM 7.0.1-42218 running as a Virtual Machine inside ESXi 7.0 has native NVMe support:

For VMware its a but confusing. In my case and on many test VMs that i have SATA0:0 is always on PCI 02:04.0 and SATA 1:0 is on PCI 02.01.0 Having the following set : dmesg |grep -ie "Index Map" -ie "Port Map" [ 0.000000] Disk Index Map: 001008 [ 0.000000] Sata Port Map: 818 i get the following disks : ./lsscsi [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda --------> SATA 1:0 , Data disk 1 [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot ----------> Synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj ---------------> SCSI DISK 1 So counting the lspci -nnq output below, i conclude that the SATA devices come first on the list sorted by PCI bus and then the SCSI and SAS devices come next. ----------------------------- lspci -nnq | grep -ie SATA -ie SCSI -ie SAS ----------------------- 0000:00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) --> SCSI 0 0000:02:01.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 1:0 0000:02:04.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] --> SATA 0:0 0001:01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) ----> Redpill FAKE PCI devices 0001:02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)----> Redpill FAKE PCI devices 0001:08:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)----> Redpill FAKE PCI devices ------------------------------------------------------------------------------------------------- So with my settings Sata Port Map: 818 Disk Index Map: 001008 i get the following when i run lsscsi inside DSM. [0:0:0:0] disk VMware Virtual SATA Hard Drive 0001 /dev/sda [8:0:0:0] disk SATADOM- TYPE D 3SE 0001 /dev/synoboot [9:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sdj 8 disks for controller 02.01.0 SATA 1:0 --> Disk starting at 00 sda (1st disk) 1 disk for controller 02.04.0 SATA 0:0 --> Disk starting at 10 hex 8 disks for controller 00.10.0 SCSI 0 --> Disk starting at 08 sdj And that matches the output of lsscsi -Hv as well. sh-4.4# ./lsscsi -Hv |grep devices device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:10.0/host9 ------------------------------------------------------------ Same system with SataPortMap=1 and DiskIdxMap=00, also proves that SataPortMap acts also as a limit to the number of available ports. So if you set it wrong you might leave some disks outside. ./lsscsi -Hv |grep dev device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata7/host6 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata8/host7 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata9/host8 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata10/host9 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata11/host10 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata12/host11 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata13/host12 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata14/host13 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata15/host14 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata16/host15 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata17/host16 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata18/host17 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata19/host18 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata20/host19 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata21/host20 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata22/host21 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata23/host22 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata24/host23 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata25/host24 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata26/host25 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata27/host26 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata28/host27 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata29/host28 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata30/host29 device dir: /sys/devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata31/host30 device dir: /sys/devices/pci0000:00/0000:00:10.0/host31

ive added a new function to mount a smb share from tinycore.. could be handy to use it as a work folder to copy the loader.img to after build and pat etc.. u need to install cifs-utils. could be some better bash code.. its a bit rusty function mountshare(){ echo "smb user of the share, leave empty when you do not want to use one" read -r user echo "smb password of the share, leave empty when you do not want to use one" read -r password if [ -n "$user" ] && [ -z "$password" ]; then echo "u used a username, so we need a password too" echo "smb password of the share" read -r password fi echo "smb host ip or hostname" read -r server echo "smb shared folder. Start always with /" read -r share echo "local mount folder. Use foldername for the mount. This folder is created in /home/tc (default:/home/tc/mount)" read -r mountpoint if [ -z "$mountpoint" ] ; then echo "use /home/tc/mount folder, nothing was entered to use so we use the default folder" mountpoint="/home/tc/mount" if [ ! -d "$mountpoint" ]; then sudo mkdir -p "$mountpoint" fi else sudo mkdir -p "$mountpoint" fi if [ -n "$user" ] && [ -n "$password" ]; then sudo mount.cifs "//$server$share" "$mountpoint" -o user="$user",pass="$password" else echo "No user/password given, mount without. Press enter" sudo mount.cifs "//$server$share" "$mountpoint" fi } mountshare) mountshare ;; use: ./rploader.sh mountshare now

For the error , i've tested it thouroughly running it with user tc, do you run this as root or tc or sudo ? To add an extension run (**already in the help page): ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json to specify the mac address manually to match your adapter (which you shouldn't you should use a generated mac address) you can modify manually user_config.json

Compile is not heavily tested i should say. But its not very crucial, i plan to update the static RedPill extension regularly or once we have an update at least.

Hi, you can bring your own json configs, these are placeholders. They might work or they might not. I do not intent to maintain them anyway.

Well as i see it, you have only one PCI SATA controller 00:1f:2 that has 5 hosts (host0/1/2/3/4). There are cases where a single host can have multiple ports and other cases where each host is a single port. You may find it by running : ls -ldtr /sys/class/scsi_host//host*/device/port* ls -ldtr /sys/class/scsi_host/host*/device/target* ls -ldtr /sys/class/scsi_host/host*/device/phy* The USB disk which is host5 /home/tc$ lsscsi -Hv [0] ahci dir: /sys/class/scsi_host//host0 device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0 [1] ahci dir: /sys/class/scsi_host//host1 device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1 [2] ahci dir: /sys/class/scsi_host//host2 device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2 [3] ahci dir: /sys/class/scsi_host//host3 device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3 [4] ahci dir: /sys/class/scsi_host//host4 device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4 [5] usb-storage dir: /sys/class/scsi_host//host5 device dir: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/host5

The PCIID -> Module -> extensions is calculated using the available modules.alias that is available on Tinycore. A modules.alias.json exists on the repo where you downloaded the image. If you use that you will have your extensions identified correctly. Download the file and gunzip it in /home/tc https://github.com/pocopico/tinycore-redpill/blob/main/modules.alias.json.gz?raw=true

Good question, the loader is used to boot an OS that will assist on creating the two required partitions with all the required contents for installing DSM on the same USB stick. Still under development but if you like you can give it a try.

Oh, OK yes Class 0c04 is not take into consideration ... i will fix that.

Hi all, I find all great ideas ! I like the webui but maybe it’s overkill we’ll see how it goes. Loader capacity is not a big issue cause In tinycore you can download software upon request, same like I do for compiling the modules. The command is tce-load -iw xxx software As for the extensions, there is a function on version 0.2.2, that tries to figure out the class/pciid and then tries to match the extensions listed on my repo and automatically adds them. I’m still missing the manual add function though but It in my plans to do that soon.

As I am using a "DS918" I downloaded the pat file for DS1618 matching the same revision as mine ie 6.2.3-25426-3 Extracted: nvidia-modeset.ko nvidia-uvm.ko nvidia.ko Copied them into a folder in Volume1 Logged in via ssh and then did sudo -i Copied them from the folder in Volume1 to /usr/lib/modules/ Insmod the 3 nvidia files. Downloaded the runtime file and removed all reference to DVA and versions, so on installation it doesn't check it's a DVA machine. Installed the runtime library. Then nvidia-smi works. But need to work out how to get nvidia-docker2 on there so you can use containers in Docker with the GPU

Can you make an "guide for stupids" how to install nvidia drivers? I read all the post and I cant understand a ******* 😕 OK I will try to make a summary: First, install the drivers in /usr/lib/modules/ nvidia-modeset.ko nvidia-uvm.ko nvidia.ko Second, install the runtime library: https://archive.synology.com/download/Package/NVIDIARuntimeLibrary I can't download any of the driver files in this thread, my Syonology its an DS3617xs. Where I can find the drivers?