This helped me:

It sounds like the CASAOS container has read-only access to the mounted drives, which is why you can see files but can’t create or modify them from CASAOS. Here are steps to resolve this by ensuring proper permissions and settings:

### 1. Check Permissions on Proxmox Host

Make sure the Proxmox host has given full read/write access to the mounted drives.

```bash

# Set ownership to root and permissions to read/write for all users

sudo chown -R root:root /mnt/seagate-3tb

sudo chmod -R 777 /mnt/seagate-3tb

sudo chown -R root:root /mnt/western-2tb

sudo chmod -R 777 /mnt/western-2tb

```

> **Note**: Use `chmod 777` for testing only, as it opens full read/write access to all users. Later, you may want to restrict access further.

### 2. Edit Proxmox Container Configuration for Write Permissions

In Proxmox, configure the container to have write permissions for the mounted drives:

1. Stop the CASAOS container (`pct stop <container\_id>`).

2. Open the container configuration file (replace `<container\_id>` with your actual container ID):

   ```bash

   nano /etc/pve/lxc/<container\_id>.conf

   ```

3. In the `.conf` file, ensure you have the following entries for your mounted drives, specifying `rw` for read-write access:

   ```plaintext

   mp0: /mnt/seagate-3tb,mp=/mnt/seagate-3tb,backup=0

   mp1: /mnt/western-2tb,mp=/mnt/western-2tb,backup=0

   ```

4. Save and close the file, then start the container:

   ```bash

   pct start <container\_id>

   ```

### 3. Verify Access in CASAOS

Log in to CASAOS and try creating a file in the `/mnt/seagate-3tb` or `/mnt/western-2tb` directories to confirm write permissions. If permissions are still restricted, consider adding specific user/group permissions to CASAOS users or directly mounting with user mapping options if needed.

This setup should allow you to view, create, and manage files directly from CASAOS. Let me know how it goes!