spl147 Posted February 3, 2015 Share Posted February 3, 2015 Feb 3 09:26:40 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:26:45 SERVER kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 131105) Feb 3 09:26:45 SERVER kernel: FAT-fs (sda1): bread failed in fat_clusters_flush Feb 3 09:26:46 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:26:46 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:26:51 SERVER kernel: FAT-fs (sda1): bread failed in fat_clusters_flush Feb 3 09:26:51 SERVER kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 131105) Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:26:56 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:01 SERVER kernel: fat__get_entry: 2 callbacks suppressed Feb 3 09:27:01 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:01 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:01 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:01 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:06 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:27:12 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:27:12 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:39 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:49 SERVER kernel: fat__get_entry: 4 callbacks suppressed Feb 3 09:28:49 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:49 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:54 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:54 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:28:54 SERVER kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 3 09:28:54 SERVER kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:09 SERVER kernel: FAT-fs (sda1): FAT read failed (blocknr 1277) Feb 3 09:36:14 SERVER kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 11716999) Feb 3 09:36:14 SERVER kernel: FAT-fs (sda1): bread failed in fat_clusters_flush Quote Link to comment
Squid Posted February 3, 2015 Share Posted February 3, 2015 Usually directory bread errors are because the system thinks the drive was pulled out then reinserted. I used to get them intermittently on my machine, until I disabled USB3 support and made sure the stick was in a USB2 port. btw the unRaid is going to want to do a parity check when you reboot since it can't save the info to the flash drive But it could also be that the stick itself is kaput. Quote Link to comment
spl147 Posted February 3, 2015 Author Share Posted February 3, 2015 Usually directory bread errors are because the system thinks the drive was pulled out then reinserted. I used to get them intermittently on my machine, until I disabled USB3 support and made sure the stick was in a USB2 port. btw the unRaid is going to want to do a parity check when you reboot since it can't save the info to the flash drive But it could also be that the stick itself is kaput. anyway to test the flash drive? Quote Link to comment
Squid Posted February 3, 2015 Share Posted February 3, 2015 Beyond seeing if it works by putting it into a machine, I don't think so.... Although, I suppose you could throw it into you windows machine, run chkdsk on it (to look for corruption), but everytime I've seen the error its always been port related. Whether USB3 was enabled in BIOS, etc. try a different port, ideally a USB2 one Quote Link to comment
spl147 Posted February 3, 2015 Author Share Posted February 3, 2015 Beyond seeing if it works by putting it into a machine, I don't think so.... Although, I suppose you could throw it into you windows machine, run chkdsk on it (to look for corruption), but everytime I've seen the error its always been port related. Whether USB3 was enabled in BIOS, etc. try a different port, ideally a USB2 one it has been fine for almost a year, then today all of a sudden....it's a supermicro onboard A slot Quote Link to comment
Frank1940 Posted February 3, 2015 Share Posted February 3, 2015 As suggested earlier, run chkdsk on a Windows machine and report the results back here. (There is a simple program on Apple computers but I do not know what Apple calls it. ) Quote Link to comment
spl147 Posted February 3, 2015 Author Share Posted February 3, 2015 As suggested earlier, run chkdsk on a Windows machine and report the results back here. (There is a simple program on Apple computers but I do not know what Apple calls it. ) i was hoping for a solution without pulling the server out of the rack and opening it up! Quote Link to comment
growlith Posted November 20, 2016 Share Posted November 20, 2016 Just wanted to comment here that I was having the same issue, the flash drive would continuously disconnect and re-connect. I solved this by moving to one of he usb2 connections as suggested. Sadly the ports behind the lock on my server are all 3.0 so not the drive is accessible, but it is a micro drive and the back of the server is hard to get to so I will live. Thanks for the help! Quote Link to comment
Recommended Posts
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.