Plex won't start Dev/mapper/Plex--vg-root at 100%

Plex Media Server Desktops & Laptops
1

Hi,

This is the result of df -h

david@Plex:/$ df -h
Filesystem                 Size  Used Avail Use% Mounted on
udev                       1.6G     0  1.6G   0% /dev
tmpfs                      343M  3.1M  340M   1% /run
/dev/mapper/Plex--vg-root  216G  216G     0 100% /
tmpfs                      1.7G  8.0K  1.7G   1% /dev/shm
tmpfs                      5.0M  4.0K  5.0M   1% /run/lock
tmpfs                      1.7G     0  1.7G   0% /sys/fs/cgroup
/dev/sdc1                  1.8T  1.6T  214G  89% /media/hdd2
/dev/sdb1                  2.7T  1.9T  825G  71% /media/mainhdd
/dev/sda1                  472M  208M  240M  47% /boot
/dev/sdd1                  3.6T  2.4T  1.2T  67% /media/backuphdd
/dev/loop1                  55M   55M     0 100% /snap/core18/1754
/dev/loop3                  72M   72M     0 100% /snap/lxd/16099
/dev/loop2                  72M   72M     0 100% /snap/lxd/16048
/dev/loop0                  55M   55M     0 100% /snap/core18/1705
/dev/loop4                  31M   31M     0 100% /snap/snapd/7777
/dev/loop5                  30M   30M     0 100% /snap/snapd/8140
/dev/sdf1                  1.9T  1.6T  278G  86% /media/networkdisk
/dev/sde1                  3.7T  2.4T  1.3T  66% /media/travelplex
tmpfs                      343M  8.0K  343M   1% /run/user/1000
david@Plex:/$

I’m guessing the fact it’s at 100% is the problem Also, Ubuntu can’t update itself as I’m getting no space left on device error.

Any ideas as to how I can get round this please?

MOD EDIT Took the liberty to add formatting for legibility

2

Just to add, the server is dedicated to Plex, has an entire SSD to play with and is the latest Ubuntu and Plex media server software

3

You could boot up into Single user mode and clean out the root file system.

Some suggestions would be, don’t run the Snap version of Plex, download the .deb install file. Don’t use /media for your storage mount points. It would probably be faster to start over with a larger boot volume or relocate Plex to a different drive.

Filesystem Size Used Avail Use% Mounted on
udev 1.6G 0 1.6G 0% 
/dev tmpfs 343M 3.1M 340M 1% /run 
/dev/mapper/Plex--vg-root 216G 216G 0 100% / 
tmpfs 1.7G 8.0K 1.7G 1% 
/dev/shm tmpfs 5.0M 4.0K 5.0M 1% 
/run/lock tmpfs 1.7G 0 1.7G 0% /sys/fs/cgroup 
/dev/sdc1 1.8T 1.6T 214G 89% /media/hdd2 
/dev/sdb1 2.7T 1.9T 825G 71% /media/mainhdd 
/dev/sda1 472M 208M 240M 47% /boot 
/dev/sdd1 3.6T 2.4T 1.2T 67% /media/backuphdd 
/dev/loop1 55M 55M 0 100% /snap/core18/1754 
/dev/loop3 72M 72M 0 100% /snap/lxd/16099 
/dev/loop2 72M 72M 0 100% /snap/lxd/16048 
/dev/loop0 55M 55M 0 100% /snap/core18/1705 
/dev/loop4 31M 31M 0 100% /snap/snapd/7777 
/dev/loop5 30M 30M 0 100% /snap/snapd/8140 
/dev/sdf1 1.9T 1.6T 278G 86% /media/networkdisk 
/dev/sde1 3.7T 2.4T 1.3T 66% /media/travelplex 
tmpfs 343M 8.0K 343M 1% /run/user/1000
4

To augment the above:

The tip most applicable here is:

5

Thanks for the replies.

I don’t use snap to install anything. That’s there for when I was playing around with something that used it. My plex update is via wget and dpkg -i route.

The plex system has a SSD all of it’s own and I would have thought 260Gb would be enough???

Is it likely to be caused by the metadata library gone mad?

I really want to avoid doing a reinstall, but if I have to I will.

Not as au-fait with Linux as you guys - where do I start please?

many thanks

6

