Boot times have slowed down considerably, especially since installing Tailscale. I have since removed Tailscale but no change, Diagnostics included

tower-diagnostics-20261111-1443.zip

I should mention that at one point I was unable to logon via the web interface until I removed Tailscale

What happens if you boot into safemode? Same boot times? From my own experience my server takes about a minute or two to boot which is about how long I see it take in your server logs.

Edited Wednesday at 07:57 PM3 days by MowMdown

It takes about 9 mins to boot from cold...5 mins 30 secs spent verifying boot/* checksums. I'll try safe mode.

About the same in safe mode (with GUI)

Edited Wednesday at 10:50 PM3 days by Steviewunda
More detail

Have you tried another USB port or even another boot drive?

I just created more problems. I updated the BIOS to the latest, and now it won't boot at all. SATA drives 0, 1, 2, 3, and 6 are not being recognized. The boot sequence loops on "SATA link down..limiting speed to 1.5 Gbps" or something similar. I loaded the optimized defaults, but no go. The PC won't let me update the BIOS either - it only recognizes my Unraid flash drive now, not the other flash drive I used to update the bios. Any suggestions?

The PC booted up eventually but the array is stopped with missing disks. Diagnostics attached

tower-diagnostics-20261113-1958.zip

The diagnostics confirm the BIOS changed from F54a to F54c. On the previous boot, with F54a, all 8 SATA devices were detected normally. Now SATA ports 1-4 and 7 (as Linux numbers them) see no device at all. These are the two SSDs and disks 1, 3 and 5. The other 3 ports on the same controller work. The "SATA link down" messages mean those ports don't see a drive connected at all, which usually points to power or cabling. It could also be a SATA setting the new BIOS or the optimized defaults changed.

First, and most important: do not start the array, do not use New Config, and do not change any disk assignments while the disks are missing. Once all disks are detected again, the array should start normally with the current assignments.

Then please check:

1. Power off and check the power and SATA cables of the missing drives. Pay special attention to whether those 5 drives share the same power cable or splitter, since it's easy to disturb something when working inside the case.

2. Enter the BIOS and check whether the missing drives are listed there. If the BIOS doesn't see them, Unraid won't either.

3. Look at the SATA and M.2 settings in the BIOS. Make sure all onboard SATA ports are enabled and in AHCI mode, and that no M.2 or SATA Express setting is disabling some of the ports.

4. Try connecting one of the missing drives to a port and cable that currently works. If it shows up there, the problem is the port or cable it was on. If it still doesn't show, it's the drive or its power.

5. If nothing else helps, flash back to F54a. For the USB stick that Q-Flash doesn't see, make sure it's FAT32 formatted and try a USB 2.0 port.

Once all disks are back, post new diagnostics before starting the array. We can then look at the slow boot separately.

Thanks Jorge - I removed the Unraid flash drive, reverted to F54a, shutdown and replaced the Unraid drive, booted and everything appears normal. Thanks for your help 😉