Since things are working and I don't know what happened, I can't really work on what the minimum steps would be. It may not have required the SIP change in recovery mode but that is the steps I was taking to try to get those phantom mount points deleted. What caused the immutable flag to be set on the directory?Īnyway, if someone else has this problem, this was the solution. It is confusing as to how this ever happened. I don't know which of the flags were set or what was up with not seeing it before but this finally got the machine back into operation. After returning SIP to enabled and restarting into normal operation, USB drives once again mounted! However, "ls -O" was not showing it.Īnyway, just out of a fit of desperation, I tried this: chflags noschg,nouchg "/Volumes/Kit - Data/Volumes"Īfter that I was able to delete the phantom mount points. So, finally I said to myself "what if the immutable flag was somehow set on a directory. I was thinking that the filesystem was somehow corrupted but then again First Aid did not find anything. That failed (as always) with "Operation not permitted" but I also tried: echo test > testĪnd it also failed with the same error. Then, I opened the recovery mode terminal and did cd "/Volumes/Kit -Data/Volumes" What I did was mount the volume with the recover mode Disk Utility. Even after turning of SIP within recovery mode. I was still trying to figure out why, even in recovery mode, I could not delete the Volumes/Andromeda directory. (Albeit it is not the machine that is normally used for this work)Īfter many reboots and different attempts at resetting firmware and SMC, I tried one more time today to address the problem in recovery mode. It is sad that the other MacBookPro is working just fine. This has made using these external drives very complex as I must go into terminal and manually mount them. I have run first aid from Disk Utility (and in the recovery console) and it always says things are just fine. It may be that the existence of those directories in /Volumes is the problem. Unfortunately, MacOS has changes a lot from when I did lower level work on it so I don't know where the data may be about the automounting and existing volumes.įinally, I can not seem to delete the /Volumes/Andromeda and two other mountpoints even after rebooting, rebooting into safe mode, and rebooting into the recovery console. The exact same drives mount perfectly fine on another MacBookPro running the same version of the MacOS (11.2.3)Īs best as I can tell, the OS has corrupted itself somewhere with respect to the mount volumes. That drive also has multiple partitions on it.įinally, I tried reformatting one of the drives (it was a backup) and named it the same as the prior volume and it would not mount, even with a full reformat. This has now spread to a second drive that was working just fine for well over a year of temporary mounting and unmounting. The other thing is that the directory in /Volumes continues to remain to be there for the drive/volume. Everything seems fine until I unmount it (via Disk Utility or Finder) and I can then no longer mount it again. However, if I use the terminal via "sudo diskutil mount -mountPoint /tmp/Andromeda /dev/disk2s1" it does work and everything sees the volume. Specifically, the error "Could not mount “Andromeda”. But I always get an error when trying to mount it via the Disk Utility GUI. So, I have a USB drive I have used for years and it suddenly does not mount anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |