1dirtypanda

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

1dirtypanda's Achievements

Noob

Noob (1/14)

0

Reputation

  1. removed UD and preclear plugins. rebooted. now booting up fine. does UD not work well with the preclear plugin? then i reinstalled UD via the Apps tab ( I did not install preclear plugin) and on the Main tab I'm seeing spinning circle with "Please wait, retrieving information..." If I go to Plugins>UD> I get the same Please wait message. Attached is the latest syslog. syslog
  2. Downloading from Diagnostics is getting stuck so here's my syslog file right after a reboot. Now it seems like my disks aren't mounting correctly and array isn't starting up correctly when I have this plugin installed. Then I deleted the plugin from the boot/config directory and then rebooted, but I still see errors in the syslog related to unassigned devices and it's again stuck mounting. any help/thoughts would be much appreciated! syslog syslog
  3. having some issues with the unassigned devices plugin and wonder if someone can help. the plugin installs fine but on the Main page in the Unassigned Devices section all I see is a spinning "Please wait, retrieving information..." It is just stuck in this state. My syslog spits out: Feb 4 12:42:53 Tower nginx: 2018/02/04 12:42:53 [error] 4720#4720: *1183 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.174, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net", referrer: "https://091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net/Main" Feb 4 12:46:37 Tower nginx: 2018/02/04 12:46:37 [error] 4720#4720: *1183 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.174, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net", referrer: "https://091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net/Main"
  4. ok. so fixed the attributes problem. i've now moved my disks from reiserFS to xfs (some of them encrypted), except for the wd 8tb which i will take out of the array. now i'm running into an issue with the assigned.devices plugin getting stuck intermittently. I was starting up the array and now it's hung with the array trying to start and "Mounting disks..." at the bottom of the screen. The syslog is attached ( I couldn't get a diagnostic) and the main error message is; Jan 24 16:44:55 Tower nginx: 2018/01/24 16:44:55 [error] 5294#5294: *84506 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.2.20.2, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net", referrer: "https://091673bb5fb1dc42b44767e28426796bafe88ef4.unraid.net/Main" Any idea how to get this working properly? Sometimes it seems to work, sometimes it doesn't. Second problem I've been having is that the system doesn't seem to reboot properly whether I issue the command via the GUI or whether I do it via ssh terminal. I suspect because of the problems causing the hang and I can't reboot cleanly? I end up having to hard reboot the system. syslog
  5. from syslog, seeing a lot of them now. do you happen to know what this means? (i'm trying to move files off the reiserFS disks so I can convert them to xfs). Jan 22 16:53:09 Tower kernel: REISERFS warning (device md3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.quarantine) associated with [12665 12685 0x0 SD] Also moving some files around in the disks, I'm getting this error: mv: getting attribute 'user.com.apple.quarantine' of 'user.com.apple.quarantine': Input/output error mv: getting attribute 'user.com.apple.metadata:kMDItemWhereFroms' of 'user.com.apple.metadata:kMDItemWhereFroms': Input/output error how do i fix these?
  6. got it! but on the release notes i do see where is says to remove the S3 plugin but it says to install FCP! can/should I install FCP after I remove both plugins and reboot or just not bother with FCP?
  7. okie... so i moved the ssd and hdd's off of the marvel controller. got the system back up. removed the seagate disk4. put in the wd 8tb as disk4. the system rebuilt the drive and all was good. I converted one of my drives from reiserFS to xfs. i did this all on 6.3.5. then this morning i upgraded to 6.4.0 and now my system seems a bit wonky again. plex isn't working right. sluggishness in the UI. i see some Call Traces in the syslog. When I run Diagnostics it just sits there and nothing downloads. Diagnostics is usually pretty quick. I grabbed the syslog and here it is. I'm not sure if there are other files that are needed that could help? syslog
  8. Oh! So it's best not to put any [sized] hdd on those sata ports? Not near my keyboard but I may have drives on there since I got this Mobo.
  9. so just tried the rebuild and got the red X again. It looks like the same problem. attaching the latest diag. I'll try a new sata cable later today. should i physically remove the original seagate? anything else to try? tower-diagnostics-20180119-1019.zip
  10. sorry, how would I rebuild again with the new wd disk ?
  11. hmm. I powered down, checked the cables (haven't replaced any yet), powered back on. for array disk4 if I choose: - no disk - red X, - the WD, there is a red X, (maybe this one is bad too? it was an amzn warehouse deal and came in a static bag and brown amzn box) - but if I choose the original seagate it's now a blue square. I think this is "new device" and can't use it bc a) it has my original data, b) unraid is saying I can't use this anymore bc "Replacement disk is too small." i stopped here as I don't know what to try next. here's the diag now. can i try plugging the hdd cables into a different sata port on the mobo or will the mess something up? tower-diagnostics-20180119-0850.zip
  12. so i was trying to use unbalance to move all the files off and noticed that at some point the time stopped going down. i noticed that now there was a red X next to disk4 (This is a seagate 3TB). I actually just got a new wd 8TB and it precleared ok. So i stopped the array (I may have rebooted, can't remember), took the seagate disk out of the array and it shows up in unassigned drives, put the wd in it's place disk4 of the array and restarted building the drive. I wake up this morning and now there is a red X next to disk4 which is the new wd drive and log says there are write errors. i'm not sure what to do next... should i retry building the wd drive in disk4? not sure how to do that. attaching the latest diagnostic file. tower-diagnostics-20180119-0745.zip
  13. thanks for the awesomely fast reply. that's actually one of the disks i am trying to move files off now so i can yank it and put the sledgehammer to!
  14. First time running FixCommonProblems and found some call traces. If someone wouldn't mind to kindly take a look, much appreciated. I'm finally getting around to converting from ReiserFS to xfs and doing a bunch of other maintenance that I've put off for too long. tower-diagnostics-20180117-2321.zip