Metadata isn’t usually the cause.

  1. Chapter thumbnail images are big (1 image per 5m of video)
  2. Music has a lot of metadata (it’s per-track metadata0
7

OK, working through the tutorial:-

It returns systemd

However this is the result I get when I try to do the first instruction:-

david@Plex:~ cat /proc/1/comm systemd david@Plex:~ sudo sh
[sudo] password for david:

systemctl edit plexmediaserver

Failed to create directories for “/etc/systemd/system/plexmediaserver.service.d/override.conf”: No space left on device

8

if your disk is full, then you will have to clear some space first.

you might also need to run fstrim -av to force the ssd to reclaim freed space.

there may also be file system specific issues with a full drive, you would need to google whatever your filesystem is to know more

ie google ext4 out of space

df -hT --total

this will show what file systems each mount is

df -hT --total                                                                                                                                tekno@proximo:~$ df -hT --total
Filesystem     Type      Size  Used Avail Use% Mounted on                                                                                                      Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs   32G     0   32G   0% /dev                                                                                                            udev           devtmpfs   32G     0   32G   0% /dev
tmpfs          tmpfs     6.3G   19M  6.3G   1% /run                                                                                                            tmpfs          tmpfs     6.3G   19M  6.3G   1% /run
/dev/sdy2      ext4      376G   44G  313G  13% /                                                                                                               /dev/sdy2      ext4      376G   44G  313G  13% /
tmpfs          tmpfs      32G   20K   32G   1% /dev/shm                                                                                                        tmpfs          tmpfs      32G   20K   32G   1% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock                                                                                                       tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs      32G     0   32G   0% /sys/fs/cgroup                                                                                                  tmpfs          tmpfs      32G     0   32G   0% /sys/fs/cgroup
/dev/sdaa1     btrfs     448G   51G  397G  12% /datassd                                                                                                        /dev/sdaa1     btrfs     448G   51G  397G  12% /datassd
tmpfs          tmpfs      95G     0   95G   0% /tmpdl                                                                                                          tmpfs          tmpfs      95G     0   95G   0% /tmpdl
tmpfs          tmpfs      51G  225M   51G   1% /transcode                                                                                                      tmpfs          tmpfs      51G  225M   51G   1% /transcode
/dev/sdy1      vfat      511M  5.6M  506M   2% /boot/efi                                                                                                       /dev/sdy1      vfat      511M  5.6M  506M   2% /boot/efi
/dev/sdz       btrfs     932G  795G  137G  86% /dataplex                                                                                                       /dev/sdz       btrfs     932G  795G  137G  86% /dataplex
/dev/sda       btrfs      22T  8.9T  5.8T  61% /data5                                                                                                          /dev/sda       btrfs      22T  8.9T  5.8T  61% /data5
/dev/md127     btrfs      28T   26T  2.2T  93% /databackup                                                                                                     /dev/md127     btrfs      28T   26T  2.2T  93% /databackup
tmpfs          tmpfs     6.3G  4.0K  6.3G   1% /run/user/1000                                                                                                  tmpfs          tmpfs     6.3G  4.0K  6.3G   1% /run/user/1000
/dev/md126     btrfs      33T   32T  1.4T  96% /data4                                                                                                          /dev/md126     btrfs      33T   32T  1.4T  96% /data4
/dev/md125     btrfs      59T   57T  1.3T  98% /data                                                                                                           /dev/md125     btrfs      59T   57T  1.3T  98% /data
total          -         143T  124T   12T  92% -
9

Ok… we will need to make just a little bit of space.

Let’s sacrifice the codecs for now (they will download again)

sudo bash
rm -rf "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/*"
systemctl edit plexmediaserver

# Now perform the move
.
.
.
.
10

So I’ve done the sudo bash as above and still got the same no space error.

I’ve also tried fstrim -av and that frees up a teeny, tiny bit but it still wont run

This is my result for ailed to create directories for df -hT --total

“/etc/systemd/system/plexmediaserver.service.d/override.conf”: No space left on device
root@Plex:/home/david# df -hT --total
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 1.6G 0 1.6G 0% /dev
tmpfs tmpfs 343M 38M 306M 11% /run
/dev/mapper/Plex–vg-root ext4 216G 216G 0 100% /
tmpfs tmpfs 1.7G 4.0K 1.7G 1% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 1.7G 0 1.7G 0% /sys/fs/cgroup
/dev/sdc1 ext4 1.8T 1.6T 214G 89% /media/hdd2
/dev/loop1 squashfs 55M 55M 0 100% /snap/core18/1754
/dev/sda1 ext2 472M 208M 240M 47% /boot
/dev/sdb1 ext4 2.7T 1.9T 825G 71% /media/mainhdd
/dev/sdd1 ext4 3.6T 2.4T 1.2T 67% /media/backuphdd
/dev/loop0 squashfs 55M 55M 0 100% /snap/core18/1705
/dev/loop2 squashfs 72M 72M 0 100% /snap/lxd/16048
/dev/loop3 squashfs 30M 30M 0 100% /snap/snapd/8140
/dev/loop4 squashfs 72M 72M 0 100% /snap/lxd/16099
/dev/loop5 squashfs 31M 31M 0 100% /snap/snapd/7777
/dev/sdf1 fuseblk 1.9T 1.6T 278G 86% /media/networkdisk
/dev/sde1 fuseblk 3.7T 2.4T 1.3T 66% /media/travelplex
tmpfs tmpfs 343M 8.0K 343M 1% /run/user/1000
total - 14T 10T 3.8T 73% -

11

Given your lack of space on the source drive, you’d probably be best served by moving the data to the new location before creating the override configuration. For example, if you wanted to move it to /dev/sde1 (/media/travelplex), you could do something like (this would replace step B from the how-to):

sudo mkdir /media/travelplex/plexdata
sudo cp -a -r "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/" /media/travelplex/plexdata/
sudo rm -rf /var/lib/plexmediaserver/

That third step is the point of no return; after performing it, your Plex data is completely deleted from the old location. Be very certain that the copy process completed successfully before doing it. It will also likely take quite a bit of time to copy, depending upon the speed of your drives.

From there, you can proceed with step A from the linked how-to to tell Plex where the data is now located.

I’d not normally suggest this as it’s much more desirable to have your Plex data copied to the new location and tested before deleting it. But to do so, you’re going to have to find a significant amount of space you can free up on your source drive.

12

Change the procedure up. (you’re probably out of inodes too)

  1. Move the data (tar | tar )
  2. Delete from var/lib/plexmediaserer
  3. Now construct the override

It doesn’t matter if the data moves first or last. Data must move and override must be done before restarting Plex. That’s the only requirement.

13

Ok many thanks.

It’s late here, but I’ll be fresh in the morning and have a go then and report back. Worst comes to worst I can remaster if I have to. All the data is on separate drives to the OS and Plex for that reason.

14

If I may make a recommendation?

sudo bash
cd /var/lib/plexmediaserver
tar cf  /path/to/somewhere/with/space/PlexLibrary.tar  ./Library

Now you have a perfect image backup which is easily restored / moved to another location.

1 Like
15

Well, I think I’m getting somewhere :slight_smile:

I followed the instructions to move plex data to /media/backuphdd/plexdata. It’s all there and I removed /var/lib/plexmediaserver.

It’s no longer on the ssd

At this point I can run update and upgrade (I couldn’t before) and Sonarr is working again (It didn’t before)

But Plex doesn’t want to start.

Here are the last few commands

david@Plex:/ sudo chown -R david:david /media/backuphdd/plexdata david@Plex:/ systemctl daemon-reload
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: david, (david)
Password:
==== AUTHENTICATION COMPLETE ===
david@Plex:/ systemctl start plexmediaserver ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start 'plexmediaserver.service'. Authenticating as: david,,, (david) Password: ==== AUTHENTICATION COMPLETE === Job for plexmediaserver.service failed because the control process exited with error code. See "systemctl status plexmediaserver.service" and "journalctl -xe" for details. david@Plex:/

Despite moving the plex data, df -h returns

/dev/mapper/Plex–vg-root 216G 209G 7.2G 97% /

so I guess there is still a problem with the root being clogged and there is Plex not working, but we are getting there and thanks for the help :slight_smile:

16

Gone nuclear and doing a remaster.

I upgraded from 18.xx to 20.xx rather than fresh install.

I don’t know if that’s part of the problem but I figured as the data was all on other drives then unplug them, flatten the drive and start a fresh ubuntu install.

The only thing we will lose is the watched / unwatched bits. But I did put a copy of the folder on another drive so maybe that can be restored?

I’ll get plex up and running first though.

17

If you have a tar ball of the Library directory,
and mount the media at the same mount points,
we can restore it and everything will “wake up” as it was before.

18

Thanks for the reply.

At the moment Plex is up and running and all the media is back so we can watch stuff again.

We have decided to use this as an opportunity go through the library and cull stuff we will never see again and when we get round to re-watching stuff mark as read as we go along.

But so much of it we haven’t seen in a while, when we do get round to rewatching we will have forgotten it completely!

The benefits of getting old :slight_smile:

Thanks for the invaluable support.

19

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.