Gronaldo

Found updating to TCRP 10.0.0.10 resolved issue. Also removed additional USB-devices showing up in DS-file App.

@fbelavenuto Wanted to test arpl-1.1-beta2a.img and created successfully a DSM 3622XS+ build 42962. Update to build 69057 failed unfortunately, as there is no configuration for this version found? Could not recover from this, needed to start from scratch building new loader disk. Known issue, or any advice?

Running TCRP/friend on DS3622xs+ with DSM 7.2.1-69057, I cannot install anu updates. Using automatic update, or via manual uploading update file. Applying an update shows a 1% progress for checking the file, this takes around 2 minutes, then the upgrade stops showing the file is damaged. Any ideas or suggestions?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 Update 3 - DSM version AFTER update: DSM 7.2.1 69057 - Loader version and model: TCRP v0.9.4.9c with Friend - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Additional comments: All drives (WD-REDs) are now marked as non-verified and pools have a warning! Further update to 7.2.1-69057-1 not possible

This indicates a hardware issue, not related to the loader. Drives should allways spin up when machine starts/boots.

@pocopico Using the WEBUI and tinycore-redpill-uefi.v0.9.4.9.img I got a bare metal build operational. (Asus P9D-I serverboard / Xeon E3-1225v2) However, Info Center- General page was completely empty (no info) and the USB-bootdrive was visible and accessible in File Explorer (as 3 devices) Reverted back to tinycore-redpill-uefi.v0.9.4.8.img, used the manual SSH procedure (including updating loader) and all issues were resolved.

@pocopico is the TC password not saved, when changed?

Correct, USB boot. /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 Please explain how to deduct correct setting from this output. Thanks!

@pocopico thanks for this great tool! Being aan noob at Linux, I did need the additional details provided by @haydibe, but it works! Great gjob guys!! I almost gave up on Version 7, as compiling my own kernel / drivers was a brigde to far. Still need to figure on how to make second drive visable. Currently only have "SataPortMap": "4" on Asus H81T in user_config.

Seems to be a serious issue. Effects many platforms. @jensmanderthanks for the heads up.

https://www.synology.com/en-global/beta/DSM70Beta Dec. 8

Just upgraded existing DS3615 / 6.2.1 build to DS918+ / 6.2.2 / loader 1.04b build. All running okay, however MAC used on network is not actual hardware MAC address. In Grub this same hardware MAC address is entered correctly, I verified. What am i missing? Is this related to serial number? Edit: found my mistake, I used the semicolon when changing the MAC address in Grub 🤪

okay, understood! Thank for the support!

Thanks for your help again, Jens. I already tested setup as you described. Only for the second Xpenology unit I was trying to find a way to use the VPN connection of the first unit. This I was unable to do. Your solution is to have 2 individual VPN connections to the backup location. So LAN IP ranges would be x.x.1.x, VPN-1 x.x.2.x and VPN-2 x.x.3.x for instance, right?

Thanks for the feedback. I am not very familiar with the way QC works, I expected it to be a DDNS solution, but now understand it to be a gateway. Probably not going to use it, knowing this. I want to backup 2 Xpenology units to 1 off-site unit. VPN is via one of these Xpenology units. This I can get working, but having the second one use this VPN connection as well seems to be too complex for me. 😣

I purchased an older Synology DSxxx unit and intend to use Quickconnect for accessing it. I plan to use it for off-site backup of my Xpenology unit. So my Xpenology unit would query Quickconnect to find the real Synology unit Would there be any issues or advices against doing so?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-1 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock H370M-ITX/ac + Intel Gigabit CT + Intel G5400 - Additional comment: reboot required after manual upload (no notifications received of updates in DSM 1 or 2 )

Minor energy saving However, if system is fully installed, i would not bother to take it out, just for that.

Plex is likely to keep system awake. Other packages may also do this, like indexing services etc. PS. you can remove the wifi module of the mainboard, by removing 2 little screws on the back of the mainboard, fixing the module.

Same here, although I did not notice it at first. Added simple Intel Gigabit CT desktop card in the end.

Okay, understood. That is a pity! Thanks for explaining in detail.

You make it sound, like it never will? Why?

Well, in the meantime, I did. No success, up to v0.5 😓

My humble apologies. I just checked and although the bond seems okay (from migration of previous build) it only has a single LAN connection. Sorry to have been providing incorrect info. My perfect picture is now shattered 😫 Anyone tried with alternative extra.lzma?

You are correct, never noticed this (or expected...silly actually) Nevertheless they do work 😀