16

Hey all, recently I was doing some work on the machine where I host my plex and audiobookshelf servers and I noticed that there were 3 new devices listed in the disk manager.

All 3 of the new devices have a description along the lines of "78MB Loop Device" and lists a backing file at location /var/lib/snapd/snaps/snapd_22291.snap (not exactly but they're all similar to this). They show as unmounted and I'm not really sure what this is.

Additionally when I try to use libation to pull my latest audible books down it says it can't read my local file location folder.

I recently saw the post about the plex vulnerability (which is part of why i was doing work on it, to make sure that my auto update was working) when I noticed this and it got me worried.

Are these new devices that showed up indicative that a malicious user has accessed my system through the internet and has setup a crypto miner to run in the background on my server or is it more likely that a disk is failing and this is the first sign?

Also before anyone feels the need to say it, I know that plex is not ideal and jellyfin is better, but I have remote users that I cannot talk through troubleshooting to get jellyfin when I can tell them to just install plex on their end.

Any help would be greatly appreciated

you are viewing a single comment's thread
view the rest of the comments
[-] TheBlindPew@lemmy.dbzer0.com 3 points 2 days ago

Okay, I have used snap to install things before but it never generated these faux disks that I can't seem to delete. Would you guess that it is a temporary issue and a restart should resolve? (haven't restarted yet because I have been using the audiobookshelf and plex and haven't scheduled a maintenance window yet)

[-] frongt@lemmy.zip 2 points 2 days ago

What makes you think it's an issue? What problem is it causing? You can probably identify which snap they belong to.

[-] TheBlindPew@lemmy.dbzer0.com 1 points 2 days ago

I don't know for certain that these unexpected devices in my disk manager are causing the issue, but I noticed them at the same time as the issue with libation being unable to access the directory it normally uses and so I may be conflating 2 unrelated issues

[-] Skyline969@piefed.ca 3 points 2 days ago

I believe you are conflating two unrelated things. Snap regularly creates those devices, it’s normal, required for snaps to work, and nothing to worry about at all.

[-] TheBlindPew@lemmy.dbzer0.com 1 points 2 days ago

Oh okay, so do they go away on their own or do they persist potentially indefinitely? I have used snap in the past but had never noticed these until now. I guess I was just paranoid after the plex vulnerability news haha. Thanks.

this post was submitted on 21 Oct 2026
16 points (94.4% liked)

Selfhosted

63158 readers
589 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS