# A disk won't connect

> Why a disk added to BeamDisk shows Retrying or Can't connect, what each explanation means (initiator name, CHAP, the disk's size, a missing target, another computer), and how to fix it.

A disk that can't connect says so in its state, with since when. Its page shows why in plain words, with the technical detail under it, and **Try Again**.

- **Connecting…**: BeamDisk is logging in to the server. Wait a moment.
- **Retrying** (amber): the server didn't answer, or turned the login away for a reason that may pass. BeamDisk tries again by itself and says when: **Trying again in 20 s.**
- **Can't connect** (red): the server refused the login. Fix the cause, then click **Try Again**.

## What the explanation means

| The disk's page says | What to do |
|---|---|
| **The server can't be reached right now.** | Check that the server is on, its iSCSI service is running, and the network between them works. BeamDisk keeps trying. |
| **The server doesn't allow this Mac to use this target.** | Add this Mac's initiator name to the target's allowed initiators on the server. The page shows the name with a **Copy** button. Then click **Try Again**. |
| **The server refused the CHAP user name or secret.** | Remove the disk, then add it again with the right CHAP details. |
| **This target needs CHAP.** | Remove the disk, then add it again with its CHAP user name and secret. |
| **This target doesn't use CHAP, but CHAP is set for it here.** | Remove the disk, then add it again without CHAP. |
| **The server no longer has this target.** | The target was removed or renamed on the server. Remove the disk, or put the target back. |
| **BeamDisk needs the disk's size to be a multiple of 16 KiB.** | Change its size on the server to a whole number of MiB or GiB. |
| **The CHAP secret couldn't be read from the keychain.** | Remove the disk, then add it again. |
| **Another computer is using this disk.** | It connects here once the other computer lets go of it. See [One Mac per disk](https://beamdisk.app/docs/disks/exclusive-access/). |
| **BeamDisk stopped twice while checking what's on this disk (damaged data?).** | The disk's contents may be damaged. **Try Again** checks it again. |

To change a disk's CHAP details, remove it and add it again: its data stays on the server. See [Connect, eject and remove disks](https://beamdisk.app/docs/disks/connect-and-eject/).

## A changed setting was refused

Some settings, such as CRC32C digests, apply when a disk next logs in to its server. If the server refuses the new setting, the disk keeps working with the previous one, and BeamDisk says so, with when: on the disk's page, under **New settings** (**The server refused them at 11:09 AM: it doesn't support CRC32C header digests. The previous ones stay in use.**), and in Settings → Connection. Choose a setting the server supports, such as **When the target asks**.

## Several disks at once

If every disk on one server stops connecting at once, look at the server first: its iSCSI service, its network, or a change to its allowed initiators or CHAP settings.

Still stuck? [Get help](https://beamdisk.app/docs/troubleshooting/get-help/).