Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Operating System
Unable to write to remote drive?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MacInWin" data-source="post: 1926224" data-attributes="member: 396914"><p>Don't do that. Don't partition. That divides the hardware up and basically could erase the entire drive in the process.</p><p></p><p>From your image, "Bob" is the system drive, as I suspected. You cannot write to "Bob" because it is owned by the system and NO user has access to it. But, "Bob - Data" is also part of that drive and you CAN write to it. Not only that, but the space that you think Bob has is also available to Bob-Data. How that works is that "Container Disk3" has the entire drive (hardware) available, then within that Container are two Volumes, as Apple calls them, "Bob" and "Bob-Data." As I said, Bob has the system and is very strongly write protected. The good news is that "Bob" is relatively small and doesn't consume a ton of space. "Bob-Data" is another Volume, and it holds the /User folder in which your own account space was when it was a boot drive. That Volume is read/write, and there should be a folder on it for your account when it was boot, which you may be able to write to. The way APFS works is that all the volumes in a container have access to all the space in the container that is free, so both Bob and Bob-Data have access, as I said, to the free space on the drive.</p><p></p><p>Now, if you never plan to boot from that drive, ever, you can try to remove the volume named "Bob" by selecting it and then click on the "-" on the bar where it says "Volume." I don't know if that will work, and it won't save you much space, but if it does, "Bob" will disappear and only "Bob-Data" will remain.</p><p></p><p>BTW, one of the "smarts" of the OS is that when you boot from that drive, the system will mount what you have highlighted, namely, "Bob volumes," both Bob and Bob-data get mounted, then merged into one virtual drive named "Bob." On that virtual drive, you can write to /Users, but not the other root folders because they are the system files stored on Bob, while /Users is stored on Bob-data.</p><p></p><p>Hope that helped. To summarize, just use Bob-Data instead of Bob and you should be able to write to the drive.</p></blockquote><p></p>
[QUOTE="MacInWin, post: 1926224, member: 396914"] Don't do that. Don't partition. That divides the hardware up and basically could erase the entire drive in the process. From your image, "Bob" is the system drive, as I suspected. You cannot write to "Bob" because it is owned by the system and NO user has access to it. But, "Bob - Data" is also part of that drive and you CAN write to it. Not only that, but the space that you think Bob has is also available to Bob-Data. How that works is that "Container Disk3" has the entire drive (hardware) available, then within that Container are two Volumes, as Apple calls them, "Bob" and "Bob-Data." As I said, Bob has the system and is very strongly write protected. The good news is that "Bob" is relatively small and doesn't consume a ton of space. "Bob-Data" is another Volume, and it holds the /User folder in which your own account space was when it was a boot drive. That Volume is read/write, and there should be a folder on it for your account when it was boot, which you may be able to write to. The way APFS works is that all the volumes in a container have access to all the space in the container that is free, so both Bob and Bob-Data have access, as I said, to the free space on the drive. Now, if you never plan to boot from that drive, ever, you can try to remove the volume named "Bob" by selecting it and then click on the "-" on the bar where it says "Volume." I don't know if that will work, and it won't save you much space, but if it does, "Bob" will disappear and only "Bob-Data" will remain. BTW, one of the "smarts" of the OS is that when you boot from that drive, the system will mount what you have highlighted, namely, "Bob volumes," both Bob and Bob-data get mounted, then merged into one virtual drive named "Bob." On that virtual drive, you can write to /Users, but not the other root folders because they are the system files stored on Bob, while /Users is stored on Bob-data. Hope that helped. To summarize, just use Bob-Data instead of Bob and you should be able to write to the drive. [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
Apple Computing Products:
macOS - Operating System
Unable to write to remote drive?
Top