Today I simply want to change my shares configuration, and after some try and fail, I eventually see that I cannot change this at all, all parameters stay rock solid.

So I look at the syslog and see 6 unusuals errors (in red) with three different kind of.

 

1. fat_get_cluster

Aug  6 20:15:58 Tower kernel: FAT-fs (sdf1): error, fat_get_cluster: invalid cluster chain (i_pos 9503) (Errors)

Aug  6 20:15:58 Tower kernel: FAT-fs (sdf1): Filesystem has been set read-only (Drive related)

Aug  6 20:15:58 Tower kernel: FAT-fs (sdf1): error, fat_get_cluster: invalid cluster chain (i_pos 9503) (Errors)

Aug  6 20:15:58 Tower last message repeated 8 times

.../...

Sep 14 22:48:30 Tower kernel: fat_get_cluster: 33 callbacks suppressed

Sep 14 22:48:30 Tower kernel: FAT-fs (sdf1): error, fat_get_cluster: invalid cluster chain (i_pos 9503) (Errors)

Sep 14 22:48:30 Tower last message repeated 9 times

 

2. secrets.tdb

Aug  6 20:15:59 Tower emhttp: shcmd (5): /etc/rc.d/rc.samba start |$stuff$ logger (Other emhttp)

Aug  6 20:15:59 Tower logger: mv: reading `/boot/config/secrets.tdb': Input/output error (Errors)

Aug  6 20:15:59 Tower logger: Starting Samba:  /usr/sbin/nmbd -D

Aug  6 20:15:59 Tower kernel: FAT-fs (sdf1): Filesystem has been set read-only (Drive related)

 

3. super.dat

Aug  6 20:16:00 Tower kernel: write_file: error 30 opening /boot/config/super.dat (Errors)

Aug  6 20:16:00 Tower kernel: md: could not write superblock from /boot/config/super.dat (unRAID engine)

.../...

Aug  6 20:16:08 Tower kernel: md: recovery thread checking parity... (unRAID engine)

Aug  6 20:16:08 Tower kernel: write_file: error 30 opening /boot/config/super.dat (Errors)

Aug  6 20:16:08 Tower kernel: md: could not write superblock from /boot/config/super.dat (unRAID engine)

.../...

Aug  7 13:47:09 Tower kernel: md: sync done. time=63061sec (unRAID engine)

Aug  7 13:47:09 Tower kernel: write_file: error 30 opening /boot/config/super.dat (Errors)

Aug  7 13:47:09 Tower kernel: md: could not write superblock from /boot/config/super.dat (unRAID engine)

Aug  7 13:47:09 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine)

.../...

 

I'm pretty sure all those errors are bounded (no configuration change, etc..) and coming from the fat_get_cluster problem, of the FAT-fs (sdf1), and I think it's from the flash.

I've already save the key, but what should I do to be safe?

Power down unraid, take the key and format it as new, put back everything (w or w/o super.dat and secrets.tdb ?)

Thanks for some help

 

 

Normally this sort of problem can be fixed by plugging the USB stick into a PC/Mac and running a disk check to fix any file system corruption.