Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fresh MinIO install on K8s with Helm: "unable to use the drive, drive not found" #2382

Closed
butlergroup opened this issue Jan 11, 2025 · 4 comments
Assignees

Comments

@butlergroup
Copy link

butlergroup commented Jan 11, 2025

(removed)

@ramondeklein
Copy link
Contributor

ramondeklein commented Jan 12, 2025

First of all... Using NFS shares with MinIO is strongly discouraged. It's preferred to use DirectPV to connect to local disks.
Second... It look like you are using two nodes with a single disk, which is an unsupported scenario (for production) as well.

Manually creating persistent volumes is not a scenario where MinIO operator was designed for. Why are you creating your own persistent volumes? MinIO just expects an empty directory when you attach a persistent-volume. You may want to shell into the MinIO container and see what's actually is mounted under /export/data.

If the problem is that nodes can see their own disk, but cannot see the other instance, then shell into the pod and try to curl the other node. If it doesn't work, it's a networking issue.

@ramondeklein
Copy link
Contributor

You may want to try to create a tenant the "normal" way. Make sure it works and check the differences...

@cniackz
Copy link
Contributor

cniackz commented Jan 13, 2025

I have done this in the past by manually creating the PVs, which then bound to the PVCs, and everything worked fine. However, as Ramon mentioned, this is a manual process we should avoid because it is time-consuming and prone to errors.

This is precisely why we introduced DirectPV—to address the challenge of providing persistent volumes efficiently.

Now, regarding your error: drive not found. When this error occurs, it could also be due to a network issue. If that’s the case, it is unrelated to the manual process described earlier. I’m not certain what specific firewalld rule might block the traffic, but I suggest trying an alternative approach. Rather than modifying the firewall rules, please use DirectPV and check if the issue persists.

Additionally, run this command:

mc admin info myminio

This will help determine if only some disks are offline or if all of them are. In cases of network issues, it’s common to see some disks offline while others remain online. This could provide valuable clues to identify the root of the problem.

@butlergroup
Copy link
Author

butlergroup commented Jan 13, 2025

(removed)

@butlergroup butlergroup closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants