| 1 |
On 06/15/2017 10:11 AM, J. Roeleveld wrote: |
| 2 |
> On June 15, 2017 5:26:36 PM GMT+02:00, thelma@×××××××××××.com wrote: |
| 3 |
>> I'm trying to repair USB disk (64GB) originally formatted with ext4 |
| 4 |
>> |
| 5 |
>> I read the USB stick on Windows via some kind of windows ext4 driver |
| 6 |
>> now I can not open it on Linux box. |
| 7 |
>> |
| 8 |
>> e2fsck -a /dev/sdb1 |
| 9 |
>> 64gb: recovering journal |
| 10 |
>> |
| 11 |
>> (just stays there and does nothing). |
| 12 |
>> when I unplug it I get: |
| 13 |
>> |
| 14 |
>> e2fsck: No such file or directory while trying to re-open 64gb |
| 15 |
>> |
| 16 |
>> 64gb: ********** WARNING: Filesystem still has errors ********** |
| 17 |
>> |
| 18 |
>> (dmesg): |
| 19 |
>> usb-storage 8-1:1.0: USB Mass Storage device detected |
| 20 |
>> [1175553.773966] scsi host8: usb-storage 8-1:1.0 |
| 21 |
>> [1175554.790598] scsi 8:0:0:0: Direct-Access Verbatim STORE N GO |
| 22 |
>> 5.00 PQ: 0 ANSI: 6 |
| 23 |
>> [1175554.791142] sd 8:0:0:0: Attached scsi generic sg2 type 0 |
| 24 |
>> [1175558.511554] sd 8:0:0:0: [sdb] 120933888 512-byte logical blocks: |
| 25 |
>> (61.9 GB/57.7 GiB) |
| 26 |
>> [1175558.511720] sd 8:0:0:0: [sdb] Write Protect is off |
| 27 |
>> [1175558.511722] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 |
| 28 |
>> [1175558.511890] sd 8:0:0:0: [sdb] No Caching mode page found |
| 29 |
>> [1175558.511891] sd 8:0:0:0: [sdb] Assuming drive cache: write through |
| 30 |
>> [1175558.514906] sdb: sdb1 |
| 31 |
>> [1175558.515986] sd 8:0:0:0: [sdb] Attached SCSI removable disk |
| 32 |
>> [1176008.633223] usb 8-1: USB disconnect, device number 46 |
| 33 |
>> [1176008.641063] sd 8:0:0:0: [sdb] tag#0 FAILED Result: |
| 34 |
>> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK |
| 35 |
>> [1176008.641069] sd 8:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 38 08 |
| 36 |
>> 00 00 00 08 00 |
| 37 |
>> [1176008.641073] blk_update_request: I/O error, dev sdb, sector |
| 38 |
>> 20449280 |
| 39 |
>> [1176008.641076] Buffer I/O error on dev sdb1, logical block 2555904, |
| 40 |
>> lost async page write |
| 41 |
>> [1176008.641113] sd 8:0:0:0: [sdb] tag#0 FAILED Result: |
| 42 |
>> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK |
| 43 |
>> [1176008.641116] sd 8:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 3c 08 |
| 44 |
>> 00 00 00 08 00 |
| 45 |
>> [1176008.641118] blk_update_request: I/O error, dev sdb, sector |
| 46 |
>> 20711424 |
| 47 |
>> [1176008.641120] Buffer I/O error on dev sdb1, logical block 2588672, |
| 48 |
>> lost async page write |
| 49 |
>> [1176008.651400] VFS: Dirty inode writeback failed for block device |
| 50 |
>> sdb1 (err=-5). |
| 51 |
> |
| 52 |
> Try increasing verbosity of the e2fsck.... |
| 53 |
> |
| 54 |
> And why would you trust some random ms windows ext4 driver in RW mode? |
| 55 |
> |
| 56 |
> -- |
| 57 |
> Joost |
| 58 |
|
| 59 |
Increasing verbosity doesn't help much :-/ |
| 60 |
e2fsck -v /dev/sdb1 |
| 61 |
e2fsck 1.43.3 (04-Sep-2016) |
| 62 |
64gb: recovering journal |
| 63 |
|
| 64 |
e2fsck: No such device or address while trying to re-open 64gb |
| 65 |
|
| 66 |
64gb: ********** WARNING: Filesystem still has errors ********** |
| 67 |
|
| 68 |
I had copied bunch of picture from my box into largest USB disk I could |
| 69 |
find on my desk, little I realized that that disk had been format to ext4. |
| 70 |
When I went to presented it (I had only Windows box available) and had |
| 71 |
to use some kind of "ext" driver from http://www.ext2fsd.com/ to read |
| 72 |
the disk on Windows. |
| 73 |
|
| 74 |
-- |
| 75 |
Thelma |
Archives