# Changelog v1.18.1

**URL:** <https://forum.storj.io/t/changelog-v1-18-1/10525>\
**Category:** STORJLINGS\
**Tags:** official-changelog\
**Created:** [December 3, 2020, 2:49pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525 "2020-12-03T14:49:07Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\
**Post date:** [December 4, 2020, 6:53pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/21 "2020-12-04T18:53:59Z")

</div>

yeah because it is uncommon to have a changelog and no update. And by the time you get the uptime, you have forgotten about the changelog 😃

---

<div class="post-metadata">

**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:** [December 4, 2020, 7:41pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/22 "2020-12-04T19:41:44Z")

</div>

just run it without `-d`. It will print errors to console

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_449c533f586939b6e5f246632a46421f.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [December 4, 2020, 8:42pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/23 "2020-12-04T20:42:28Z")

</div>

is it in cmd or must run in power shel? tried in cmd got error

---

<div class="post-metadata">

**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:** [December 4, 2020, 8:56pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/24 "2020-12-04T20:56:51Z")

</div>

In the cmd, but you should either use a full path with quotes or change the current location to the binary location

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_449c533f586939b6e5f246632a46421f.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [December 4, 2020, 9:37pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/25 "2020-12-04T21:37:32Z")

</div>

So as i found in help it shold be somethink like this  
storagenode.exe setup --config-dir D:\  
then it wil make there map storage with default conf and all databases is it posible that it dont make this folder storage, i just then need to add this by defauld to path in config.

---

<div class="post-metadata">

**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:** [December 4, 2020, 10:21pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/26 "2020-12-04T22:21:46Z")

</div>

Yes, add the `--storage.path D:\`

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:18am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/27 "2020-12-05T02:18:42Z")

</div>

Where is the test file located and what is it named?  
Will it be created automatically during upgrade for existing nodes running on docker in linux?

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [December 5, 2020, 2:22am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/28 "2020-12-05T02:22:48Z")

</div>

> [@mike](#):
>
> Will it be created automatically during upgrade for existing nodes running on docker in linux?

As you can see it ⬇

> [@littleskunk](#):
>
> No action required for old docker nodes. You can keep your current docker run command.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:27am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/29 "2020-12-05T02:27:01Z")

</div>

Well - yes and no. It could mean that only new nodes after this release will receive this feature and existing nodes will continue to monitor the same way they’re doing today…  
(Wouldn’t make much sense tho’)

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 5, 2020, 2:32am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/30 "2020-12-05T02:32:52Z")

</div>

It means unless you are new and start the node with the new command it wouldnt make a difference. Or if you stop the node removed container and started node with the new command.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:37am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/31 "2020-12-05T02:37:22Z")

</div>

That could contradict @nerdatwork 's statement above… As I read your post, I would only benefit from this addition protection feature if I manually took action to start an existing node once with the `-e SETUP="true"` option once.

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 5, 2020, 2:38am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/32 "2020-12-05T02:38:22Z")

</div>

Yes which you wouldn’t do. Unless you were starting a completely new node.  
You can see the new updated command here.  
[https://documentation.storj.io/setup/cli/storage-node](https://documentation.storj.io/setup/cli/storage-node)

It doesn’t really explain if people with old docker commands should run it or not. But if your an old SNO you should already have nodes running, So you wouldn’t really need to do it less you were unsure if you were in the wrong dir or not.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:45am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/33 "2020-12-05T02:45:18Z")

</div>

Agreed.

However, the check seems to be an additional safeguard for drives becoming unavailable as RW mounts as well. (like we’ve seen so many threads on ie. USB drives, causing issues in the past)

And if so - I guess it would be beneficial for existing nodes as well.

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 5, 2020, 2:46am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/34 "2020-12-05T02:46:47Z")

</div>

I could try but unfortunately I switched my test nodes over to binary files now.

> [@mike](#):
>
> However, the check seems to be an additional safeguard for drives becoming unavailable as RW mounts as well

I believe this was already introduced before 1.18.1.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:52am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/35 "2020-12-05T02:52:24Z")

</div>

Indeed.

But as far as I recall it wasn’t based on a file check… ?

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 5, 2020, 2:53am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/36 "2020-12-05T02:53:52Z")

</div>

It was based on if the file was writeable or not and it would check every 30mins or so.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [December 5, 2020, 2:55am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/37 "2020-12-05T02:55:32Z")

</div>

> [@littleskunk](#):
>
> The old filesystem check would have continued as long as the mounted folder is read and writeable. The new check will error out because the test file is missing.

Lets wait for clarification from someone at Storj 🙂

(It’s 4am here, not sure I’m making much sense anyway… )

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 5, 2020, 2:58am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/38 "2020-12-05T02:58:52Z")

</div>

Good idea there’s been so many updates recently I honestly can’t remember all the details I’d have to go back and read every change log.

---

<div class="post-metadata">

**Author:** ![peem](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/peem/32/6323_2.png) [@peem](https://forum.storj.io/u/peem)\
**Post date:** [December 5, 2020, 11:18am UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/39 "2020-12-05T11:18:01Z")

</div>

It’s about a file “storage-dir-verification” in the database directory

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_449c533f586939b6e5f246632a46421f.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [December 5, 2020, 4:31pm UTC](https://forum.storj.io/t/changelog-v1-18-1/10525/40 "2020-12-05T16:31:04Z")

</div>

> [@Alexey](#):
>
> –storage.path D:\

Itried this ““C:\Program Files\Storj2\Storage Node\storagenode.exe””", setup --storage2.database-dir F:\ --storage.path F:\ --config-dir F:  
It works for directory put dont make databases at all

[Previous page](https://forum.storj.io/t/changelog-v1-18-1/10525.md?page=1)

[Next page](https://forum.storj.io/t/changelog-v1-18-1/10525.md?page=3)
