(v0.4.3) Macintosh HD & External Drives show 404

[alexjustdoit]

Check for other issues

• I've checked for other issues, and none exist.

Issue description

Macintosh HD and any external drives I connect all show 404 when selected. They appear in Finder. Also, I noticed that whenever one is selected and 404 screen is showing, the window cannot be dragged around.

MBP M1 Pro - 16 in, 2021, 16GB model
MacOS Tahoe 26.2

Steps to reproduce

Click Macintosh HD or any external drive
404 screen shows
Try to drag window around

Platform and versions

• OS: MacOS 26.2
• Spacedrive: 0.4.3

Stack trace

Additional context

No response

Code of Conduct

• I agree to follow the Code of Conduct.

[tembo]

Investigation Summary

I've analyzed this issue and found some important context that may help diagnose the problem.

Environment Notes

The user reports running macOS Tahoe 26.2, which appears to be a pre-release/beta version of macOS (the current release cycle would typically be macOS 15.x Sequoia). This could be relevant as pre-release macOS versions may have API changes or permissions differences that affect volume detection.

Code Analysis (v0.4.3)

In v0.4.3, drives/volumes are displayed in the sidebar via the Local section (interface/app/$libraryId/Layout/Sidebar/sections/Local/index.tsx). When clicking on a volume, navigation is handled as follows:

1. Tracked volumes navigate to: location/${locationId}
2. Untracked volumes navigate to: ephemeral/${key}?path=${mount_point}

The ephemeral route (interface/app/$libraryId/ephemeral.tsx) reads the path query parameter to display the filesystem contents. If the path is malformed or missing, the route won't match properly and falls through to the 404 catch-all route.

Potential Root Causes

1. Volume path encoding issue: The navigation constructs the path as:

   `ephemeral/${key}?path=${volume.mount_point}`

   If mount_point contains special characters or is undefined, the URL could be malformed.

2. macOS Tahoe compatibility: The volume detection uses sysinfo crate and diskutil commands. macOS beta versions may return different output formats or have changed permissions for these operations.

3. Read-only system volume handling: In v0.4.3, there's logic to skip the root mount point if it's both read-only and a system volume:

   if mount_point == PathBuf::from("/") && read_only {
       continue;
   }

   On macOS Tahoe, the system volume permissions could be different.

Recommended Next Steps

1. Enable debug logging: Could you run Spacedrive from the terminal with verbose logging to capture any errors during volume detection?

   /Applications/Spacedrive.app/Contents/MacOS/Spacedrive --log-level debug

2. Check volume detection output: In the browser dev tools (View > Toggle Developer Tools), check the console for any errors when clicking on a drive.

3. Verify disk detection: Could you run this command and share the output?

   diskutil list

4. Window dragging issue: The window becoming non-draggable when showing 404 is likely a side effect - the 404 page's layout may not include the standard window chrome/draggable regions.

Questions for Reporter

• Are these volumes appearing correctly in the sidebar before clicking on them?
• Does this affect all volumes, or just specific ones (e.g., only Macintosh HD, or only external drives)?
• Did this work in a previous version of Spacedrive on the same macOS version?

---

This issue appears to be legitimate and affects the volume browsing functionality. I've tagged it for further investigation.