Jump to content
XPEnology Community

Gronaldo

Member
  • Posts

    90
  • Joined

  • Last visited

  • Days Won

    3

Gronaldo last won the day on April 11 2019

Gronaldo had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Gronaldo's Achievements

Regular Member

Regular Member (3/7)

4

Reputation

  1. Found updating to TCRP 10.0.0.10 resolved issue. Also removed additional USB-devices showing up in DS-file App.
  2. @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?
  3. 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?
  4. - 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
  5. This indicates a hardware issue, not related to the loader. Drives should allways spin up when machine starts/boots.
  6. @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.
  7. @pocopico is the TC password not saved, when changed?
  8. 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!
  9. @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.
  10. Seems to be a serious issue. Effects many platforms. @jensmanderthanks for the heads up.
  11. https://www.synology.com/en-global/beta/DSM70Beta Dec. 8
  12. 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 🤪
  13. 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?
  14. 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. 😣
×
×
  • Create New...