Add Disk can't find my disks
When Find Disks can’t list a server’s disks, Add Disk says why, in a red note under the form. Most problems are the address or the allowed initiator name.
What Add Disk says
Section titled “What Add Disk says”| Message | What to do |
|---|---|
| No server named “storage.local” answered on the network. | Check the address, or use the server’s IP address. |
| storage.local can’t be reached. | Check the address, and that the server is on and on your network. |
| storage.local refused the connection. | Check the port (usually 3260), and that iSCSI is turned on on the server. |
| “…” isn’t a server address | Enter a name or an IP address, with :port only if it isn’t 3260. |
| storage.local doesn’t allow this Mac’s initiator name. | Add this Mac’s name (at the top of Add Disk, with Copy) to the target’s allowed initiators on the server, then try again. |
| storage.local offers no disks to this Mac. | The server lists no targets for this Mac. It may not allow this Mac’s initiator name for any of them. |
| storage.local wants CHAP to list its disks. / storage.local wants CHAP. | Choose CHAP (Add Disk may switch to it for you) and enter the user and secret set on the server. |
| storage.local refused the CHAP user or secret. | Check them against the server’s settings, character for character. |
| storage.local couldn’t prove who it is. | With Mutual CHAP, check the server’s own user and secret under Verify the server too. |
| BeamDisk isn’t allowed to use the local network. | Turn BeamDisk on in System Settings → Privacy & Security → Local Network, then try again. |
Under some messages, a second line in smaller type gives the technical detail, in the words your server’s logs are likely to use.
Some disks are missing
Section titled “Some disks are missing”- A whole target is missing. The server may not allow this Mac’s initiator name for it: add the name to that target’s allowed initiators, then click Back and Find Disks again.
- A target is listed without its disks. A note under the list says why, such as projects didn’t list its disks. followed by the reason.
- A disk is listed as Already added as a name: it’s on this Mac already.
The checklist
Section titled “The checklist”If the messages don’t settle it, work down this list.
- The address and port. Check the server’s address, and that its iSCSI service is running and listening on the port you entered (usually 3260).
- The allowed initiator name. Most storage servers hide a target from initiators they don’t allow. Copy this Mac’s name from BeamDisk (Add Disk, This Mac, or Settings → General) and add it to the target’s allowed initiators.
- CHAP. The user and secret must match exactly what the server expects. BeamDisk uses the same pair for discovery and for the target. For mutual CHAP, check the server’s own user and secret too.
- Local network access. If macOS asked whether BeamDisk may find devices on your local network and it was refused, allow it in System Settings → Privacy & Security → Local Network.
Found it, but it won’t connect
Section titled “Found it, but it won’t connect”The disk’s state says why: see A disk won’t connect and What a disk’s state means. Reserved by another computer means another computer is using it: see One Mac per disk.
Still stuck? Get help.