External SSD btrfs volume not detected about btrfs HOT 9 CLOSED

Thank you, I'll look into it. It looks like we need to implement FSCTL_INVALIDATE_VOLUMES.

from btrfs.

I've just released version 0.5, which contains an implementation of FSCTL_INVALDIATE_VOLUMES. Can you see if it fixes your problem, please?

from btrfs.

Unfortunately the drive is still not being detected. I've also additionally scrubbed the drive and checked it for errors (none reported by btrfs-progs). Attached are more btrfs logs though it seems like nothing has really changed since version 0.4 (except during unmount/eject). I've also tried keeping the device plugged in during booting (rather than hot plug it after loading into Windows) which generated a much longer log, though still nothing appears in explorer or mountvol.

For simplicity, I've split the log into 3 files: btrfs-boot for booting a system with no btrfs partitions attached; btrfs-umount for the log that appears after the drive in question is unmounted (no log shows up when the drive is plugged in); btrfs-mboot for when the drive was already plugged in on boot (this seems to generate a lot of log with no results). The DebugView log has also been attached.

btrfs-boot.txt
btrfs-mboot.txt
btrfs-umount.txt
DebugView-v0.5.txt

from btrfs.

I've just released a new version, which improves support for removable devices. Can you try with that please?

from btrfs.

Hi, sorry for the very late reply. Unfortunately the drive is still not being detected. I have since tried to use a different external enclosure with no results. The latest log is attached below:

btrfs.txt

from btrfs.

Can you try on the version I've just released, please?

from btrfs.

Drive is still not detected in explorer. I noticed however that btrfs reports it's mounted (i.e. in registry I see the UUID listed). But explorer doesn't show it nor does any utility indicate it's presence. The closest I got was with the dir program, which gave me "The device is not ready." as opposed to a generic "The system cannot find the path specified." error. Using GPT fdisk I can read the GPT layout with the following information:

Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: 3D3CF52F-0CCA-4BA2-8CA1-DC6D89D8953E
First sector: 2048 (at 1024.0 KiB)
Last sector: 937701375 (at 447.1 GiB)
Partition size: 937699328 sectors (447.1 GiB)
Attribute flags: 0000000000000000
Partition name: ''

Indicating that the drive is readable at least to the partition table.

Prior to the version 0.7 I did try to switch the metadata profile to DUP from single to no effect.

Also, all of the above only applies when the drive is present on boot. If I hotplug the drive I get no reaction from anything (btrfs logs show nothing, registry doesn't indicate mount, dir claims no drive is mounted, etc).

The associated log from 0.7:
btrfs-0.7.txt

from btrfs.

Hmm... there's no errors in that log - it looks like Windows is mounting the volume then ignoring it.

What does diskmgmt.msc look like? Are things any different if you use GPT fdisk to change the partition type to 0700?

from btrfs.

Sorry for the lack of response, I did not get time to test changing the partition type given I had data on the disk.

However, since version 0.9 detection now works as expected for the SSD, both hotplug and during boot, therefore I'll close the issue unless you require additional diagnostic data.

from btrfs.