Mavericks Dropping Network connection on test Mac Mini server

dkagle
New Contributor III

Hi JamfNation.

I am working on setting up a Casper 9.22 test server. Mid 2012 Mac Mini, 10.9.1, Server app 3.0.2. I have been round and round with my networking team and for some unknown reason my ethernet connection keeps dropping every 15-20 minutes. I've rebuilt the server from scratch once but the issue still exists. I made sure all of my energy saver settings were setup to never and even went as far as making ethernet the only network interface. I ruled out it being a hardware issue by hooking up a new Macbook pro with 10.9.1 to my port and it even dropped the connection. I check Apple forums and a lot of people seem to be having issues with Mavericks and staying connected. I was just curious is anyone else out there have run into any issues like this.

104 REPLIES 104

gskibum
Contributor III

@GaToRAiD, have you tried any 10/100/1000 USB 3 ethernet adapters?

GaToRAiD
Contributor II

@gskibum, no I haven't, but that will be bought on monday.

Jayant371
New Contributor

Hmmmm hate to hear the problem still exists in Yosemite because we were just so happy with the poing, which I kinda forgot, but resulted in:

Ping statistics for x.x.x.173: Packets: Sent = 21514, Received = 21480, Lost = 34 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 50ms, Average = 0ms

We continue to test Yosemite on monday cause today is not as busy as normal on the network. The USB --> ethernet solves to problem but is not really an option for 100 or somewhat clients...next to the 100 mbit connection..

@GaToRAiD: how does the script solve the connection drops in production??

@macstadium and @sullivanj, is there any news from your contact with Apple about the fact that USB --> ethernet works and the normal NIC doesn't??

Jayant371
New Contributor

Also, it looks like it's a hardware problem of not all/some Mac mini's....because not everyone is experiencing this issue plus in the test where we put the Mac Mini server to the 3750 Cisco we also connected two other Mac mini servers of the same model (late 2012) to the 3750 and they didn't have the network drops like our test machine. When there were dropped pings with the other two machines, there were every time just 4-6 pings lost....they recovered fast and our Mac mini with the network issue experienced serious network interruptions.

We might consult 'The Geniuses' next week on this issue our self. Hope we'll get some info on the subject and move it to a higher priority with Apple

sullivanj
New Contributor

@Jayant371 My ticket with Apple was closed on Oct. 11 2014 with the following comments:

STATUS: Thank you for the reply, much appreciated. I wasn't sure if that step had been done, since I hadn't mention it before and just recently was presented that it needed to be hardcoded. As far as any updates to the report I submitted on your behalf, it is has been related to a similar report and will be in a future release. I understand this is not what you were hoping for, but this is what engineering has presented. When we first submitted, I mention there were no guarantees that it would be implemented in the current release, but I wanted to go the extra miles on your behalf and see if it would possibly be. Have a great day. End of Comments / Instructions

I wasn't able to get an actual answer to why the USB dongles fix the issue, but I would guess that it has to do with bypassing the affected network stack. We ended up purchasing 300 Belkin 100mbps USB to Ethernet adapters because in our environment we utilize applications that require constant connections for licensing and normal functionality (Citrix). It's not the best solution, but it is a working solution and with Apple telling us we were SOL we had no other choice.

zwolfe1
New Contributor

I recently purchased a 2014 27-inch iMac, running Mavericks. I'm having issues with the network connection timing out, whether I use wifi or plug directly into the modem with an ethernet cable. I had no such issues with my 2011 21.5-inch running Mountain Lion. This issue is the closest to my own I have found; might the USB to Ethernet adapter fix my problem?

GaToRAiD
Contributor II

@Jayant371 the script basically is a keep alive, which doesn't allow for the packets to drop. We are currently using this in production and haven't noticed any problems since we have implemented this.

dkagle
New Contributor III

My post from back in March :I had to put my Mac mini server back on 10.8.5 for now. I setup a NetBoot/SUS appliance to handle managing updates for 10.9 clients. I am waiting for the 10.9.3 GM seed and then crossing my fingers.

As you all are well aware from your own experiences, updating didn't fix my issue either. My servers are still stuck on 10.8.5 and I'm running NetSUS appliances for ASUS and netbooting. Has anyone had luck with updating to 10.10?

I updated my test server to 10.10 on Monday and I've seen a random drop here and there but nothing consistent like before. After a full test JSS setup, I'm hoping I can move forward.

