-
Notifications
You must be signed in to change notification settings - Fork 237
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
WinBtrfs cannot read any content of the home directory #722
Comments
Update: Turning off "Allow files on this drive to have contents indexed in addition to file properties" in the drive properties as stated in issue #705 didn't do anything. |
If your filesystem is corrupted so much that Linux is unable to mount it, it's unlikely that this driver will do any better. What does |
I have attempted to run said command, but neither PowerShell nor the regular Command Prompt (both run as administrator) seem to be able to find the related executable. Is there another way to check? |
Update: Neither using Windows on-board checking tool (via the Properties) nor the scrubbing feature of WinBtrfs (via the Properties) helped. |
Update: It appears that the |
I recently was able to recover nearly all files from a partly corrupted btrfs filesystem using btrfs restore with the appropriate flags, but YMMV. |
Description
I want to recover some files stored on my BTRFS-formatted SSD containing an openSUSE Tumbleweed installation which became unbootable almost immediately after I had reinstalled Windows 11 onto an NVMe SSD I had bought. The files I primarily want to recover are my Minecraft saves - which are on my
/home/nicolas
(F:\home\nicolas
on Windows if I didn't have the issue) directory - which Windows Explorer couldn't recognise. The DiskInternals Linux Reader was able to recognise said directory, but recovering the files from there would cost money I simply do not have right now.The Linux Reader recognised the directory...
...while Windows didn't.
Expected behaviour
Assuming the drivers are installed correctly, the
/home/nicolas
directory should show up.Steps to reproduce
F:\home
(replace F with the actual drive letter) directory.Environment
The text was updated successfully, but these errors were encountered: