This is the second time that this has happened in 4 days. It's happened across two different USB sticks (brand new ones).

I assume I need to replace the USB stick yet again?

    Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed
    Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed
    Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed
    Apr 10 14:27:01 Tower root: 
    Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35
    Apr 10 14:27:01 Tower root: 
    Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39
    Apr 10 14:27:07 Tower kernel: fat__get_entry: 150 callbacks suppressed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed
    Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed
    Apr 10 14:27:16 Tower kernel: fat__get_entry: 54 callbacks suppressed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed
    Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed
    Apr 10 14:27:25 Tower kernel: fat__get_entry: 54 callbacks suppressed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed
    Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed

 

Could be bad flash drive, maybe a port problem, probably just corrupted. Put it in your PC and let it checkdisk.

 

Are you shutting your server down from the webUI? If not then that is probably the cause.

I didn't shut the system down at all. Nor was I working on it. I just opened the UI and noticed the errors.

 

The first time this happened, I had the USB stick plugged in the front USB port.

The second time (this time), with a brand new, completely different USB stick, I have it plugged in the back USB port.

 

Can I just unplug the USB stick to run checkdisk without my unraid server going down?

 

 

8 minutes ago, runraid said:

Can I just unplug the USB stick to run checkdisk without my unraid server going down?

Yes...

 

But, whenever "bread" errors happen it means that unRaid lost track of the flash drive.  Net result is that when you plug it back in, if you try and change a setting on the UI that requires a write to the flash, it will fail and be like nothing happened.  More noticeably, when you reboot, you will have a parity check happen because the flag that gets set  on the flash to indicate a clean shutdown can't get written.

 

My personal opinion is that this is going to wind up being a port thing rather than a stick issue.  If its plugged into a USB 3, plug it into a USB 2 (or vice versa)

12 minutes ago, runraid said:

Can I just unplug the USB stick to run checkdisk without my unraid server going down?

That would be similar to yanking the power as far as the flash drive is concerned.

 

Are you saying you have never shutdown or otherwise powered off your server?

@trurl I shut it down a day or two ago, but things were fine until today. I did not do anything else on the machine.

 

@Squid I want to say that I have it plugged into a USB 3 port (during both failures). I'll move to a USB 2 port.

Just now, runraid said:

I shut it down a day or two ago, but things were fine until today. I did not do anything else on the machine.

But did you use the webUI to shutdown?

@trurl Yes I did use the UI to shut down. But the odd thing is, when it started back up, it said I did an unclean shutdown and it had to do a full parity check.

 

I might have been ssh'ed into the machine at that time which could have prevented a clean shutdown. For now on, I will stop the array, then do the shut down just to make sure I get a clean shutdown.

26 minutes ago, runraid said:

But the odd thing is, when it started back up, it said I did an unclean shutdown and it had to do a full parity check.

 

Because of this...

 

46 minutes ago, Squid said:

But, whenever "bread" errors happen it means that unRaid lost track of the flash drive.  Net result is that when you plug it back in, if you try and change a setting on the UI that requires a write to the flash, it will fail and be like nothing happened.  More noticeably, when you reboot, you will have a parity check happen because the flag that gets set  on the flash to indicate a clean shutdown can't get written.

 

@Squid when I did a shut down in the UI, at that time I was not having any USB issues. A day later (right now) I've started having the issue

Also, it's showing as a flash drive and as Unmounted. See the attached pic. 

Yes.  Once a bread error occurs, the "boot" flash does not exist anymore, and nothing you can do to bring it back short of a reboot.  IE: the flash drive dropped offline (either due to a flash problem or controller (hence why I suggest USB3<-->USB2)), and when it came back it was assigned a different drive letter.

Thanks all. I'll do a shutdown, USB swap, then parity check. I'll report back if it this happens again.

Put the USB drive into my PC and it immediately said it had errors. Running checkdisk now.  This is two USB sticks with issues in about 4 days. 

 

 

USB stick is now in a USB 2.0 port (was a 3.0). Stopped the array. Rebooted the system. Came up with "unclean shutdown detected". It's now doing a full parity check. Nothing appears to have been lost (I love unraid).

 

>  Array Started•Parity-Check 0.1 %• Dynamix webGui v2017.03.30

 

I'm going to purchase a high quality USB stick. I wish unraid didn't depend on the USB stick though

 

 

I have a Kingston DataTraveler Micro 3.1 and got this error. It was USB 3, plugged in a USB 3 port. The server has a history with memory failure, so doing a memtest now... Trying a USB 2 port later.

 

I thought Kingston was pretty high quality USB stick, so I think that's not it... Right?

On 5/27/2022 at 2:05 PM, CSmits said:

I have a Kingston DataTraveler Micro 3.1 and got this error. It was USB 3, plugged in a USB 3 port. The server has a history with memory failure, so doing a memtest now... Trying a USB 2 port later.

 

I thought Kingston was pretty high quality USB stick, so I think that's not it... Right?

Today out of nowhere, I got `fat_get_cluster: invalid start cluster` and a reboot failed. So, I guess I'll be requesting another key 😓

On 5/27/2022 at 8:05 AM, CSmits said:

Trying a USB 2 port later

USB2 ports are more reliable and USB3 speed doesn't provide any advantages for the Unraid flash drive.

@runraid / @CSmits -- Any luck with this? I'm running into the same issue with a new flash drive on a USB2 port direct to the MB.

If switching ports didn't fix, then you should replace the flash https://unraid.net/blog/top-support-and-forum-questions-answered#:~:text=Head over to Tools -> Registration,section and you are done!

Thanks! Will do, I just switched ports this morning so I'll give it another day or two to see if I have the issue again. I'll post back with what works for me.

Hi folks, just bought a basic subscription, and I've run into this error three times now while doing initial setup. 

 

I pulled the first flash drive, checked it through Windows 10 (no errors), started again with that drive, immediately downloaded a backup, errored out after about an hour.  Swapped to a PNY 16GB drive, and about an hour into the new first parity setup it errored out again. 

 

My (old af) mobo only has USB 2.0.  Anything else I can try?

 

Jan 11 13:00:01 Makalii kernel: fat__get_entry: 6 callbacks suppressed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30218) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30219) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30220) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30221) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30222) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30223) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30224) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30225) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30226) failed
Jan 11 13:00:01 Makalii kernel: FAT-fs (sda1): Directory bread(block 30227) failed
Jan 11 13:00:02 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:03 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:04 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:05 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:06 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:07 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:08 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:09 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:10 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:11 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:12 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:13 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:14 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:15 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:16 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config
Jan 11 13:00:17 Makalii  emhttpd: error: get_key_info, 537: No such file or directory (2): opendir: /boot/config

 

53 minutes ago, arzin3D said:

USB 2.0

USB2 ports recommended.

 

Have you tried another port?

Yes, I swapped it to another port late last night, and achieved parity this afternoon!  Hooray!

 

Now that I have everything set up and was starting a back up, it happened again.  I have two more ports to try, so I will swap to another one.

Got an unclean shutdown error upon restarting in a different port, even though I stopped the array then shut it down through the GUI.  See you all in 15 hours after another parity check...