@GaToRAiD I'll be using a keep alive script if the issue persists or be getting the USB 3.0 gigabit dongles. While my network admin wasn't very helpful with trying to update our Cisco switches, he is more than happy to help with me with a keep alive script.

Thanks to everyone who commented on my original post earlier in the year. Helped me keep my sanity knowing I wasn't alone. JAMF Nation Rules!!!

cbrewer
Valued Contributor II

This issue appears to be unchanged in 10.10. Hugely disappointing.

edit: It's been a couple months now on 10.10 and I have not seen the issue in quite a while.

jbutler47
Contributor

Seeing same issue with:

Mac OS X 10.9.5
JSS 9.32
Mac Pro 2014 (x2)

Initial resolution was Apple USB to Ethernet, as it stopped lost/dropped packets. Awaiting delivery of USB 3.0 to GigaBit Ethernet, let you know how it goes. Yes, we get throttled down, but better to be slow than constant drop-out.

Tried all other solutions mentioned here to no avail. So far, the USB option worked, but time will tell.

sburrows
New Contributor III

@jbutler135 How did those USB 3 to gig adapters work for you? Which ones did you end up going with?

wonfuji
New Contributor

Wondering if anyone has tried Ethernet to Thunderbolt for this issue?

cbrewer
Valued Contributor II

Knock on wood, but I haven't seen this issue since moving my Mac Minis to 10.10.

jbutler47
Contributor

Much success here.

Had used a HiRO H50224 USB 3.0 10/100/1000 Gigabit Ethernet Adapter with my Mac Pros, worked like a charm, all issues went away. You will need to download their driver, works for 10.9.x.

JSS never freezes, communication to/from separate MySQL server resolved instantly with the USB adapters.

BTW, Thunder-2-Ethernet did not work at all, all ports, no joy. YMMV.

wonfuji
New Contributor

James

That sounds promising. Just amazoned two of them. I'll report back.

Stephen

sburrows
New Contributor III

We ended up getting some Linksys USB 3.0 gig adapters and so far so good. We've had them installed for a good 2 weeks now. We have one Mac Mini on Mavericks and another on Yosemite.

vonkas
New Contributor

read this blog with interest. Have had TCP/IP timeout issues with running VMs (Fusion & Vbox) between late 2014 iMacs & 2014 mini - all running 10.9.5 ws or server. No matter which way, it appears the ethernet I/F goes to sleep after 10-20 secs no activity. WHen it finally dawned on me I got a ping-forever going on the server mini/Vbox PC command console pinging any of the other VM. This fixed it! The load on the network traffic is not measurable. So for now this will do. I bet - as mentioned before - ping between 2 Macs will do the the same.

CypherCookie
Contributor

it sounds like this. http://www.macstadium.com/blog/osx-10-9-mavericks-bugs/

FelloWizard
New Contributor

Man I'm glad that I've finally found this thread! I've been searching High and Low for a resolution. I have a 2011 Mac Mini Server 10.7.5, 2014 Mac Mini 10.10 and 3 (late 2014) Macbook Pros 10.10 that are having the exact problem on our LAN. I'm going to try the USB 3.0 to ethernet fix first and if that doesn't work I will give the bash script a try.

I'll keep you guys posted on my results.

rviets
New Contributor

I had the same issue with a M2011 Mini Server running 10.9.5 and a Filemaker database we use for inventory. Sometimes it was 3 minutes, sometimes it was 3 hours, but our clients always dropped their connection. USB to ethernet was the only thing that worked. Solid for a month now.

This thread saved me! Thanks guys

zimou13
New Contributor

I was about to cancel UVerse and call Comcast (yikes!). No joke. I have a house full of MacBooks and iPhones. Our area recently became available to upgrade to the 50 Mbps internet speed so I jumped on upgrading. They replaced my router with the Motorola SVG589. We ran speed tests and everything was looking great. Then for the next two months I almost went insane. see: ShowBox VidMate Mobdro

bradtchapman
Valued Contributor II

I'm reviving this thread because it's 2021, and there are only exactly two relevant Google results for this combination of terms:

Mac Mini, AppleBCM5701Ethernet, LimitMinFragSize, unable to realloc packet

Here's a snippet of the logs from my 2014 Mac Mini running 10.14.6:

