# Windows Node keeps crashing **URL:** \ **Category:** troubleshooting\ **Tags:** windows-gui, hardware\ **Created:** [July 27, 2023, 7:41am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347 "2023-07-27T07:41:17Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 27, 2023, 7:41am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/1 "2023-07-27T07:41:18Z")
Hello together, since some STORJ-Versions the Windows Node keeps crashing. It runs for like a day, then crashes and I need to restart it so it lasts another day. I checked the logs and they looked fine with all the INFO messages with sucessful up- and downloads. Can you tell what may be the reason for the constant crashes? Thanks and kind regards, ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/5_5575768a8748004e209b776fc1b2916d.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [July 27, 2023, 7:44am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/2 "2023-07-27T07:44:05Z")
can you show the logs, it is in program Files\Storj\Storagenode Search Fatal Errors ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 27, 2023, 7:44am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/3 "2023-07-27T07:44:50Z")
Just now I deleted the logs. Am still curious how they just keep increasing without limitation. Need to wait then till next crash. ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/5_5575768a8748004e209b776fc1b2916d.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [July 27, 2023, 7:46am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/4 "2023-07-27T07:46:13Z")
so when it crash, check the logs, last lines should be with errors ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 27, 2023, 7:53am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/5 "2023-07-27T07:53:53Z")
I guess it’s likely the same issue as discussed in > [@Fatal Error on my Node](https://forum.storj.io/t/fatal-error-on-my-node/22052): > > Hello Everyone, a week ago i got several errors on my main node. Maybe someone can help me to solve the problem. The Node runs on Windows 10. Thanks for your Help. 2023-03-27T05:11:25.897+0200 INFO piecestore download started {Piece ID: 7WMQ364BMF672RLAQWDD76IQ6EORNXMYXIL5PGN46I4VUT4P4JXA, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 110336, Size: 469504, Remote Address: 184.104.224.98:48702} 2023-03-27T05:11:25.916+0200 ERROR services unexp… And solution would be: 1. Stop the node 2. Check the disk for errors and fix them 3. Run defragmentation, make sure that the automated defragmentation is enabled for this drive 4. Check for timeouts after a while 5. If the node would stop with a timeout again - increase the related timeout and restart If the timeout would be too great (more or equal 5 minutes), it’s time to check what’s wrong with that drive or your setup, perhaps it has hidden issues, which should be addressed. ---
**Author:** ![daki82](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/daki82/32/1128_2.png) [@daki82](https://forum.storj.io/u/daki82)\ **Post date:** [July 27, 2023, 11:19am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/6 "2023-07-27T11:19:45Z")
Please set the node service in windows to restart after x minutes. After errors Eg: 20 Configure uptimerobot with check all x-3 min. So you dont need to do it manualy. Also follow and read Alexeys link. Most likely the timeout error. Could be databases. Post version running and screenshot of percentages audit suspension and online. Also log with the fatal line. For unskilled SNO maybe set loglevel to error or fatal. ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 27, 2023, 11:50am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/7 "2023-07-27T11:50:31Z")
Thanks for your answer. Do you mean this answer: # the minimum log level to log log.level: info then to “error” or to “fatal”? Thanks and kind regards, ---
**Author:** ![daki82](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/daki82/32/1128_2.png) [@daki82](https://forum.storj.io/u/daki82)\ **Post date:** [July 27, 2023, 11:58am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/8 "2023-07-27T11:58:20Z")
Yes. Error=much less log but still a lot for me Fatal=no logs until it crashes. Im personaly fine with that. The other option is using the logrotate script if that is on your skill level. ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 28, 2023, 7:16am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/9 "2023-07-28T07:16:42Z")
It is this error message and the node crashed again: FATAL Unrecoverable error {“error”: “piecestore monitor: timed out after 1m0s while verifying writability of storage directory”, “errorVerbose”: “piecestore monitor: timed out after 1m0s while verifying writability of storage directory\n\tstorj.io/storj/storagenode/monitor.(\*Service).Run.func2.1:169\n\tstorj.io/common/sync2.(\*Cycle).Run:160\n\tstorj.io/storj/storagenode/monitor.(\*Service).Run.func2:161\n\tgolang.org/x/sync/errgroup.(\*Group).Go.func1:75”} Am now checking the disk with the command: chkdsk E: /F It must be written in capital letters otherwise it can’t find it. 😉 Edit: How often should the defragmentation run? Once in a month is enough? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 28, 2023, 7:28am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/10 "2023-07-28T07:28:47Z")
The default schedule is fine. I do not remember what Windows uses by default, never changed it. ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 28, 2023, 7:41am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/11 "2023-07-28T07:41:13Z")
It is weekly and I didn’t change it. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 28, 2023, 7:52am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/12 "2023-07-28T07:52:05Z")
Then perhaps your node collected enough data to slow down your disk (if it doesn’t have issues though), so you may try to increase a timeout for a writeability check in your case. ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 28, 2023, 7:55am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/13 "2023-07-28T07:55:51Z")
Can you tell which line it is exactly in the config.yaml? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 28, 2023, 8:05am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/14 "2023-07-28T08:05:30Z")
You need to add a new parameter, if it doesn’t exist > [@Fatal Error on my Node](https://forum.storj.io/t/fatal-error-on-my-node/22052/109): > > `storage2.monitor.verify-dir-writable-timeout: 1m30s` save the config, and restart the node. Use a Notepad++ editor to edit the config file and do not forget to save it. ---
**Author:** ![daki82](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/daki82/32/1128_2.png) [@daki82](https://forum.storj.io/u/daki82)\ **Post date:** [July 28, 2023, 8:51am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/15 "2023-07-28T08:51:39Z")
since it will take ages to defrag anyway, i would do it once a 1TB filled up every new TB. maybe al 2-3 month ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 28, 2023, 9:01am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/16 "2023-07-28T09:01:48Z")
OK did it and pasted it above the other storage2 entries. Am now curious if it passes trough stable. The defragmentation is also still runnning but shouldn’t be a problem parallel. Right? ---
**Author:** ![daki82](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/daki82/32/1128_2.png) [@daki82](https://forum.storj.io/u/daki82)\ **Post date:** [July 28, 2023, 9:12am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/17 "2023-07-28T09:12:18Z")
on healthy node no problem. on slow node you can set it to full for less disturbing write while defrag. atm my node with databases on ssd fragments at 0.2% per 50GB disk space used.or al 2days so all 40-60 days defrag is ok i think. maybe 3 times a year also. on my 7.8TB node with databases on disk. defrag will run for one whole week. ---
**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\ **Post date:** [July 28, 2023, 9:14am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/18 "2023-07-28T09:14:08Z")
I have also like ~8 TB and with database on it. That’s why I turned it on before the defragmentation is complete. ^^ ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [July 28, 2023, 7:16pm UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/19 "2023-07-28T19:16:50Z")
Why are we discussing defragmentation here? Disable it. Vast majority of files are smaller than sector size. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 29, 2023, 7:08am UTC](https://forum.storj.io/t/windows-node-keeps-crashing/23347/20 "2023-07-29T07:08:44Z")
This is a bad practice, because the regular defragmentation will be shorter than if you run it once in several months especially on the storage location, where pieces moves very often (if it still has a free space). > [@Walter1](#): > > Am now curious if it passes trough stable. The defragmentation is also still runnning but shouldn’t be a problem parallel. Right? right, it has a low priority. > [@daki82](#): > > atm my node with databases on ssd fragments on SSD the fragmentation has almost no impact on latency, since there is no mechanical moves. > [@arrogantrabbit](#): > > Why are we discussing defragmentation here? Disable it. I strongly disagree. Unlike ext4 the NTFS fs has a serious impact on latency due fragmentation. So, please do not disable it for the storage location. To support my opinion I can invite @Vadim to confirm that defragmentation has fixed an issue with disk timeouts for his setup. [Next page](https://forum.storj.io/t/windows-node-keeps-crashing/23347.md?page=2)