docker : /mnt/user: file exists.

[Plexi09]

Hi, there,
When I install or modify a docker container (any container), it tells me something like this 

docker: Error response from daemon: error while creating mount source path '/mnt/user': mkdir /mnt/user: file exists.

Because of this, when I launch a container, it tells me 

Execution error
Server error

 

I can't get anything to work, please help me.

tower-diagnostics-20231205-1737.zip tower-syslog-20231205-1550.zip

[itimpi]

You have file system corruption on disk1.  You should run a check filesystem on disk1 to check/repair this corruption.

[Plexi09]

Hello, sorry for the late reply.

I did the ckeck, but i'm not sure what to do next.

Here is the result of the check
https://paste.gloriouseggroll.tv/?1d4ec01307ff370b#CgUEo1mCfk9EhAegutDiEqNBbHazWc46NS3B71fyXfFF
The disk is in XFS.

I'm curently reading this : https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/#xfs_repair

[JorgeB]

Run it again without -n or nothing will be done.

[Plexi09]

ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

 

Should i do it ?

[trurl]

6 minutes ago, Plexi09 said:

If you are unable to mount the filesystem

Unraid has already determined the filesystem is unmountable.

6 minutes ago, Plexi09 said:

then use the -L option to destroy the log and attempt a repair

You have no other option

[Plexi09]

Ok now i get that 

fatal error -- couldn't map inode 281491201, err = 117

 

full log : https://paste.gloriouseggroll.tv/?b5e751f69c2fb1a2#8G2DogpgYnHHBm8aJK7qkr97j6bZrCArBJs5sDfb6YZv

[trurl]

43 minutes ago, Plexi09 said:

I'm curently reading this : https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/#xfs_repair

You should be reading this

https://docs.unraid.net/unraid-os/manual/storage-management/#checking-a-file-system

 

@SpencerJ seems like the check filesystem link doesn't go to the current documentation

 

@Plexi09 Are you running the check from the webUI or from the command line? Easy to get the command wrong, better to use the webUI.

[SpencerJ]

49 minutes ago, trurl said:

You should be reading this

https://docs.unraid.net/unraid-os/manual/storage-management/#checking-a-file-system

 

@SpencerJ seems like the check filesystem link doesn't go to the current documentation

 

@Plexi09 Are you running the check from the webUI or from the command line? Easy to get the command wrong, better to use the webUI.

 

check filesystem link has been updated.

[Kev600]

I've had this issue twice in two consecutive days whilst removing and reinstalling a docker container..

 

UR: 7.0.0 Beta 2

 

XFS checked successfully on all drives.

 

Reboot resolved it yesterday. About to reboot again now...

Appears to relate to 

 

Logs attached.

kbnas-syslog-20240831-2003.zip kbnas-syslog-20240830-2358.zip

[JorgeB]

2 hours ago, Kev600 said:

Appears to relate to

Yep.