Raspberry Pi - PROHARDVER! Hozzászólások

Legfrissebb anyagok

PROHARDVER! témák

Mobilarena témák

IT café témák

GAMEPOD témák

LOGOUT témák

Téma összefoglaló

Utoljára frissítve: 2024-09-03 13:31

PROHARDVER!

Amit érdemes tudni a Raspberry Pi-kről:
A legelső változat 2012-ben jelent meg. Pici, olcsó és nagyon alacsony fogyasztású, hobby-célú kártyagép. Felépítése ARM alapú, nem PC-architektúra, hanem kb. egy régi mobilhoz hasonló. Nagyon sok mindenre használható! A Linux-nak és a magas eladási mennyiségnek köszönhetően jelentős fejlesztőtáborral rendelkezik.

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

#44177 Shummo senior tag

Új Válasz 2022-05-14 16:49:40 #44177
Ú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

Shummo

senior tag

Sajnos mégse jó. Elindulni elindul szépen felcsatolódik, de ha a HDDről akarok másolni, akkor egyből behal.
Dmesg az alábbit írja, ebből valaki ki tud hámozni valamit??
sdb a 2. drive (külső tápja is van a háznak)

91.132758] usb 2-1.1: cmd cmplt err -71 [ 91.133768] usb 2-1.1: cmd cmplt err -71 [ 91.148707] usb 2-1.1: cmd cmplt err -71 [ 91.164134] usb 2-1.1: cmd cmplt err -71 [ 91.183128] usb 2-1.1: cmd cmplt err -71 [ 91.198858] usb 2-1.1: cmd cmplt err -71 [ 91.216662] usb 2-1.1: cmd cmplt err -71 [ 93.176447] usb 2-1.1: USB disconnect, device number 4 [ 93.185436] sd 1:0:0:0: [sdb] tag#25 uas_zap_pending 0 uas-tag 1 inflight: CMD [ 93.185449] sd 1:0:0:0: [sdb] tag#25 CDB: opcode=0x28 28 00 0c 6b e1 40 00 04 00 00 [ 93.185460] sd 1:0:0:0: [sdb] tag#26 uas_zap_pending 0 uas-tag 2 inflight: CMD [ 93.185466] sd 1:0:0:0: [sdb] tag#26 CDB: opcode=0x28 28 00 0c 6b e5 40 00 04 00 00 [ 93.185475] sd 1:0:0:0: [sdb] tag#27 uas_zap_pending 0 uas-tag 3 inflight: CMD [ 93.185476] sd 1:0:0:0: [sdb] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185481] sd 1:0:0:0: [sdb] tag#27 CDB: opcode=0x28 28 00 0c 6b e9 40 00 04 00 00 [ 93.185490] sd 1:0:0:0: [sdb] tag#24 uas_zap_pending 0 uas-tag 4 inflight: CMD [ 93.185491] sd 1:0:0:0: [sdb] tag#25 CDB: opcode=0x28 28 00 0c 6b e1 40 00 04 00 00 [ 93.185494] sd 1:0:0:0: [sdb] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185498] sd 1:0:0:0: [sdb] tag#24 CDB: opcode=0x28 28 00 0b 0b 40 00 00 04 00 00 [ 93.185498] blk_update_request: I/O error, dev sdb, sector 208396608 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185500] sd 1:0:0:0: [sdb] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185505] sd 1:0:0:0: [sdb] tag#28 uas_zap_pending 0 uas-tag 5 inflight: CMD [ 93.185505] sd 1:0:0:0: [sdb] tag#26 CDB: opcode=0x28 28 00 0c 6b e5 40 00 04 00 00 [ 93.185510] sd 1:0:0:0: [sdb] tag#28 CDB: opcode=0x28 28 00 0b 0b 48 00 00 04 00 00 [ 93.185512] sd 1:0:0:0: [sdb] tag#27 CDB: opcode=0x28 28 00 0c 6b e9 40 00 04 00 00 [ 93.185513] blk_update_request: I/O error, dev sdb, sector 208397632 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185518] sd 1:0:0:0: [sdb] tag#0 uas_zap_pending 0 uas-tag 6 inflight: CMD [ 93.185520] blk_update_request: I/O error, dev sdb, sector 208398656 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185524] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 0b 0b 50 00 00 04 00 00 [ 93.185531] sd 1:0:0:0: [sdb] tag#1 uas_zap_pending 0 uas-tag 7 inflight: CMD [ 93.185537] sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x28 28 00 0b 0b 58 00 00 04 00 00 [ 93.185544] sd 1:0:0:0: [sdb] tag#2 uas_zap_pending 0 uas-tag 8 inflight: CMD [ 93.185549] sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 0b 0b 60 00 00 04 00 00 [ 93.185577] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185579] sd 1:0:0:0: [sdb] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185584] sd 1:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=2s [ 93.185587] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 0b 0b 50 00 00 04 00 00 [ 93.185588] sd 1:0:0:0: [sdb] tag#28 CDB: opcode=0x28 28 00 0b 0b 48 00 00 04 00 00 [ 93.185595] sd 1:0:0:0: [sdb] tag#24 CDB: opcode=0x28 28 00 0b 0b 40 00 00 04 00 00 [ 93.185594] blk_update_request: I/O error, dev sdb, sector 185288704 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185595] blk_update_request: I/O error, dev sdb, sector 185290752 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185604] blk_update_request: I/O error, dev sdb, sector 185286656 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185648] sd 1:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=1s [ 93.185658] sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x28 28 00 0b 0b 58 00 00 04 00 00 [ 93.185665] blk_update_request: I/O error, dev sdb, sector 185292800 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.185705] sd 1:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=1s [ 93.185704] blk_update_request: I/O error, dev sdb, sector 185290752 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 93.185715] sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 0b 0b 60 00 00 04 00 00 [ 93.185721] blk_update_request: I/O error, dev sdb, sector 185286656 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 93.185723] blk_update_request: I/O error, dev sdb, sector 185294848 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 [ 93.187921] Aborting journal on device sdb3-8. [ 93.187969] Buffer I/O error on dev sdb3, logical block 121667584, lost sync page write [ 93.187988] JBD2: Error -5 detected when updating journal superblock for sdb3-8. [ 93.402674] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 94.032695] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK [ 96.676905] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097417: block 8388656: comm smbd: unable to read itable block [ 96.691517] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097417: block 8388656: comm smbd: unable to read itable block [ 96.713396] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097417: block 8388656: comm smbd: unable to read itable block [ 96.734350] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097417: block 8388656: comm smbd: unable to read itable block [ 96.756573] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097153: block 8388640: comm smbd: unable to read itable block [ 96.782828] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097153: block 8388640: comm smbd: unable to read itable block [ 96.809998] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097593: block 8388667: comm smbd: unable to read itable block [ 96.830396] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097593: block 8388667: comm smbd: unable to read itable block [ 96.849925] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097593: block 8388667: comm smbd: unable to read itable block [ 96.869336] EXT4-fs error (device sdb3): ext4_get_inode_loc:4382: inode #2097593: block 8388667: comm smbd: unable to read itable block [ 96.886061] EXT4-fs warning (device sdb3): htree_dirblock_to_tree:1028: inode #2097153: lblock 0: comm smbd: error -5 reading directory block [ 96.887258] EXT4-fs warning (device sdb3): htree_dirblock_to_tree:1028: inode #2097593: lblock 0: comm smbd: error -5 reading directory block [ 96.888670] EXT4-fs warning (device sdb3): htree_dirblock_to_tree:1028: inode #2097593: lblock 0: comm smbd: error -5 reading directory block [ 96.889611] EXT4-fs warning (device sdb3): htree_dirblock_to_tree:1028: inode #2097153: lblock 0: comm smbd: error -5 reading directory block [ 96.911973] EXT4-fs warning (device sdb3): htree_dirblock_to_tree:1028: inode #2097153: lblock 0: comm