On June 15, 2017 5:26:36 PM GMT+02:00, the...@sys-concept.com wrote: >I'm trying to repair USB disk (64GB) originally formatted with ext4 > >I read the USB stick on Windows via some kind of windows ext4 driver >now I can not open it on Linux box. > >e2fsck -a /dev/sdb1 >64gb: recovering journal > >(just stays there and does nothing). >when I unplug it I get: > >e2fsck: No such file or directory while trying to re-open 64gb > >64gb: ********** WARNING: Filesystem still has errors ********** > >(dmesg): >usb-storage 8-1:1.0: USB Mass Storage device detected >[1175553.773966] scsi host8: usb-storage 8-1:1.0 >[1175554.790598] scsi 8:0:0:0: Direct-Access Verbatim STORE N GO > 5.00 PQ: 0 ANSI: 6 >[1175554.791142] sd 8:0:0:0: Attached scsi generic sg2 type 0 >[1175558.511554] sd 8:0:0:0: [sdb] 120933888 512-byte logical blocks: >(61.9 GB/57.7 GiB) >[1175558.511720] sd 8:0:0:0: [sdb] Write Protect is off >[1175558.511722] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 >[1175558.511890] sd 8:0:0:0: [sdb] No Caching mode page found >[1175558.511891] sd 8:0:0:0: [sdb] Assuming drive cache: write through >[1175558.514906] sdb: sdb1 >[1175558.515986] sd 8:0:0:0: [sdb] Attached SCSI removable disk >[1176008.633223] usb 8-1: USB disconnect, device number 46 >[1176008.641063] sd 8:0:0:0: [sdb] tag#0 FAILED Result: >hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK >[1176008.641069] sd 8:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 38 08 >00 00 00 08 00 >[1176008.641073] blk_update_request: I/O error, dev sdb, sector >20449280 >[1176008.641076] Buffer I/O error on dev sdb1, logical block 2555904, >lost async page write >[1176008.641113] sd 8:0:0:0: [sdb] tag#0 FAILED Result: >hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK >[1176008.641116] sd 8:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 3c 08 >00 00 00 08 00 >[1176008.641118] blk_update_request: I/O error, dev sdb, sector >20711424 >[1176008.641120] Buffer I/O error on dev sdb1, logical block 2588672, >lost async page write >[1176008.651400] VFS: Dirty inode writeback failed for block device >sdb1 (err=-5).
Try increasing verbosity of the e2fsck.... And why would you trust some random ms windows ext4 driver in RW mode? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
