TibixDev
[Bug] WinBoat/Docker messing around with my drives on /media/USER folder
What version of WinBoat are you running?
v0.8.7
Your Environment
Distro: KDE neon Environment: KDE plasma 6.5 running on Wayland FreeRDP: flatpak 3.17.2
Steps to Reproduce / Context
Greetings.
This problem is a little bit complex, sorry for writing a lot! Also I marked it as WinBoat/Docker because I don't know which one is causing this.
I'm using a desktop setup with 3 drives: One SSD (main drive), and two HDD's (data and other stuff). I use one of my HDD to store downloads and data, the other one for games.
First, I downloaded an LTSC ISO of Windows 10 to do a custom ISO install, so it was stored on the HDD I use for downloads. Then, I performed the WinBoat install and everything went OK, there were no errors, no problems.
Second, I installed all my programs and stopped the VM from WinBoat. Closed it and turned off my system.
Third, I turned on my system next day and surprisingly, my MEGAsync app wasn't detecting the synced directory for it. Went to check and the directory was there, I could open it from my file manager normally. So what now? I went back one folder (drives are mounted on media folder so /media/USER)
Fourth, I found in that folder three drives in this way (it should only display two). example: /media/USER/HDD /media/USER/HDD1 /media/USER/DATA
Interestingly, in the HDD folder, there is another folder created at boot which has the name of the Windows ISO I used, while on the HDD1 all the data remained intact, including my Windows ISO per se.
I tested it with my other drive and it behaves the same. Screenshots:
My drives:
How they should normally appear on /media/USER and how they appear before reboot:
How they appear after rebooting the system:
Insides of the duplicated "volume":
Insides of the REAL volume:
Screenshot of WinBoat log (the only error over there, line 407 on provided winboat.log file):
Logs
Expected Behavior
WinBoat/Docker should not make any changes to my drives directories in my system, everything works well and system is happy.
Current Behavior
WinBoat/Docker is messing around with my drives directories in my system on every boot and I have to manually delete the drive folder or delete the VM to get my system working as it was again.
Possible Solution
- Forcing users to use an ISO located in the main drive (for example, /home/<USER>/windows.iso) instead of another drive. When installed like that, no problems arise (I have it like that in my laptop).
2. WORKAROUND to anyone having this problem (until it's fixed/patched).
I'M NOT RESPONSIBLE FOR DATA LOSS, FOLLOW THE STEPS THOROUGHLY AND DOUBLE CHECK WHAT ARE YOU DOING IN YOUR SYSTEM.
- UNMOUNT the affected drive on your file manager so you can't lose your data there.
- Open your terminal.
- (Change <USER> with your user), then type and run:
cd /media/<USER>
- (Change <DRIVE> with the name of the affected drive) then type and run:
sudo rm -rf <DRIVE>
- You can mount your drive again. It will mount normally and your programs (including WinBoat will run again)
If you are more comfortable, you can also do the same with your file manager. Be sure to run it as administrator in the way it's intended to. Different files manager usually have different methods so above steps should work on any distro.
Maybe it's a Docker problem but I'm not sure.
Quality Notice
- [x] I have checked the issue tracker and verified that this bug is a unique case.
This is likely a duplicate of #296. So this should also be fixed by #315 *correct me if Im wrong
This is likely a duplicate of #296. So this should also be fixed by #315 *correct me if Im wrong
Hi there and thanks for pointing those out.
I would say it's not a duplicate but it could be related because I haven't deleted the iso file used for installation, it is just on another drive.
The symptoms are different AFAIK. On #296 deleting the iso even from home folder for example makes the WinBoat container to not boot up (which I've experienced too!).
In my case, I have the iso file on another physical drive in the system, which are mounted on the /media/user folder. On boot, the iso is still there but WinBoat creates another "ghost volume" in the folder, as provided on screenshots.
It only happens when WinBoat is set up (Windows installed) and doesn't happen if the iso file is on any other directory (like /home/user folder).
That's why I think it could be a problem with Docker but I'm unsure.