Skip to content

A server's page

Every server you add disks from has a row in the window’s sidebar, with its disks under it. Click it to open its page. The title is the server’s name, or its address, with a summary under it, such as 8 targets · 6 disks added · 1 reconnecting.

A server’s row shows its disks’ throughput together, or what needs a look instead:

Shows Means
2 new The server offers disks that aren’t added yet, found since its check before. They’re no longer new once you’ve been to its page.
Checking… BeamDisk is asking the server for its targets.
1 reconnecting A target’s session is reconnecting, and its disks hold their writes meanwhile.
Can’t reach Every session with the server is reconnecting.
Login refused The server refused a target’s login: it doesn’t allow this Mac’s initiator name, or it refused the CHAP details.
No disks No disk is added from it yet.
  • Check for New Disks (⌘R) asks the server which disks it offers this Mac now.
  • Server Actions (…): Edit Server…, Check for New Disks and Remove Server….
  • Settings, and Add Disk, which opens with this server’s disks.

A banner at the top says what’s going on, since when, and the one thing to do about it:

Banner What to do
Not allowed The server doesn’t allow this Mac’s initiator name for a target. Allow it there, then click Try Again.
CHAP refused The server refused the CHAP user or secret. Click Edit Server… and enter the ones set on the server.
Can’t reach the server No answer from it: every session is reconnecting, and writes are held for up to the hold time. Disconnect All ejects its disks.
A target reconnecting One target’s session is reconnecting; the others are fine. Disconnect ejects its disk.
2 new disks Click Add Disks… to add them.
Couldn’t check Why the server couldn’t list its targets, such as wanting CHAP for it. Edit Server… or Check Again.
New login settings New CHAP details, or digests changed in Settings, saved and used at each target’s next login. Reconnect and Apply Now uses them now.
No disks added Click Add Disks….
Tile Shows
Throughput Its disks’ reads and writes together, over the last second.
Latency How long its disks’ reads and writes took over the last 5 seconds, p50 in large and p99 below.
Sessions How many of its targets with disks added are logged in (4 of 6 up), and which isn’t.
Disks How many are added from it, and how many it offers that aren’t (3 not added · 2 new).

Every target the server offers this Mac, as its last check found it, with every disk added from it. Beside the title, when the server was last checked (Checked 2 min ago), and just after a check, what it found (found 1 new disk, nothing new).

Column Shows
Target Its short name, and its full name when there’s room.
Session The target’s session, which its disks share: Up 7 h 15 min · 1 reconnect, Reconnecting · 24 of 60 s, Login refused, or Not logged in for a target with no disk added.
LUN The disk’s number on the target.
Size Its capacity, as Finder counts it.
Disk The disk it’s added as, with its state’s glyph; or Not added, with New when it’s new since the check before.

Click a disk’s row to open its page. Add… opens Add Disk with that disk ticked.

BeamDisk also checks a server by itself, quietly: when its page or Add Disk opens and the last check is more than 10 minutes old, and when a target this Mac is logged in to reports that its disks changed.

  • Connection: the server’s Address, its Portal (the address it’s at now, and the port), Authentication (CHAP · user and the user, Mutual CHAP or None), Digests and Product, what the server says its disks are. Edit… opens Edit Server.
  • Remove Server…, at the bottom, once its disks are ejected.
  • Access: this Mac’s initiator name, with Copy. A server offers this Mac only the targets that allow it: Missing a disk? Allow this name for its target on the server, then check again.
  1. On the server’s page, click Edit…, or choose Edit Server… in ….
  2. Change its Name (shown in the sidebar and wherever BeamDisk names the server; left empty, its address shows), its Address and Port, or its Authentication.
  3. Click Save. BeamDisk checks new login details or a new address with the server first. If the server refuses them, nothing is saved, and your disks keep the details that work.
  • New login details are used the next time each target logs in, and your disks stay connected until then. Reconnect and Apply Now logs them in again now: reconnecting pauses each disk for a moment.
  • A new address asks first: Change Address ejects the disks attached now for a moment, connects the server’s disks again at the new address, and attaches them again. Quit apps using them first. Before it asks, BeamDisk checks that each disk at the new address is the one you use now, by the ID the server reports for it and its sector size, since a second server set up the same way can offer other disks under the same target names and LUNs. Nothing changes if one isn’t, while a disk is in use, or while the server has stopped answering and a disk still holds writes for it. A disk whose contents macOS can’t read at the new address isn’t attached, and BeamDisk says so.

Eject its disks, then choose Remove Server… and confirm. Its disks are removed from BeamDisk too, with their CHAP secrets; their data stays on the server, and you can add them again later.