Seite 2 von 4 ErsteErste 1234 LetzteLetzte
Ergebnis 11 bis 20 von 37
  1. #11
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Habe schon eine sehr teuere Steckerleiste, die kostet über 40 Euro !

  2. Thanks Thomas4711 bedankten sich
    •   Alt Advertising

       

  3. #12
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Zitat Zitat von Papi2000 Beitrag anzeigen
    Interne oder externe Platte?
    Steckst du die Platten im Betrieb aus?
    Externe Platte 2,5" ohne eigenes Netzteil?
    Code:
    ...
    StopIteration
    HOTPLUG connection!
    hotplug: ACTION=remove
    complete ACTION=remove
    HOTPLUG connection!
    hotplug: ACTION=remove
    complete ACTION=remove
    HOTPLUG connection lost!
    hotplug: {'ACTION': 'remove', 'PHYSDEVPATH': '/block//device', 'DEVPATH': '/dev/sdl1'}
    main infobar is not execing... so we ignore hotplug event!
    [@] onPartitionChange remove Partition(mountpoint=/media/hdd/,description=TOSHIBA MQ01ABB2,device=sdl1)
    [@] DVD removed
    HOTPLUG connection lost!
    hotplug: {'ACTION': 'remove', 'PHYSDEVPATH': '/block//device', 'DEVPATH': '/dev/sdl'}
    HOTPLUG connection!
    hotplug: ACTION=add
    complete ACTION=add
    HOTPLUG connection lost!
    hotplug: {'ACTION': 'add', 'PHYSDEVPATH': '/block/sdm/device', 'DEVPATH': '/dev/sdm'}
    new Harddisk sdm -> /dev/sdm -> /dev/sdm
    ...
    Die Meldungen riechen irgendwie stark nach unzureichender Stromversorgung über USB...
    Ich habe das Gerät neu gestartet, Meldung kommt das er keine Daten auf diesem Medium findet. Auf List ist keine Platte mehr zu finden. Jedoch über LAN habe ich zugriff auf der Platte.
    Geändert von Optimuss-WTaler (19.04.2015 um 15:57 Uhr)

  4. #13
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     

    Zusätzliche Daten

    System OE: OE-Alliance 2.3
    Distro: openatv
    Firmware-Version: 4.2.1
    Driver date: 20141112
    Kernelversion: 3.9.7
    GUI-Version: 2014-11-19

  5. #14
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Zitat Zitat von Papi2000 Beitrag anzeigen
    Interne oder externe Platte?
    Steckst du die Platten im Betrieb aus?
    Externe Platte 2,5" ohne eigenes Netzteil?
    Also sie intern mit Strom eingebaut, ich habe sie vom Händler direkt mit verbaut gekauft ! Es ist eine 2,5 Zoll Festplatte

  6. #15
    Avatar von Thomas4711
    Registriert seit
    07.04.2013
    Ort
    OpenATV - Wien
    Beiträge
    153
    Thanks (gegeben)
    3636
    Thanks (bekommen)
    3542
    Total Downloaded
    51,16 MB
    Total Downloaded
    51,16 MB
    ReceiverDanke
    Es bringt nichts alle 15 MInuten neue Infos zu posten.

  7. #16
    Avatar von apovis2105
    Registriert seit
    06.04.2013
    Ort
    BaWü
    Beiträge
    2.759
    Thanks (gegeben)
    1171
    Thanks (bekommen)
    686
    Total Downloaded
    688,86 MB
    Total Downloaded
    688,86 MB
    ReceiverDanke
    Box 1:
    VU+ Duo 4K SE
     
     
    Box 2:
    Octagon SF8008
     
     
    Box 3:
    LG OLED 65CX9LA
     
     
    Box 4:
    Panasonic DMP BDT-384
     
     
    Box 5:
    Yamaha RX-V483 + Teufel Ultima MK II
     
     
    Zitat Zitat von Optimuss-WTaler Beitrag anzeigen
    Also sie intern mit Strom eingebaut, ich habe sie vom Händler direkt mit verbaut gekauft ! Es ist eine 2,5 Zoll Festplatte
    Vielleicht mal ein akt. Images mit akt. Treibern installieren. Wenn ich mir das Datum von deinem Image und den Treibern
    so anschaue, auch nicht gerade das aktuellste.


    BOX 1: VU+ DUO 4K SE - OPENATV 7.5 DEVEL
    BOX 2: Octagon SF8008
    - OPENATV 7.5 DEVEL
    TV:
    LG OLED 65CX9LA
    AV Receiver: Yamaha RX-V483
    Blu-ray Player:
    Panasonic DMP BDT-384
    Boxen: Teufel Ultima 40 Mk2



  8. #17
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Hilft es den auch das Festplattenproblem zu lösen! Áuf der Festplatte sinid alle Daten auch weg.. Kein Film kein Backup drauf.. Habe das Ding an die Lan anschluss auch ein Hackerangriff möglich ?Kein Film kein Backup drauf.Welchen Treiber soll ich Installieren? Bezeichnung finde ich diese in den Lan Verbindung vom Receiver her ?
    Geändert von Optimuss-WTaler (19.04.2015 um 17:35 Uhr)

  9. #18
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Code:
    Apr 19 15:45:02 optimussos3plus user.info kernel: sd 0:0:0:0: [sdy]  
    Apr 19 15:45:02 optimussos3plus user.warn kernel: ASC=0x0 ASCQ=0x0
    Apr 19 15:45:02 optimussos3plus user.info kernel: sd 0:0:0:0: [sdy] CDB: 
    Apr 19 15:45:02 optimussos3plus user.warn kernel: cdb[0]=0x2a: 2a 00 00 00 08 00 00 00 08 00
    Apr 19 15:45:02 optimussos3plus user.err kernel: end_request: I/O error, dev sdy, sector 2048
    Apr 19 15:45:02 optimussos3plus user.err kernel: Buffer I/O error on device sdy1, logical block 0
    Apr 19 15:45:02 optimussos3plus user.warn kernel: lost page write due to I/O error on sdy1
    Apr 19 15:45:02 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:02 optimussos3plus user.info kernel: EXT4-fs (sdy1): recovery complete
    Apr 19 15:45:02 optimussos3plus user.info kernel: EXT4-fs (sdy1): mounted filesystem with ordered data mode. Opts: (null)
    Apr 19 15:45:02 optimussos3plus user.info kernel: sd 0:0:0:0: killing request
    Apr 19 15:45:02 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:02 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:02 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:02 optimussos3plus user.err kernel: sd 0:0:0:0: [sdy] Asking for cache data failed
    Apr 19 15:45:02 optimussos3plus user.err kernel: sd 0:0:0:0: [sdy] Assuming drive cache: write through
    Apr 19 15:45:02 optimussos3plus user.err kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41c0000 action 0xe frozen
    Apr 19 15:45:02 optimussos3plus user.err kernel: ata1: irq_stat 0x00000040, connection status changed
    Apr 19 15:45:02 optimussos3plus user.err kernel: ata1: SError: { CommWake 10B8B Dispar DevExch }
    Apr 19 15:45:02 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:02 optimussos3plus user.info kernel: ata1.00: detaching (SCSI 0:0:0:0)
    Apr 19 15:45:02 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdy] Stopping disk
    Apr 19 15:45:03 optimussos3plus user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 19 15:45:03 optimussos3plus user.info kernel: ata1.00: ATA-8: TOSHIBA MQ01ABB200, AY000U, max UDMA/100
    Apr 19 15:45:03 optimussos3plus user.info kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    Apr 19 15:45:03 optimussos3plus user.info kernel: ata1.00: configured for UDMA/100
    Apr 19 15:45:03 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.warn kernel: EXT4-fs warning (device sdy1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdy1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:03 optimussos3plus user.notice kernel: scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MQ01ABB2 AY00 PQ: 0 ANSI: 5
    Apr 19 15:45:03 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
    Apr 19 15:45:03 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] 4096-byte physical blocks
    Apr 19 15:45:03 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] Write Protect is off
    Apr 19 15:45:03 optimussos3plus user.debug kernel: sd 0:0:0:0: [sdz] Mode Sense: 00 3a 00 00
    Apr 19 15:45:03 optimussos3plus user.notice kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
    Apr 19 15:45:03 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Apr 19 15:45:05 optimussos3plus user.info kernel:  sdz: sdz1
    Apr 19 15:45:05 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] Attached SCSI disk
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0xc00000 action 0x6 frozen
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1.00: irq_stat 0x08000000, interface fatal error
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1: SError: { Handshk LinkSeq }
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1.00: cmd 61/08:00:00:08:00/00:00:00:00:00/40 tag 0 ncq 4096 out
    Apr 19 15:45:05 optimussos3plus user.err kernel:          res 40/00:00:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
    Apr 19 15:45:05 optimussos3plus user.err kernel: ata1.00: status: { DRDY }
    Apr 19 15:45:05 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1.00: configured for UDMA/100
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0xc00000 action 0x6 frozen
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: irq_stat 0x08000000, interface fatal error
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1: SError: { Handshk LinkSeq }
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: cmd 61/08:00:00:08:00/00:00:00:00:00/40 tag 0 ncq 4096 out
    Apr 19 15:45:06 optimussos3plus user.err kernel:          res 40/00:00:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: status: { DRDY }
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1.00: configured for UDMA/100
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0xc00000 action 0x6 frozen
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: irq_stat 0x08000000, interface fatal error
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1: SError: { Handshk LinkSeq }
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: cmd 61/08:00:00:08:00/00:00:00:00:00/40 tag 0 ncq 4096 out
    Apr 19 15:45:06 optimussos3plus user.err kernel:          res 40/00:00:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
    Apr 19 15:45:06 optimussos3plus user.err kernel: ata1.00: status: { DRDY }
    Apr 19 15:45:06 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:07 optimussos3plus user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 19 15:45:07 optimussos3plus user.info kernel: ata1.00: configured for UDMA/100
    Apr 19 15:45:07 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:07 optimussos3plus user.warn kernel: ata1: limiting SATA link speed to 1.5 Gbps
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0xc00000 action 0x6 frozen
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1.00: irq_stat 0x08000000, interface fatal error
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1: SError: { Handshk LinkSeq }
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1.00: cmd 61/08:00:00:08:00/00:00:00:00:00/40 tag 0 ncq 4096 out
    Apr 19 15:45:07 optimussos3plus user.err kernel:          res 40/00:00:00:08:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
    Apr 19 15:45:07 optimussos3plus user.err kernel: ata1.00: status: { DRDY }
    Apr 19 15:45:07 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:09 optimussos3plus user.info kernel: ata1: SATA link down (SStatus 1 SControl 310)
    Apr 19 15:45:09 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:11 optimussos3plus user.info kernel: ata1: SATA link down (SStatus 1 SControl 310)
    Apr 19 15:45:11 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:14 optimussos3plus user.info kernel: ata1: SATA link down (SStatus 1 SControl 310)
    Apr 19 15:45:14 optimussos3plus user.warn kernel: ata1.00: disabled
    Apr 19 15:45:14 optimussos3plus user.info kernel: sd 0:0:0:0: [sdz]  
    Apr 19 15:45:14 optimussos3plus user.warn kernel: Result: hostbyte=0x00 driverbyte=0x08
    Apr 19 15:45:14 optimussos3plus user.info kernel: sd 0:0:0:0: [sdz]  
    Apr 19 15:45:14 optimussos3plus user.warn kernel: Sense Key : 0xb [current] [descriptor]
    Apr 19 15:45:14 optimussos3plus user.warn kernel: Descriptor sense data with sense descriptors (in hex):
    Apr 19 15:45:14 optimussos3plus user.info kernel:         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
    Apr 19 15:45:14 optimussos3plus user.info kernel:         00 00 08 00 
    Apr 19 15:45:14 optimussos3plus user.info kernel: sd 0:0:0:0: [sdz]  
    Apr 19 15:45:14 optimussos3plus user.warn kernel: ASC=0x0 ASCQ=0x0
    Apr 19 15:45:14 optimussos3plus user.info kernel: sd 0:0:0:0: [sdz] CDB: 
    Apr 19 15:45:14 optimussos3plus user.warn kernel: cdb[0]=0x2a: 2a 00 00 00 08 00 00 00 08 00
    Apr 19 15:45:14 optimussos3plus user.err kernel: end_request: I/O error, dev sdz, sector 2048
    Apr 19 15:45:14 optimussos3plus user.err kernel: Buffer I/O error on device sdz1, logical block 0
    Apr 19 15:45:14 optimussos3plus user.warn kernel: lost page write due to I/O error on sdz1
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:14 optimussos3plus user.info kernel: EXT4-fs (sdz1): recovery complete
    Apr 19 15:45:14 optimussos3plus user.info kernel: EXT4-fs (sdz1): mounted filesystem with ordered data mode. Opts: (null)
    Apr 19 15:45:14 optimussos3plus user.info kernel: sd 0:0:0:0: killing request
    Apr 19 15:45:14 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:14 optimussos3plus user.err kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x41c0000 action 0xe frozen
    Apr 19 15:45:14 optimussos3plus user.err kernel: ata1: irq_stat 0x00000040, connection status changed
    Apr 19 15:45:14 optimussos3plus user.err kernel: ata1: SError: { CommWake 10B8B Dispar DevExch }
    Apr 19 15:45:14 optimussos3plus user.info kernel: ata1: hard resetting link
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: rejecting I/O to offline device
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: [sdz] Asking for cache data failed
    Apr 19 15:45:14 optimussos3plus user.err kernel: sd 0:0:0:0: [sdz] Assuming drive cache: write through
    Apr 19 15:45:14 optimussos3plus user.info kernel: ata1.00: detaching (SCSI 0:0:0:0)
    Apr 19 15:45:14 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdz] Stopping disk
    Apr 19 15:45:15 optimussos3plus user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 19 15:45:15 optimussos3plus user.info kernel: ata1.00: ATA-8: TOSHIBA MQ01ABB200, AY000U, max UDMA/100
    Apr 19 15:45:15 optimussos3plus user.info kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    Apr 19 15:45:15 optimussos3plus user.info kernel: ata1.00: configured for UDMA/100
    Apr 19 15:45:15 optimussos3plus user.info kernel: ata1: EH complete
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 15:45:15 optimussos3plus user.notice kernel: scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MQ01ABB2 AY00 PQ: 0 ANSI: 5
    Apr 19 15:45:15 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdaa] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
    Apr 19 15:45:15 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdaa] 4096-byte physical blocks
    Apr 19 15:45:15 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdaa] Write Protect is off
    Apr 19 15:45:15 optimussos3plus user.debug kernel: sd 0:0:0:0: [sdaa] Mode Sense: 00 3a 00 00
    Apr 19 15:45:15 optimussos3plus user.notice kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
    Apr 19 15:45:15 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdaa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Apr 19 15:45:16 optimussos3plus user.info kernel:  sdaa: sdaa1
    Apr 19 15:45:16 optimussos3plus user.notice kernel: sd 0:0:0:0: [sdaa] Attached SCSI disk
    Apr 19 16:24:43 optimussos3plus daemon.crit automount[733]: key "folder.jpg" not found in map source(s).
    Apr 19 16:24:43 optimussos3plus daemon.crit automount[733]: key "folder.gif" not found in map source(s).
    Apr 19 16:24:43 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm smbd: reading directory lblock 0
    Apr 19 16:24:43 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm smbd: reading directory lblock 0
    Apr 19 16:24:44 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm smbd: reading directory lblock 0
    Apr 19 16:24:44 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm smbd: reading directory lblock 0
    Apr 19 16:24:44 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 16:24:48 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 16:24:57 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 16:30:03 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 16:34:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:34:31 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 16:34:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:34:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:34:53 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:34:53 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:34:53 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:34:53 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:34:53 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:00 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:00 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:35:00 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:48 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:48 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:35:48 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:35:48 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:35:48 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:58 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:58 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:35:58 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:35:58 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:35:58 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:59 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:35:59 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:35:59 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:23 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:23 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:57:23 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:57:23 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:57:23 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:34 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:57:34 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:57:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:57:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:41 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:41 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:57:41 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:57:41 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:57:41 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:55 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:57:55 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:57:55 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:57:56 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:57:56 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:58:13 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:58:13 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:58:13 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:58:13 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:58:13 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:58:16 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 16:58:16 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 16:58:16 optimussos3plus user.warn kernel: path status 0
    Apr 19 16:58:16 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 16:58:16 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:31 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:12:31 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:12:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:12:31 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:33 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:33 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:12:33 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:12:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:12:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:12:50 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:12:50 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:12:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:12:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:13:18 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:13:18 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:13:18 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:13:18 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:13:18 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:39 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:39 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:19:39 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:19:40 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:19:40 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:42 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:42 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:19:42 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:19:42 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:19:42 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:19:50 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:19:50 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:19:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:19:50 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:07 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:07 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:20:07 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:20:07 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:20:07 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:08 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:34 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:34 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:20:34 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:20:35 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:20:35 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:44 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:44 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:20:44 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:20:44 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:20:44 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:45 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:45 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:20:45 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:51 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:20:51 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:20:51 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:20:52 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:20:52 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:21:04 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 17:21:04 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 17:21:04 optimussos3plus user.warn kernel: path status 0
    Apr 19 17:21:04 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 17:21:04 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 18:13:43 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:35:07 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 18:35:07 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 18:35:07 optimussos3plus user.crit kernel: EXT4-fs error (device sdz1): ext4_find_entry:1300: inode #2: comm enigma2: reading directory lblock 0
    Apr 19 18:37:07 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 18:37:07 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 18:37:07 optimussos3plus user.warn kernel: path status 0
    Apr 19 18:37:08 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 18:37:08 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 18:37:09 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 18:37:09 optimussos3plus user.warn kernel: no vt opened...
    Apr 19 18:37:09 optimussos3plus user.warn kernel: path status 0
    Apr 19 18:37:09 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings -9000  ======
    Apr 19 18:37:09 optimussos3plus user.warn kernel: NEXUS_DolbyVolume258_SetSettings 0  ======
    Apr 19 18:42:02 optimussos3plus daemon.crit automount[733]: key "*" not found in map source(s).
    Apr 19 18:42:02 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:04 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:42 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:46 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:46 optimussos3plus daemon.crit automount[733]: key "*" not found in map source(s).
    Apr 19 18:42:46 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:46 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:47 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:47 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:47 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:47 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:48 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)
    Apr 19 18:42:48 optimussos3plus user.warn kernel: EXT4-fs warning (device sdz1): __ext4_read_dirblock:907: error reading directory block (ino 2, block 0)

    Neue Logs...
    Geändert von Thomas4711 (19.04.2015 um 18:59 Uhr) Grund: In CODE gesetzt

  10. #19
    Avatar von Thomas4711
    Registriert seit
    07.04.2013
    Ort
    OpenATV - Wien
    Beiträge
    153
    Thanks (gegeben)
    3636
    Thanks (bekommen)
    3542
    Total Downloaded
    51,16 MB
    Total Downloaded
    51,16 MB
    ReceiverDanke
    Apr 19 15:45:02 optimussos3plus user.info kernel: EXT4-fs (sdy1): recovery complete
    Apr 19 15:45:02 optimussos3plus user.info kernel: EXT4-fs (sdy1): mounted filesystem with ordered data mode. Opts: (null)
    sdy? was denn da

  11. #20
    Mitglied
    Registriert seit
    28.11.2014
    Ort
    NRW Bergisches Land
    Beiträge
    65
    Thanks (gegeben)
    6
    Thanks (bekommen)
    3
    Themenstarter
    Total Downloaded
    7,37 MB
    Total Downloaded
    7,37 MB
    ReceiverDanke
    Box 1:
    Humax
     
     
    Box 2:
    Schwaiger
     
     
    Box 3:
    Optimuss OS3+
     
     
    Keine Ahnung, ich habe nix gemacht, das Problem ist gestern aufgetaucht! Kann sein das die Platte sich zerschrieben hat ? Sollte ich diese neu Initialsiseren ??
    Ich habe mein System am VDSL Moden dran ? Also gehackt wurde ich nicht oder? Könnte der Kontroller der Platte hinüber sein


Seite 2 von 4 ErsteErste 1234 LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 14:24 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2024 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,56%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com