tomorrowsman

Thank you everyone for your help; I will start a new thread with I think a much simpler question!

At the absolute most raw level, couldn't I add the SSD to the array, rebuild parity, then remove the HDD and rebuild parity again, with no data loss? I know that is a super ham-handed way to approach the problem, but wouldn't it work, given none of the drives are greater than half the size of my parity drive? I'm asking about alternatives because I do not see any "Copy" function in any of the menus that would enable me to copy the HDD to the SSD, so I'm guessing it's something above my very low level of expertise.

So I remove the HDD from the array, add the SSD to the array, mount the HDD as a UD, then copy to the SSD?

Apologies, I do not know what that means. Did I refer to that in one of my steps?

Yikes, that sounds scary...so I'm not missing anything, is it: Shut down array. Remove HDD, add SSD, reboot array. Add SSD to array via New Config tool. Rebuild Parity - I'm not technical so forgive me, but why wouldn't parity write to the new SSD at this time? I think this is the part of how parity works that confuses me the most; can't the array see the SSD as a new drive replacing a dead drive and use parity plus the other drives to rebuild? Or is this where the start sector issue becomes the issue? Format the SSD - I assume in the dashboard? Mount HDD to the array via Unassigned Devices - though if I'm already at my max SATAs I'm blocked here... Copy data back, meaning, rebuild the array again? Shut down, remove HDD, reboot?

I've been using unRaid since 2012 and have swapped out countless drives over that time. My 4TB WD HDD hard drive is on the way out, so I decided to replace it with a new Crucial MX500 SSD, others of which I've had in my array for years. For some reason I'm getting an error that "the disc must be as big or bigger than the original" even though both are 4TB. Is there any way to have my unRaid OS work through this? In all these years and swaps I've never encountered this before.

I did see this in the log, with .34 being my local machine: Mar 1 10:39:11 Tower rpcbind[20815]: connect from 192.168.4.34 to getport/addr(mountd) Mar 1 10:39:11 Tower rpcbind[20816]: connect from 192.168.4.34 to getport/addr(nfs) Mar 1 10:39:11 Tower rpcbind[20817]: connect from 192.168.4.34 to getport/addr(nlockmgr) Mar 1 10:39:11 Tower rpc.mountd[1786]: refused mount request from 192.168.4.34 for /unVideo (/unVideo): unmatched host Mar 1 10:39:11 Tower rpc.mountd[1786]: refused mount request from 192.168.4.34 for /unVideo (/unVideo): unmatched host

I had to move to a different PLEX docker last night due to the depreciation of the one I was using. I moved to the official Plex docker. All seems fine with Plex this morning, but out of nowhere I can no longer access my server -- I had it mapped as a network drive in Windows 10, but today, poof, gone, and doesn't even show up as available to re-map. I can't find anything online that explains if this is due to Windows, Plex, unRaid, or all of the above just being inscrutable at my expense. Any thoughts?

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]

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

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]

Wow, looks like I picked a bleeding edge dud all those years ago. Is there a wiki of PLEX-friendly drives?

Starting a bit over a week ago, PLEX became nearly unresponsive around the same time unRaid flagged one of my drives as red; I swapped out the drive, upgraded my parity drive, updated my OS, made sure PLEX was up to date, made sure my GB network connection was still operating as it should, everything I could think to do, yet my server remains very slow (e.g., just opening folders takes a while; file transfer speeds hover around 20MB/s), and PLEX remains nearly inoperable, especially when trying to stream larger files. I have attached logs if anyone could possibly help. I'm happy to provide any further information. Thank you. tower-diagnostics-20181126-1930.zip