Wesiwestside

Okay, thx, was empfiehlst du? Clients wären auf Fire TV Stick oder Android TV Geräten und über Browser gut.

Verstehe, gibt es noch alternativen? Den Telekom Vertrag kann ich kündigen. Grundfrage bleibt: Wie bekomme ich eine größere Zahl als nur 52 Sender in mein Heimnetz und schließlich in Plex gespeist.

Moin, ich habe kürzlich die Live TV Funktion bei Plex konfiguriert. Dazu habe ich wie in den verschiedenen Guides/Forumposts/Dokumentationen XTeve installiert und die entsprechenden Einstellungen vorgenommen. Das "Signal" kommt über einen DSL Anschluss von der Telekom mit dem frisch gebuchten Magenta TV Basic. Der Router ist die Fritzbox 7590 AX. Bei der Einrichtung hat soweit auch alles gut funktioniert und ich kann jetzt die 52 unverschlüsselten Sender, welche man ja auch direkt aus der Fritzbox abrufen kann, in Plex Streamen. Nun sind 52 Sender nur eine Teilmenge der 150 versprochenen Sender im Paket Magenta TV Basic. Soweit auch Logisch, da dies auch klar in der Anleitung geschildert wird: "Die Wiedergabe verschlüsselter TV-Programme ist ausschließlich mit dem Media Receiver (Set-Top-Box) des IPTV-Anbieters möglich." Hieraus wird spätestens klar, dass die Telekom 52 Sender unverschlüsselt und die restlichen verschlüsselt sendet. Langer Rede, kurzer sinn: Ich möchte gerne die restlichen verschlüsselten Sender in mein Heimnetz einspeisen um diese auch über Plex zu Streamen. Kann ich das irgendwie realisieren? Ich hatte gehofft, dass wenn ich eine Set-Top-Box wie die Magenta TV One kaufe, ich die auf offiziellem Weg entschlüsselten Streams irgendwie ins Heimnetz gespeist bekomme. Oder gibt es hierfür andere Hardware, vielleicht eine Tuner Karte für den Server selbst?

Abschließend: Bin umgezogen und jetzt bei der Telekom DSL Kunde. Es hat nun alles auf anhieb funktioniert. Danke für den Hinweis!

Firstly thanks a lot. like this? I still don't get whats wrong with my time range input. Is the md# part supposed to point to the whole array? Couldn't figur out where to get the info? My best guess was System devices. Where does it say on your system? Well it seems to be working.

