Jump to content
XPEnology Community
Message added by Polanskiman,

Please read the READ ME topic before posting:

 

Recommended Posts

- Outcome of the update: SUCCESSFUL

- DSM version prior update: Redpill Tinycore V0.4.6 DSM 7.0.1-42218 UPDATE 3 (DS3615XS)

- Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 Update 1 (DS3615XS)

- Using custom extra.lzma: NO

- Installation type: Baremetal on HP Proliant Microserver Gen8

- Additional comments: Use official Synology .pat file manually to finish migration. Need use the script from user Peter Suh

 

Link to comment
Share on other sites

Posted (edited)

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DS918+

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DS3622xs+

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DVA3221

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DS3617xs

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DS920+

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

- Additional comments: manual editing of ds920p.dts and re-insertion into loader build required.

TCRP cannot currently determine correct device tree values for ESXi virtual SATA controller ports due to how they are represented in the tinycore OS.  This combination (ESXi and DS920+) is not ready for general use yet.

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.4.6 DS1621+

- Using custom extra.lzma: NO

- Installation type: ESXi 7.0c VM on Intel Skylake Xeon

- Additional comments: manual editing of ds1621p.dts and re-insertion into loader build required. 

TCRP cannot currently determine correct device tree values for ESXi virtual SATA controller ports due to how they are represented in the tinycore OS.  This combination (ESXi and DS1621+) is not ready for general use yet.