2021-04-28 10:55:56.847583-0700 0x2f3      Default     0x0                  0      0    kernel: (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en0]:        8      192 LimitMinFragSize: Unable to realloc packet
2021-04-28 10:55:56.847601-0700 0x2f3      Default     0x0                  0      0    kernel: (AppleBCM5701Ethernet) 0x00000008, 0x00000192 LimitMinFragSize: Unable to realloc packet
2021-04-28 10:55:56.847603-0700 0x2f3      Default     0x0                  0      0    kernel: (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en0]:        0        0 transmitPacket: Failed to adjust fragment array
2021-04-28 10:55:56.847607-0700 0x2f3      Default     0x0                  0      0    kernel: (AppleBCM5701Ethernet) 0x00000000, 0x00000000 transmitPacket: Failed to adjust fragment array

This has been happening for YEARS. I've been able to reproduce the issue multiple times in the same day. My 2014 Mac Mini is a file server / media server at home, and it's been driving me bonkers because it only happens when there is a large amount of traffic / IOPS going to / from the mounted network volume. It has persisted across multiple versions of MacOS, and affects all protocols (afp, smb, nfs).

I am resigned to the possibility that the Broadcom 5701 Ethernet device inside the 2014 Mac Mini is flawed and cannot handle high volume traffic or heavy loads.

I'm going to connect a Thunderbolt 2 > Ethernet adapter and see if the problem goes away.

bradtchapman
Valued Contributor II

I've set the network adapters to full-duplex, flow-control, jumbo frames (9000 MTU), and turned off AVB/EAV mode.

During a high volume transfer I hit 100MB+/sec and saw rates of ~150,000 packets per second. It was going great for a while until it crashed again. The Mac was responsive locally with keyboard and mouse and monitor, but had otherwise locked up Terminal and stopped responding to pings until I unplugged one of the TB/Ethernet adapters and then it recovered instantly.

I am running VMWare Fusion on this machine. Have seen reports in the past that the vmnet kernel extension causes issues, so I'm going to migrate the virtual machine to my NAS and uninstall VMWare Fusion.

bradtchapman
Valued Contributor II

I'm leaving this here for future Googlers to find.

The issue appears to be linked to the vmnet kernel extension for VMWare Fusion.

/Applications/VMware Fusion.app/Contents/Library/kexts/vmnet.kext

The extension is responsible for routing traffic from guest VMs. When a VM is active, vmnet buffers all traffic on all interfaces. I surmise that this is because the active network interface and network mode (bridged, shared, private) are some of the few things you can modify on a guest VM without having to shut it down.

When this buffer overloads, it locks up ALL network activity on the host. Local interactive access to the computer is unaffected — the keyboard and mouse are perfectly responsive, although you may have trouble opening up Terminal sessions. There's no easy way to resolve the issue programmatically. You either have to wait until the connection dies or go physically unplug the Ethernet adapters.

There are a much larger set of search results for "vmnet failed to deep copy mbuf 12", which tend to point fingers at high-volume transfers that can soak a gigabit connection, or activities that open lots of files over AFP, SMB, and NFS. This includes busy file servers, and Time Machine backups to a network disk.

I'm including an excerpt of the logs from my own Mac showing the beginning stages of a problem with vmnet and subsequent disk failures, network errors, and dismounts. In the excerpt below, disk3s2 is an iSCSI volume (SCSI disks over Ethernet) presented by the NAS to the Mac Mini on a separate interface (Thunderbolt to Ethernet). iSCSI is way more performant than a network share. Unfortunately, vmnet's buffer problem affects all network adapters.

About 40-45 seconds into one of these buffer overflows, the iSCSI disk (disk3s2) is forcibly unmounted after globalsan reports the problem. Meanwhile, it takes at least a full minute before NFS volume "vault687" is declared "dead" and disconnected.

Finder and NotificationCenter (IconServices) are told to prepare a notification (GET_ICON_IMAGE_NO_IO) and to display an error for the disconnected iSCSI volume. There is, unfortunately, no on-screen warning about the lost network volume. It simply vanishes, and your applications are left to wonder wtf just happened.

Log snapshot follows. Portions with excessive duplicated lines were edited out manually and annotated with [ brackets ] indicating the number of repeats.

