-
IT café
ASUS RT-N56U és RT-N65U Wireless-N Gigabit útválasztók
Új hozzászólás Aktív témák
-
krealon
veterán
válasz kmartin994 #1253 üzenetére
A 10-est koltsd inkabb egy RT-N12 D1-re, amit repeater modba teve, nagyobb valoszinuseggel oldja meg az udvar lefedeset, mint egy darab eszkoz.
-
krealon
veterán
válasz tibcsi0407 #1944 üzenetére
"Problémám akad a Sambán megosztott meghajtóra való másolással:
Jan 21 17:28:23 smbd[875]: [2015/01/21 17:28:23, 0] lib/util_tdb.c:tdb_log(664)
Jan 21 17:28:23 smbd[875]: tdb(/var/locks/locking.tdb): expand_file write of 1024 bytes failed (No space left on device)
[...]
Akkor történik, ha sok kicsi fájlt másolok rá. Természetesen szabad hely van. 270 giga"Nem ertetted meg a hibauzenetet.
A /var/locks/ konyvtarban fogyott el a hely (ami tippem szerint RAM-disk).Ugy nez ki, hogy egy kicsit tulterhelted a router-t. Ne varj el tole PC-s teljesitmenyt!
-
krealon
veterán
válasz buster1989 #1957 üzenetére
A Router gondok topikban is kaptal par megoldasi otletet.
-
krealon
veterán
"Szeretnék otthon egy hálózatot kialakítani (saját) leginkább hogy az asztali és a notebook-on lévő fájlokat elérjem a 2 géppel (kölcsönösen)
-Na most ilyen esetben elég egy sima "meghajtó megosztását" végrehajtani?"
Elvileg igen.
"-Jól gondolom hogy az efajta megosztásnál a router full sebessége a mérvadó a router mellett, nem pedig az interneté?"
Pontosan.
Az adatok a leheto legrovidebb uton mozognak a forrastol a celig."-Tehát ha van egy pl 10 mbit/sec netem, de a hálózaton keresztül az asztali pc-mről töltök át a ntebook-ra filmet, akkor az mondjuk 10 mbyte/ sec fog töltődni?"
Ha a ket eszkoz kozott a legszukebb keresztmetszet egy 100 Mbps kapcsolat, akkor igen.
A Samba a Windows "Fájl és nyomtatómegosztás", illetve a "Microsoft Networks Kliens" szolgáltatásokat, valamint sok hasznos segédprogramot tartalmazó programcsomag.
[ Szerkesztve ]
-
krealon
veterán
válasz illusion111 #2182 üzenetére
"melyik firmware-t töltsem le és honnan az RT-N56U routeremhez, mert az utóbbi időben elveszti a külső vinyómmal a kapcsolatot"
A hdd leszakadas oka altalaban az elegtelen tapfeszultseg.
Okai lehetnek:
- USB csatlakozo kontakthiba
- Eletrolit kondenzatorok kiszaradasa a router-ben vagy a router tapegysegeben.Egyik esetben sem fog a firmware frissites segiteni. Celszeru ilyenkor egy masik, kompatibilis tapegyseggel kiprobalni.
Ha korabban nem jelentkezett ez a hiba, akkor szoftveres erintettseg elmeletileg kizarhato.
Legyszives jelezz vissza, hogy az uj firmware megoldotta-e a hibat! -
krealon
veterán
válasz illusion111 #2187 üzenetére
"Az előzménye az volt, hogy kihúzta a kislányom simán a vinyót, leválasztás nélkül. Előtte stabil volt."
Szomoru.
Lehetseges meg fajlrendszer serules is az unmount nelkuli levalasztastol.
Live Linux-al (pl SystemRescueCD) probald leellenorizni.Ha bebootoltal, az
fdisk -lparancs kilistazza a felismert eszkozoket es a rajtuk levo particiokat
Ha a karakteres modban nem fert ki az informacio a kepre, akkor a [Shift] + [Page-Up] kombinacioval tudsz visszagorgetni.Ha megvan milyen device nevet kapott ( /dev/sdx ), akkor az ext2/ext3/ext4 particiokat (linux tipusu az fdisk listaban) az
e2fsck -f /dev/sdxyparanccsal tudod ellenorizni.
-
krealon
veterán
válasz krealon #2189 üzenetére
A naplo (Systemlog) alapjan az EXT4 fajlrendszer serult, ezert nem tudja rendesen hasznalni a router a rakotott HDD-t.
Kezdetben /dev/sda-kent hasznalta, majd a az ujracsatlakozas utan mar /dev/sdb lett.
Fajlrendszer ellenorzes / javitas mindenkepp szukseges az elozo hozzaszolas alapjan, valamint a rend helyreallitasa vegett a router ujrainditasa is javasolt.A reszlet a log-bol, hogyha masnak is hasonlo gondja lenne:
Jan 1 00:00:08 kernel: scsi 0:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
Jan 1 00:00:08 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] Mode Sense: 27 00 00 00
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jan 1 00:00:08 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan 1 00:00:08 usb_modeswitch: no rule for device 04e8:60c6
[...]
Jan 1 00:00:09 kernel: sda: sda1
Jan 1 00:00:09 kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jan 1 00:00:09 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan 1 00:00:09 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
[...]
Jan 1 00:00:12 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:12 opt-mount.sh: started [/dev/sda1 /media/AiDisk_a1]
[...]
May 27 18:44:22 kernel: usb 1-1: USB disconnect, device number 2
May 27 18:44:23 kernel: usb 1-1: new high-speed USB device number 3 using rt3xxx-ehci
May 27 18:44:23 kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=60c6
May 27 18:44:23 kernel: usb 1-1: Product: Samsung M2 Portable 3
May 27 18:44:23 kernel: usb 1-1: Manufacturer: JMicron
[...]
May 27 18:44:23 kernel: scsi1 : usb-storage 1-1:1.0
May 27 18:44:29 kernel: scsi 1:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
May 27 18:44:29 kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] No Caching mode page found
May 27 18:44:29 usb_modeswitch: no rule for device 04e8:60c6
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] No Caching mode page found
May 27 18:44:29 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
May 27 18:44:30 kernel: sdb: sdb1
May 27 18:44:30 kernel: sd 1:0:0:0: [sdb] No Caching mode page found
May 27 18:44:30 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
May 27 18:44:30 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 27 18:44:31 kernel: EXT4-fs (sdb1): warning: checktime reached, running e2fsck is recommended
May 27 18:44:31 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 27 18:44:31 opt-mount.sh: started [/dev/sdb1 /media/AiDisk_b1]
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:36 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:36 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:38 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:39 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:39 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:39 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:39 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:39 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:39 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:41 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:41 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:41 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:41 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:41 kernel: EXT4-fs error (device sda1) in ext4_orphan_add:2039: IO failure
May 27 18:44:41 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3567: inode #93847559: block 93847554: comm transmission-da: unable to read itable block
May 27 18:44:41 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4385: IO failure
May 27 18:44:41 kernel: Buffer I/O error on device sda1, logical block 153001644
May 27 18:44:41 kernel: lost page write due to I/O error on sda1
May 27 18:44:41 kernel: JBD2: Detected IO errors while flushing file data on sda1-8
May 27 18:44:41 kernel: Aborting journal on device sda1-8.
May 27 18:44:41 kernel: Buffer I/O error on device sda1, logical block 2111
May 27 18:44:41 kernel: lost page write due to I/O error on sda1
May 27 18:44:41 kernel: JBD2: Error -5 detected when updating journal superblock for sda1-8.
May 27 18:44:43 kernel: EXT4-fs error (device sda1): ext4_journal_start_sb:328: Detected aborted journal
May 27 18:44:43 kernel: EXT4-fs (sda1): Remounting filesystem read-only
May 27 18:49:18 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #94144523: comm transmission-da: reading directory lblock 0
May 27 18:49:18 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847553: comm transmission-da: reading directory lblock 0
May 27 18:49:18 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #94144523: comm transmission-da: reading directory lblock 0
May 27 18:49:18 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847553: comm transmission-da: reading directory lblock 0
May 27 18:51:31 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 19:00:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 19:01:09 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 19:01:22 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 19:11:13 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847553: comm transmission-da: reading directory lblock 0
May 27 19:30:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 19:37:21 kernel: usb 1-1: USB disconnect, device number 3
May 27 19:37:21 kernel: Buffer I/O error on device sdb1, logical block 2111
May 27 19:37:21 kernel: lost page write due to I/O error on sdb1
May 27 19:37:21 kernel: JBD2: Error -5 detected when updating journal superblock for sdb1-8.
May 27 19:37:21 kernel: usb 1-1: new high-speed USB device number 4 using rt3xxx-ehci
May 27 19:37:21 kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=60c6
May 27 19:37:21 kernel: usb 1-1: Product: Samsung M2 Portable 3
May 27 19:37:21 kernel: usb 1-1: Manufacturer: JMicron
[...]
May 27 19:37:21 kernel: scsi2 : usb-storage 1-1:1.0
May 27 19:37:28 kernel: scsi 2:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
May 27 19:37:28 kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] Write Protect is off
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] Mode Sense: 27 00 00 00
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 27 19:37:28 usb_modeswitch: no rule for device 04e8:60c6
May 27 19:37:28 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 27 19:37:30 kernel: sdb: sdb1
May 27 19:37:30 kernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 27 19:37:30 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 27 19:37:30 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
May 27 19:37:31 kernel: EXT4-fs (sdb1): warning: checktime reached, running e2fsck is recommended
May 27 19:37:31 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 27 19:37:31 opt-mount.sh: started [/dev/sdb1 /media/AiDisk_b1]
May 27 19:53:14 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847595: comm transmission-da: reading directory lblock 1
May 27 19:53:14 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847595: comm transmission-da: reading directory lblock 0
May 27 20:29:16 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 27 21:37:18 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #106791027: comm transmission-da: reading directory lblock 0
May 27 21:37:19 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #106791027: comm transmission-da: reading directory lblock 0
May 27 21:50:48 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847595: comm transmission-da: reading directory lblock 1
May 27 21:50:48 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847595: comm transmission-da: reading directory lblock 0
May 27 23:00:50 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 00:14:03 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 00:36:34 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 00:39:14 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 00:42:04 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 01:40:15 kernel: EXT4-fs error (device sda1): ext4_find_entry:932: inode #93847618: comm transmission-da: reading directory lblock 0
May 28 02:14:46 kernel: usb 1-1: USB disconnect, device number 4
May 28 02:14:46 kernel: Buffer I/O error on device sdb1, logical block 2111
May 28 02:14:46 kernel: lost page write due to I/O error on sdb1
May 28 02:14:46 kernel: JBD2: Error -5 detected when updating journal superblock for sdb1-8.
May 28 02:14:46 kernel: usb 1-1: new high-speed USB device number 5 using rt3xxx-ehci
May 28 02:14:47 kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=60c6
May 28 02:14:47 kernel: usb 1-1: Product: Samsung M2 Portable 3
May 28 02:14:47 kernel: usb 1-1: Manufacturer: JMicron
[...]
May 28 02:14:47 kernel: scsi3 : usb-storage 1-1:1.0
May 28 02:14:53 kernel: scsi 3:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
May 28 02:14:53 kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] Write Protect is off
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] Mode Sense: 27 00 00 00
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] No Caching mode page found
May 28 02:14:53 usb_modeswitch: no rule for device 04e8:60c6
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] No Caching mode page found
May 28 02:14:53 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:14:54 kernel: sdb: sdb1
May 28 02:14:54 kernel: sd 3:0:0:0: [sdb] No Caching mode page found
May 28 02:14:54 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:14:54 kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
May 28 02:14:54 kernel: EXT4-fs (sdb1): warning: checktime reached, running e2fsck is recommended
May 28 02:14:54 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 28 02:14:54 opt-mount.sh: started [/dev/sdb1 /media/AiDisk_b1]
May 28 02:40:55 kernel: usb 1-1: USB disconnect, device number 5
May 28 02:40:55 kernel: Buffer I/O error on device sdb1, logical block 2111
May 28 02:40:55 kernel: lost page write due to I/O error on sdb1
May 28 02:40:55 kernel: JBD2: Error -5 detected when updating journal superblock for sdb1-8.
May 28 02:40:55 kernel: usb 1-1: new high-speed USB device number 6 using rt3xxx-ehci
May 28 02:40:56 kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=60c6
May 28 02:40:56 kernel: usb 1-1: Product: Samsung M2 Portable 3
May 28 02:40:56 kernel: usb 1-1: Manufacturer: JMicron
[...]
May 28 02:40:56 kernel: scsi4 : usb-storage 1-1:1.0
May 28 02:41:02 kernel: scsi 4:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
May 28 02:41:02 kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] Write Protect is off
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] No Caching mode page found
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] No Caching mode page found
May 28 02:41:02 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:41:02 usb_modeswitch: no rule for device 04e8:60c6
May 28 02:41:05 kernel: sdb: sdb1
May 28 02:41:05 kernel: sd 4:0:0:0: [sdb] No Caching mode page found
May 28 02:41:05 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
May 28 02:41:05 kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
May 28 02:41:05 kernel: EXT4-fs (sdb1): warning: checktime reached, running e2fsck is recommended
May 28 02:41:05 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 28 02:41:06 opt-mount.sh: started [/dev/sdb1 /media/AiDisk_b1]
May 28 02:41:44 kernel: usb 1-1: USB disconnect, device number 6
May 28 02:41:44 kernel: Buffer I/O error on device sdb1, logical block 2111
May 28 02:41:44 kernel: lost page write due to I/O error on sdb1
May 28 02:41:44 kernel: JBD2: Error -5 detected when updating journal superblock for sdb1-8.
May 28 02:41:44 kernel: usb 1-1: new high-speed USB device number 7 using rt3xxx-ehci
May 28 02:41:45 kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=60c6
May 28 02:41:45 kernel: usb 1-1: Product: Samsung M2 Portable 3
May 28 02:41:45 kernel: usb 1-1: Manufacturer: JMicron
[...]
May 28 02:41:45 kernel: scsi5 : usb-storage 1-1:1.0
May 28 02:41:51 kernel: scsi 5:0:0:0: Direct-Access Samsung M2 Portable 3 3 PQ: 0 ANSI: 6
May 28 02:41:51 kernel: sd 5:0:0:0: [sdb] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB) -
krealon
veterán
válasz bopeti98 #2259 üzenetére
"Gondolom az jó hozzá."
Ne gondold, hanem nezd meg hogy milyen csatlakozoju, feszultsegu, es polaritasu tapegysegre van szukseg.
A notebook-okhoz tipikusan 19-21 V-os tolto szokott jarni, a routerek pedig 5-12 V-osat hasznalnak altalaban.
Ha a 12 V-os routerre rakotsz egy 19V-os tapegyseget, akkor tonkremegy a router, radasul a garancia is elvesz, a nem rendeltetesszeru hasznalat miatt. -
krealon
veterán
válasz enginev3.0 #2861 üzenetére
Ha a routered WAN IPv4 cime nem egyezik meg azzal, amit a whatismyipaddress.com kiir, akkor az internetszolgaltatod cimforditason (NAP) atesett (privat) IP-t biztosit neked, ez esetben hiaba a port forward es a DynamikusDNS a feled erkezo keresek elakadnak a szolgaltatonal es mar a routeredet sem erik el.
Ez esetben az internetszolgaltatoval kell egyeztetni, hogy neked publikus IPv4 cimre van szukseged. -
krealon
veterán
A nyomtatoban levo AirPrint (Bonjour Printing) tamogatas nelkul, leginkabb csak szoftveres emulacioval fog mukodni a nyomtatas egy ilyen "buta" eszkozon.
https://www.cnet.com/how-to/how-to-print-wirelessly-from-your-iphone-ipad-or-ipod-touch/Letezik hardveres megoldas, de a legtobb ember szamara nem rentabilis. Radasul a kompatibilitasi listajan nincs is a felvetesben szereplo Samsung SL-M2026. (Es ennel a nyomtatonal majdnem ketszer dragabb. )
https://www.startech.com/Networking-IO/Print/usb-wireless-n-150mbps-airprint-server~PM1115UAMint lathato, halozati csatlakozo (Ethernet vagy Wifi) nelkuli nyomtatot venni manapsag, nagy ongol, mert tenyleg csak arra hasznalhato, amire kitalaltak. USB-n gepre kotni, es ugy nyomtatni.
Új hozzászólás Aktív témák
- -59% HP EliteBook x360 830 G7:i5 10310U,16GB,256GB,vil.MAGYAR bilI.,IR,13.3" Touch,100%sRGB,WWAN 4G
- Sony PS5 (1116A) + 2TB Samsung SSD bővítés a gyári 825GB mellett, két karral + venom töltőhub
- HP Laptop 15-fd051ne - ÚJ - 15,6" FullHD IPS notebook - Core i5-1335U, 8GB, 512SSD, Win11
- Brother DCP-L2532DW wifis, multifunkciós lézernyomtató
- HP Pavilion x360 14-ek Convertible - ÚJ - 14" TOUCH notebook - i5-1235U, 16GB, 512SSD, Win11
- Intel Core I5-8600
- Akció! Dell Optiplex 3080 Micro / I5-10500T / 16GB DDR4 / 256GB SSD /Windows11 Matrica BESZÁMÍTOK
- ASUS Radeon RX 5700 XT Dual EVO 8GB GDDR6
- Videoton AB 1010 autó hangszóró pár eladó a képeken látható állapotban. Mindegyik hangszóró működik,
- Ultra ritka Sound Blaster 1.5 2.0 klón Anchor Media Concept retró 8 bites ISA PC hangkártya
Állásajánlatok
Cég: Ozeki Kft.
Város: Debrecen
Cég: Alpha Laptopszerviz Kft.
Város: Pécs