errors in log : get_filesystem_status: getxattr: /mnt/user/... No data available

[P_K]

unRaid 6.1.6

several dockers and plugins

 

Recently (I think since I added a disk with the 'unassigned devices' plugin, I'm getting following every minute in the log :

 

Jan 14 11:33:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:33:01 Tower emhttp: shareColor.7 not found

Jan 14 11:34:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:34:01 Tower emhttp: shareColor.7 not found

Jan 14 11:35:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:35:01 Tower emhttp: shareColor.7 not found

 

Everything _seems_ to be working fine but would like to know what this is.

 

I restarted my server and attach a log from after restart. I stopped all dockers between 06:56 and 07:00 but the messages kept on coming in the log.

tower-syslog-20160114-1149-1.zip

[P_K]

anybody an idea about this? Would be appreciated. I upgraded to 6.1.7 in the meantime but errors keep coming.

[dlandon]

unRaid 6.1.6

several dockers and plugins

 

Recently (I think since I added a disk with the 'unassigned devices' plugin, I'm getting following every minute in the log :

 

Jan 14 11:33:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:33:01 Tower emhttp: shareColor.7 not found

Jan 14 11:34:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:34:01 Tower emhttp: shareColor.7 not found

Jan 14 11:35:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available

Jan 14 11:35:01 Tower emhttp: shareColor.7 not found

 

Everything _seems_ to be working fine but would like to know what this is.

 

I restarted my server and attach a log from after restart. I stopped all dockers between 06:56 and 07:00 but the messages kept on coming in the log.

 

I don't think this is unassigned devices, but uninstall the unassigned devices plugin and see if the log entries stop.

[P_K]

Picking this back up as I still have the errors. Didn't look into them much as all seems to be working. I didn't remove the Unassigned Devices.

 

I think however I know what the issue is. The mount point for a disk I added in Unassigned Devices is /mnt/user/Torrents_3Tb. I read that this is wrong and it should be /mnt/disks/...  Correct ? My 'Torrents_3Tb' is showing up as a user share under the Share tab of unraid. I guess that's where the errors come from. (see attached screenshots).

 

Question : is there an easy way to change that mount point without deleting all the data on that partition ?

[trurl]

Picking this back up as I still have the errors. Didn't look into them much as all seems to be working. I didn't remove the Unassigned Devices.

 

I think however I know what the issue is. The mount point for a disk I added in Unassigned Devices is /mnt/user/Torrents_3Tb. I read that this is wrong and it should be /mnt/disks/...  Correct ? My 'Torrents_3Tb' is showing up as a user share under the Share tab of unraid. I guess that's where the errors come from. (see attached screenshots).

 

Question : is there an easy way to change that mount point without deleting all the data on that partition ?

Unmount the drive, update to the latest version of Unassigned Devices, then try mounting it again.

[P_K]

I was already on 2016.12.04 for Unassigned Devices. I stopped my array which unmounted that disk and started it again : same issue.

[trurl]

I was already on 2016.12.04 for Unassigned Devices. I stopped my array which unmounted that disk and started it again : same issue.

You need to change the mount so it isn't mounting in /mnt/user. That mountpoint should only be used by unRAID for user shares. Only bad things can happen when you hijack OS functionality like this.

 

Possibly you can unmount the drive, remove it, delete it from the list so its previous settings is forgotten about, then add it again to see if you can get UD to give it a default mounting, which should be in /mnt/disks.

 

Or just change it yourself to be in /mnt/disks if it will let you. You must get it out of /mnt/user.

[P_K]

Yes, that's what I thought indeed (that it must get out of /mnt/user). I'm not sure however how to 'remove it, delete it from the list'... I had the drive unmounted but the only thing I can do then is to click the red X next to the partition. If I hover over that it says 'delete partition'. I'm afraid I'm going to lose the data on that disk if I do so. I don't see another option to remove that disk from UD.

[trurl]

Yes, that's what I thought indeed (that it must get out of /mnt/user). I'm not sure however how to 'remove it, delete it from the list'... I had the drive unmounted but the only thing I can do then is to click the red X next to the partition. If I hover over that it says 'delete partition'. I'm afraid I'm going to lose the data on that disk if I do so. I don't see another option to remove that disk from UD.

After you unmount it, unplug it. Then it should appear in a list of drives that are not available and I think you can delete it from that list to make it forget how you had it mounted before.

[trurl]

Just checked mine. In Unassigned Devices, the list of "missing" unassigned devices is labeled Historical Devices. I think this is how it remembers what you did last time you plugged the drive in and if you remove it from that list it should let you start over.

[P_K]

That worked, thanks a lot. Got indeed rid of the errors now that my UD disk is not mounted on /mnt/user anymore.