Search Results
7/11/2025, 3:34:14 PM
>>105867294
>you've only got 1 slash in the error which means it's being interpreted as escaping a character and you need to double up
Ah, that was it. Adding a single open and close quote around the drive path fixed it. I can now read/write files to the drive and share them with my linux install.
Thanks, anon. Seems like such a silly error, now that I think about it. I normally quote drive paths by default in native linux. Dunno how I missed that.
>>105868835
Just for storage. It's an internal HDD connected by SATA. In my old setup, I had it formatted to NTFS when Windows was my main OS, and my backup Linux OS could still read and write to the drive. Now that Windows is my backup OS, I wanted the drive to be formatted to something Linux could use more efficiently but still let Windows be able to read/write to it if needed. This new setup works perfect now.
>you've only got 1 slash in the error which means it's being interpreted as escaping a character and you need to double up
Ah, that was it. Adding a single open and close quote around the drive path fixed it. I can now read/write files to the drive and share them with my linux install.
Thanks, anon. Seems like such a silly error, now that I think about it. I normally quote drive paths by default in native linux. Dunno how I missed that.
>>105868835
Just for storage. It's an internal HDD connected by SATA. In my old setup, I had it formatted to NTFS when Windows was my main OS, and my backup Linux OS could still read and write to the drive. Now that Windows is my backup OS, I wanted the drive to be formatted to something Linux could use more efficiently but still let Windows be able to read/write to it if needed. This new setup works perfect now.
Page 1