Selfhosted

60024 readers

980 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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

submitted 2 years ago by Reygle@lemmy.world to c/selfhosted@lemmy.world

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?

you are viewing a single comment's thread
view the rest of the comments

[–] dartanjinn@lemm.ee 0 points 2 years 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.

[–] Reygle@lemmy.world 1 points 2 years ago (1 children)

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

Were you using the "Combine storage" function?

[–] dartanjinn@lemm.ee 0 points 2 years 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.