Mark Levitt
Explorer
- Joined
- May 21, 2017
- Messages
- 56
Hi,
Not sure if this a TrueNAS problem or macOS or (most likely) a combination of the two.
I've been getting the error:
Disk Not Ejected Properly
Event "Backup of [computer name]" before disconnecting or turning it off.
It seems to happen when the macs sleep.
I've looked through log.smbd and the only errors I can see regularly are:
scavenger_timer: Failed to cleanup share modes and byte range locks for file 7326153584521250802:366184:37956416 open 3453878756
The time machine share has been working fine for a while. It's a standard SMB share set to "Multi-user time machine". The only change to the default settings was to add fruit:time machine max size = 2T in the advanced settings.
The errors only started after upgrading to 13-U3. Initially, I thought it might be related to macOS Ventura, but I have other macs running Montery that are showing similar errors. I upgraded to 13-U4 yesterday, but I'm still getting the error message today.
Anyone else seeing the same thing?
EDIT: Seems like it's more likely a macOS bug https://discussions.apple.com/thread/254445879
Not sure if this a TrueNAS problem or macOS or (most likely) a combination of the two.
I've been getting the error:
Disk Not Ejected Properly
Event "Backup of [computer name]" before disconnecting or turning it off.
It seems to happen when the macs sleep.
I've looked through log.smbd and the only errors I can see regularly are:
scavenger_timer: Failed to cleanup share modes and byte range locks for file 7326153584521250802:366184:37956416 open 3453878756
The time machine share has been working fine for a while. It's a standard SMB share set to "Multi-user time machine". The only change to the default settings was to add fruit:time machine max size = 2T in the advanced settings.
The errors only started after upgrading to 13-U3. Initially, I thought it might be related to macOS Ventura, but I have other macs running Montery that are showing similar errors. I upgraded to 13-U4 yesterday, but I'm still getting the error message today.
Anyone else seeing the same thing?
EDIT: Seems like it's more likely a macOS bug https://discussions.apple.com/thread/254445879
Last edited: