kman13

No solution yet - I got tied up with work and didn't manage to get back to my server in the last few months. Hoping that I can get in touch with them over the next few weeks and get an Xmas reprieve on those USB drives. Have 3 now that have passed the end of trial before I could get any time to restore my Unraid 🤦‍♂️

Thanks - sorry for the delay in my response. 1. Checked in BIOS - details not available there unfortunately. Its an old bios. However, the >lsusb command seems to suggest its USB 2.0 (said minimum speed 480 mbps) 2. Wanted to do the trial install to compare as you suggested but all the USBs I have on hand seem to be "blacklisted". Funny thing is, they worked earlier. Will do this and get back in a couple of days, though I dont think that is the issue here. ~

Hi, I find that some USB drives which I'd used for (trial) Unraid installs don't work with the Unraid USB Creator anymore. They show as blacklisted when I use the USB creator now, though they worked just fine earlier - why? My licensed Unraid is now on another USB, which I am trying to compare performance with because I have slow boot times. Isn't there a way to manage this so we can reuse disks post trial for legitimate reasons? Would appreciate feedback on how this can be addressed. It's a bit annoying to have to get another USB (?) just to test this. Thanks

Hi, and thanks for the response... 1. Is there a way to check if the USB is working at 2.0? I am not sure of a command for this. 2. yes, I have removed the mover tuning plugin already

Hi, Yes, I have made a couple of flash backups - one locally off the server and another via Unraid Connect. Just in case...

Hi folks, I',m new to Unraid, and would appreciate some help with issues I am facing. My Unraid server seems to be really slow to boot (over 4 minutes overall) since I had a improper shutdown event (power loss), and I am unable to figure out how to address this. Once its started, it seems to be working fine, with the exception of mover which didn't seem to run on its own. Admittedly, this is an oldish system (AMD A10 FM2+ processor), but I recall it being much quicker when I set it up a couple of months ago. A few observations from scanning the boot sequence on startup for ERRORS... 1. Differences between boot sector and its backup Fat-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. - fsck doesn't seem to execute because the /sda1 device is still mounted. - Tried unmounting, /sda1 but that didn't work for me. Seems to be locked (I'd already shut down the array) 2. There seems to be a longish wait for the following modules Verifying bzmodules checksum...MEDIUM WAIT Verifying bzfirmware checksum...LONG WAIT 3. I also noticed that mover doesn't seem to be starting? mv: cannot stat '/usr/local/bin/mover' : No such file or directory I figure it may have been the Mover Tuning plugin causing the problem. I removed the plugin and then a manual move seemed to work fine. Any clue how I can avoid this in future? The plugin seems so useful, though I've not started using it yet. Would appreciate if you can share advice or point me to a solution for the slow boot issues. Thanks!