Server Version#:
I did a fresh clean install of Ubuntu Server 20.04.1 and then executed
echo deb https://downloads.plex.tv/repo/deb public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
and
curl https://downloads.plex.tv/plex-keys/PlexSign.key | sudo apt-key add -
from this page , and then
sudo apt update
and
sudo apt install plexmediaserver
After this, I stopped the server, replaced /var/lib/plexmediaserver/Library/Application Support/Plex Media Server with my back-up, and restarted the machine.
After 1-2 days, SSH stopped working and these show up:
Note that this is the third time I try to set up my server. I even ordered new SSD and HDD components for it, thinking that they’re broken. I initially thought that it’s caused by Home Assistant, but I didn’t install it this time. I have no idea why this happens on a fresh machine (the NUC was newly purchased), on a fresh Ubuntu Server installation with default settings (a widely used distribution), and a fresh Plex installation.
Does anybody know how to fix these errors?
It’s trying to install on the Live installer SquashFS.
You install on the main system installation & reboot.
Could you please be more explicit? Do you mean that sudo apt install plexmediaserver is incorrect?
Is this a fresh Linux installation?
Yes, downloaded from https://ubuntu.com/download/server , and installed using an USB flash drive.
It looks like you’re installing Plex ON the flash drive.
SquashFS is used by the boot ramdisk and the Ubuntu Installer USB
Install Ubuntu
After install, let it shut down (full power off)
Remove the installation media
Start up
Install updates
Download and install plex sudo apt install PlexPackage.deb
No, I’m not installing on the flash drive, I’m installing on the SSD.
revolt@nuc:~$ sudo parted -l
Model: ATA ST2000LM015-2E81 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB ext4 primary
Model: KINGSTON SA2000M8250G (nvme)
Disk /dev/nvme0n1: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 250GB 250GB ext4
disagree.
This is how it should be.
[chuck@lizum ~.515]$ df
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/nvme0n1p2 122526 103690 12570 90% /
/dev/nvme0n1p1 476 27 450 6% /boot/efi
/dev/nvme0n1p4 788400 411119 377282 53% /home
[chuck@lizum ~.516]$ sudo parted -l
Model: Samsung SSD 970 PRO 1TB (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 500MB 499MB fat16 EFI System Partition boot, esp
2 500MB 132GB 131GB ext4
3 132GB 197GB 65.5GB linux-swap(v1) swap
4 197GB 1024GB 827GB xfs
[chuck@lizum ~.517]$
There should be NO reference to the USB in that.
Ubuntu should be booted.
In this state, at this command prompt, I’m installed on the NVME SSD
There is no USB reference in my output
Here is df too, if it helps:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 8087524 0 8087524 0% /dev
tmpfs 1626292 1612 1624680 1% /run
/dev/nvme0n1p2 238797468 11325996 215271488 5% /
tmpfs 8131448 8 8131440 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 8131448 0 8131448 0% /sys/fs/cgroup
/dev/nvme0n1p1 523248 7984 515264 2% /boot/efi
/dev/loop0 100224 100224 0 100% /snap/core/10444
/dev/loop1 100224 100224 0 100% /snap/core/10577
/dev/loop2 73088 73088 0 100% /snap/lxd/16099
/dev/loop4 128896 128896 0 100% /snap/docker/471
/dev/loop3 69376 69376 0 100% /snap/lxd/18150
/dev/loop5 279680 279680 0 100% /snap/nextcloud/24940
/dev/loop6 31872 31872 0 100% /snap/snapd/10238
/dev/loop7 31872 31872 0 100% /snap/snapd/10492
/dev/loop8 56832 56832 0 100% /snap/core18/1944
/dev/loop9 56704 56704 0 100% /snap/core18/1932
/dev/loop10 279680 279680 0 100% /snap/nextcloud/25276
/dev/sda1 1921802432 1131498916 692611460 63% /drive
thank you. that makes sense.
NO idea why you were showing squashFS .
Plex will install in the root filesystem here.
Could it be related to this maybe?
No.
Looking up the error codes – there is/was major corruption at that point.
It wanted to read from block 0 – where no application data exists so therefore the filesystem clearly exhibited corruption.
The thing is that I installed Ubuntu Server and left it running non-stop for 1-2 months. And ~2 days ago I installed Plex and today I noticed those errors.
NUC8i7BEH2, Core i7-8559U 2.7GHz
ChuckPa
January 4, 2021, 11:31pm
16
NUC8-i7-HVK here.
I7-8809G CPU @3.10 Ghz
@iulianOnofrei
I have been pondering this problem overnight.
From everything I’ve seen, PMS doesn’t just ‘fail’ like this when installing on Ubuntu 20.04 on a NUC. If you knew how many times I’ve reinstalled both Ubuntu and PMS on this NUC, you’d roar.
I really wonder what is going on with that SSD. Is it new or repurposed?
I really wonder what is going on with that SSD. Is it new or repurposed?
The second brand new SSD, specifically, SSD Kingston A2000 250GB PCI Express 3.0 x4 M.2 2280.
Can I presume Ubuntu is all up to date with updates?
No:
alsa-ucm-conf/focal-updates 1.2.2-1ubuntu0.5 all [upgradable from: 1.2.2-1ubuntu0.4]
apport/focal-updates 2.20.11-0ubuntu27.14 all [upgradable from: 2.20.11-0ubuntu27.12]
busybox-initramfs/focal-updates 1:1.30.1-4ubuntu6.3 amd64 [upgradable from: 1:1.30.1-4ubuntu6.2]
busybox-static/focal-updates 1:1.30.1-4ubuntu6.3 amd64 [upgradable from: 1:1.30.1-4ubuntu6.2]
cloud-init/focal-updates 20.4-0ubuntu1~20.04.1 all [upgradable from: 20.3-2-g371b392c-0ubuntu1~20.04.1]
grub-common/focal-updates 2.04-1ubuntu26.7 amd64 [upgradable from: 2.04-1ubuntu26.6]
grub-efi-amd64-bin/focal-updates 2.04-1ubuntu26.7 amd64 [upgradable from: 2.04-1ubuntu26.6]
grub-efi-amd64-signed/focal-updates 1.142.9+2.04-1ubuntu26.7 amd64 [upgradable from: 1.142.8+2.04-1ubuntu26.6]
grub-efi-amd64/focal-updates 2.04-1ubuntu26.7 amd64 [upgradable from: 2.04-1ubuntu26.6]
grub2-common/focal-updates 2.04-1ubuntu26.7 amd64 [upgradable from: 2.04-1ubuntu26.6]
libasound2-data/focal-updates 1.2.2-2.1ubuntu2.3 all [upgradable from: 1.2.2-2.1ubuntu2.1]
libasound2/focal-updates 1.2.2-2.1ubuntu2.3 amd64 [upgradable from: 1.2.2-2.1ubuntu2.1]
libefiboot1/focal-updates 37-2ubuntu2.2 amd64 [upgradable from: 37-2ubuntu2]
libefivar1/focal-updates 37-2ubuntu2.2 amd64 [upgradable from: 37-2ubuntu2]
libp11-kit0/focal-updates,focal-security 0.23.20-1ubuntu0.1 amd64 [upgradable from: 0.23.20-1build1]
libparted2/focal-updates 3.3-4ubuntu0.20.04.1 amd64 [upgradable from: 3.3-4]
libplymouth5/focal-updates 0.9.4git20200323-0ubuntu6.2 amd64 [upgradable from: 0.9.4git20200323-0ubuntu6.1]
linux-firmware/focal-updates 1.187.7 all [upgradable from: 1.187.3]
linux-generic/focal-updates,focal-security 5.4.0.59.62 amd64 [upgradable from: 5.4.0.58.61]
linux-headers-generic/focal-updates,focal-security 5.4.0.59.62 amd64 [upgradable from: 5.4.0.58.61]
linux-image-generic/focal-updates,focal-security 5.4.0.59.62 amd64 [upgradable from: 5.4.0.58.61]
parted/focal-updates 3.3-4ubuntu0.20.04.1 amd64 [upgradable from: 3.3-4]
plexmediaserver/public 1.21.1.3842-b0c7a97d9 amd64 [upgradable from: 1.21.1.3830-6c22540d5]
plymouth-theme-ubuntu-text/focal-updates 0.9.4git20200323-0ubuntu6.2 amd64 [upgradable from: 0.9.4git20200323-0ubuntu6.1]
plymouth/focal-updates 0.9.4git20200323-0ubuntu6.2 amd64 [upgradable from: 0.9.4git20200323-0ubuntu6.1]
python3-apport/focal-updates 2.20.11-0ubuntu27.14 all [upgradable from: 2.20.11-0ubuntu27.12]
python3-distupgrade/focal-updates 1:20.04.29 all [upgradable from: 1:20.04.28]
python3-problem-report/focal-updates 2.20.11-0ubuntu27.14 all [upgradable from: 2.20.11-0ubuntu27.12]
python3-software-properties/focal-updates 0.98.9.3 all [upgradable from: 0.98.9.2]
snapd/focal-updates 2.48+20.04 amd64 [upgradable from: 2.47.1+20.04]
software-properties-common/focal-updates 0.98.9.3 all [upgradable from: 0.98.9.2]
ubuntu-release-upgrader-core/focal-updates 1:20.04.29 all [upgradable from: 1:20.04.28]
I will update all of them and see if it happens again.
system
April 5, 2021, 6:57pm
19
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
