On 06/15/2017 06:21:44 PM, the...@sys-concept.com wrote:
> Try increasing verbosity of the e2fsck....
>\u200b
> And why would you trust some random ms windows ext4 driver in RW
mode?
>\u200b
> --
> Joost
Increasing verbosity doesn't help much :-/
e2fsck -v /dev/sdb1
e2fsck 1.43.3 (04-Sep-2016)
64gb: recovering journal
e2fsck: No such device or address while trying to re-open 64gb
64gb: ********** WARNING: Filesystem still has errors **********
I had copied bunch of picture from my box into largest USB disk I
could
find on my desk, little I realized that that disk had been format to
ext4.
When I went to presented it (I had only Windows box available) and had
to use some kind of "ext" driver from http://www.ext2fsd.com/ to read
the disk on Windows.
--
Thelma
This looks like a hardware failure. You could try to use
sys-fs/ddrescue
to recover all / most files.
If this doesn't work as expected, you can try to use app-admin/testdisk.
Then you can format the drive and copy the files back.
P.S. Have you used the "save eject feature" of Windows before
disconnection the drive from your PC?
(Cheap) USB sticks are by no means a safe data storage.
If you don't change any data while the drive is attached to Windows try
using a stick with a write protection toggle.
If you have to write to the drive from Windows it would be better to
format it as NTFS which can be read/written on Linux.
Helmut
