November 22, 20178 yr Hi, I'm fairly new to using unRAID and have just migrated to a new Ryzen based machine & upgraded to 6.4 and are seeing some weird messages in the log related to the mover process: Nov 23 00:03:21 unraid Docker Auto Update: No updates will be installed Nov 23 03:40:01 unraid root: mover: started Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3030]: segfault at 0 ip 000000000040272c sp 00007fffb938d900 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3029 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3030 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3037]: segfault at 0 ip 000000000040272c sp 00007ffd0b95fee0 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3036 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3037 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3047 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3048 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid kernel: move[3048]: segfault at 0 ip 000000000040272c sp 00007ffd88ddb930 error 6 in move[400000+4000] Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3054 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid kernel: move[3055]: segfault at 0 ip 000000000040272c sp 00007ffc3af66130 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: 3055 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid root: move_object: /mnt/disk2/downloads: No such file or directory Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3065]: segfault at 0 ip 000000000040272c sp 00007ffd3bb7e220 error 6 in move[400000+4000] Nov 23 03:40:18 unraid root: /usr/local/sbin/mover: line 69: 3064 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:18 unraid root: 3065 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:18 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:18 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:18 unraid root: /usr/local/sbin/mover: line 69: 3086 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:18 unraid root: 3087 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:18 unraid kernel: move[3087]: segfault at 0 ip 000000000040272c sp 00007ffd108742d0 error 6 in move[400000+4000] Nov 23 03:40:18 unraid root: mover: finished I have 3 drives added to the array, but haven't configured a cache or parity drive yet, as I want to confirm its running ok before I start pulling drives out of my old server. Please advise if I need to post any more information? Thanks Edited November 22, 20178 yr by Zylan
November 22, 20178 yr 33 minutes ago, Zylan said: Hi, I'm fairly new to using unRAID and have just migrated to a new Ryzen based machine & upgraded to 6.4 and are seeing some weird messages in the log related to the mover process: Nov 23 00:03:21 unraid Docker Auto Update: No updates will be installed Nov 23 03:40:01 unraid root: mover: started Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3030]: segfault at 0 ip 000000000040272c sp 00007fffb938d900 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3029 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3030 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3037]: segfault at 0 ip 000000000040272c sp 00007ffd0b95fee0 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3036 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3037 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3047 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid root: 3048 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid kernel: move[3048]: segfault at 0 ip 000000000040272c sp 00007ffd88ddb930 error 6 in move[400000+4000] Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid root: /usr/local/sbin/mover: line 69: 3054 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:01 unraid kernel: move[3055]: segfault at 0 ip 000000000040272c sp 00007ffc3af66130 error 6 in move[400000+4000] Nov 23 03:40:01 unraid root: 3055 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:01 unraid root: move_object: /mnt/disk2/downloads: No such file or directory Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:01 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:01 unraid kernel: move[3065]: segfault at 0 ip 000000000040272c sp 00007ffd3bb7e220 error 6 in move[400000+4000] Nov 23 03:40:18 unraid root: /usr/local/sbin/mover: line 69: 3064 Broken pipe find "${SHAREPATH%/}" -depth Nov 23 03:40:18 unraid root: 3065 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:18 unraid shfs: error: move_object: No such file or directory (2): get_times: Nov 23 03:40:18 unraid shfs: error: move_object: No such file or directory (2): lstat: Nov 23 03:40:18 unraid root: /usr/local/sbin/mover: line 69: 3086 Done find "${SHAREPATH%/}" -depth Nov 23 03:40:18 unraid root: 3087 Segmentation fault | /usr/local/sbin/move Nov 23 03:40:18 unraid kernel: move[3087]: segfault at 0 ip 000000000040272c sp 00007ffd108742d0 error 6 in move[400000+4000] Nov 23 03:40:18 unraid root: mover: finished I have 3 drives added to the array, but haven't configured a cache or parity drive yet, as I want to confirm its running ok before I start pulling drives out of my old server. Please advise if I need to post any more information? Thanks Please to to Tools/Diagnostics and post the resulting diagnostics.zip file.
November 23, 20178 yr 37 minutes ago, Zylan said: Diagnostics attached unraid-diagnostics-20171123-0921.zip Thanks. Does this directory exist? /mnt/cache If so, did you manually create it?
November 23, 20178 yr 7 minutes ago, Zylan said: Correct, it exists and contains some appdata files. I didn't create it. Well that's the problem. What is in /mnt/cache/appdata? Probably there is a plugin or docker container "hard coded" to use "/mnt/cache/appdata" and if it doesn't exist, creates it. Probably using something like: mkdir -p /mnt/cache/appdata when it should be doing mkdir /mnt/cache/appdata and then do something if it fails (meaning there is no cache device). The /mnt/cache directory is only created when there is a cache disk, and it serves as the mount point. The 'mover' script looks for this directory to determine if a cache disk exists. Normally this isn't an issue, but agreed, the 'move' operation should at least not segfault. (but there is no harm to your server because of the segfault) The simple way to fix this for you is to add a cache device or remove the misbehaving app.
Archived
This topic is now archived and is closed to further replies.