UNRAID REBUILT, PLEX FAILING

[tomorrowsman]

I got my unRaid server rebuilt, and got everything backed up, but PLEX (via Docker) will not start.  I restarted PLEX, installed the latest version, but still getting 'Connection Refused' errors. 

 

I checked my unRaid logs and I have a lot of this, which I do not understand; any thoughts?

 

Dec 4 02:12:57 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:12:57 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:25 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:25 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:25 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:26 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:26 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:13:26 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:44 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:44 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:44 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:46 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:46 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:15:46 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:18:58 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:18:58 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:18:58 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:19:01 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:19:01 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:19:01 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 02:31:05 Tower kernel: mdcmd (91): spindown 4
Dec 4 02:33:39 Tower kernel: mdcmd (92): spindown 0
Dec 4 02:33:40 Tower kernel: mdcmd (93): spindown 3
Dec 4 06:52:06 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 06:52:06 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 06:52:06 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 06:52:09 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 06:52:09 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 06:52:09 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:07 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:10 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:10 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]
Dec 4 10:52:10 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]

[Hoopster]

46 minutes ago, tomorrowsman said:

I checked my unRaid logs and I have a lot of this, which I do not understand; any thoughts?

 

Dec 4 02:12:57 Tower kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (system.posix_acl_default) associated with [3 140584 0x0 SD]

 

You should post your diagnostics zip file (Tools --> Diagnostics) in case there is more helpful info in there.

 

From the log snippet you posted, it is clear there are file system issues on device md1 (your cache drive, perhaps, if you store docker appdata there?).

 

This could be docker container related and is not necessarily a corrupt file system.

 

You really ought to, at some point soon, try to migrate your disks to the xfs file system. ReiserFS is no longer maintained and is no longer the recommended unRAID rile system.

 

Post your diagnostics so one of the disk/file system experts can give you some guidance on correcting the error(s)

[trurl]

26 minutes ago, Hoopster said:

From the log snippet you posted, it is clear there are file system issues on device md1 (your cache drive, perhaps, if you store docker appdata there?).

md1 is always disk1. Each of the md# is exactly the array disk given by #. It can't be otherwise.

[Hoopster]

md1 is always disk1. Each of the md# is exactly the array disk given by #. It can't be otherwise.

That’s what I thought but wasn’t sure. As I said, I was hoping a disk/fs expert would chime in because I am not said expert.


Sent from my iPhone using Tapatalk

[tomorrowsman]

I just had to rebuild unRaid, and I did indeed see the notes to move all to xfs; in fact, md4 is brand newly to xfs.  The others were pending this weekend, but now PLEX is hosed, and I can't figure out how to rebuild it.  Is there an easy way to un/reinstall PLEX in the docker?  I've never had to before, and would rather not, but whatever needs to be done and all....

 

Diagnostics attached!

tower-diagnostics-20181204-1943.zip

[tomorrowsman]

I rebooted PLEX and checked the logs, and you can see where there's definitely a snag:

 

ErrorWarningSystemArrayLogin

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
Dec 5 03:48:08 Tower syslog-ng[13]: syslog-ng starting up; version='3.5.6'
Dec 5 03:48:09 Tower syslog-ng[13]: EOF on control channel, closing connection;
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 19
Dec 5 03:48:09 Tower cron[24]: (CRON) INFO (pidfile fd = 3)
Dec 5 03:48:09 Tower cron[24]: (CRON) INFO (Running @reboot jobs)
6 10000 /config/Library/Application Support
10000
6 10000 /config/Library/Application Support
10000
6 10000 /config/Library/Application Support
10000
6 10000 /config/Library/Application Support
10000
6 10000 /config/Library/Application Support
10000
[Ad Infinitum]

[Hoopster]

59 minutes ago, tomorrowsman said:

Is there an easy way to un/reinstall PLEX in the docker?

If you have been backing up appdata, perhaps you can try restoring Plex from a backup before you started having problems.

 

If you really want to completely uninstall and start over with Plex, you can remove it (with image) from the Plex icon in the docker page.  Then, you should delete the Plex folder in appdata (this will blow away the current Plex database and stats).

 

After everything is removed, you can reinstall the docker with its current configuration from the Previous Apps selection in Community Applications.  You will then have to recreate your Plex Libraries and rescan content.