Edited by flyride
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426 (JUN's loader 1.03b

- Loader version and model: RedPill 0.4.6 DS3622xs v7.1.0-42218

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP MediaSmart Server EX485 with updated process E8200

- Additional comments: I ran in to one problem. After install I can't access the server as long as there is a hard drive in the bottom slot. With only the 3 drives it works fine.

 

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: jun’s loader 1.03a2 DS918+ DSM 6.2-23739 Update 2

- Loader version and model: RedPill 0.4.6 DS920+ DSM 7.1-42661 Update 1

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Asrock j5005

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 Update 1 (DS918+)

- Using custom extra.lzma: NO

- Installation type: HP ProDesk 600 G1 SFF

- Additional comments: Only one HDD must be connected for install and use "SataPortMap": "1", after install you can connect other drives and change to "SataPortMap": "4"

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426(Jun's Loader v1.03b DS3617XS)

- Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 (DS3622xs+)

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - MB:Asrock E3C236D4U, LSI 9207 IT mode

- Additional comments: All hdd can identify, smart info can read. Internal network adapters also work. MB can't boot with uefi. I can't migrate from 6.23, fresh install DSM 7.1.

 

 

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: RedPill  TinyCore DS3615xs DSM 7.0.1-42218

- Loader version and model: RedPill  TinyCore bromolow-7.1.0-42661

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Gigabyte-BACE-3160 - Celeron j3160 NIC: Realtek RTL8111H

Link to comment
Share on other sites

  - Outcome of the update:  SUCCESSFUL  

- DSM version prior update: RedPill DS918+ v7.0.1-42218

- Loader version and model: RedPill DS918+ v7.1-42661

- Using custom extra.lzma: NO  

- Installation type: BAREMETAL - GigaByte Z370M DS3H - i3-8100 - HP NC360T NIC

- Additional comments: no problem sata port Map, with 9 disks, but AME pakage doesn't work anymore on dsm 7.1

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: NONE - fresh install

- Loader version and model: redpill.v0.4.6.img DS3622xs+ DSM 7.1.0-42661u1

- Using custom extra.lzma: NO (added ext drivers manually)

- Installation type: VM Proxmox v7.2: cpu: E3-1270v2 mobo: SuperMicro X9-SCM-F

- Additional comments: Successful as Q35 and i440fx system. PCIe/PCI Pass Thru LSI HBA controller (Dell H710 flashed IT MODE ver P20) using ext MPT3SAS. Paravirtual nic using ext V9FS. ACPI working using ext https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: Redpill Tinycore V0.4.6 DSM 7.0.1-42218 UPDATE 3 (DS918)

- Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 Update 1 (DS920)

- Using custom extra.lzma: NO

- Installation type: Baremetal on msi-h510m-a pro migrated from ds918+ to ds920+

- Additional comments: Added i915 patched modules to enable gpu transcoding on i3-10105 and libsynonvme.so.1 patch i made on ds918 7.01 seems to be already in place after migration to 7.1.u1 ds920

  • Like 1
Link to comment
Share on other sites

  • Outcome of the update: SUCCESSFUL
  • DSM version prior update: DSM 6.2.3-25426 Update 3 using JUN'S LOADER v1.04b - DS918+
  • Loader version and model: RedPill 0.4.6 (DS3622xs+ broadwellnk-7.1.0-42661)
  • Using custom extra.lzmaNO
  • Installation typeBAREMETAL - MSI H110M-VH PLUS | NIC: Realtek RTL8111H Gigabit LAN controller | Intel G4400
  • Additional comments: The upgrade path DSM 6.2.3 -> 7.0.1-42218  ->7.1.0-42661

The upgrade process was done in 2 phase, both using Redpill TinyCore 0.4.6.
Initally I tried multiple times with apollolake varient, as my earlier model was DS918+. After much failures, I tried broadwellnk for DS3622xs+ and it worked smoothly.

Here are my commands

sudo su
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh backup now
./rploader.sh build broadwellnk-7.0.1-42218

I didn't use the generated serial and MAC address, instead I updated user_config.json with original serial and my NIC MAC address.
(With original and actual serial number; I could use video transcoding on my NAS.)

 

Using this loader I upgraded from DSM 6.2.3 to DSM 7.0.1, and migrated my NAS from web UI using the PAT file created by the loader.

Next I booted into TC and executed these commands

sudo su
./rploader.sh build broadwellnk-7.1.0-42661

With this, I upgrade my NAS from DSM-7.0.1 to DSM 7.1.0. Here I did the migrated using the PAT file downloaded from synology website.

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DS3615xs+ 6.2.3-25426 U3 (Jun 1.03b loader)

- Loader version and model: TCRP 0.4.6 DS3615xs

- Using custom extra.lzma: NO

- Installation type: Baremetal HP N54L. Stock BIOS. Integrated nic

- Additional comments: Using "disable_mtrr_trim": null in user_config.json 

 

Link to comment
Share on other sites

Posted (edited)

- Outcome of the update: UNSUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.8.0.0 DS918+

- Using custom extra.lzma: NO

- Installation type: ESXi 6.7.0 Update 3 (Build 16713306) VM on Xeon(R) CPU E5-2650 v3

- Additional comments: Recovery loop

 

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.8.0.0 DS3622xs+

- Using custom extra.lzma: NO

- Installation type: ESXi 6.7.0 Update 3 (Build 16713306) VM on Xeon(R) CPU E5-2650 v3

- Additional comments: Control panel -> Update & Restore -> DSM Update -> "Status" shows "Connection failed. Please check your Internet connection." and "Release notes" link points to example.com webpage (it's a little strange)

Edited by piter
Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426-2

- Loader version and model: RedPill  TinyCore V.04.6 DS3615xs DSM-7.1.0-42661

- Using custom extra.lzma: NO

- Installation type: Bare-metal on ASRock Z390M Pro4 - i5-9500 - 32 GB Corsair Vengeance LPX - S. 860 EVO 250GB - RAID Mirror Seagate IronWolf 3TB 

- Additional comments: Use official Synology .pat file from https://archive.synology.com/download/Os/DSM

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: Redpill Tinycore  DSM 7.0.1-42218 UPDATE 2 (DS918+)

- Loader version and model: Redpill Tinycore latest version at the time of writing  DSM 7.1-42661 Update 1 (DS918+)

- Using custom extra.lzma: NO

- Installation type: Baremetal on Fujitsu Celsius W530

- Additional comments: Use official Synology .pat file manually to finish migration. Update 2 fails - recovery loop, even though there is a workaround provided in the link below, it did not work for me. 

 

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 7.1-42661
- Loader version and model: Tinycore-Redpill v0.8 - DS3622xs+
- Using custom extra.lzma: NO
- Installation type: VMware ESXi 7.0 update 3
- Additional comments: After update, booted into TCRP and:

 

./rploader.sh update
sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661

 

The sudo was important as without I got an error:

 

...
Creating temp ramdisk space
Mounting partition sdb1}
Mounting partition sdb2}
Extracting update ramdisk
unlzma: /mnt/sdb2/rd.gz: Compressed data is corrupt
cpio: dev/net/tun: Cannot mknod: Operation not permitted
cpio: dev/console: Cannot mknod: Operation not permitted
52176 blocks
Found Version : 7.1-42661-2
Do you want to use this for the loader ? [yY/nN] : y
Extracting redpill ramdisk
cpio: dev/console: Cannot mknod: Operation not permitted
cpio: dev/net/tun: Cannot mknod: Operation not permitted
cpio: lib not created: newer or same age version exists
...
cpio: ./etc/shadow: Cannot open: Permission denied
...


Just run the command again with sudo and DSM boots correctly after Update 2.

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.1.7-15284

- Loader version and model: Tinycore-Redpill v0.8 - DS3615xs

- Using custom extra.lzma: NO

- Installation type: Baremetal Asrock Q1900-ITX

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL (mostly)

- DSM version prior update: DS3617xs 6.2.3-25426 U3 (Jun 1.03b loader)

- Loader version and model: TCRP 0.8 DS3622xs+

- Using custom extra.lzma: NO

- Installation type: VM ESXi 7

- Additional comments: driver conflict encountered with Mellanox ConnectX-3 10Gbe NIC

 

This particular system is very complex - RDM NVMe boot drives, RAIDF1, passthrough SATA and 10Gbe network and multiple storage pools. It is not unusual to encounter problems with this system even after extensive testing and other successful upgrades. The Mellanox card created a driver conflict, resulting in an incomplete upgrade. The system would boot to junior mode and instantly ACPI shutdown as soon as any http connection was made to the system.

 

Finally a reinstall was forced (synodsdefault --reinstall), which allowed me to see that TCRP was injecting the mlx4/mlx5 modules on top of the native Mellanox support in the DS36xx platforms.  After rebuilding the loader WITHOUT the Mellanox extension, the system operated normally and 10Gbe network was functional with the DSM native Mellanox drivers. The Storage Pools and package/Docker configurations survived the event completely intact, so no significant harm was done.

  • Like 3
Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: v6.2.3.3_25426 - DS3617xs

- Loader version and model: TinyCore 0.8.0 - DS3622xs+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP GEN8 - Xeon E3_1265L - Intel Nic X520-DA1

- Additional comments: Had to install TinyCore with the drives on, and use the "manual" 7.0.1 then cleanup then 7.1 install. Flawless migration besides Plex.

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: v6.2.3.3_25426 - DS918+

- Loader version and model: TinyCore 0.8.0 - DS3622xs+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HPE MicroServer Gen10 Plus - Xeon E-2224 - Embedded Intel i350 AM41Gb 4-port

- Additional comments: Had to install TinyCore with the drives in, only got 1 without and had to rebuild the loader.

 

Updated the MicroServer to the latest firmware stack (2.58 UEFI/BIOS, 2.70 iLO5, Latest SPP with latest updates added)

 

Downloaded TC 0.8.0

Created an Image of Jun's loader from the USB drive in case I needed to revert

Imaged the USB drive with Rufus 3.18

 

Used the following commands I found from Fireball:7.0.1
create directory "/mnt/sdb3/auxfiles" (if not created, upgrade to 7.1.0 will fail)

 

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build broadwellnk-7.0.1-42218

7.1.0

./rploader.sh clean now
./rploader.sh build broadwellnk-7.1.0-42661
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;
sudo poweroff

Once booted I couldn't get the compiled *.pat file I downloaded from TC to work. Errored at 40% with a corrupt file.

 

I downloaded the Nano-Packed Update 1 pat file for the DS3622xs+ from Synology and the install completed successfully. The system is online and all the packages came back in including Plex (after a re-install). My Storage was failed because it only detected the single drive when I ran the commands. I rebooted into TC and ran:

./rploader.sh satamap
./rploader.sh build broadwellnk-7.1.0-42661
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;
sudo poweroff

The system is successfully updated and all the data is back. DSM had to repair the system partitions on the other 3 drives after boot since they weren't upgraded with the first one.

Link to comment
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update:  DSM 6.2.3-25426 Update 2 ((Jun 1.03b loader)

- Loader version and model: TinyCore 0.8.0 - DS3622xs+

- Using custom extra.lzma: No

- Installation type: Proxmox 7.2-3 VM (i440fx and SeaBIOS) - Supermicro X10SL7-F - E3-1246 v3 - Storage Disks using LSI 2308 PCI Device Pass-through

- Additional comments: Use dodo-dk rpext for ACPI to work properly inside VM.  Restart and Shutdown VM from Proxmox GUI works fine.

./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json
Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: v6.2.3.3_25426 - DS918+

- Loader version and model: TinyCore 0.8.0 - DS3622xs+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - old terminal Fujitsu Futro S720 with AMD GX-217GA + 4GB RAM + ASM1061 PCIe to SATA 3.0 adapter.

- Additional comments: Migration in two steps - first to 7.0.1 and to 7.1 then.

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: new install

- Loader version and model: TCRP 0.8.0.0 DS3622xs+

- Using custom extra.lzma: NO

- Installation type: Core i5-2400, 8GB RAM, Motherboard: Asus – P8H61-M

Link to comment
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update:  DSM 6.2.3-25426 Update 3 w/ Jun's Loader v1.03b DS3615XS

- Loader version and model: TinyCore RedPill 0.8.0.0 DS3615XS

- Using custom extra.lzma: NO

- Installation type: BAREMETAL HPE Microserver Gen10, using integrated NIC

 

Upgrade cliff notes:

 

-1. Backed up all important data

0. Disconnected all the drives (probably not needed)

1. Downloaded the latest tinycore-redpill.vx.x.x.img.gz from https://github.com/pocopico/tinycore-redpill

2. extracted the .img file, burned it to USB via BalenaEtcher

3. boot the server from new USB pen drive

4. SSH to TinyCore

5. ./rploader.sh update now
6. ./rploader.sh fullupgrade now
7. ./rploader.sh serialgen DS3615xs
7. a. I added the serial from the original DSM-6.2.3 and both MAC addresses to user_config.json manually
8. ./rploader.sh identifyusb now
9. ./rploader.sh satamap now
10. ./rploader.sh ext bromolow-7.0.1-42218 auto
11. ./rploader.sh build bromolow-7.0.1-42218
12. ./rploader.sh clean now
13. ./rploader.sh build bromolow-7.1.0-42661
14. ./rploader.sh clean now
15. rm -rf /mnt/sdb3/auxfiles
16. rm -rf /home/tc/custom-module
17. ./rploader.sh backup now

18. shutdown

19. reconnect the drives and power up

20. restore 7.1-42661 (with Update 1) with a .pat file downloaded from https://www.synology.com/en-us/support/download

22. wait for DSM migration and package upgrade to finish

23. manually upgrade to 7.1-42661 Update 2 via the control panel

24. reboot into TinyCore

25. ./rploader.sh update

26. ./rploader.sh postupdate bromolow-7.1.0-42661

27. sudo reboot

 

All Synology packages get upgraded OK and seem to be working, including Docker and ActiveBackup (it also remains activated!). Some old packages need to be removed, as they're incompatible with DSM7, some packages need to be repaired. The power button package is not needed anymore.

 

Stuff I needed to recreate/reapply:

  • /usr/syno/synosdk/texts/enu/events gets reset. If you use it to write custom messages to syslog you need to re-add your custom templates.
  • re-run the script to free ports 80/443 and reboot.
  • re-apply changes for having static IPs in OpenVPN for users (https://www.wundertech.net/setup-a-static-ip-address-for-openvpn-clients-on-your-synology-nas/)
    • only /volume1/@appstore/VPNCenter/etc/openvpn/radiusplugin.cnf got reverted to default, all the other changes remained.
  • acme.sh (https://github.com/acmesh-official/acme.sh/wiki/Synology-NAS-Guide) seemed to be working, including forced certificate renewal and deployment via --deploy-hook synology_dsm, but running /usr/local/share/acme.sh/acme.sh --force --upgrade --nocron --home /usr/local/share/acme.sh probably doesn't hurt.
  • the Portainer container needed to be recreated but Docker volumes and networks created with it remained and are working.
  • Nginx Proxy Manager started working once ports 80 and 443 were freeed.
Link to comment
Share on other sites

- Outcome of the update: PARTLY SUCCESSFUL

- DSM version prior update: RedPill DS918+ DSM 7.0-41890

- Loader version and model: RedPill  TinyCore APOLLOLAKE-7.1.0-42661

- Using custom extra.lzma: NO

- Installation type: BAREMETAL

  • Original Hardware: ASUS H81M-K/i5-4570
  • New Hardware: ASUS PRIME B360M-A/i3-8100T

- Additional comments:

Update using Tinycore directly, when log in, it tells "SYSTEM IS GOING READY" sometimes and doesn't let me log in.

If no show, DSM interface and SSH's response very slow, needs to force reboot to get "5 min only" normally work.

I reset DSM settings and apps by reinstalling DSM with SSH:

/usr/syno/sbin/./synodsdefault --reinstall

After reinstall DSM, now works perfectly.

image.png.2de4d4e8e7000a181956e63190ba2ef5.png

By modifying /lib64/libsynonvme.so.1 , using HEX Editor to change NVME port, now m.2 works perfectly.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...