# Docker Node Keeps Restarting **URL:** \ **Category:** troubleshooting\ **Tags:** database\ **Created:** [July 15, 2021, 3:19am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583 "2021-07-15T03:19:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![node42](https://storj.bcdn.literatehosting.com/letter_avatar/node42/32/6_22734026db12803ebb3e059622ac3534.png) [@node42](https://forum.storj.io/u/node42)\ **Post date:** [July 15, 2021, 3:19am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/1 "2021-07-15T03:19:23Z")
My little node was doing good, then I went to check today and the dashboard would not load so I remoted in and saw it was in restarting status, checked the logs and this is what showed up, not sure how to fix this as I am still learning storj node things Error: Error starting master database on storagenode: database: unable to open database file: no such file or directory storj[.]io/storj/storagenode/storagenodedb.(\*DB).openDatabase:323 storj[.]io/storj/storagenode/storagenodedb.(\*DB).openExistingDatabase:305 storj[.]io/storj/storagenode/storagenodedb.(\*DB).openDatabases:281 storj[.]io/storj/storagenode/storagenodedb.OpenExisting:248 main.cmdRun:160 storj[.]io/private/process.cleanup.func1.4:363 storj[.]io/private/process.cleanup.func1:381 github[.]com/spf13/cobra.(\*Command).execute:852 github[.]com/spf13/cobra.(\*Command).ExecuteC:960 github[.]com/spf13/cobra.(\*Command).Execute:897 storj[.]io/private/process.ExecWithCustomConfig:88 storj[.]io/private/process.ExecCustomDebug:70 main.main:385 runtime.main:204 ---
**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 15, 2021, 8:17am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/2 "2021-07-15T08:17:08Z")
Seems your storage location have lost files or permissions. Please, stop the storagenode and check your disk for errors first. Please also check the path to the data location, maybe your mount point (disk letter) has changed and you should update your `docker run` command (to apply the changes you need to stop and remove the container, then run it again with all your parameters include changed ones). Please show result of the command: ```auto docker inspect storagenode --format "{{.Mounts}}" ``` And result of this command (replace `/path/to/data/` to your actual path to data) (bash/PowerShell): ```auto ls /path/to/data/*.db ``` If you are on Linux, please show result of the command: ```auto df -HT ``` if you are on Windows, please show result of the command (PowerShell): ```auto Get-WmiObject Win32_LogicalDisk ``` ---
**Author:** ![node42](https://storj.bcdn.literatehosting.com/letter_avatar/node42/32/6_22734026db12803ebb3e059622ac3534.png) [@node42](https://forum.storj.io/u/node42)\ **Post date:** [July 16, 2021, 2:41am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/3 "2021-07-16T02:41:51Z")
first command [{bind /root/.local/share/storj/identity/storagenode /app/identity true rprivate} {bind /mnt/storj/node /app/config true rprivate}] second command /mnt/storj/node/storage/bandwidth.db /mnt/storj/node/storage/orders.db /mnt/storj/node/storage/pricing.db /mnt/storj/node/storage/storage\_usage.db /mnt/storj/node/storage/heldamount.db /mnt/storj/node/storage/piece\_expiration.db /mnt/storj/node/storage/reputation.db /mnt/storj/node/storage/used\_serial.db /mnt/storj/node/storage/info.db /mnt/storj/node/storage/piece\_spaced\_used.db /mnt/storj/node/storage/satellites.db /mnt/storj/node/storage/notifications.db /mnt/storj/node/storage/pieceinfo.db /mnt/storj/node/storage/secret.db third command /dev/sda1 ext4 5.0T 36G 4.7T 1% /mnt/storj ---
**Author:** ![node42](https://storj.bcdn.literatehosting.com/letter_avatar/node42/32/6_22734026db12803ebb3e059622ac3534.png) [@node42](https://forum.storj.io/u/node42)\ **Post date:** [July 16, 2021, 2:44am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/4 "2021-07-16T02:44:35Z")
UUID has not changed, i could switch it in fstab from UUID to just /dev/sda1 if I issue ls a bunch, randomly I will get ls: cannot access ‘/mnt/storj/node/storage/pieceinfo.db-shm’: No such file or directory then if I run ls again its fine a drive check is underway and will update this post with the results ---
**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 16, 2021, 7:37am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/5 "2021-07-16T07:37:14Z")
This is not good. Seems your drive disappears sometimes or stop responding. This file is a database log, if it’s missed when node is working, then something wrong with the disk or something deletes these files from the storage. I would like to suggest you to check this disk for errors, check its cables and if it’s an external disk, then check the external case and power supply. Either of them is not reliable enough. It could lead to quick disqualification, so the storagenode is trying to protect you and shutdown itself when the disk is disappearing. By the way do you have a second node on this device? ---
**Author:** ![node42](https://storj.bcdn.literatehosting.com/letter_avatar/node42/32/6_22734026db12803ebb3e059622ac3534.png) [@node42](https://forum.storj.io/u/node42)\ **Post date:** [July 19, 2021, 12:45am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/6 "2021-07-19T00:45:43Z")
so I had to start over, bad partition, I wiped the drive and let it stay connected to the system for the past 48 hours and ran fsck once per day and as of today it still shows clean, hoping that fixes it otherwise a new drive it will be, current drive is only about 2 months old as I went to see if I could replace it ---
**Author:** ![node42](https://storj.bcdn.literatehosting.com/letter_avatar/node42/32/6_22734026db12803ebb3e059622ac3534.png) [@node42](https://forum.storj.io/u/node42)\ **Post date:** [July 19, 2021, 1:12am UTC](https://forum.storj.io/t/docker-node-keeps-restarting/14583/7 "2021-07-19T01:12:51Z")
bad drive, gonna order a new one, as soon as I created the folder after mount the setup command froze trying to bind