Null Posted March 24, 2022 Share #3901 Posted March 24, 2022 dsm 7.1 has launched,when will our loader update? Link to comment Share on other sites More sharing options...
Carl10 Posted March 25, 2022 Share #3902 Posted March 25, 2022 @Peter Suh@progressives, I got my 5th drive and wanted to give you my data on the "hot Swap" and muxed ports for my x99 chipset. I originally had drive install errors and then set my SataPortMap=2 (for my 2 drives) and DiskIdxMap=00 and my problems went away. I then added 2 more drives and I learned about/changed both the bios sata ports to "Hot Swappable" and I changed the SataPortMap=4. New drives added no problem. Today I added a 5th drive, and knowing ports 5&6 are muxed with the M.2 slot on my MB and reading Peter's summary of how the ports worked, I connected the 5th drive to port 7 (avoiding 5&6) and left SataPortMap=4 . The drive worked fine but the mapping moved the new drive attached to port 7 in position 1 and the original 4 drives were then moved to position 5,6,7,8. I changed SataPortMap=5 and the drives moved to 6,7,8,9 and setting SataPortMap=7 (why not try since the new drive was on port 7) kept the new drive on port 7 in position 1 and the original 4 were then on 8,9,10,11. Lastly I changed SataPortMap=1 and the port 7 drive stayed in position 1 and the original 4 are now in position 2,3,4,5. Conclusion: Hot Swap definitely resolved the drive installation/recognition issues. SataPortMap=1 and DiskIdxMap=00 solved the random disk placement. Port 7=disk 1 makes sense to me in that port 7 is the first port of the other sata controller (2 controllers on this MSI X99 SLI MB for 10 ports, or 8 ports if you use the M.2 slot) Hope this helps someone. 2 Link to comment Share on other sites More sharing options...
Hackaro Posted March 25, 2022 Share #3903 Posted March 25, 2022 On 3/20/2022 at 8:38 AM, Peter Suh said: After installing DSM during the test...I found something strange. Checking out lspci...I found the bus below. 0001:09: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) 0001:0c: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) It's strange. I'm working on a XPE 918+ and I do have Marvell9215 but I guess it's because it's builtin hardware directly in the .pat file of this specific DS918 version of DSM 7.0.1 . In other words DSM loads Marvell SATA controller because it knows a real DS918 has a Marvell controller among its peripherals. it loads without checking a real presence of that peripheral, just because it's built-in. I was wondering whether I really insert a PCI Marvell 9215 controller card, Synology DSM correctly recognises it in the appropriate PCI address... 1 Link to comment Share on other sites More sharing options...
Hackaro Posted March 25, 2022 Share #3904 Posted March 25, 2022 On 3/23/2022 at 9:55 PM, RedwinX said: With Redpill 7.0.1-42218 based on ds918+, it works fine, with a modded i915.ko how have you modded i915.ko? @RedwinX Link to comment Share on other sites More sharing options...
RedwinX Posted March 25, 2022 Share #3905 Posted March 25, 2022 13 minutes ago, Hackaro said: how have you modded i915.ko? @RedwinX https://xpenology.com/forum/applications/core/interface/file/attachment.php?id=13629 Link to comment Share on other sites More sharing options...
Hackaro Posted March 25, 2022 Share #3906 Posted March 25, 2022 (edited) 18 minutes ago, RedwinX said: https://xpenology.com/forum/applications/core/interface/file/attachment.php?id=13629 2.48 MB · 123 downloads Thanks! @RedwinX Recently I've installed RedPill-TC (0.46-uefi version) with DSM 7.0.1-42818 on my hardware (in signature) and everything is working pretty well after one month of testing. But one small problem is with HW acceleration of my iGPU... my CPU is an i3-8100 and its Device ID is 3e91 which is supported OOB from Synology DSM (at least the 6.x version). lspci -nnQ 0000:00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] [8086:3e1f] (rev 08) 0000:00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e91] but if I check: more /usr/syno/etc/codec/activation.conf {"success":false,"msg":"SN format is wrong."} it seems there is no HW acceleration... even if this check of the presence of dev/dri: ls -al /dev/dri total 0 drwxr-xr-x 2 root root 80 Mar 25 10:47 . drwxr-xr-x 12 root root 14440 Mar 25 10:48 .. crw------- 1 root root 226, 0 Mar 25 10:47 card0 crw-rw---- 1 root videodriver 226, 128 Mar 25 10:47 renderD128 which might indicate me that the HW GPU acceleration is in place. Using VideoStation I can see it can transcode FHD H.264 movies with roughly 25/26% of CPU utilisation, which is significant higher than expected for a 4 cores CPU. Can someone help me in going in the right direction? Edited March 25, 2022 by Hackaro Link to comment Share on other sites More sharing options...
Peter Suh Posted March 29, 2022 Share #3907 Posted March 29, 2022 Is DS3622xs+ the only platform with stable HBA in baremetal? I need to migrate while maintaining HBA stability to other platforms on baremetal. Is there anyone who can confirm this part? Link to comment Share on other sites More sharing options...
RacerX Posted March 31, 2022 Share #3908 Posted March 31, 2022 Today I tested twice on G7 Ds918+ apollolake-7.0.1-42218 The script runs but after the pat is downloaded it says [!] Failed to unpack tar /usr/local/bin/tar: bios.ROM: Wrote only 5120 of 10240 bytes /usr/local/bin/tar: platform.ini: Cannot write: No space left on device /usr/local/bin/tar: hda1.tgz: Cannot write: No space left on device /usr/local/bin/tar: indexdb.txz: Cannot write: No space left on device /usr/local/bin/tar: synohdpack_img.txz: Cannot write: No space left on device /usr/local/bin/tar: packages/dsm6-ui-compatible-1.0.0-0090.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/USBCopy-x86_64-2.2.0-1076.spk: Cannot write: No spa ce left on device /usr/local/bin/tar: packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk: Cann ot write: No space left on device /usr/local/bin/tar: packages/SecureSignIn-x86_64-1.0.3-0138.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/ScsiTarget-x86_64-1.0.2-0207.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/SMBService-x86_64-4.10.18-0316.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/Python2-x86_64-2.7.18-1004.spk: Cannot write: No sp ace left on device /usr/local/bin/tar: packages/OAuthService-x86_64-1.1.2-0071.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/HybridShare-apollolake-1.2.0-0650.spk: Cannot write : No space left on device /usr/local/bin/tar: packages/HighAvailability-x86_64-2.1.1-1279.spk: Cannot writ e: No space left on device /usr/local/bin/tar: packages/FileStation-x86_64-1.3.1-1382.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/DhcpServer-x86_64-1.0.0-0034.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/ActiveInsight-x86_64-1.1.0-1121.spk: Cannot write: No space left on device /usr/local/bin/tar: texts/chs/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/cht/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/csy/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/dan/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/enu/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/fre/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ger/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/hun/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ita/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/jpn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/krn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/nld/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/nor/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/plk/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ptb/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ptg/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/rus/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/spn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/sve/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/tha/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/trk/strings: Cannot write: No space left on device /usr/local/bin/tar: expired_models: Cannot write: No space left on device /usr/local/bin/tar: DiskCompatibilityDB.tar: Cannot write: No space left on devi ce /usr/local/bin/tar: ha_dummy_ocf/infoset: Cannot write: No space left on device /usr/local/bin/tar: ha_dummy_ocf/dsm_rear: Cannot write: No space left on device /usr/local/bin/tar: ha_dummy_ocf/dsm_first: Cannot write: No space left on devic e /usr/local/bin/tar: ha_dummy_ocf/PromoteBegin: Cannot write: No space left on de vice /usr/local/bin/tar: synohamessaged-update: Cannot write: No space left on device /usr/local/bin/tar: checksum.syno: Cannot write: No space left on device /usr/local/bin/tar: Synology.sig: Cannot write: No space left on device /usr/local/bin/tar: Exiting with failure status due to previous errors *** Process will exit *** Then I ran df Filesystem Size Used Avail Use% Mounted on rootfs 439M 439M 0 100% / tmpfs 244M 0 244M 0% /dev/shm /dev/sdb3 899M 50M 849M 6% /mnt/sdb3 /dev/loop0 24K 24K 0 100% /tmp/tcloop/attr /dev/loop1 40K 40K 0 100% /tmp/tcloop/acl /dev/loop2 252K 252K 0 100% /tmp/tcloop/ncursesw /dev/loop3 144K 144K 0 100% /tmp/tcloop/readline /dev/loop4 484K 484K 0 100% /tmp/tcloop/bash /dev/loop5 5.3M 5.3M 0 100% /tmp/tcloop/binutils /dev/loop6 32K 32K 0 100% /tmp/tcloop/bzip2-dev /dev/loop7 1.8M 1.8M 0 100% /tmp/tcloop/openssl-1.1.1 /dev/loop8 148K 148K 0 100% /tmp/tcloop/ca-certificates /dev/loop9 24K 24K 0 100% /tmp/tcloop/libcap /dev/loop10 244K 244K 0 100% /tmp/tcloop/gmp /dev/loop11 2.3M 2.3M 0 100% /tmp/tcloop/coreutils /dev/loop12 88K 88K 0 100% /tmp/tcloop/cpio /dev/loop13 284K 284K 0 100% /tmp/tcloop/curl /dev/loop14 72K 72K 0 100% /tmp/tcloop/expat2 /dev/loop15 200K 200K 0 100% /tmp/tcloop/findutils /dev/loop16 3.9M 3.9M 0 100% /tmp/tcloop/git /dev/loop17 92K 92K 0 100% /tmp/tcloop/grep /dev/loop18 48K 48K 0 100% /tmp/tcloop/gzip /dev/loop19 816K 816K 0 100% /tmp/tcloop/isl /dev/loop20 216K 216K 0 100% /tmp/tcloop/jq /dev/loop21 68K 68K 0 100% /tmp/tcloop/jsoncpp /dev/loop22 52K 52K 0 100% /tmp/tcloop/liblz4 /dev/loop23 308K 308K 0 100% /tmp/tcloop/libzstd /dev/loop24 76K 76K 0 100% /tmp/tcloop/liblzma /dev/loop25 600K 600K 0 100% /tmp/tcloop/libxml2 /dev/loop26 56K 56K 0 100% /tmp/tcloop/lzo /dev/loop27 272K 272K 0 100% /tmp/tcloop/nettle3 /dev/loop28 384K 384K 0 100% /tmp/tcloop/libarchive /dev/loop29 24K 24K 0 100% /tmp/tcloop/libpci /dev/loop30 84K 84K 0 100% /tmp/tcloop/librhash /dev/loop31 128K 128K 0 100% /tmp/tcloop/udev-lib /dev/loop32 48K 48K 0 100% /tmp/tcloop/libusb /dev/loop33 68K 68K 0 100% /tmp/tcloop/libuv /dev/loop34 44K 44K 0 100% /tmp/tcloop/lsscsi /dev/loop35 60K 60K 0 100% /tmp/tcloop/m4 /dev/loop36 104K 104K 0 100% /tmp/tcloop/make /dev/loop37 492K 492K 0 100% /tmp/tcloop/raid-dm-5.10.3-tinycore64 /dev/loop38 352K 352K 0 100% /tmp/tcloop/mdadm /dev/loop39 4.0K 4.0K 0 100% /tmp/tcloop/mirrors /dev/loop40 232K 232K 0 100% /tmp/tcloop/mpfr /dev/loop41 48K 48K 0 100% /tmp/tcloop/mpc /dev/loop42 88K 88K 0 100% /tmp/tcloop/ncursesw-utils /dev/loop43 740K 740K 0 100% /tmp/tcloop/ncursesw-terminfo /dev/loop44 1.4M 1.4M 0 100% /tmp/tcloop/openssh /dev/loop45 76K 76K 0 100% /tmp/tcloop/patch /dev/loop46 276K 276K 0 100% /tmp/tcloop/pciutils /dev/loop47 80K 80K 0 100% /tmp/tcloop/sed /dev/loop48 220K 220K 0 100% /tmp/tcloop/tar /dev/loop49 288K 288K 0 100% /tmp/tcloop/usb-utils /dev/loop50 2.1M 2.1M 0 100% /tmp/tcloop/util-linux /dev/loop51 52K 52K 0 100% /tmp/tcloop/xz tc@box:~$ apollolake-7.0.1-42218[!] Failed to unpack tar -sh: apollolake-7.0.1-42218[!]: not found Just a test, any ideas? This is in a Proxmox VM Link to comment Share on other sites More sharing options...
RedwinX Posted April 1, 2022 Share #3909 Posted April 1, 2022 Hi, for those wants 918/920 7.1 : https://github.com/RedwinX/redpill-load Just execute the script into buildpat folder first 2 1 Link to comment Share on other sites More sharing options...
pocopico Posted April 1, 2022 Share #3910 Posted April 1, 2022 On 4/1/2022 at 1:30 AM, RacerX said: Today I tested twice on G7 Ds918+ apollolake-7.0.1-42218 The script runs but after the pat is downloaded it says [!] Failed to unpack tar /usr/local/bin/tar: bios.ROM: Wrote only 5120 of 10240 bytes /usr/local/bin/tar: platform.ini: Cannot write: No space left on device /usr/local/bin/tar: hda1.tgz: Cannot write: No space left on device /usr/local/bin/tar: indexdb.txz: Cannot write: No space left on device /usr/local/bin/tar: synohdpack_img.txz: Cannot write: No space left on device /usr/local/bin/tar: packages/dsm6-ui-compatible-1.0.0-0090.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/USBCopy-x86_64-2.2.0-1076.spk: Cannot write: No spa ce left on device /usr/local/bin/tar: packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk: Cann ot write: No space left on device /usr/local/bin/tar: packages/SecureSignIn-x86_64-1.0.3-0138.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/ScsiTarget-x86_64-1.0.2-0207.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/SMBService-x86_64-4.10.18-0316.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/Python2-x86_64-2.7.18-1004.spk: Cannot write: No sp ace left on device /usr/local/bin/tar: packages/OAuthService-x86_64-1.1.2-0071.spk: Cannot write: N o space left on device /usr/local/bin/tar: packages/HybridShare-apollolake-1.2.0-0650.spk: Cannot write : No space left on device /usr/local/bin/tar: packages/HighAvailability-x86_64-2.1.1-1279.spk: Cannot writ e: No space left on device /usr/local/bin/tar: packages/FileStation-x86_64-1.3.1-1382.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/DhcpServer-x86_64-1.0.0-0034.spk: Cannot write: No space left on device /usr/local/bin/tar: packages/ActiveInsight-x86_64-1.1.0-1121.spk: Cannot write: No space left on device /usr/local/bin/tar: texts/chs/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/cht/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/csy/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/dan/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/enu/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/fre/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ger/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/hun/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ita/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/jpn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/krn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/nld/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/nor/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/plk/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ptb/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/ptg/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/rus/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/spn/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/sve/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/tha/strings: Cannot write: No space left on device /usr/local/bin/tar: texts/trk/strings: Cannot write: No space left on device /usr/local/bin/tar: expired_models: Cannot write: No space left on device /usr/local/bin/tar: DiskCompatibilityDB.tar: Cannot write: No space left on devi ce /usr/local/bin/tar: ha_dummy_ocf/infoset: Cannot write: No space left on device /usr/local/bin/tar: ha_dummy_ocf/dsm_rear: Cannot write: No space left on device /usr/local/bin/tar: ha_dummy_ocf/dsm_first: Cannot write: No space left on devic e /usr/local/bin/tar: ha_dummy_ocf/PromoteBegin: Cannot write: No space left on de vice /usr/local/bin/tar: synohamessaged-update: Cannot write: No space left on device /usr/local/bin/tar: checksum.syno: Cannot write: No space left on device /usr/local/bin/tar: Synology.sig: Cannot write: No space left on device /usr/local/bin/tar: Exiting with failure status due to previous errors *** Process will exit *** Then I ran df Filesystem Size Used Avail Use% Mounted on rootfs 439M 439M 0 100% / tmpfs 244M 0 244M 0% /dev/shm /dev/sdb3 899M 50M 849M 6% /mnt/sdb3 /dev/loop0 24K 24K 0 100% /tmp/tcloop/attr /dev/loop1 40K 40K 0 100% /tmp/tcloop/acl /dev/loop2 252K 252K 0 100% /tmp/tcloop/ncursesw /dev/loop3 144K 144K 0 100% /tmp/tcloop/readline /dev/loop4 484K 484K 0 100% /tmp/tcloop/bash /dev/loop5 5.3M 5.3M 0 100% /tmp/tcloop/binutils /dev/loop6 32K 32K 0 100% /tmp/tcloop/bzip2-dev /dev/loop7 1.8M 1.8M 0 100% /tmp/tcloop/openssl-1.1.1 /dev/loop8 148K 148K 0 100% /tmp/tcloop/ca-certificates /dev/loop9 24K 24K 0 100% /tmp/tcloop/libcap /dev/loop10 244K 244K 0 100% /tmp/tcloop/gmp /dev/loop11 2.3M 2.3M 0 100% /tmp/tcloop/coreutils /dev/loop12 88K 88K 0 100% /tmp/tcloop/cpio /dev/loop13 284K 284K 0 100% /tmp/tcloop/curl /dev/loop14 72K 72K 0 100% /tmp/tcloop/expat2 /dev/loop15 200K 200K 0 100% /tmp/tcloop/findutils /dev/loop16 3.9M 3.9M 0 100% /tmp/tcloop/git /dev/loop17 92K 92K 0 100% /tmp/tcloop/grep /dev/loop18 48K 48K 0 100% /tmp/tcloop/gzip /dev/loop19 816K 816K 0 100% /tmp/tcloop/isl /dev/loop20 216K 216K 0 100% /tmp/tcloop/jq /dev/loop21 68K 68K 0 100% /tmp/tcloop/jsoncpp /dev/loop22 52K 52K 0 100% /tmp/tcloop/liblz4 /dev/loop23 308K 308K 0 100% /tmp/tcloop/libzstd /dev/loop24 76K 76K 0 100% /tmp/tcloop/liblzma /dev/loop25 600K 600K 0 100% /tmp/tcloop/libxml2 /dev/loop26 56K 56K 0 100% /tmp/tcloop/lzo /dev/loop27 272K 272K 0 100% /tmp/tcloop/nettle3 /dev/loop28 384K 384K 0 100% /tmp/tcloop/libarchive /dev/loop29 24K 24K 0 100% /tmp/tcloop/libpci /dev/loop30 84K 84K 0 100% /tmp/tcloop/librhash /dev/loop31 128K 128K 0 100% /tmp/tcloop/udev-lib /dev/loop32 48K 48K 0 100% /tmp/tcloop/libusb /dev/loop33 68K 68K 0 100% /tmp/tcloop/libuv /dev/loop34 44K 44K 0 100% /tmp/tcloop/lsscsi /dev/loop35 60K 60K 0 100% /tmp/tcloop/m4 /dev/loop36 104K 104K 0 100% /tmp/tcloop/make /dev/loop37 492K 492K 0 100% /tmp/tcloop/raid-dm-5.10.3-tinycore64 /dev/loop38 352K 352K 0 100% /tmp/tcloop/mdadm /dev/loop39 4.0K 4.0K 0 100% /tmp/tcloop/mirrors /dev/loop40 232K 232K 0 100% /tmp/tcloop/mpfr /dev/loop41 48K 48K 0 100% /tmp/tcloop/mpc /dev/loop42 88K 88K 0 100% /tmp/tcloop/ncursesw-utils /dev/loop43 740K 740K 0 100% /tmp/tcloop/ncursesw-terminfo /dev/loop44 1.4M 1.4M 0 100% /tmp/tcloop/openssh /dev/loop45 76K 76K 0 100% /tmp/tcloop/patch /dev/loop46 276K 276K 0 100% /tmp/tcloop/pciutils /dev/loop47 80K 80K 0 100% /tmp/tcloop/sed /dev/loop48 220K 220K 0 100% /tmp/tcloop/tar /dev/loop49 288K 288K 0 100% /tmp/tcloop/usb-utils /dev/loop50 2.1M 2.1M 0 100% /tmp/tcloop/util-linux /dev/loop51 52K 52K 0 100% /tmp/tcloop/xz tc@box:~$ apollolake-7.0.1-42218[!] Failed to unpack tar -sh: apollolake-7.0.1-42218[!]: not found Just a test, any ideas? This is in a Proxmox VM Are you using tiny core ? The root disk size is 80% of the memory size. You need to increase your VM memory size Link to comment Share on other sites More sharing options...
RacerX Posted April 2, 2022 Share #3911 Posted April 2, 2022 one of my posts is missing! Basically I setup the vm with on 512mb, I changed the memory size to 8gb an it no longer runs out of space. I'm going try bare metal on the z370 now that mellanox is working on g7...... Link to comment Share on other sites More sharing options...
phone guy Posted April 2, 2022 Share #3912 Posted April 2, 2022 11 hours ago, RedwinX said: Hi, for those wants 918/920 7.1 : https://github.com/RedwinX/redpill-load Just execute the script into buildpat folder first I'm still a little unclear... I downloaded the json and zimage bsp file, where and how do I execute? I'd love to test 7.1 on my baremetal nas box. THANKS! Link to comment Share on other sites More sharing options...
scoobdriver Posted April 2, 2022 Share #3913 Posted April 2, 2022 15 hours ago, RedwinX said: Hi, for those wants 918/920 7.1 : https://github.com/RedwinX/redpill-load Just execute the script into buildpat folder first 3 hours ago, phone guy said: I'm still a little unclear... I downloaded the json and zimage bsp file, where and how do I execute? I'd love to test 7.1 on my baremetal nas box. THANKS! Many thanks @RedwinX , can i use this with @pocopico rploader post update script ? , is there any guide to where I would need to add your repo ? Assuming I add this repo in custom_config.json somewhere, but not sure of syntax ? Link to comment Share on other sites More sharing options...
RedwinX Posted April 2, 2022 Share #3914 Posted April 2, 2022 (edited) 43 minutes ago, scoobdriver said: Many thanks @RedwinX , can i use this with @pocopico rploader post update script ? , is there any guide to where I would need to add your repo ? Assuming I add this repo in custom_config.json somewhere, but not sure of syntax ? I send everything to @pocopico, he just need to update his script . I'm not un expert in dev, I know the shell, but my implementation and indentation is really bad. IN short: I have to put my cleaner code back lol Edited April 2, 2022 by RedwinX 2 Link to comment Share on other sites More sharing options...
RedwinX Posted April 2, 2022 Share #3915 Posted April 2, 2022 The goal for me to be in 7.1 is for this : Works fine actually Link to comment Share on other sites More sharing options...
dolbycat Posted April 3, 2022 Share #3916 Posted April 3, 2022 On 4/2/2022 at 12:36 AM, RedwinX said: Hi, for those wants 918/920 7.1 : https://github.com/RedwinX/redpill-load Just execute the script into buildpat folder first Hi~ The ds918+ worked very well. However, the ds920+ gave an error of mismatching. What's wrong with this? Link to comment Share on other sites More sharing options...
Peter Suh Posted April 3, 2022 Share #3917 Posted April 3, 2022 On 4/3/2022 at 5:59 PM, dolbycat said: Hi~ The ds918+ worked very well. However, the ds920+ gave an error of mismatching. What's wrong with this? @dolbycat Replace the config.json's sha256 checksum value below with the computed checksum shown in the log. I got that error on 918+, so I fixed the checksum on config.json on 918+, and it went on without errors. root@box:/home/redpill-load/config/DS920+/7.1-42621# cat config.json { "os": { "id": "ds920p_42621", "pat_url": "https://global.download.synology.com/download/DSM/release/7.1/42621/DSM_DS918%2B_42621.pat", "sha256": "e7fa975757d5faa6a275b68b130e7fd552263157a39bc71507ea6f2f466bb359" }, Link to comment Share on other sites More sharing options...
dolbycat Posted April 3, 2022 Share #3918 Posted April 3, 2022 20 minutes ago, Peter Suh said: @dolbycat 아래의 config.json의 sha256 체크섬 값을 로그에 표시된 계산된 체크섬으로 바꿉니다. 918+에서 해당 오류가 발생하여 918+에서 config.json의 체크섬을 수정했고 오류 없이 진행되었습니다. root@box:/home/redpill-load/config/DS920+/7.1-42621# cat config.json { "os": { "id": "ds920p_42621", "pat_url": "https://global.download. synology.com/download/DSM/release/7.1/42621/DSM_DS918%2B_42621.pat", "sha256": "e7fa975757d5faa6a275b68b130e7fd552263157a39bc71507 " WOW~ Thank you Link to comment Share on other sites More sharing options...
Peter Suh Posted April 3, 2022 Share #3919 Posted April 3, 2022 34 minutes ago, dolbycat said: WOW~ Thank you Pocopico also supports 918+ and 920+ builds on the same redpill-load. Did you know that? https://github.com/pocopico/redpill-load Link to comment Share on other sites More sharing options...
apriliars3 Posted April 3, 2022 Share #3920 Posted April 3, 2022 Pocopico also supports 918+ and 920+ builds on the same redpill-load. Did you know that? https://github.com/pocopico/redpill-loadSupport DSM 7.1-42621 Redpill-load? Link to comment Share on other sites More sharing options...
Peter Suh Posted April 3, 2022 Share #3921 Posted April 3, 2022 3 minutes ago, apriliars3 said: Support DSM 7.1-42621 Redpill-load? @pocopico said said as follows. I am also working on a build test at XUTUNTU for a long time. Link to comment Share on other sites More sharing options...
Peter Suh Posted April 3, 2022 Share #3922 Posted April 3, 2022 On 4/3/2022 at 8:03 PM, Peter Suh said: Pocopico also supports 918+ and 920+ builds on the same redpill-load. Did you know that? https://github.com/pocopico/redpill-load @dolbycat The tar command recognizes that the .pat file cannot be unpacked. How did you get past this problem? The tar version in my xubuntu is as follows and cannot be upgraded. tar --version tar (GNU tar) 1.30 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. ---------------------------------------------------------------------------------------- #] Unpacking /home/toolc/redpill-load/cache/ds918p_42621.pat file to /home/toolc/redpill-load/build/1648993060/pat-ds918p_42621-unpacked... [ERR] [!] Failed to unpack tar /bin/tar: This does not look like a tar archive /bin/tar: Skipping to next header /bin/tar: Exiting with failure status due to previous errors *** Process will exit *** Link to comment Share on other sites More sharing options...
dolbycat Posted April 3, 2022 Share #3923 Posted April 3, 2022 42 minutes ago, Peter Suh said: Pocopico also supports 918+ and 920+ builds on the same redpill-load. Did you know that? https://github.com/pocopico/redpill-load No!! That's amazing. Link to comment Share on other sites More sharing options...
javivanco Posted April 3, 2022 Share #3924 Posted April 3, 2022 Hi guys. After some test with a spare disk. I tried to migrate my NUC j3455 from 6.2.3 to 7.0.1 using RedPill and Tinycore Whenever I use a system disk (The NUC has just one bay) empty or with anything different from DSM installed everything is fine, but when I try to use my real production 1T SSD with jun's 6.2.3 to migrate, the RedPill bootloader gets stuck at some point and find.synology.com is not able to find anything. Anyone with this problem? Otherwise I'll have to backup the full disk and then do a clean install. Thanks a lot in advance Link to comment Share on other sites More sharing options...
phone guy Posted April 3, 2022 Share #3925 Posted April 3, 2022 I can tell you that sometimes find.synology.com doesn't aways work. I have 2 authentic DS and 1 RP box, and sometimes they all show up, sometimes none do. Figure out which ip that mac is using (go to dhcp list and search your mac) and trying just going to that ip. At least this has worked for me.... (but I wanted to say, find sometimes doesnt see real syno too sometimes) Link to comment Share on other sites More sharing options...
Recommended Posts