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
Invalid RPC response. #583
Comments
This was caused by this change in 5.2.6 - bd2c696 which causes the wrong value returned for the device file. |
It seems that all filesystems that do not refer to /dev/xxxx cause this issue. I made a workaround to search the fs by type if the backend cannot be detected. I created a pull request. |
Same issue here. |
What is the output of |
… the file system implementation. This is necessary to support union file systems. Fixes: openmediavault#583 Fixes: openmediavault#582 Signed-off-by: Volker Theile <votdev@gmx.de>
… the file system implementation. This is necessary to support union file systems. Fixes: openmediavault#583 Fixes: openmediavault#582 Signed-off-by: Volker Theile <votdev@gmx.de>
… the file system implementation. This is necessary to support union file systems. Fixes: openmediavault#583 Fixes: openmediavault#582 Signed-off-by: Volker Theile <votdev@gmx.de>
… the file system implementation. This is necessary to support union file systems. Fixes: openmediavault#583 Fixes: openmediavault#582 Signed-off-by: Volker Theile <votdev@gmx.de>
In the web GUI, I get
In
The output of the command is
|
Description of issue/question
the inclusion of the data pool (unionfilesystem) is not possible
Steps to reproduce issue
After setting up the Snapraid network I set up the unionfilesystem "data pool".
When I select the desired target under CIFS and choose the data pool for sharing, I get the mentioned error.
Versions report
Version: 5.2.6-1 (Usul)
Kernel: 5.4.0.0.bpo.2-amd64
Snapraid 5.0.5
unionfilesystem 5.1
The text was updated successfully, but these errors were encountered: