gm.cinalli

Keep an eye on it then and let us know if indeed everything continues to go as it should.

Unfortunately, what happened is normal, the first backup always goes very well, it is from the second that they start to slow down incredibly.

Very strange, you are in my exact situation, I also disabled hard links, but I still have very slow backups with Time Machine.

Hi, your share is in the array or is a separate pool of only one disk?

I'm on a wired connection and I can confirm that is unusable.

Hi, do you have any updates on this?

My Time Machine share is already on one drive (excluding parity), so I don't think that's the reason for your speed bump. I don't know why, and maybe this is your case, the first Time Machine backup, on a brand new share, is always fast and without slowdowns. Over time I could also learn how Time Machine does not play well with cached shares, before 6.9.1 I had these problems with the cache enabled, once I removed it, backups became fast. Now with 6.9.1 we are in the same situation again, even without cache. However keep us updated on the results of the subsequent backups, with and without cache.

I noticed that too! This thing is driving me crazy, I have tried everything I found online and on this forum with no success.

In fact it isn't, it's just a Bug Sur bug.

I probably understood why, this morning I set a new icon (Macmini) manually in the smb.service file, everything worked until now, I don't know how, but the Xserve icon returned.

I will try that.

The icon is correctly visible in the same view like the screenshot you attached above, the only bug about it is the small icon in the sidebar that appears as a generic blank sheet.

@CS01-HS How can we make these changes permanent to the reboot?

I can confirm this bug, here's a screenshot on a Big Sur clean install.

So, it seems to be a problem only of 6.8.3? Really strange, however in my case, with SMB I don't have this problem.

How did you go about setting up a raid that is not part of the array?

Have you ever tried the Unassigned Devices plugin? It does exactly that.

In my case that was the problem, so I don't know what to tell you!

Hi, do you have the cache enabled on this share?

Has anyone understood what is causing these messages? My permissions are set correctly, Proxmox writes in the NFS shares and the latter are successfully mounted, what can it be?

Hi @Cadal, have you ever solved it? My logs are full of these messages. Do you use Proxmox?