$ log show --style compact --start "2021-04-29 19:32:00" --end "2021-04-29 19:34:59" --predicate 'process == "kernel" && sender == "AppleBCM5701Ethernet" || sender == "vmnet" || sender == "Sandbox" || sender == "IOStorageFamily" || eventMessage contains "nfs" && sender != "IOPlatformPluginFamily" && sender != "AirPortBrcmNIC" && sender != "IO80211Family"' --predicate 'process == "DiskUnmountWatcher"' --predicate 'sender == "IconServices"'

Skipping info and debug messages, pass --info and/or --debug to include.
Timestamp               Ty Process[PID:TID]

2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:00.291 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.

[ Sequence repeats 25 times in 8.6 seconds ]

2021-04-29 19:33:08.940 Df kernel[0:16b] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        8      5ea LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:08.940 Df kernel[0:16b] (AppleBCM5701Ethernet) 0x00000008, 0x000005ea LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:08.940 Df kernel[0:16b] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        0        0 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:08.940 Df kernel[0:16b] (AppleBCM5701Ethernet) 0x00000000, 0x00000000 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:09.750 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:09.750 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:11.752 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:11.752 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.

[ Sequence repeats 32 times in 3.7 seconds ]

2021-04-29 19:33:15.359 Df kernel[0:2e6c7] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:15.359 Df kernel[0:2e6c7] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:15.359 Df kernel[0:2e6c7] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:15.359 Df kernel[0:2e6c7] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:15.526 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:15.526 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:15.663 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:15.664 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.

[ Sequence repeats 50 times in 13.9 seconds ]

2021-04-29 19:33:29.597 Df kernel[0:16b] nfs server 192.168.11.5:/volume3/vault687: not responding
2021-04-29 19:33:29.694 Df kernel[0:16b] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:29.694 Df kernel[0:16b] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:29.694 Df kernel[0:16b] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:29.694 Df kernel[0:16b] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:32.829 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:32.829 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:33.160 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:33.160 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:33.685 Df kernel[0:7af6] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en7]:        8      162 LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:33.685 Df kernel[0:7af6] (AppleBCM5701Ethernet) 0x00000008, 0x00000162 LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:33.685 Df kernel[0:7af6] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en7]:        0        0 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:33.685 Df kernel[0:7af6] (AppleBCM5701Ethernet) 0x00000000, 0x00000000 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:33.742 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:33.742 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:33.829 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:33.829 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:34.021 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.021 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.236 Df kernel[0:2881] (vmnet) vmnet: VMNetSetopt: Set link state DOWN
2021-04-29 19:33:34.237 Df kernel[0:2881] (vmnet) vmnet: VMNetSetopt: Set link state UP
2021-04-29 19:33:34.710 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.711 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.712 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.712 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.712 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.712 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.712 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.715 Df kernel[0:46a] (vmnet) vmnet: Failed to shallow copy mbuf: 12.
2021-04-29 19:33:34.717 Df kernel[0:46a] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:34.717 Df kernel[0:46a] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:34.717 Df kernel[0:46a] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:34.717 Df kernel[0:46a] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:34.725 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.725 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.725 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.910 Df kernel[0:90451] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:34.955 Df kernel[0:6b2] :
2021-04-29 19:33:34.991 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.991 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        8      4dd LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) 0x00000008, 0x000004dd LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        0        0 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) 0x00000000, 0x00000000 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        8      4f1 LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) 0x00000008, 0x000004f1 LimitMinFragSize: Unable to realloc packet
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) AppleBCM5701Ethernet [en6]:        0        0 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:34.994 Df kernel[0:fe0e] (AppleBCM5701Ethernet) 0x00000000, 0x00000000 transmitPacket: Failed to adjust fragment array
2021-04-29 19:33:36.051 Df kernel[0:90451] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:40.436 Df kernel[0:398] (vmnet) vmnet: Failed to deep copy mbuf: 12.
2021-04-29 19:33:40.436 Df kernel[0:398] (vmnet) vmnet: bridge-en0: SendToVNet copy failed: 12.
2021-04-29 19:33:41.623 Df kernel[0:903ef] (globalSAN) GLO Warning: Error during the recovery 0xe3ff8201.
2021-04-29 19:33:41.623 Df kernel[0:903ef] (globalSAN) GLO Warning: Error during the recovery 0xe3ff8201.
2021-04-29 19:33:41.624 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.624 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.624 Df kernel[0:17e] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.624 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.624 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:17e] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.625 Df kernel[0:8fb6a] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.626 Df kernel[0:1014c] (IOStorageFamily) disk3s2: device/channel is not attached.
2021-04-29 19:33:41.626 Df kernel[0:8fb6a] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.626 Df kernel[0:8fb6a] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.626 Df kernel[0:8fb6a] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:41.626 Df kernel[0:8fb6a] (IOStorageFamily) disk3s2: media is not present.