root@Tower:~# ^[[200~wget https://github.com/ianka/xfs_undelete/archive/refs/tags/v12.0.zip -O temp.zip ~ bash: $'\E[200~wget': command not found root@Tower:~# wget https://github.com/ianka/xfs_undelete/archive/refs/tags/v12.0.zip -O temp.zip --2023-08-18 15:35:20-- https://github.com/ianka/xfs_undelete/archive/refs/tags/v12.0.zip Resolving github.com (github.com)... 140.82.121.4 Connecting to github.com (github.com)|140.82.121.4|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/ianka/xfs_undelete/zip/refs/tags/v12.0 [following] --2023-08-18 15:35:20-- https://codeload.github.com/ianka/xfs_undelete/zip/refs/tags/v12.0 Resolving codeload.github.com (codeload.github.com)... 140.82.121.10 Connecting to codeload.github.com (codeload.github.com)|140.82.121.10|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/zip] Saving to: ‘temp.zip’ temp.zip [ <=> ] 26.44K --.-KB/s in 0.01s 2023-08-18 15:35:21 (2.26 MB/s) - ‘temp.zip’ saved [27076] root@Tower:~# unzip temp.zip Archive: temp.zip 4c15e5763e1c560b0b6c8dbdc5f1b06d1530d3fc creating: xfs_undelete-12.0/ inflating: xfs_undelete-12.0/LICENSE inflating: xfs_undelete-12.0/README.md inflating: xfs_undelete-12.0/shell.nix inflating: xfs_undelete-12.0/xfs_undelete inflating: xfs_undelete-12.0/xfs_undelete.man root@Tower:~# rm temp.zip root@Tower:~# cd xfs_undelete-12.0/ root@Tower:~/xfs_undelete-12.0# ./xfs_undelete --help xfs_undelete [options] device -- options are: -t value deleted since <> -T value modified since <> -r value list of file extensions and mimetypes to recover <*> -i value list of file extensions and mimetypes to ignore <bin> -z value list of file extensions and mimetypes to remove all trailing zeroes from <text/*> -o value target directory for recovered files <xfs_undeleted> -s value restart at inode number <> -m value magic path passed to the 'file' utility <> -l list file extensions understood -no-remount-readonly do not remount read-only before recovery -- Forcibly stop option processing -help Print this message -? Print this message root@Tower:~/xfs_undelete-12.0# xfs_undelete -t 2023-08-16 /dev/sdc bash: xfs_undelete: command not found root@Tower:~/xfs_undelete-12.0# -t 2023-08-16 /dev/sdc bash: -t: command not found root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 /dev/sdc This isn't an XFS filesystem or filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 /dev/sde This isn't an XFS filesystem or filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 /dev/sdb This isn't an XFS filesystem or filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16../dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16/dev/sdc -o/mnt/external_harddisk/dev/sdi xfs_undelete [options] device -- options are: -t value deleted since <> -T value modified since <> -r value list of file extensions and mimetypes to recover <*> -i value list of file extensions and mimetypes to ignore <bin> -z value list of file extensions and mimetypes to remove all trailing zeroes from <text/*> -o value target directory for recovered files <xfs_undeleted> -s value restart at inode number <> -m value magic path passed to the 'file' utility <> -l list file extensions understood -no-remount-readonly do not remount read-only before recovery -- Forcibly stop option processing -help Print this message -? Print this message root@Tower:~/xfs_undelete-12.0# -o/mnt/external_harddisk/dev/sdi bash: -o/mnt/external_harddisk/dev/sdi: No such file or directory root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -o/mnt/external_harddisk/dev/sdi xfs_undelete [options] device -- options are: -t value deleted since <> -T value modified since <> -r value list of file extensions and mimetypes to recover <*> -i value list of file extensions and mimetypes to ignore <bin> -z value list of file extensions and mimetypes to remove all trailing zeroes from <text/*> -o value target directory for recovered files <xfs_undeleted> -s value restart at inode number <> -m value magic path passed to the 'file' utility <> -l list file extensions understood -no-remount-readonly do not remount read-only before recovery -- Forcibly stop option processing -help Print this message -? Print this message root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..2023-08-18/dev/sdc -o/mnt/external_harddisk/dev/sdi xfs_undelete [options] device -- options are: -t value deleted since <> -T value modified since <> -r value list of file extensions and mimetypes to recover <*> -i value list of file extensions and mimetypes to ignore <bin> -z value list of file extensions and mimetypes to remove all trailing zeroes from <text/*> -o value target directory for recovered files <xfs_undeleted> -s value restart at inode number <> -m value magic path passed to the 'file' utility <> -l list file extensions understood -no-remount-readonly do not remount read-only before recovery -- Forcibly stop option processing -help Print this message -? Print this message root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..2023-08-18/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..-6hours/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t -96hours/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -o/mnt/disks/Overflow/dev/sdc xfs_undelete [options] device -- options are: -t value deleted since <> -T value modified since <> -r value list of file extensions and mimetypes to recover <*> -i value list of file extensions and mimetypes to ignore <bin> -z value list of file extensions and mimetypes to remove all trailing zeroes from <text/*> -o value target directory for recovered files <xfs_undeleted> -s value restart at inode number <> -m value magic path passed to the 'file' utility <> -l list file extensions understood -no-remount-readonly do not remount read-only before recovery -- Forcibly stop option processing -help Print this message -? Print this message root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t -96hours../dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t -96hours../dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 6hours../dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t <-96hours..>/dev/sdc bash: -96hours..: No such file or directory root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 -r 'video/*' -o /mnt/disks/Overflow/xfs_undeleted/ /dev/sdc This isn't an XFS filesystem or filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 -r 'video/*' -o /mnt/disks/Overflow/ /dev/sdc This isn't an XFS filesystem or filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16 -r 'video/*' -o /mnt/disks/Overflow//dev/sdc Please specify a block device or an XFS filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..2023-08-18 -r 'video/*' -o /mnt/disks/Overflow/dev/sdc Please specify a block device or an XFS filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..2023-08-18 Please specify a block device or an XFS filesystem image. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-08-16..2023-08-18/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ./xfs_undelete -t 2023-16-08..2023-18-08/dev/sdc Unable to parse time range. Please put it as a range of time specs Tcl's [clock scan] can understand, e.g. 2022-06-04..-2hours. A single value as -2hours is considered the same as a range -2hours..now. root@Tower:~/xfs_undelete-12.0# ^C root@Tower:~/xfs_undelete-12.0# xfs_undelete -t 2023-08-16 -r 'video/*' -o /mnt/disks/Overflow/xfs_undeleted/ /dev/sdc bash: xfs_undelete: command not found root@Tower:~/xfs_undelete-12.0# Im looking into installing the GNU Coreutils now.

