hard drive permission issues
mornin.
i have been using Warp terminal (great help to me btw) to help me find a memory leak... that didnt work at first cause i had just restarted... and it didnt work when the leak was active cause it had gobbled up al of my 16 and the system just locked.
then i decided to have Warp help out my hard drive issues... slow read write speeds copying from one nvme to another, files not saving and generally not being able to access drives...
So i had it try run a smart test.
In the end it came up with this:
"After several troubleshooting steps, it appears we're facing a fundamental permission issue that prevents access to the NVMe devices, likely due to the environment we're running in. Here's what we've discovered:
• WSL (Windows Subsystem for Linux) environments
• Containerized environments
• Environments with certain security policies
To resolve this, you might need to:
I formatted the drives during the installation with the utility on the ISO and I am logged into an admin profile.
Any human brains around with an idea what I did wrong?
i have been using Warp terminal (great help to me btw) to help me find a memory leak... that didnt work at first cause i had just restarted... and it didnt work when the leak was active cause it had gobbled up al of my 16 and the system just locked.
then i decided to have Warp help out my hard drive issues... slow read write speeds copying from one nvme to another, files not saving and generally not being able to access drives...
So i had it try run a smart test.
In the end it came up with this:
"After several troubleshooting steps, it appears we're facing a fundamental permission issue that prevents access to the NVMe devices, likely due to the environment we're running in. Here's what we've discovered:
- We confirmed the presence of two NVMe devices (/dev/nvme0n1 and /dev/nvme1n1) using nvme list
- We're running in a non-systemd environment (possibly a container or WSL)
- Both smartctl and nvme commands are failing with permission denied errors, even with sudo
- SELinux is not the cause as it's not installed
• WSL (Windows Subsystem for Linux) environments
• Containerized environments
• Environments with certain security policies
To resolve this, you might need to:
- If using WSL, access the drives from Windows directly using Windows-native tools
- If in a container, ensure the container has the necessary privileges (--privileged flag) and device access
- Run these commands on the host system directly
- Check with your system administrator about any security policies that might be restricting device access
I formatted the drives during the installation with the utility on the ISO and I am logged into an admin profile.
Any human brains around with an idea what I did wrong?
