TP-Link WR1043ND router - PROHARDVER! Hozzászólások

Legfrissebb anyagok

PROHARDVER! témák

Mobilarena témák

IT café témák

GAMEPOD.hu témák

LOGOUT.hu témák

Hirdetés

Összemoshatja a Google és a Magic Leap a valódi és a digitális világokat

it Együttműködésbe kezdett a Google és a Magic Leap nevű AR-startup.
Megjelenési dátumot kapott a Tomb Raider animációs sorozat

gp A tervek szerint október elején debütál a teljes első évad Netflixen.
Féltucat régi Samsung kapott új One UI-t, köztük az A52s

ma A 6.1 olcsó, drága, ütésálló és közönségkedvenc készülékekre is megérkezett.

Téma összefoglaló

Utoljára frissítve: 2023-12-13 05:20

PROHARDVER!

TP-Link WR1043ND - N450 router

Új hozzászólás Aktív témák

#3729 tomi7711 aktív tag

Új Válasz 2010-09-15 22:24:03 #3729
Új hozzászólás
Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra
Privát üzenet küldése

tomi7711

aktív tag

Sziasztok! Több alkalommal előfordult már, hogy nem tudok bejelentkezni a routerre. Net van, de ssh-n keresztül invalid passworddel elhajt. Megnéztem a logokat és ezt találtam benne. Előtte minden rendben volt...
Sep 15 21:43:57 kernel: usb 1-1.4: reset high speed USB device using ar71xx-ehci and address 4 Sep 15 21:43:59 kernel: sd 1:0:0:0: [sdb] Media Changed Sep 15 21:43:59 kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Sep 15 21:43:59 kernel: sd 1:0:0:0: [sdb] Sense Key : 0x6 [current] Sep 15 21:43:59 kernel: Info fld=0x0 Sep 15 21:43:59 kernel: sd 1:0:0:0: [sdb] ASC=0x28 ASCQ=0x0 Sep 15 21:43:59 kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 29 80 ae 00 00 a0 00 Sep 15 21:43:59 kernel: end_request: I/O error, dev sdb, sector 2719918 Sep 15 21:43:59 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 21:45:13 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 21:45:13 kernel: ------------[ cut here ]------------ Sep 15 21:45:13 kernel: WARNING: at fs/buffer.c:1159 0x800fd4d8() Sep 15 21:45:13 kernel: Modules linked in: fuse nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipt_R Sep 15 21:45:13 kernel: Call Trace:[<800683a4>] 0x800683a4 Sep 15 21:45:13 kernel: [<800683a4>] 0x800683a4 Sep 15 21:45:13 kernel: [<8007cb80>] 0x8007cb80 Sep 15 21:45:13 kernel: [<800fd4d8>] 0x800fd4d8 Sep 15 21:45:13 kernel: [<800fe0d0>] 0x800fe0d0 Sep 15 21:45:13 kernel: [<800fd4d8>] 0x800fd4d8 Sep 15 21:45:13 kernel: [<81b4d7a0>] 0x81b4d7a0 Sep 15 21:45:13 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0 Sep 15 21:45:13 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #81968 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #82332 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #81968 offset 0 Sep 15 21:45:14 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=2, block=115 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1) in ext3_reserve_inode_write: IO failure Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #65537 offset 0 Sep 15 22:02:56 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #40961 offset 0 Sep 15 22:03:01 dropbear[28411]: Child connection from 192.168.1.144:52917 Sep 15 22:03:02 kernel: journal_bmap: journal block not found at offset 3849 on sdb1 Sep 15 22:03:02 kernel: Aborting journal on device sdb1. Sep 15 22:03:06 kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #8193 offset 0 Sep 15 22:03:06 dropbear[28411]: login attempt for nonexistent user from 192.168.1.144:52917 Sep 15 22:03:09 dropbear[28411]: login attempt for nonexistent user from 192.168.1.144:52917 Sep 15 22:06:42 dropbear[28411]: exit before auth: Exited normally Sep 15 22:06:59 dropbear[28422]: Child connection from 192.168.1.144:52944 Sep 15 22:07:03 dropbear[28422]: login attempt for nonexistent user from 192.168.1.144:52944 Sep 15 22:07:07 dropbear[28422]: login attempt for nonexistent user from 192.168.1.144:52944 Sep 15 22:07:10 dropbear[28422]: login attempt for nonexistent user from 192.168.1.144:52944 Sep 15 22:07:12 dropbear[28422]: login attempt for nonexistent user from 192.168.1.144:52944 Sep 15 22:07:13 dropbear[28422]: login attempt for nonexistent user from 192.168.1.144:52944 Sep 15 22:07:14 dropbear[28422]: exit before auth: Max auth tries reached - user 'is invalid' from 192.168.1.144:52944 Sep 15 22:07:57 dropbear[28423]: Child connection from 188.157.228.20:48586 Sep 15 22:08:09 dropbear[28423]: login attempt for nonexistent user from 188.157.228.20:48586 Sep 15 22:10:12 dropbear[28424]: Child connection from 192.168.1.144:52977 Sep 15 22:10:16 dropbear[28424]: login attempt for nonexistent user from 192.168.1.144:52977 Sep 15 22:10:28 dropbear[28424]: login attempt for nonexistent user from 192.168.1.144:52977 Sep 15 22:10:34 dropbear[28424]: login attempt for nonexistent user from 192.168.1.144:52977 Sep 15 22:10:39 dropbear[28424]: login attempt for nonexistent user from 192.168.1.144:52977 Sep 15 22:10:42 dropbear[28424]: login attempt for nonexistent user from 192.168.1.144:52977 Sep 15 22:10:43 dropbear[28424]: exit before auth: Max auth tries reached - user 'is invalid' from 192.168.1.144:52977