Shared root of drive, upgraded, now shares broken

TrueNAS General
1

I was on FreeNAS 11.2U7 and I created an SMB share of the root of a pool. There were several directories (not datasets) created after this. Now I have upgraded to TrueNAS, imported the pool, and I cannot get the shares to work. Windows says the password is incorrect every time. Im virtualized with the HBA passedthrough if that matters.

What do I need to do to fix this?

Thanks.

2

In freenas it was possible to use the root dataset and root as user for smb shares. That has been changed to improve security. You now need a dedicated smb user and have to create a child dataset for smb shares. Then you have to move all your data from the root dataset to the child dataset. Since you can’t share it out anymore you probably have to use an ssh session and tmux so that the copy process can keep running in the background

1 Like
6

Thank you. Should I just use mv?

7

Yes use mv, but do it in a midnight commander session so it keeps running in the background and doesn’t stop when the shell or ssh session is cut

2 Likes
8

Ty sir. Running now.

Since I got you here, I have a single drive that I mirrored from a failing single drive vdev and it has some zfs errors after the resilver and removal of the bad drive. Since I cannot recover those files, how do I remove those bad files and flag the pool as healthy again?

9

just rm them and run a scrub?

10

from shell if you use

sudo zpool status -v

it should tell you which files are affected.
But if it’s metadata that’s affected it’s propably a destroy pool and rebuild from backup szenario. Hard to know without the output of the command i posted…

1 Like
11

just movies and music. i rm’d them and the list tunred into some variables so im running a scrub now. hoping that’ll make the list empty instead. i dont know about the unhealthy flag tho

12

Scrub cleared the list, then zpool clear marked the pool as healthy again. Thank you again.

1 Like
13

Setting up the new SMB share and:

FAILED
[EPERM] Filesystem Persmission on path /mnt/vol1 prevent access for group “mygroup” to the path /mnt/vol1/Media. This may be fixed by granting the aforementioned group execute permissions on the path: /mnt/vol1.

Is it jacked up from when I shared the root before? Do I need to chmod something?

14

according to this post

yes it can be solved by chmod