Hello,

 

unRAID starts fine for me but once everything have started, the following error usually occurs and I cannot seem to fix it.

 

Here's the link to my diagnostics file:

https://drive.google.com/open?id=1Qaf70W0qLVgXQw26n93abkfBw07t0YB3

 

Please help, thank you.

4 hours ago, bearbear23 said:

unRAID starts fine for me but once everything have started, the following error usually occurs and I cannot seem to fix it.

What are you doing to remedy this situation?  IF you are setting up the Notifications (   Settings   >>>   Notification Settings  ), are you setting up a notification method-- Either SMTP or an Agent)?  Are you remembering to click on the "Apply' button at the bottom of each page when you have finished your setup? 

6 hours ago, bearbear23 said:

Here's the link to my diagnostics file

In future, please attach your diagnostics directly to your post instead of linking to another site. Thanks

 

You are having issues with your flash drive. Put it in your PC and let it checkdisk. Try another port, preferably USB2.

 

On 6/15/2019 at 9:32 AM, trurl said:

In future, please attach your diagnostics directly to your post instead of linking to another site. Thanks

 

You are having issues with your flash drive. Put it in your PC and let it checkdisk. Try another port, preferably USB2.

 

Hi, I replaced the USB flash drive twice and also used all available ports on the motherboard but the problem is persisting. Is there any other solutions or is this a motherboard issue?

New diagnostics

16 hours ago, trurl said:

New diagnostics

Please take a look, thank you.

tower-diagnostics-20190624-0249.zip

The syslog is showing read errors on the flash drive when Unraid tries to read your configuration information from it.  

Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29550) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29551) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29552) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29553) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29554) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29555) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29556) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29557) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29558) failed
Jun 23 21:47:13 Tower kernel: FAT-fs (sda1): Directory bread(block 29559) failed
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/T_Media.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/anime.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/animemovies.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/movies.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/podcasts.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg
Jun 23 21:47:13 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/tvshows.cfg

It us obviously initially fine as one can see all the plugins being loaded and the licence file being loaded.    You then start getting errors like the ones I have shown.   Since Unraid cannot read (or write) any config files things then start going wrong.    The diagnostics you posted also contain none of the usual configuration files which is consistent with being unable to read them from the flash drive.

 

Have you tried putting the drive into a Windows system and done a full scan (where windows tries to read every block)?   I normally do this myself in Windows from a command line using a command like:

chkdsk /r x:

where x: is the drive letter corresponding to the flash drive.    You can also do it from the Windows GUI by asking for the properties of the drive and then selecting the `check option from the tools tab.

 

If you have done everything to check the drive on a Windows system then I am not sure what to suggest if you say you have tried a different one with the same symptoms.    Wiping it and trying to recreate it seems to be the only way forward.  Do you have a backup of its contents (and in particular the licence file)?