[Erledigt] Aufnahmen brechen nach wenigen sekunden ab - Speicherfehler

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

  • [Erledigt] Aufnahmen brechen nach wenigen sekunden ab - Speicherfehler

    Hallo zusammen,

    ich habe seit kurzem ein merkwürdiges Problem mit Aufnahmen. Diese brechen nach einer kurzen Laufzeit von wenigen Sekunden (~20) ab und ich erhalten die Meldung, dass es einen Speicherfehler gibt und die Festplatte möglicherweise voll ist. Bisher hatte ich das nicht und an meiner Konfiguration hat sich nichts geändert.

    Die VU+ Solo² ist mehr NFS Mount mit Freigaben auf einem Synology NAS verbunden und speichert dort Aufnahmen ab. Eine interne HDD gibt es nicht. Die Freigaben habe ich mit dem AutoFS Plugin hier aus dem Forum erstellt und die funktionieren auch bisher einwandfrei.

    Ich habe dann nach Fehlern gesuch und bin im Log auf eine Meldung gestoßen: NFS: Server not responding, timed out

    Diese finde ich dort mehrfach. Ich habe dann die Verbindung zwischen VU+ und NAS geprüft aber auch das scheint zu funktionieren. zumindest kann ich die Synology von der VU+ anpingen und erhalte eine Antwort.

    Die VU+ läuft mit dem VTI IMage und ist auf dem aktuellen Stand (update / upgrade).

    Hier bin ich nun etwas ratlos, woran es noch liegen könnte bzw. wie ich das Problem lokalisieren kann.

    Habt ihr da ein paar Tipps für mich?


    Danke und Gruß
    Matthias
  • Die Freigabe aufs NAS "als HDD-Ersatz" erstellt ?
    Wenn nicht dran, steck einen USB-Stick an die Box - einhängen nach /media/usb .
    Wie siehts dann aus, wenn du vom NAS Daten auf die Box (und umgehehrt) kopierst (z.B. mit dem Filebrowser-VTI) ?
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    KAPIERVORGANG beendet.

    Zubehör : Philips 46PFL-9705 / 37PFL-9604, Samsung HT-E6759W, Samsung SPF 107H-105P-87H, Qnap TS-253A, Harmony 650, Fritzbox 7490, Cisco WAP4410N, Netgear M4100-D12G, TPLink HS100/HS110/LB110
  • Ja genau das gleiche passiert auch bei mir. Hab die Platte neu formatiert aus und eingehängt usw.. Leider bekomme ich das nicht in den Griff und die Meldung kommt weiter.
  • HD intern oder extern ?
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    KAPIERVORGANG beendet.

    Zubehör : Philips 46PFL-9705 / 37PFL-9604, Samsung HT-E6759W, Samsung SPF 107H-105P-87H, Qnap TS-253A, Harmony 650, Fritzbox 7490, Cisco WAP4410N, Netgear M4100-D12G, TPLink HS100/HS110/LB110
  • markusw schrieb:

    Die Freigabe aufs NAS "als HDD-Ersatz" erstellt ?
    Wenn nicht dran, steck einen USB-Stick an die Box - einhängen nach /media/usb .
    Wie siehts dann aus, wenn du vom NAS Daten auf die Box (und umgehehrt) kopierst (z.B. mit dem Filebrowser-VTI) ?
    Ich nutze die Standard-Einstellungen aus dem AutoFS Plugin (s. Anhang). Dort werden die Mounts als Simlinks angelegt und erscheinen (wie mir jetzt aufgefallen ist) nicht in der Freigabe-Verwaltung. Die Liste ist dort leer.

    Jetzt ist mir aufgefallen, dass ich beim Wiedergeben von Aufnahmen das gleiche Problem habe. Im Log erscheint dann eben auch dieselbe Meldung. Die Wiedergabe stock dann kurz mit Ladebalken.2018-01-10 17_53_06-auto.network Eintrag bearbeiten.png


    HIer noch der Auszug aus dem Log:

    Quellcode

    1. Jan 10 17:34:06 vusolo2 syslog.info syslogd started: BusyBox v1.23.2
    2. Jan 10 17:34:06 vusolo2 user.info kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
    3. Jan 10 17:34:06 vusolo2 user.notice kernel: NFS: Registering the id_resolver key type
    4. Jan 10 17:34:06 vusolo2 user.notice kernel: Key type id_resolver registered
    5. Jan 10 17:34:06 vusolo2 user.notice kernel: Key type id_legacy registered
    6. Jan 10 17:34:06 vusolo2 user.info kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
    7. Jan 10 17:34:06 vusolo2 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    8. Jan 10 17:34:06 vusolo2 user.info kernel: msgmni has been set to 1118
    9. Jan 10 17:34:06 vusolo2 user.info kernel: io scheduler noop registered
    10. Jan 10 17:34:06 vusolo2 user.info kernel: io scheduler cfq registered (default)
    11. Jan 10 17:34:06 vusolo2 user.info kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    12. Jan 10 17:34:06 vusolo2 user.info kernel: serial8250.0: ttyS0 at MMIO 0x10406900 (irq = 65, base_baud = 5062500) is a 16550A
    13. Jan 10 17:34:06 vusolo2 user.info kernel: console [ttyS0] enabled
    14. Jan 10 17:34:06 vusolo2 user.info kernel: bootconsole [early0] disabled
    15. Jan 10 17:34:06 vusolo2 user.info kernel: serial8250.0: ttyS1 at MMIO 0x10406940 (irq = 66, base_baud = 5062500) is a 16550A
    16. Jan 10 17:34:06 vusolo2 user.info kernel: serial8250.0: ttyS2 at MMIO 0x10406980 (irq = 67, base_baud = 5062500) is a 16550A
    17. Jan 10 17:34:06 vusolo2 user.info kernel: loop: module loaded
    18. Jan 10 17:34:06 vusolo2 user.err kernel: ahci strict-ahci.0: can't get clock
    19. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: sata [1]
    20. Jan 10 17:34:06 vusolo2 user.debug kernel: bcm40nm_pm_sata_enable 00
    21. Jan 10 17:34:06 vusolo2 user.info kernel: ahci strict-ahci.0: SSS flag set, parallel bus scan disabled
    22. Jan 10 17:34:06 vusolo2 user.info kernel: ahci strict-ahci.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl platform mode
    23. Jan 10 17:34:06 vusolo2 user.info kernel: ahci strict-ahci.0: flags: ncq sntf stag clo slum part
    24. Jan 10 17:34:06 vusolo2 user.info kernel: scsi0 : ahci_platform
    25. Jan 10 17:34:06 vusolo2 user.info kernel: scsi1 : ahci_platform
    26. Jan 10 17:34:06 vusolo2 user.info kernel: ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 41
    27. Jan 10 17:34:06 vusolo2 user.info kernel: ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 41
    28. Jan 10 17:34:06 vusolo2 user.info kernel: brcmstb_nand: NAND controller driver is loaded
    29. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: network [1]
    30. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: enet [1]
    31. Jan 10 17:34:06 vusolo2 user.debug kernel: bcm40nm_pm_genet_enable 00
    32. Jan 10 17:34:06 vusolo2 user.crit kernel: Found PHY at Address 3
    33. Jan 10 17:34:06 vusolo2 user.info kernel: bcmgenet: configuring instance #0 for external RGMII
    34. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_disable: enet [0]
    35. Jan 10 17:34:06 vusolo2 user.debug kernel: bcm40nm_pm_genet_disable 00
    36. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_disable: network [0]
    37. Jan 10 17:34:06 vusolo2 user.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    38. Jan 10 17:34:06 vusolo2 user.info kernel: ata1: SATA link down (SStatus 0 SControl 300)
    39. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: usb [1]
    40. Jan 10 17:34:06 vusolo2 user.debug kernel: bcm40nm_pm_usb_enable 00
    41. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.0: Broadcom STB EHCI
    42. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
    43. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.0: irq 69, io mem 0x10480300
    44. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
    45. Jan 10 17:34:06 vusolo2 user.info kernel: hub 1-0:1.0: USB hub found
    46. Jan 10 17:34:06 vusolo2 user.info kernel: hub 1-0:1.0: 1 port detected
    47. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.1: Broadcom STB EHCI
    48. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
    49. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.1: irq 70, io mem 0x10480500
    50. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
    51. Jan 10 17:34:06 vusolo2 user.info kernel: hub 2-0:1.0: USB hub found
    52. Jan 10 17:34:06 vusolo2 user.info kernel: hub 2-0:1.0: 1 port detected
    53. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.2: Broadcom STB EHCI
    54. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.2: new USB bus registered, assigned bus number 3
    55. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.2: irq 74, io mem 0x10490300
    56. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.2: USB 0.0 started, EHCI 1.00
    57. Jan 10 17:34:06 vusolo2 user.info kernel: hub 3-0:1.0: USB hub found
    58. Jan 10 17:34:06 vusolo2 user.info kernel: hub 3-0:1.0: 1 port detected
    59. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.3: Broadcom STB EHCI
    60. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.3: new USB bus registered, assigned bus number 4
    61. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.3: irq 75, io mem 0x10490500
    62. Jan 10 17:34:06 vusolo2 user.info kernel: ehci-brcm ehci-brcm.3: USB 0.0 started, EHCI 1.00
    63. Jan 10 17:34:06 vusolo2 user.info kernel: hub 4-0:1.0: USB hub found
    64. Jan 10 17:34:06 vusolo2 user.info kernel: hub 4-0:1.0: 1 port detected
    65. Jan 10 17:34:06 vusolo2 user.info kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    66. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.0: Broadcom STB OHCI
    67. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 5
    68. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.0: irq 71, io mem 0x10480400
    69. Jan 10 17:34:06 vusolo2 user.info kernel: hub 5-0:1.0: USB hub found
    70. Jan 10 17:34:06 vusolo2 user.info kernel: hub 5-0:1.0: 1 port detected
    71. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.1: Broadcom STB OHCI
    72. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
    73. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.1: irq 72, io mem 0x10480600
    74. Jan 10 17:34:06 vusolo2 user.info kernel: ata2: SATA link down (SStatus 0 SControl 300)
    75. Jan 10 17:34:06 vusolo2 user.info kernel: hub 6-0:1.0: USB hub found
    76. Jan 10 17:34:06 vusolo2 user.info kernel: hub 6-0:1.0: 1 port detected
    77. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.2: Broadcom STB OHCI
    78. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
    79. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.2: irq 76, io mem 0x10490400
    80. Jan 10 17:34:06 vusolo2 user.info kernel: hub 7-0:1.0: USB hub found
    81. Jan 10 17:34:06 vusolo2 user.info kernel: hub 7-0:1.0: 1 port detected
    82. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.3: Broadcom STB OHCI
    83. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
    84. Jan 10 17:34:06 vusolo2 user.info kernel: ohci-brcm ohci-brcm.3: irq 77, io mem 0x10490600
    85. Jan 10 17:34:06 vusolo2 user.info kernel: hub 8-0:1.0: USB hub found
    86. Jan 10 17:34:06 vusolo2 user.info kernel: hub 8-0:1.0: 1 port detected
    87. Jan 10 17:34:06 vusolo2 user.info kernel: usbcore: registered new interface driver usb-storage
    88. Jan 10 17:34:06 vusolo2 user.info kernel: mousedev: PS/2 mouse device common for all mice
    89. Jan 10 17:34:06 vusolo2 user.info kernel: i2c /dev entries driver
    90. Jan 10 17:34:06 vusolo2 user.info kernel: IR NEC protocol handler initialized
    91. Jan 10 17:34:06 vusolo2 user.info kernel: IR RC5(x) protocol handler initialized
    92. Jan 10 17:34:06 vusolo2 user.info kernel: IR RC6 protocol handler initialized
    93. Jan 10 17:34:06 vusolo2 user.info kernel: IR JVC protocol handler initialized
    94. Jan 10 17:34:06 vusolo2 user.info kernel: IR Sony protocol handler initialized
    95. Jan 10 17:34:06 vusolo2 user.info kernel: IR RC5 (streamzap) protocol handler initialized
    96. Jan 10 17:34:06 vusolo2 user.info kernel: IR SANYO protocol handler initialized
    97. Jan 10 17:34:06 vusolo2 user.info kernel: IR MCE Keyboard/mouse protocol handler initialized
    98. Jan 10 17:34:06 vusolo2 user.info kernel: gspca_main: v2.14.0 registered
    99. Jan 10 17:34:06 vusolo2 user.info kernel: sdhci: Secure Digital Host Controller Interface driver
    100. Jan 10 17:34:06 vusolo2 user.info kernel: sdhci: Copyright(c) Pierre Ossman
    101. Jan 10 17:34:06 vusolo2 user.info kernel: sdhci-pltfm: SDHCI platform and OF driver helper
    102. Jan 10 17:34:06 vusolo2 user.info kernel: hidraw: raw HID events driver (C) Jiri Kosina
    103. Jan 10 17:34:06 vusolo2 user.info kernel: usbcore: registered new interface driver usbhid
    104. Jan 10 17:34:06 vusolo2 user.info kernel: usbhid: USB HID core driver
    105. Jan 10 17:34:06 vusolo2 user.info kernel: TCP: cubic registered
    106. Jan 10 17:34:06 vusolo2 user.info kernel: NET: Registered protocol family 17
    107. Jan 10 17:34:06 vusolo2 user.notice kernel: Key type dns_resolver registered
    108. Jan 10 17:34:06 vusolo2 user.info kernel: PM: CP0 COUNT/COMPARE frequency does not depend on divisor
    109. Jan 10 17:34:06 vusolo2 user.info kernel: EBI CS0: setting up NAND flash (primary)
    110. Jan 10 17:34:06 vusolo2 user.info kernel: NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix H27U2G8F2CTR-BC)
    111. Jan 10 17:34:06 vusolo2 user.info kernel: NAND device: 256MiB, SLC, page size: 2048, OOB size: 64
    112. Jan 10 17:34:06 vusolo2 user.info kernel: NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix H27U2G8F2CTR-BC)
    113. Jan 10 17:34:06 vusolo2 user.info kernel: NAND device: 256MiB, SLC, page size: 2048, OOB size: 64
    114. Jan 10 17:34:06 vusolo2 user.info kernel: brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
    115. Jan 10 17:34:06 vusolo2 user.info kernel: Bad block table found at page 131008, version 0x01
    116. Jan 10 17:34:06 vusolo2 user.info kernel: Bad block table found at page 130944, version 0x01
    117. Jan 10 17:34:06 vusolo2 user.notice kernel: Creating 4 MTD partitions on "brcmnand.0":
    118. Jan 10 17:34:06 vusolo2 user.notice kernel: 0x000001f00000-0x000010000000 : "rootfs"
    119. Jan 10 17:34:06 vusolo2 user.notice kernel: 0x000001f00000-0x000010000000 : "rootfs(redundant)"
    120. Jan 10 17:34:06 vusolo2 user.notice kernel: 0x000000200000-0x000000900000 : "kernel"
    121. Jan 10 17:34:06 vusolo2 user.notice kernel: 0x000000900000-0x000000a00000 : "mac"
    122. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: attaching mtd0 to ubi0
    123. Jan 10 17:34:06 vusolo2 user.notice kernel: random: nonblocking pool is initialized
    124. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: scanning is finished
    125. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: attached mtd0 (name "rootfs", size 225 MiB) to ubi0
    126. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    127. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    128. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
    129. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: good PEBs: 1796, bad PEBs: 4, corrupted PEBs: 0
    130. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
    131. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: max/mean erase counter: 58/24, WL threshold: 4096, image sequence number: 2087669699
    132. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: available PEBs: 0, total reserved PEBs: 1796, PEBs reserved for bad PEB handling: 36
    133. Jan 10 17:34:06 vusolo2 user.notice kernel: UBI: background thread "ubi_bgt0d" started, PID 52
    134. Jan 10 17:34:06 vusolo2 user.info kernel: ALSA device list:
    135. Jan 10 17:34:06 vusolo2 user.info kernel: No soundcards found.
    136. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: parse sync
    137. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: background thread "ubifs_bgt0_0" started, PID 55
    138. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: mounted UBI device 0, volume 0, name "rootfs"
    139. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
    140. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: FS size: 221573120 bytes (211 MiB, 1745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
    141. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: reserved for root: 0 bytes (0 KiB)
    142. Jan 10 17:34:06 vusolo2 user.notice kernel: UBIFS: media format: w4/r0 (latest is w4/r0), UUID 055021F8-02FE-4DA4-8A73-9239AEF36157, small LPT model
    143. Jan 10 17:34:06 vusolo2 user.info kernel: VFS: Mounted root (ubifs filesystem) on device 0:12.
    144. Jan 10 17:34:06 vusolo2 user.info kernel: devtmpfs: mounted
    145. Jan 10 17:34:06 vusolo2 user.info kernel: Freeing unused kernel memory: 256K (80780000 - 807c0000)
    146. Jan 10 17:34:06 vusolo2 daemon.info kernel: udevd[73]: starting version 182
    147. Jan 10 17:34:06 vusolo2 user.err kernel: UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
    148. Jan 10 17:34:06 vusolo2 user.warn kernel: procmk_init
    149. Jan 10 17:34:06 vusolo2 user.warn kernel: bcm_event: module license 'Proprietary' taints kernel.
    150. Jan 10 17:34:06 vusolo2 user.warn kernel: Disabling lock debugging due to kernel taint
    151. Jan 10 17:34:06 vusolo2 user.info kernel: DVB: registering new adapter (_vuplus_solo2_)
    152. Jan 10 17:34:06 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    153. Jan 10 17:34:06 vusolo2 user.warn kernel: Hotplug - status.connected 0:0:0
    154. Jan 10 17:34:06 vusolo2 user.warn kernel: [GP]:brcm_pwm_init
    155. Jan 10 17:34:06 vusolo2 user.info kernel: brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
    156. Jan 10 17:34:06 vusolo2 user.warn kernel: [MPVR]: >> misc_pvr_init
    157. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: ^A6bcm7335_video_init
    158. Jan 10 17:34:06 vusolo2 user.warn kernel: [AUD]: ^A6bcm7335_audio_init
    159. Jan 10 17:34:06 vusolo2 user.info kernel: BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (BCM7346 FE)...
    160. Jan 10 17:34:06 vusolo2 user.info kernel: BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (BCM7346 FE)...
    161. Jan 10 17:34:06 vusolo2 user.warn kernel: BKNI_P_GetTrackAllocEntry_resize: resizing from 5376->8704
    162. Jan 10 17:34:06 vusolo2 user.warn kernel: BKNI_Malloc(linuxkernel) top users:
    163. Jan 10 17:34:06 vusolo2 user.warn kernel: blocks, bytes, filename:line
    164. Jan 10 17:34:06 vusolo2 user.warn kernel: 1024, 176128, portinginterface/hsm/src/common/bhsm.c:500
    165. Jan 10 17:34:06 vusolo2 user.warn kernel: 612, 133680, BSEAV/lib/utils/balloc.c:31
    166. Jan 10 17:34:06 vusolo2 user.warn kernel: 388, 24832, magnum/commonutils/mrc/src/bmrc_monitor.c:666
    167. Jan 10 17:34:06 vusolo2 user.info kernel: input: dreambox advanced remote control (native) as /devices/virtual/input/input0
    168. Jan 10 17:34:06 vusolo2 user.info kernel: [LCD]: registered
    169. Jan 10 17:34:06 vusolo2 user.warn kernel: 0:0
    170. Jan 10 17:34:06 vusolo2 user.info kernel: [CI]: registered ci0
    171. Jan 10 17:34:06 vusolo2 user.info kernel: [CI]: CI interface initialised
    172. Jan 10 17:34:06 vusolo2 user.info kernel: [DFP]: registered dbox fp
    173. Jan 10 17:34:06 vusolo2 user.info kernel: [DFP]: Scart 9597 is found 4
    174. Jan 10 17:34:06 vusolo2 user.info kernel: [SC]: registered sci0
    175. Jan 10 17:34:06 vusolo2 user.info kernel: [SC]: registered sci1
    176. Jan 10 17:34:06 vusolo2 user.warn kernel: system_time_set wakeup mode get
    177. Jan 10 17:34:06 vusolo2 user.warn kernel: system_time_set wakeup mode get 0xc5
    178. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
    179. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1 0
    180. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
    181. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
    182. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
    183. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: network [1]
    184. Jan 10 17:34:06 vusolo2 user.debug kernel: __clk_enable: enet [1]
    185. Jan 10 17:34:06 vusolo2 user.debug kernel: bcm40nm_pm_genet_enable 00
    186. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
    187. Jan 10 17:34:06 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    188. Jan 10 17:34:06 vusolo2 user.info kernel: bcmgenet bcmgenet.0 eth0: link up, 1000 Mbps, full duplex
    189. Jan 10 17:34:06 vusolo2 user.info kernel: NET: Registered protocol family 10
    190. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Found user 'avahi' (UID 998) and group 'avahi' (GID 997).
    191. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Successfully dropped root privileges.
    192. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: avahi-daemon 0.6.31 starting up.
    193. Jan 10 17:34:06 vusolo2 daemon.warn avahi-daemon[456]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
    194. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Successfully called chroot().
    195. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Successfully dropped remaining capabilities.
    196. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Loading service file /services/sftp-ssh.service.
    197. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Loading service file /services/ssh.service.
    198. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.10.78.
    199. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: New relevant interface eth0.IPv4 for mDNS.
    200. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Network interface enumeration completed.
    201. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Registering new address record for fe80::21d:ecff:fe0b:7b0a on eth0.*.
    202. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Registering new address record for 192.168.10.78 on eth0.IPv4.
    203. Jan 10 17:34:06 vusolo2 daemon.info avahi-daemon[456]: Registering HINFO record with values 'MIPS'/'LINUX'.
    204. Jan 10 17:34:07 vusolo2 daemon.err wsdd[477]: udp_send: Failed to send udp packet with Invalid argument
    205. Jan 10 17:34:07 vusolo2 daemon.err wsdd[477]: Failed to send hello with Invalid argument
    206. Jan 10 17:34:07 vusolo2 daemon.info avahi-daemon[456]: Server startup complete. Host name is vusolo2.local. Local service cookie is 3952689876.
    207. Jan 10 17:34:07 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
    208. Jan 10 17:34:07 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1 0
    209. Jan 10 17:34:07 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
    210. Jan 10 17:34:07 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
    211. Jan 10 17:34:07 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
    212. Jan 10 17:34:08 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
    213. Jan 10 17:34:08 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    214. Jan 10 17:34:08 vusolo2 daemon.info avahi-daemon[456]: Service "vusolo2" (/services/ssh.service) successfully established.
    215. Jan 10 17:34:08 vusolo2 daemon.info avahi-daemon[456]: Service "vusolo2" (/services/sftp-ssh.service) successfully established.
    216. Jan 10 17:34:10 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
    217. Jan 10 17:34:10 vusolo2 user.err kernel: UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
    218. Jan 10 17:34:18 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=0
    219. Jan 10 17:34:18 vusolo2 user.warn kernel: [AUD]: connected : 0, 7 (Ac3 : 7) is not supported in this hdmi
    220. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MUTE 0
    221. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -863232528
    222. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
    223. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
    224. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    225. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -863232528
    226. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
    227. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    228. Jan 10 17:34:26 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    229. Jan 10 17:34:27 vusolo2 user.warn kernel: FE tune
    230. Jan 10 17:34:27 vusolo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0
    231. Jan 10 17:34:27 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 0
    232. Jan 10 17:34:27 vusolo2 user.warn kernel: [AUD]: AC3 downmix 1 state : 1
    233. Jan 10 17:34:27 vusolo2 user.warn kernel: [AUD]: AUDIO_PAUSE 7725632
    234. Jan 10 17:34:27 vusolo2 user.warn kernel: [AUD]: AUDIO_PLAY 7725632 decoder start : 0
    235. Jan 10 17:34:27 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    236. Jan 10 17:34:27 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 1
    237. Jan 10 17:34:27 vusolo2 user.warn kernel: [VID]: VIDEO_FREEZE 7725632 0
    238. Jan 10 17:34:27 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 7725632 5 2
    239. Jan 10 17:34:28 vusolo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0 1
    240. Jan 10 17:34:28 vusolo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0 1
    241. Jan 10 17:34:28 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 7725632 1
    242. Jan 10 17:34:28 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7725632 1 aph=0xccb51600
    243. Jan 10 17:34:28 vusolo2 user.warn kernel: [AUD]: Mute : 0
    244. Jan 10 17:34:28 vusolo2 user.warn kernel: [AUD]: AUDIO_CHANNEL_SELECT 0
    245. Jan 10 17:36:02 vusolo2 auth.info login[660]: root login on 'pts/0'
    246. Jan 10 17:36:21 vusolo2 user.err kernel: UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
    247. Jan 10 17:41:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    248. Jan 10 17:41:15 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:0
    249. Jan 10 17:41:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    250. Jan 10 17:41:15 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xf
    251. Jan 10 17:41:16 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    252. Jan 10 17:41:16 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    253. Jan 10 17:41:29 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    254. Jan 10 17:41:29 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    255. Jan 10 17:41:29 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    256. Jan 10 17:41:29 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    257. Jan 10 17:41:29 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    258. Jan 10 17:41:29 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    259. Jan 10 17:41:30 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    260. Jan 10 17:41:30 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:2
    261. Jan 10 17:41:30 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    262. Jan 10 17:41:30 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xe
    263. Jan 10 17:41:30 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    264. Jan 10 17:41:30 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    265. Jan 10 17:41:35 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    266. Jan 10 17:41:35 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    267. Jan 10 17:41:35 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    268. Jan 10 17:41:35 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    269. Jan 10 17:41:36 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    270. Jan 10 17:41:36 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:2
    271. Jan 10 17:41:36 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    272. Jan 10 17:41:36 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xe
    273. Jan 10 17:41:36 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    274. Jan 10 17:41:36 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    275. Jan 10 17:43:14 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    276. Jan 10 17:43:14 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    277. Jan 10 17:43:14 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    278. Jan 10 17:43:14 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    279. Jan 10 17:43:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    280. Jan 10 17:43:15 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:2
    281. Jan 10 17:43:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    282. Jan 10 17:43:15 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xe
    283. Jan 10 17:43:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    284. Jan 10 17:43:15 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    285. Jan 10 17:43:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    286. Jan 10 17:43:15 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    287. Jan 10 17:43:15 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    288. Jan 10 17:43:15 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    289. Jan 10 17:45:51 vusolo2 auth.info login[1280]: root login on 'pts/1'
    290. Jan 10 17:46:48 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    291. Jan 10 17:46:48 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:2
    292. Jan 10 17:46:48 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    293. Jan 10 17:46:48 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xe
    294. Jan 10 17:46:48 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    295. Jan 10 17:46:48 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    296. Jan 10 17:46:50 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    297. Jan 10 17:46:50 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    298. Jan 10 17:46:50 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    299. Jan 10 17:46:50 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    300. Jan 10 17:46:51 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    301. Jan 10 17:46:51 vusolo2 user.warn kernel: Hotplug - status.connected 1:0:2
    302. Jan 10 17:46:51 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    303. Jan 10 17:46:51 vusolo2 user.warn kernel: Hotplug - connecting HDMI to display 0xe
    304. Jan 10 17:46:51 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    305. Jan 10 17:46:51 vusolo2 user.warn kernel: Hotplug - status.connected 1:1:2
    306. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "VIDEO_TS" not found in map source(s).
    307. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "video_ts" not found in map source(s).
    308. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "VIDEO_TS.IFO" not found in map source(s).
    309. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "video_ts.ifo" not found in map source(s).
    310. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key ".jpg" not found in map source(s).
    311. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key ".png" not found in map source(s).
    312. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key ".jpeg" not found in map source(s).
    313. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "folder.jpg" not found in map source(s).
    314. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "folder.png" not found in map source(s).
    315. Jan 10 17:47:12 vusolo2 daemon.crit automount[392]: key "folder.jpeg" not found in map source(s).
    316. Jan 10 17:47:16 vusolo2 daemon.crit automount[392]: key ".hidden_movielist_entries" not found in map source(s).
    317. Jan 10 17:47:16 vusolo2 daemon.crit automount[392]: key "Filme.txt" not found in map source(s).
    318. Jan 10 17:47:16 vusolo2 daemon.crit automount[392]: key "Filme.info" not found in map source(s).
    319. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "VIDEO_TS" not found in map source(s).
    320. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "video_ts" not found in map source(s).
    321. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "VIDEO_TS.IFO" not found in map source(s).
    322. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "video_ts.ifo" not found in map source(s).
    323. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key ".jpg" not found in map source(s).
    324. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key ".png" not found in map source(s).
    325. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key ".jpeg" not found in map source(s).
    326. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "folder.jpg" not found in map source(s).
    327. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "folder.png" not found in map source(s).
    328. Jan 10 17:47:22 vusolo2 daemon.crit automount[392]: key "folder.jpeg" not found in map source(s).
    329. Jan 10 17:47:46 vusolo2 daemon.crit automount[392]: key "VIDEO_TS" not found in map source(s).
    330. Jan 10 17:47:46 vusolo2 daemon.crit automount[392]: key "video_ts" not found in map source(s).
    331. Jan 10 17:47:46 vusolo2 daemon.crit automount[392]: key "VIDEO_TS.IFO" not found in map source(s).
    332. Jan 10 17:47:46 vusolo2 daemon.crit automount[392]: key "video_ts.ifo" not found in map source(s).
    333. Jan 10 17:47:52 vusolo2 daemon.crit automount[392]: key "Filme.txt" not found in map source(s).
    334. Jan 10 17:47:52 vusolo2 daemon.crit automount[392]: key "Filme.info" not found in map source(s).
    335. Jan 10 17:47:55 vusolo2 daemon.crit automount[392]: key "VIDEO_TS" not found in map source(s).
    336. Jan 10 17:47:55 vusolo2 daemon.crit automount[392]: key "video_ts" not found in map source(s).
    337. Jan 10 17:47:55 vusolo2 daemon.crit automount[392]: key "VIDEO_TS.IFO" not found in map source(s).
    338. Jan 10 17:47:55 vusolo2 daemon.crit automount[392]: key "video_ts.ifo" not found in map source(s).
    339. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 1 1
    340. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_STOP 7725632
    341. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7725632 0 aph=0x0
    342. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE aph=0 0 0
    343. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0
    344. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 1
    345. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: downmix 1 state : 1
    346. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_PAUSE 7725632
    347. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_PLAY 7725632 decoder start : 0
    348. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    349. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
    350. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_FREEZE 7725632 0
    351. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 7725632 2 2
    352. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0 1
    353. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0 1
    354. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 7725632 1
    355. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7725632 1 aph=0xcca11c00
    356. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: Mute : 0
    357. Jan 10 17:48:09 vusolo2 user.warn kernel: [AUD]: AUDIO_CLEAR_BUFFER 1 0
    358. Jan 10 17:48:09 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 7725632 1 1
    359. Jan 10 17:48:10 vusolo2 user.warn kernel: [VID]: VIDEO_GET_SIZE src w: 720 h:576 display w:720 h:576
    360. Jan 10 17:48:10 vusolo2 user.warn kernel: [VID]: VIDEO_GET_SIZE aspect: 1 3
    361. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    362. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    363. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    364. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    365. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    366. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    367. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    368. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    369. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    370. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    371. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    372. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    373. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    374. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    375. Jan 10 17:49:30 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    376. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    377. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    378. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    379. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    380. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    381. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    382. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    383. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    384. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    385. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    386. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    387. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    388. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    389. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    390. Jan 10 17:49:31 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    391. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    392. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    393. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    394. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    395. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    396. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    397. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    398. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    399. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    400. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    401. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    402. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    403. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    404. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    405. Jan 10 17:51:39 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    406. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    407. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    408. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    409. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    410. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    411. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    412. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    413. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    414. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    415. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    416. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    417. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    418. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    419. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    420. Jan 10 17:51:40 vusolo2 user.notice kernel: nfs: server 192.168.1.7 not responding, timed out
    421. Jan 10 17:51:59 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 1 1
    422. Jan 10 17:51:59 vusolo2 user.warn kernel: [AUD]: AUDIO_STOP 7725632
    423. Jan 10 17:51:59 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7725632 0 aph=0x0
    424. Jan 10 17:51:59 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE aph=0 0 0
    425. Jan 10 17:51:59 vusolo2 user.warn kernel: FE tune
    426. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0
    427. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 0
    428. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AC3 downmix 1 state : 0
    429. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: HDMI Max Audio PCM Channels=8
    430. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AUDIO_PAUSE 7725632
    431. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AUDIO_PLAY 7725632 decoder start : 0
    432. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    433. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 1
    434. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_FREEZE 7725632 0
    435. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 7725632 5 2
    436. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0 1
    437. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0 1
    438. Jan 10 17:52:00 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 7725632 1
    439. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7725632 1 aph=0xcff15a80
    440. Jan 10 17:52:00 vusolo2 user.warn kernel: [AUD]: Mute : 0
    441. Jan 10 17:52:28 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    442. Jan 10 17:52:28 vusolo2 user.warn kernel: Hotplug - status.connected 0:1:0
    443. Jan 10 17:52:28 vusolo2 user.warn kernel: bcm7356: hotplug_callback():
    444. Jan 10 17:52:28 vusolo2 user.warn kernel: Hotplug - Disconnecting HDMI from display
    Alles anzeigen
  • Ist das NAS immer verfügbar ?

    Wie sehen die Mounts in /etc/auto.network aus ?
    Die mal deaktivieren und die Freigaben an der Box mit dem Networkbrowser - als HDD-Ersatz aktivieren .

    Kannst auch mit Cifs testen .
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    KAPIERVORGANG beendet.

    Zubehör : Philips 46PFL-9705 / 37PFL-9604, Samsung HT-E6759W, Samsung SPF 107H-105P-87H, Qnap TS-253A, Harmony 650, Fritzbox 7490, Cisco WAP4410N, Netgear M4100-D12G, TPLink HS100/HS110/LB110
  • So kommt das Ganze in auto.network an:

    Quellcode

    1. #***** Edit by "AutoFS Assistent" *****
    2. Filme -fstype=nfs,rw,soft,tcp,nolock,rsize=32768,wsize=32768 192.168.1.7:/volume1/video/Filme
    3. Serien -fstype=nfs,rw,soft,tcp,nolock,rsize=32768,wsize=32768 192.168.1.7:/volume1/video/Serien
    4. Timeshift -fstype=nfs,rw,soft,tcp,nolock,rsize=32768,wsize=32768 192.168.1.7:/volume1/video/Timeshift
    5. Backup -fstype=nfs,rw,soft,tcp,nolock,rsize=32768,wsize=32768 192.168.1.7:/volume1/video/Backup
    Werde ich mal einbinden. Hatte aber vorher viele Probleme und diese Konfig hat jetzt über Jahre funktioniert.

    Und ja, das NAS ist grundsätzlich immer an, lediglich die Platten gehen aus.

    Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von hgdo () aus folgendem Grund: unnötiges Komplettzitat entfernt

  • ok, das ist etwas komplexer, aber so gewollt.

    Ich trenne das Netz in verschiedene VLAN's auf, um Bereiche voneinander zu trennen, z.B. Gast-WLAN, Voice, interne Clients etc. Alle Geräte hängen an einem Cisco Switch, der die VLAN's zuweist. Das Routing zwischen den VLAN's übernimmt dann ein Router von Draytek.

    Alle zentralen Geräte wie Drucker, NAS, etc. befinden sich im VLAN 1 - 192.168.1.x
    Alle internen Clients wie VU+, PC, Ipad, etc. befinden sich im VLAN 10 - 192.168.10.x

    Das Routing zwischen beiden VLAN'S ist hier gewährleistet und funktioniert einwandfrei.

    Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von hgdo () aus folgendem Grund: unnötiges Komplettzitat entfernt

  • ok - das war zunächst mal das Auffällige ;-).

    Dann solltest Du letztlich nur prüfen, ob Dein Mount auch tatsächlich funktioniert.

    Ich würde das am einfachsten so machen:
    ein ls auf /media/net/autofs/Filme

    und anschließend ein schlichtes
    mount

    Und: nochmals die Aufnahmepfade kontrollieren
    [i][b]Kein Backup - kein Mitleid[/b][/i]
  • Ich verstehe zwar noch nicht ganz, was du damit erreichen möchtest, aber beides funktioniert, soweit ich das beurteilen kann.

    Der ls liefert mir den Verzeichnis-Inhalt auf der Freigabe und der mount:

    Spoiler anzeigen
    rootfs on / type rootfs (rw)
    ubi0:rootfs on / type ubifs (rw,sync,relatime)
    devtmpfs on /dev type devtmpfs (rw,relatime,size=286340k,nr_inodes=71585,mode=755)
    proc on /proc type proc (rw,relatime)
    sysfs on /sys type sysfs (rw,relatime)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
    tmpfs on /var/volatile type tmpfs (rw,relatime)
    devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
    nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
    /etc/auto.hotplug on /autofs type autofs (rw,relatime,fd=5,pgrp=1263,timeout=5,minproto=5,maxproto=5,indirect)
    /etc/auto.network on /media/net/autofs type autofs (rw,relatime,fd=11,pgrp=1263,timeout=5,minproto=5,maxproto=5,indirect)
    192.168.1.7:/volume1/video/Filme on /media/net/autofs/Filme type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.7)


    Das ist nun wiederum lustig. Ich habe kurz gewartet und den ls dann noch mal probiert. Dann erhalte ich dieses Ergebnis:

    ls: can't open '/media/net/autofs/Filme': No such file or directory

    Gleich danach nochmal und es wird wieder der Inhalt des Pfads angezeigt.

    Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von hgdo () aus folgendem Grund: unnötiges Komplettzitat entfernt