TrueNAS-12.-U8.1
Disk pools: /mnt/pool01
Dataset: ds1 (pool01/ds1
SMB Share: /mnt/pool01/ds1
Servername \\TRUENAS
I had a sudden power outage, and my server went down hard. Fortunately, it's a pretty passive box, nothing's been written to it in months. It's used as a media server, and even at that, no one's even read from it. Kodi decided to go bonkers, and I was looking at another media player software that would run reasonably well on the Android TV. The power came back up, and when I rebooted, I was able to scan the pool for errors, and bring it back on line. (don't ask me to recall the command used, I found it here.
I can see the \\TRUENAS server in network neighborhood, and I can see the \ds1 share, but it fails to map a drive, or if at maps a drive, I can't browse it.
While poking around and trying to troubleshoot this, I've noticed that there's a "ROOT cannot be an SMB user." new rule. While trying to verify *that*, I ran into a problem:
Editing the share's Filesystem ACL or running getfacl causes either the GUI or the console to hang. There's only one share and 3 users, so I can't see that this is some huge datamining exercise for the system.
Rather than trying to un-FUBAR that, I thought it might be easier to simply re-do the share, somehow, and have some confidence that the table/database is now uncorrupted.
I haven't done anything yet!
How do you go about deleting and recreating the share, but keeping the file system (and files) in place? I can even delete all of the users (there's only 3, I think) and the groups (3 made while trying to figure things out.)
Disk pools: /mnt/pool01
Dataset: ds1 (pool01/ds1
SMB Share: /mnt/pool01/ds1
Servername \\TRUENAS
I had a sudden power outage, and my server went down hard. Fortunately, it's a pretty passive box, nothing's been written to it in months. It's used as a media server, and even at that, no one's even read from it. Kodi decided to go bonkers, and I was looking at another media player software that would run reasonably well on the Android TV. The power came back up, and when I rebooted, I was able to scan the pool for errors, and bring it back on line. (don't ask me to recall the command used, I found it here.
zpool -F
or something like that.)I can see the \\TRUENAS server in network neighborhood, and I can see the \ds1 share, but it fails to map a drive, or if at maps a drive, I can't browse it.
While poking around and trying to troubleshoot this, I've noticed that there's a "ROOT cannot be an SMB user." new rule. While trying to verify *that*, I ran into a problem:
Editing the share's Filesystem ACL or running getfacl causes either the GUI or the console to hang. There's only one share and 3 users, so I can't see that this is some huge datamining exercise for the system.
Rather than trying to un-FUBAR that, I thought it might be easier to simply re-do the share, somehow, and have some confidence that the table/database is now uncorrupted.
I haven't done anything yet!
How do you go about deleting and recreating the share, but keeping the file system (and files) in place? I can even delete all of the users (there's only 3, I think) and the groups (3 made while trying to figure things out.)