Hey, any pointers on what to do ? I was was moving some videos around, after which i routinely deleted the then empty folders. At 03:30AM I must have accidentaly selected the parent folder and pressed delete. I noticed immidiatly and canceled the deletion but lost 3tb in movies. BtW there was a parity check running. I shut down my server and removed each of the 5 disks. I tried to recover the files with UFS Explorer Standard Recovery but only found empty folders. The cause may be that the movie folder is in a share which has all five disks included. Now i put the disks back in my server and am trying to get it to work with XFS_undelete. I don't seem to get the command right. This is the best i can make from the instructions: ./xfs_undelete -t 2023-08-16..2023-08-18/dev/sdc I also want the restored files to be written to an unnasigned device which i plugged in to the server so: -o/mnt/disks/Overflow/dev/sdc do i type this in the same line?Like: ./xfs_undelete -t 2023-08-16..2023-08-18/dev/sdc -o/mnt/disks/Overflow /dev/sdc Obviously i am rather unexperienced using Commandline so any help will be grately appreciated.

ipv6 habe ich doch mit der ersten option angewählt oder verstehe ich dich falsch? besten Dank!

Moin, ich habe mich jetzt schon gefühlt durch jedes Forum geklickt und habe keine zufriedenstellende Antwort gefunden. Ich möchte den Remote Access des My Server Plugins nutzen und bekomme jedes mal die Fehlermeldung: die Freigabe sieht so aus: Ich finde die Anleitung von AWM zur Portfreigabe nicht besonders einleuchtend: https://avm.de/service/wissensdatenbank/dok/FRITZ-Box-7490/893_Statische-Portfreigaben-einrichten/ "Wenn ein einzelner Port freigegeben werden soll, tragen Sie unter "Port an Gerät", "bis Port" und "Port extern gewünscht (IPv4)" die Portnummer ein, auf der der Serverdienst bzw. die Anwendung Verbindungen entgegen nimmt." Klingt für mich als müsste ich drei mal den gleichen Port eingeben? Ich habe alle möglichen anordnungen der Portnummern in den drei Feldern ausprobiert. Trotzdem sagt mir die FReigaben Übersicht: Wie man erkennen kann nutze ich eine AWM Fritzbox 6660 Cable. Der Unraid server ist für IPV4 und IPV6 konfiguriert. Die FRITZ!Box verwendet einen DS-Lite-Tunnel Portscanner sagt auch, dass die Ports geschlossen sind. Danke schonmal im Voraus.