USB Flash Read Errors - Unmounted


daze

Recommended Posts

Hi folks,

 

Every now and then, I see my 2GB SanDisk Flash drive going bananas. For example, I logged on to the UI today and noticed it had errors importing configuration files from /boot/config. SSHing in showed bunch of read errors. So I remounted the drive, and everything came back just fine.

 

[288173.271885] FAT-fs (sda1): Directory bread(block 7861) failed
[288173.271886] FAT-fs (sda1): Directory bread(block 7862) failed
[288173.271886] FAT-fs (sda1): Directory bread(block 7863) failed
[288174.118417] FAT-fs (sda1): Directory bread(block 7856) failed
[288174.118419] FAT-fs (sda1): Directory bread(block 7857) failed
[288175.216670] FAT-fs (sda1): FAT read failed (blocknr 2681)
[288178.469426] fat__get_entry: 54 callbacks suppressed
[288178.469427] FAT-fs (sda1): Directory bread(block 7856) failed
[288178.469429] FAT-fs (sda1): Directory bread(block 7857) failed
[288178.469430] FAT-fs (sda1): Directory bread(block 7858) failed
[288178.469431] FAT-fs (sda1): Directory bread(block 7859) failed
[288178.469432] FAT-fs (sda1): Directory bread(block 7860) failed
[288178.469433] FAT-fs (sda1): Directory bread(block 7861) failed
[288178.469434] FAT-fs (sda1): Directory bread(block 7862) failed
[288178.469435] FAT-fs (sda1): Directory bread(block 7863) failed
[288178.469440] FAT-fs (sda1): Directory bread(block 7856) failed
[288178.469441] FAT-fs (sda1): Directory bread(block 7857) failed
[288178.469449] FAT-fs (sda1): FAT read failed (blocknr 2681)
[288181.691228] FAT-fs (sda1): FAT read failed (blocknr 2681)
[288183.820515] fat__get_entry: 54 callbacks suppressed

I have a bunch of 64GB USB drives that I ought to transfer config to and swap it off. Before I do, can anyhow give the diag logs a once over to see if there isn't something more wrong?

 

Diags - see attached.

 

Thanks!

 

Daze

titan-diagnostics-20200411-1717.zip

Edited by daze
Removed external link
Link to comment
7 hours ago, johnnie.black said:

Flash drive is dropping out, you appear to be using a USB 3.0 port, if yes try a USB 2.0 port instead, 3.0 is not recommended.

Thanks for the taking a look. Yes it was a very old USB 2.0 drive from 2008. I have switched the license to a newer drive on a USB 3.0 port, let's see if that works fine. If it doesn't I'll move the drive to a USB 2.0 port.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.