Jump to content
XPEnology Community

tdse13

Member
  • Posts

    117
  • Joined

  • Last visited

Everything posted by tdse13

  1. Ja. Mit der vorhanden Version ging es -trotz update- nicht. Ich habe dann den Stick neu mit einer anderen, neueren Version befüllt
  2. Bei mir habe ich den Grund für das extreme zähe Verhalten von einer Windows 10 VM gefunden, nachdem ich alles andere inkl. einer älteren Version von VMM vorher ausprobiert hatte. Es lag am TCRP Loader. Nachdem ich den Stick neu aufgesetzt hatte, ist das zähe Verhalten weg und Windows wieder halbwegs vernünftig nutzbar.
  3. In my case Toshiba, but any manufacture should work.
  4. I am actually using a Raid1 with 2 Toshiba 18 TB drives without problems for 2 months now (918+).
  5. Eine Frage: Wie kann ich eine ältere Version von vmm installieren? Windows 10 ist bei mir nicht mehr nutzbar. Früher war es einigermaßen nutzbar. Aber auch meine VM mit Home Assistant mit wenigen Prozessen läuft zähflüssiger seit einiger Zeit.
  6. Ich kann dieses Problem voll nachvollziehen. Mit DSM 6.xxx lief Windows 10 einigermaßen gut. Mit DSM 7.1.1-42962 Update 2 ist Windows nicht mehr nutzbar.
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1-42661 Update 3 - Loader version and model: TCRP 0.9 DS918+ - Using custom extra.lzma: NO - Installation type: Bare Metal, Asrock J4105-ITX 16 GB - Additional comments: Updated to new TCRP 0.9 stick prior to update - Outcome of the update: unsuccessful -->SUCCESSFUL - DSM version prior update: DSM 7.1-42661 Update 3 - Loader version and model: TCRP 0.9 DS918+ - Using custom extra.lzma: NO - Installation type: Bare Metal, Asrock J4105-ITX 8 GB - Additional comments: normal update with TCRP 0.9 did not work. With ARPL update to DS920+ and then back to DS918+ with TCRP. Lost some configuration on my backup system.
  8. Thank you very much. I added a second mac adress manually to the user_config.json even though my board (Asrock J4105-ITX) has only one LAN port. This did the trick. Now I can upgrade my other machine. Should I apply the upgrade to 7.1.1-42962 before I change the USB stick with TCRP 0.9?
  9. So, I finally downgraded from DS920+ to DS918+ using TCRP 0.9. However, I lost the Advanced Media Extension even though it was working with DSM 7.1-42661 Update 3 and TCRP 0.8 using an original sn and mac. Any idea how to fix this problem before I apply the upgrade to my main machine?
  10. As I said in one of my previous posts I upgraded to 7.1.1-42962 but with a different type of DSM (920+ instead of 918+). I guess the log does not help in my case. Or do you want me to try to install DSM 918+ with TCRP 0.9 again?
  11. After booting I installed DSM. But it failled after around 60 % with a message that the file is corrupt. I downloaded the file again with the same result. I do not have a serial console connected. Therefore, I cannot give an further information. There was no Sata port related message.
  12. I did this and it failed. I then built a new stick with the latest loader version 0.9 and it failed installing DSM 918+ 7.1.1-42962. Finally, I used the automated redpill loader 0.4 alpha 7 and I could upgrade to 7.1.1 but for the 920+ model which I did not want to do. Any idea how to get to DS918+ with 7.1.1-42962? I have another machine which I want to update. But I do not want to switch to 920+.
  13. Thank you for your quick reply. Unfortunately, it does not work either. Any other idea? I tried it 3 times with your commands. Thank you. tc@box:~$ ./rploader.sh postupdate apollolake-7.1.1-42962 Rploader Version : 0.9.1.5 Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master Extensions : redpill-misc Extensions URL : "https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json" TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.apollolake-7.0.dev.txz/download TOOLKIT_SHA : d349fa644392d4cfab8191243ee38aaa32bd517208c144678e0c855cb5a619ea SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/apollolake-source/linux-4.4.x.txz/download SYNOKERNEL_SHA : af815ee065775d2e569fd7176e25c8ba7ee17a03361557975c8e5a4b64230c5b COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : apollolake TARGET_VERSION : 7.1.1 TARGET_REVISION : 42962 REDPILL_LKM_MAKE_TARGET : test-v7 KERNEL_MAJOR : 4 MODULE_ALIAS_FILE : modules.alias.4.json SYNOMODEL : ds918p_42962 MODEL : DS918+ Local Cache Folder : /mnt/sdd3/auxfiles DATE Internet : 14092022 Local : 14092022 Checking Internet Access -> OK Cloning into 'redpill-lkm'... remote: Enumerating objects: 1317, done. remote: Counting objects: 100% (389/389), done. remote: Compressing objects: 100% (66/66), done. remote: Total 1317 (delta 334), reused 335 (delta 310), pack-reused 928 Receiving objects: 100% (1317/1317), 484.29 KiB | 4.32 MiB/s, done. Resolving deltas: 100% (897/897), done. Cloning into 'redpill-load'... remote: Enumerating objects: 2287, done. remote: Counting objects: 100% (221/221), done. remote: Compressing objects: 100% (120/120), done. remote: Total 2287 (delta 107), reused 203 (delta 94), pack-reused 2066 Receiving objects: 100% (2287/2287), 117.36 MiB | 20.63 MiB/s, done. Resolving deltas: 100% (1077/1077), done. Removing any old redpill.ko modules Looking for redpill for : ds918p_42962 Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill/releases/redpill-4.4.180plus.tgz Extracting module Checking user config for general block Result={ "model": "DS3622xs+", "version": "7.1.1-42951", "zimghash": "", "rdhash": "", "usb_line": "", "sata_line": "" }, File does not contain general block, adding block Creating temp ramdisk space Mounting partition sdd1 mount: /mnt/sdd1: /dev/sdd1 already mounted on /mnt/sdd1. Mounting partition sdd2 mount: /mnt/sdd2: /dev/sdd2 already mounted on /mnt/sdd2. Backing up /home/tc/user_config.json Extracting update ramdisk cpio: dev/net/tun: Cannot mknod: Operation not permitted cpio: dev/console: Cannot mknod: Operation not permitted unlzma: /mnt/sdd2/rd.gz: Compressed data is corrupt 38500 blocks Found Version : 7.1-42661-3 Do you want to use this for the loader ? [yY/nN] :
  14. I tried to upgrade to DSM 7.1.1-42962 from DSM 7.1-42661 Update 3 but in vain. First of all I upgraded TC 0.8 to TC 0.9. However it does not work. Any idea how to upgrade? Thank you. tc@box:~$ sudo ./rploader.sh postupdate apollolake-7.1.1-42962 bspatch does not exist, bringing over from repo % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 10232 100 10232 0 0 44681 0 --:--:-- --:--:-- --:--:-- 44681 Rploader Version : 0.9.1.4 Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master Extensions : redpill-misc Extensions URL : "https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json" TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.apollolake-7.0.dev.txz/download TOOLKIT_SHA : d349fa644392d4cfab8191243ee38aaa32bd517208c144678e0c855cb5a619ea SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/apollolake-source/linux-4.4.x.txz/download SYNOKERNEL_SHA : af815ee065775d2e569fd7176e25c8ba7ee17a03361557975c8e5a4b64230c5b COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : apollolake TARGET_VERSION : 7.1.1 TARGET_REVISION : 42962 REDPILL_LKM_MAKE_TARGET : test-v7 KERNEL_MAJOR : 4 MODULE_ALIAS_FILE : modules.alias.4.json SYNOMODEL : ds918p_42962 MODEL : DS918+ Local Cache Folder : /mnt/sdd3/auxfiles DATE Internet : 14092022 Local : 14092022 Checking Internet Access -> OK Redpill sources already downloaded, pulling latest remote: Enumerating objects: 60, done. remote: Counting objects: 100% (60/60), done. remote: Compressing objects: 100% (23/23), done. remote: Total 60 (delta 25), reused 45 (delta 25), pack-reused 0 Unpacking objects: 100% (60/60), 15.30 KiB | 746.00 KiB/s, done. From https://github.com/pocopico/redpill-lkm 169d8fb..a6b4ae9 master -> origin/master Updating 169d8fb..a6b4ae9 Fast-forward .github/workflows/main.yml | 125 ++++++++++++++++++++++++---------------------------------------------------------------------------- .github/workflows/sync.yml | 15 ------------ PLATFORMS | 7 ++++++ compile-lkms.sh | 21 +++++++++++++++++ config/cmdline_delegate.c | 40 +++++++++++++++++++++++++++----- config/cmdline_opts.h | 1 - config/platforms.h | 207 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------------------------------- config/runtime_config.c | 12 +++++----- 8 files changed, 209 insertions(+), 219 deletions(-) delete mode 100755 .github/workflows/sync.yml create mode 100644 PLATFORMS create mode 100755 compile-lkms.sh Loader sources already downloaded, pulling latest remote: Enumerating objects: 245, done. remote: Counting objects: 100% (234/234), done. remote: Compressing objects: 100% (120/120), done. remote: Total 245 (delta 120), reused 216 (delta 107), pack-reused 11 Receiving objects: 100% (245/245), 2.65 MiB | 22.57 MiB/s, done. Resolving deltas: 100% (121/121), completed with 9 local objects. From https://github.com/pocopico/redpill-load c6ac089..38a3bb8 develop -> origin/develop Updating c6ac089..38a3bb8 error: Your local changes to the following files would be overwritten by merge: config/DS918+/7.1.0-42661/config.json Please commit your changes or stash them before you merge. Aborting Removing any old redpill.ko modules Looking for redpill for : ds918p_42962 Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill/releases/redpill-4.4.180plus.tgz Extracting module Creating temp ramdisk space Mounting partition sdd1 Mounting partition sdd2 Extracting update ramdisk unlzma: /mnt/sdd2/rd.gz: Compressed data is corrupt 38500 blocks Found Version : 7.1-42661-3 Do you want to use this for the loader ? [yY/nN] : n Saving user session for future use. Saving current extensions -> OK ! Saving current user_config.json -> OK !
  15. I assume that my board was broken. I exchanged it for a brand new board and there were no more continuity errors. I spent a lot of time analyzing the errors but I could not find any other solution.
  16. 1. Backup Server Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.1-42661 (DS918+) Update1 Loader version and model: tinycore-redpill-uefi.v0.8.0.0.img, DSM 7.1-42661 (DS918+) Installation type: Baremetal ASRock J4105-ITX, 8 GB RAM, 3x SATA drives 1. Production Server Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.1-42661 (DS918+) Update1 Loader version and model: tinycore-redpill-uefi.v0.8.0.0.img, DSM 7.1-42661 (DS918+) Installation type: Baremetal ASRock J4105-ITX, 16 GB RAM, 3x SATA drives
  17. May-be this issue is related to Version: 7.1-42661 Update 3 Fixed Issues Fixed an unexpected issue that may occur when users Safe Ejected a single-volume storage pool that was created on DSM 6.2.4 or earlier. Fixed an issue where certain packages couldn't function properly shortly after restarting DSM. Fixed an unexpected issue that may occur when users tried to repair degraded storage pools that were previously migrated from a different version of DSM.
  18. 1. Backup Server - Outcome of the update: SUCCESSFUL - DSM version prior update: Jun's Loader v1.04b DS918+, DSM 6.2.3-25426 Update 3 (DS918+) - Loader version and model: tinycore-redpill-uefi.v0.8.0.0.img, DSM 7.1-42661 (DS918+) - Installation type: Baremetal ASRock J4105-ITX, 8 GB RAM, 3x SATA drives (coming from a N36L with DSM 6.x and DS3615) 1. Production Server - Outcome of the update: SUCCESSFUL with problems - DSM version prior update: Jun's Loader v1.04b DS918+, DSM 6.2.3-25426 Update 3 (DS918+) - Loader version and model: tinycore-redpill-uefi.v0.8.0.0.img, DSM 7.1-42661 (DS918+) - Installation type: Baremetal ASRock J4105-ITX, 16 GB RAM, 3x SATA drives Additional comments: After the successful upgrade of my backup server I started the same process on my production server. The installation of the pat file stopped at 68 % saying that the file is corrupt (same file as backup server). I saw a small error message when creating the stick about the disk size. Since 2 drives are 14 TB drives I guessed that this is the reason. However, I startet the process again without any strange message. I redid the stick again with the same message. Then I wanted to go back to the old version 6.3 without success. My final approach was to create the stick for DS3622XS which finally did the job. I then did it again with a stick for DS918+. However, most individual setup information and apps were lost. Files, Docker, VMs, etc. are still working.
  19. I was running during many years a N36L. I then switched to an ASRock J4105-ITX. You would have to add a PCI card for additional SATA ports. It is very energy efficient and silent.I was running during many years a N36L. I then switched to an ASRock J4105-ITX. You would have to add a PCI card for additional SATA ports. It is energy efficient and silent.
  20. Den Grund habe ich mittlerweile herausgefunden. Es handelt sich um ein Zertifikateproblem, welches bis DSM 6.2.3-25426 Update 3 besteht und mit den Folgeversionen behoben ist. Man muß das Datum auf ein Datum vor dem 1.11.21 zurücksetzen, dann klappt die Installation von https://packages.synocommunity.com/ auch. Ansonsten kommt die Fehlermeldung "ungültiger Speicherort". Ich belasse es bei volume3. Ein Neuaufsetzten vom DSM wäre wahrscheinlich einfacher gewesen. Bis auf Docker und ein VM (Home Assistant) konnte ich alles retten. Es hat aber viel Zeit gekostet.
  21. Mein Raid1 mit BTRFS ist kaputtgegangen. Ich habe dann nach flyride's Hinweis, daß ein BTRFS Volume nicht wiederherstellbar ist, wenn es einmal read-only ist, eine Platte aus dem Raid1 entfernt, die zweite Platte formatiert und als Volume3 neu installiert und alle Daten per Hyperbackup auf das Volume 3 kopiert. Die beiden Platten waren nagelneu, da ich sie schon beim Crash ausgetauscht hatte. Zuletzt habe ich noch die gemeinsamen Ordner eingerichtet und die Docker Container versucht neu aufzusetzen. Und mit der zweiten Platte das Raid1 wiederhergestellt. Dabei scheint es Rechteprobleme zu geben. Zumindest bei Dcoker und bei dem Einrichten von alternativen Paketquellen. Dort erhalte ich die Fehlermeldung "ungültiger Speicherort". Welche Rechte brauchen Docker und die Unterordner, wo werden die Paketquellen gespeichert und mit welchen Rechten und habe ich weitere Probleme zu erwarten? Auch würde die gerne das Volume3 in Volume1 umbenennen. Wie geht das? Vielen Dank.
  22. @flyride I do not use a basic volume but Raid1. I formated one of the 2 disks and started again. Unfortunately, I cannot move shares from the read-only remaining disk from the degraded Raid1 volume1 to the new basic volume3 since it is read-only. Any idea how to fix it? Thank you.
  23. I made a backup of most data. However, I would like to use the setup (users, vm's, apps, docker, etc.) as they are. Moving all shared folders to a new volume should then do it. One more question: My production system died with the volume read-only problem. Now I am using a similar backup system (918+ and raid5). When checking dmesg I find btrfs errros related to docker: BTRFS error (device dm-1): cannot find qgroup item, qgroupid=2419 ! I don't want to get a second read only system. Do you have any idea what causes the errors and how to fix it? Thank you.
×
×
  • Create New...