MacOS Server Alerts for Volume not responding

Volumes have unique ID's (at least for most formats). In Disk Utility select a volume & get info on it.

The Universal Unique Identifier should be listed.

You can also use Terminal…

diskutil info disk0s2

(you need to edit the identifier accordingly)

See if that tallies with the notifications.

The UUID should be written within the file system format so it should not change until the volume is reformatted. Some filesystems do not support UUID's so they normally use the same one (FAT volumes show an 8 figure UUID if I recall correctly).

I don't know what server is complaining about there, sorry. I'd check your RAID is functioning correctly and start digging into the other logs, there may be more info in diskarbitration.log diskutility.log or fsck_hfs.log. Also check the All Messages section of Console.app at the times listed in those notifications.

My Mac Mini is doing this too!!!

Its done it 4 times in the last 24 hours.

It has been really slow and freezes/crashes regularly for the last week or so.

I replaced the HDD about 3 months ago and the freeze symptoms were the same but without the "Volume X not responding" messages.

It's at the stage where sometimes it won't boot and other times it will ?? Very random, so I started suspecting that the new drive is failing just like the original one.

I run the disk utility, and it says the disk is fine, whereas last time it clearly highlighted disk problems.

I run the activity monitor, and it show everything reasonably ok, but then when various apps don't respond and it freezes, I can see they show up as not responding.

Not sure what to do?

Hi,

I have exactly the same problem. Each time a different UUID but none of the numbers have any relation to the volumes in the machine. I made two clean installs but each time it came again. Any update on this? Could you solve the problem? Are you in contact with Apple support?

Thank you.

Has anyone gotten on updates on this issue. I have a freshly installed 10.12.3 server and its exhibiting the same errors.

None is the UUID that come up have an correlation to the volumes we are using.

Same issue here. I noticed my "Volume XXXX not responding errors" all seem to correspond to Eclipse installation attempts I was making. The installer probably created a hidden volume and then removed it and Sierra's Server app just thought I should know.

Glad it is not chronic.

sbwinn wrote:

Same issue here. I noticed my "Volume XXXX not responding errors" all seem to correspond to Eclipse installation attempts I was making. The installer probably created a hidden volume and then removed it and Sierra's Server app just thought I should know.

Glad it is not chronic.

That is a valid point, disk images could be a culprit. I think certain apps will download, mount and unmount disk images for updates. I think Adobe & Google apps have a habit of doing that.

I can't think of a way to monitor it, I guess you could run 'mount' every few minutes & compare the output?

I think disk arbitration should be able to log interactions on 10.7, it became diskmanagementd in later OS's (10.8 or 10.9 if I recall correctly).

4NDY17 wrote:

Are you referring to the file system UUID?

I am getting the same issue. My uuid' change each time. I believe it may be a Plex update. I am going to check the uuid next time it mounts.

Yep, you can see the UUID for a disk in Disk Utility via it's info panel or via Terminal…

diskutil info disk3s2

Replace the disk identifier (disk3s2) based on the output of

diskutil list

The hdiutil command handles the same feature for disk images…

hdiutil imageinfo /path-to-diskimage

I suspect you can use a combination of the find command & hditutil to scan for all the UUID's of disk images on the system, however I don't know the file suffixes to look for, some developers may not use suffixes for updates despite using disk image containers (or may use .iso etc). Some updaters will also remove the downloads after completion too.

This is a rough start…

find ~ -name \*.dmg -type f -exec hdiutil imageinfo {} \; | egrep "partition-UUID|0: "

Change the search location to wherever you like, it searches your home folder.

It pulls out the file name (listed as '0: /path/to/file.dmg') & the partition-UUID but not all disk images have that info stored so you would have to mount them all to see that!

Same problem here. The primary purpose of this server is to house Time Machine backups. Could the long string be the image UUID of the hosted Time Machine disk image? How could I verify that? How can it be repaired?

I have the same problem and none of my disks’ UUIDs match the ever-changing ones in the alert message. I am pretty sure that this is a sparseimage used by macOS Server to backup services like Open Directory or other databases. I remember that back in the PPC days Mac OS X Server would not completely be backed up by Time Machine since services with databaes in use would be ignored by it. You needed to rely on 3rd party applications or shell scripts to stop, backup and resume services. With a later release Apple improved TM in this regard and I suppose they are backing up services to a sparseimage. Maybe the alert ist caused by the image disappearing when not in use due to it getting unmounted. But that’s just my guess…

Seeing this here also. Multiple errors with erroneous UUIDs.

OS X version 10.12.3

Server version 5.2