Selfhosted

40183 readers

631 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

New Zimaboard, weird ass SMB issue (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

Got a new Zimaboard yesterday, running through using it to migrate the Plex workload off of my Synology NAS- but running in to a strange issue.

When mounting the NAS (which I'm still using for the storage of my media) everythiing works great, authenticates with a user I created just for it, finds the shares and displays them correctly, but entering any of the shares, they "appear" to be empty in CasaOS's file browser, which of course they're not.

Things I've tested- connected to my NAS with that same user credential in a VM, shares appear/work correctly. User has read/write permissions inside those folders.

Triple-checked file permissions on the NAS- all good from test VM.

Updated the Zimaboard's Debian OS from SSH, updated CasaOS afterward. Rebooted numerous times.

Anyone here familiar with CasaOS that ships on Zimaboard who might be able to enlighten me?

top 5 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

I'm no expert, but this sounds like a permissions issue.

Check what permissions your user has on that folder from both connections (local, remote).

My bet is you have a user in your smbconfig that has read permission on a folder that generic users don't have, and while you can see the folder as a new generic user, you cannot see its contents.

I think this because I have run into similar problems when trying to sync my media to a backup drive. Backup drive was all like "yup, got all the folders. Shame they're empty! So weird" no compy, there's 8tb in those folder let's try again...

As I said In no expert, very possible Im completely off base. Good luck!

Edit: I know you said you triple checked. But for my story, my machine had permission, but my new backup drive did not. So, I'd quadruple check. Like, try temporarily removing all permissions and see if it works. If it does, you know it was permission based.

[–] [email protected] 1 points 1 year ago

Will do.

[–] [email protected] 0 points 1 year ago (1 children)

I'm running casa on Debian on a pi 4. I have three drives attached, two in an external enclosure and one nvme in an Argon nvme case. The last update the two external drives disconnected and won't reconnect. Last night I took another update and today the nvme is disconnected and doesn't show up in lsblk of fdisk. I'm pretty sure I'm gonna stop using casa all together. Two updates in a row and three drives lost.

[–] [email protected] 1 points 1 year ago (1 children)

Yikes- those are all local drives huh? Physically attached to the machine?

Were you using the "Combine storage" function?

[–] [email protected] 0 points 1 year ago

Yeah they're USB attached. I was using the combine storage function on the two external drives but not the nvme. I figured that was the issue for the two in the enclosure but the nvme going mia after this latest update is suspect.

load more comments