npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Getting an unknown error related to mkdir?

Just started happening today for me. I’ve tried force clearing the cache (got a different error) and uninstalling and reinstalling Node/npm. Any help would be appreciated :slight_smile:

Unhandled rejection Error: UNKNOWN: unknown error, mkdir 'C:\Users\philm\AppData\Roaming\npm-cache\_cacache\content-v2\sha512\e6\72'

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\philm\AppData\Roaming\npm-cache\_logs\2018-10-04T21_15_40_222Z-debug.log
Package install failed, see above.

2018-10-04T21_15_40_222Z-debug.log (161.4 KB)


So I appear to have fixed my problem. Posting what I did for posterity.

I tried uninstalling node and manually deleting the npm and npm-cache folders found in %AppData%. I noticed that even with an elevated bash and rm -rf there were files in the cache folder that would not delete. I ended up running chkdsk on the drive:

chkdsk C: /f /r /x

Booted back into windows and I could then delete the folder, reinstall node and things appear to be working again. I might have been able to just get away with the chkdsk in hindsight.