• Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

1 Follower

About tdse13

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. 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.
  2. 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 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.
  3. 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 Rechtepro
  4. @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.
  5. 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.
  6. Now I have time to fix my system after a faulty btrfs Raid1 volume crashed. The volume is read only. Since the disks are new and already replaced my idea is to use one of the 2 disks of the crashed volume and create a new volume3. Once all data are moved II would delete the remaining disk of volume1 and build a new raid1 out of the new volume3. Volume2 is in use for VMs. Is this plan feasible? Thank you.
  7. Some more information: lvm> vgs VG #PV #LV #SN Attr VSize VFree vg1000 1 1 0 wz--n- 442.52g 0 lvm> pvs PV VG Fmt Attr PSize PFree /dev/md3 vg1000 lvm2 a-- 442.52g 0 lvm> lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv vg1000 -wi-ao---- 442.52g lvm> lvscan ACTIVE '/dev/vg1000/lv' [442.52 GiB] inherit lvm> lvmdiskscan /dev/md2 [ 12.73 TiB] /dev/md3 [ 442.52 GiB] LVM physical volume 0 disks 1 pa
  8. Recently, 1 of the 2 drives in my 12 TB Raid1 failed. I then stopped the server and changed the 2 disks with larger ones (14 TB Toshiba MG08ACA14TE) and rebuild the raid1 one by one. Unfortunately, now the volume still crashes and the volume size does not recognize the new disks whereas the storage pool shows the new value (12,73 TB instead of 10.47 TB). In Fille Station I can still see my data. #cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid1 sda3[2] sdb3[3] 13667655616 blocks super 1.2 [2/2] [UU] md3 : act
  9. I did the same but HW transcoding does not work. How die you setup the docker file? /dev/dri:/dev/dri Thank you. Context @ 0x56337b535b00] libva: /usr/lib/x86_64-linux-gnu/dri/ has no function __vaDriverInit_1_0 [AVHWDeviceContext @ 0x56337b535b00] Failed to initialise VAAPI connection: -1 (unknown libva error). Error creating a QSV device qsv hwaccel requested for input stream #0:0, but cannot be initialized. [hevc_qsv @ 0x56337b549880] Error initializing the MFX video decoder: invalid handle (-6) Error while decoding stream #0:0: Invalid argu
  10. With my setup WIN 10 Pro is running (slowly but smoohtly) both in 32 and 64 versions with legacy bios. My setup: J4105 board 918+ with 1.04b loader.
  11. No solution so far. But I could install this package as well as Moments in the latest version in my virtual DSM. The virtual DSM accepted the latest firmware DSM 6.2.4-25556.
  12. One more question (a litte bit off topic): Is it difficult to move a baremetal installation to an ESXi based installation? And would that setup run on an Asrock J3345-ITX 16 GB RAM, 2 x 12 TB with xpenology as a vm and other vms with access to the USB ports? Thank you.
  13. What's about USB devices connected to a docker image or a vm, e. g. a zigbee stick?
  14. My xpenology installation is running smoothly on an Asrock J4105 ITX Board (baremetal loader 1.04b, DSM platform DS918+ version 6.2.3). Now I would like to add Volumino as a VM for audio. Is it possible to use the onboard audio (Optical SPDIF Port). Is this possible? I tried audio station with an USB DAC. The iphone software from Synology is not that good and it does not support AirPlay. Thank you.