MobileRead Forums - View Single Post

jorlando · 01-10-2011, 11:45 AM

louisvd,

if fsck tells that you have a corrupt file system, you have a corrupt filesystem, even if that filesystem appears to be ok under certain circunstances (different computers and/or operating systems)

Maybe windows is more forginving with FAT32 errors than linux (by the way, don't you get an allert message in Windows when you connect the jetbook asking for a filesystem check in the USB drive?)

For now the easier solution is to reformat the card and test it again.

Take care when transfering files to dismount the drive before removing the card I already damged files due late writes.

By the way, it is considered better/faster to use card readers to transfer files to the SD card of your JB, since the JB is a USB 1.1 device. It takes forever to transfer large data amounts to USB 1.1 devices. I really don't have the patience...

01-10-2011, 11:45 AM	#13
jorlando Member Posts: 24 Karma: 50 Join Date: Oct 2010 Location: Brazil Device: jetbook lite (RIP), Sony PRS-350	louisvd, if fsck tells that you have a corrupt file system, you have a corrupt filesystem, even if that filesystem appears to be ok under certain circunstances (different computers and/or operating systems) Maybe windows is more forginving with FAT32 errors than linux (by the way, don't you get an allert message in Windows when you connect the jetbook asking for a filesystem check in the USB drive?) For now the easier solution is to reformat the card and test it again. Take care when transfering files to dismount the drive before removing the card I already damged files due late writes. By the way, it is considered better/faster to use card readers to transfer files to the SD card of your JB, since the JB is a USB 1.1 device. It takes forever to transfer large data amounts to USB 1.1 devices. I really don't have the patience...