November 27, 20241 yr Hey all, Unraid 6.12.13 on a AMD Ryzen 7 1800X system with 64GB RAM. For the last couple of months I have the issue where randomly (as it seems) the Unraid server shows having issues. The symptoms always seem to be the same, namely; - SAMBA is inaccessible - WebUI is inaccessible - Reverse Proxy Docker SWAG is not able to connect to other Docker Containers. - Docker Contains are still working and can be accessed via server-ip:port normally. - Looks like it can be shut down via the power button (though no double beep conformation). - I have to repair the boot USB drive in Windows before I can boot Unraid again. I already swapped the USB drive thinking it was getting old, 'twas over 2 years old, but same issues keep happening. I already tried different USB ports, before and after swapping out the USB drive. I do not have the Unraid WebUI open in a tab in Chrome, I read somewhere that it the standby tab feature causes logs to overfill currently. I eventually had a syslog server running on an old Synology NAS and attached part of it to this post. The start of the errors and then part of the errors that keep repeating a lot so I omitted those to keep the size small. It looks like the USB gets randomly disconnected due to something, and then the shit hits the pan. liliruca-diagnostics-20241127-1929.zip syslog-output-start-of-errors.txt
November 27, 20241 yr The squashfs is the liveusb feature (the booted USB). It's having issues writing. Dumb question when you swapped drives, did your full USB get copied over or just the config folder? Slight chance a bad interaction and more likely the flash drive.
November 27, 20241 yr Community Expert Solution Flash drive issues: 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32770) failed 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32769) failed 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32768) failed 2024-11-27,12:26:00,Information,Liliruca,user,emhttpd,Unregistered Flash device error (ENOFLASH3)
November 27, 20241 yr Author Just now, nimble_bitz said: The squashfs is the liveusb feature (the booted USB). It's having issues writing. Dumb question when you swapped drives, did your full USB get copied over or just the config folder? Slight chance a bad interaction and more likely the flash drive. If i remember correctly, I recovered from the USB backup I made before swapping drives, or I copied over everything. I did not only copy a config folder. I do remember that at first boot, Unraid was seeing multiple keys that I had to remove first (like the trial key and normal key).
November 27, 20241 yr Author 3 minutes ago, JorgeB said: Flash drive issues: 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32770) failed 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32769) failed 2024-11-27,12:26:00,Error,Liliruca,kern,kernel,FAT-fs (sda1): Directory bread(block 32768) failed 2024-11-27,12:26:00,Information,Liliruca,user,emhttpd,Unregistered Flash device error (ENOFLASH3) Yeah it looks like it, though I did not had logs back then with the other drive, the symptoms seemingly were/are the same as before the USB swap so I was thinking maybe else was the root cause. I'll see if I can find a drive somewhere I can use to test with (though I would have to transfer drive UUID again) if no other things appear to be apparent to cause a potential issue.
November 27, 20241 yr Remember if you swapped your USB in under 1 year you'll have to contact support for help with the key activation against the new GUID.
November 27, 20241 yr Author 4 minutes ago, nimble_bitz said: Remember if you swapped your USB in under 1 year you'll have to contact support for help with the key activation against the new GUID. Ah yeah, thanks for the reminder. I did swap last month Oct 16 so yup would need to go through support.
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.