Open unabletoconnect2429 opened 1 month ago
Not sure if yours is saying wrong file type, fstype btrfs, but I'm using btrfs on my cache drive and zfs on my main array, and both are unsupported. btrfs was supported on beta 2... so I don't know whats up.
Yes, Mine is doing the same error in the logs of the docker container.
Well, I'm not glad its happening, but I am glad we've narrowed it down. I know SpaceinvaderOne is a busy guy, but hopefully he gets around to this. I do wonder though, if we might have to wait until v7 is out of beta, since things keep changing.
On Mon, Oct 14, 2024 at 12:07 AM unabletoconnect2429 < @.***> wrote:
Yes, Mine is doing the same error in the logs of the docker container.
— Reply to this email directly, view it on GitHub https://github.com/SpaceinvaderOne/RetroNASinabox/issues/12#issuecomment-2410086830, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDX3RYTAWQXGJ2FCYTXENTZ3NNRHAVCNFSM6AAAAABPPOGKW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGA4DMOBTGA . You are receiving this because you commented.Message ID: @.***>
Hello,
I'm getting an error starting the VM under unraid 7beta3. Tried removing the vm config and letting it regenerate, same error as below. Any ideas?
Execution error
internal error: Child process (/usr/libexec/virtiofsd --print-capabilities) unexpected exit status 2: error: invalid value '' for '--fd ': cannot parse integer from empty string For more information, try '--help'.