[ Message repeats 968 times in 0.2 seconds ]

2021-04-29 19:33:41.827 Df DiskUnmountWatcher[1337:7eaf3] DiskUnmountWatcher: callback
2021-04-29 19:33:41.827 Df DiskUnmountWatcher[1337:7eaf3] DiskUnmountWatcher: callback
2021-04-29 19:33:41.828 Df DiskUnmountWatcher[1337:7eaf3] DiskUnmountWatcher: callback find and release <private>
2021-04-29 19:33:41.828 Df DiskUnmountWatcher[1337:7eaf3] [com.apple.KerberosHelper:KerberosHelper] NAHFindByLabelAndRelease: looking for label <private>
2021-04-29 19:33:41.835 Df kernel[0:905ef] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.835 Df kernel[0:905ef] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.837 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.837 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.839 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.839 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.839 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.839 Df kernel[0:90856] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:33:41.964 A  NotificationCenter[455:b77] (IconServices) PREPARE_ICON_IMAGE
2021-04-29 19:33:42.044 A  NotificationCenter[455:b77] (IconServices) GET_ICON_IMAGE_NO_IO
2021-04-29 19:33:42.269 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.284 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.284 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.284 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.

[ Message repeats 31 times in 0.03 seconds ]

2021-04-29 19:33:42.317 A  Finder[417:9d4] (IconServices) PREPARE_ICON_IMAGE
2021-04-29 19:33:42.317 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.319 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.319 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.319 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.

[ Message repeats 134 times in 0.15 seconds ]

2021-04-29 19:33:42.469 Df DiskUnmountWatcher[1337:7eaf3] DiskUnmountWatcher: callback
2021-04-29 19:33:42.473 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.478 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.478 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.478 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.

[ Message repeats 343 times in 0.22 seconds ]

2021-04-29 19:33:42.594 A  Finder[417:9d4] (IconServices) GET_ICON_IMAGE_NO_IO
2021-04-29 19:33:42.594 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.594 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.594 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.
2021-04-29 19:33:42.595 Df kernel[0:90833] (IOStorageFamily) disk3s2: media is not present.

[ Message repeats 68 times in 0.54 seconds ]

2021-04-29 19:33:43.035 Df kernel[0:90833] (HFS) hfs: unmount initiated on transfer on device disk3s2
2021-04-29 19:33:43.035 Df kernel[0:90833] (HFS) jnl: disk3s2: close: journal is invalid.  aborting outstanding transactions
2021-04-29 19:33:43.362 A  Finder[417:9d4] (IconServices) PREPARE_ICON_IMAGE
2021-04-29 19:33:43.362 A  Finder[417:9d4] (IconServices) GET_ICON_IMAGE_NO_IO
2021-04-29 19:33:43.365 A  Finder[417:9d4] (IconServices) PREPARE_ICON_IMAGE
2021-04-29 19:33:43.365 A  Finder[417:9d4] (IconServices) GET_ICON_IMAGE_NO_IO

[ Sequence repeats 10 times in 4 seconds ]

2021-04-29 19:33:47.872 Df dmd[1116:51da] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:33:47.874 Df dmd[817:2e1c] [com.apple.dmd:ConfigurationEngine] Detected network change
2021-04-29 19:34:04.918 Df kernel[0:90abc] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:34:05.107 Df kernel[0:90abc] (Sandbox) syscall_extension_issue failed: 2
2021-04-29 19:34:21.870 Df kernel[0:e941] nfs_connect: socket connect taking a while for 192.168.11.5:/volume3/vault687
2021-04-29 19:34:43.891 Df kernel[0:e941] nfs_connect: socket connect aborted for 192.168.11.5:/volume3/vault687
2021-04-29 19:34:43.891 Df kernel[0:e941] nfs server 192.168.11.5:/volume3/vault687: dead
2021-04-29 19:34:43.891 Df kernel[0:e941] nfs server 192.168.11.5:/volume3/vault687: can not connect, error 60

salimmp
New Contributor

Test