Skip to content
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

[Bug] Can't get DASHDOT_FS_DEVICE_FILTER to work #1063

Open
bdog720 opened this issue Jun 26, 2024 · 0 comments
Open

[Bug] Can't get DASHDOT_FS_DEVICE_FILTER to work #1063

bdog720 opened this issue Jun 26, 2024 · 0 comments

Comments

@bdog720
Copy link

bdog720 commented Jun 26, 2024

Description of the bug

I'm running Dash. on windows from host, I tried running it via Docker but I couldn't get it to see my actual disk drives. I've got it running on windows from source just fine but I can't get the DASHDOT_FS_DEVICE_FILTER variable to filter out my boot drive

What am I missing?

This is how I'm setting the variable, I've tried with and without quotations
set DASHDOT_FS_DEVICE_FILTER=\\\\.\\PHYSICALDRIVE0,\\\.\\PHYSICALDRIVE0,\\.\\PHYSICALDRIVE0,\.\\PHYSICALDRIVE0,.\\PHYSICALDRIVE0,\\PHYSICALDRIVE0,\PHYSICALDRIVE0,PHYSICALDRIVE0

This is my config (I'm trying all variants of the device name because I can't get any of them to work
"fs_device_filter": [ "\\\\\\\\.\\\\PHYSICALDRIVE0", "\\\\\\.\\\\PHYSICALDRIVE0", "\\\\.\\\\PHYSICALDRIVE0", "\\.\\\\PHYSICALDRIVE0", ".\\\\PHYSICALDRIVE0", "\\\\PHYSICALDRIVE0", "\\PHYSICALDRIVE0", "PHYSICALDRIVE0" ]

How to reproduce

No response

Relevant log output

storage: [
    {
      size: 256052966400,
      disks: [
        {
          device: '\\\\.\\PHYSICALDRIVE0',
          brand: 'Samsung',
          type: 'SSD'
        }
      ]
    },
    {
      size: 2000396321280,
      disks: [
        {
          device: '\\\\.\\PHYSICALDRIVE1',
          brand: 'Seagate',
          type: 'HD'
        }
      ]
    }
  ]

Info output of dashdot cli

INFO
=========
Yarn: 3.7.0
Node: v20.15.0
Dash: unknown

Cwd: C:\Program Files\Dashdot\dashdot
Hash: 609c1103070348d707df4ccce5c930df91168f96
Platform:
Docker image: $DASHDOT_IMAGE
In Docker: false
In Docker (env): $DASHDOT_RUNNING_IN_DOCKER
In Podman: false

What browsers are you seeing the problem on?

Chrome

Where is your instance running?

Windows Server

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant