jasperjames

Members
  • Posts

    11
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

jasperjames's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks all, really appreciate your help. I'm keen to upgrade to v6 asap but wanted sort this loop I'm stuck in first. Will install the powerdown plugin first before moving on to v6, will mark topic as solved shortly!
  2. Hi all, Have done extensive searching and would appreciate some help. I'm having a spot of bother with my server where the array won't stop. In the GUI, I stop the array and normally that page refreshes the offering the powerdown/reboot options - in this case the browser just hangs. Going in through telnet I could see there were various processes holding up a couple of drives. Firstly, Plex which I updated recently seemed to be using the cache drive. Found and killed those processes. The system stilled seemed in limbo and appeared disk2 was failing to unmount - again killed processes pertaining to that drive, upon which the tower stopped talking to me altogether. Couldn't reach via GUI or telnet - I'm on the third hard reboot now and it's doing another parity check. I'm pretty sure when that's down and I go to shutdown again, the same thing will happen (have also tried using the power button on the tower, same problem). Is there anything else I can try (like removing plex?) to get to the bottom of why I can't shutdown?
  3. Thanks RobJ and NAS, am exploring the guide now!
  4. Hi all, I'm a bit behind the times and currently living with 5.0-rc8a. Is it wise to upgrade from this to 5.0.6 first (or an earlier version as some post suggest?) to enact the permissions tool before moving to ver. 6? I believe my Celeron E3200 is 64bit and hope to replace this and the mobo in the near future with a Xeon and new mobo. Any advice much appreciated! Jasp
  5. Thanks itimpi, First thought, will running Reiserfsck work if I've already started a rebuild on the drive? As instructed by the support wiki, both the red and green have attempted a typical rebuild. I will give that a go shortly and report back, thank you again.
  6. Thanks Lime, I've used Western Digital's RMA system before for the Red originally, will go down that path again if needs be!
  7. Syslog was too big to attach so have cut in half! syslog_pt1.txt.zip
  8. Unraid Version: 5.0-rc8a Hi all, I have been trying to fix my server for some weeks intermittently and now feeling a bit lost. I have done a lot of searching and head scratching but now would really appreciate some support! My array is currently four drives including parity. Recently disk 2 (a 2tb fairly new WD Red) became disabled (red icon) showing DISK_DSBL. Tried a rebuild but that failed, not having much time to investigate or dig further I plumped for ordering a new WD Green 2tb to replace and do a simple rebuild. Once installed in the Red's palce, the rebuild was happily working away for 3 days on the WD Green until that failed too and now also displays DISK_DSBL and has left me scratching my head. Logic would suggest to me this is not a coincidence, happening to both WD drives. On attempting a 2nd rebuild on the Green today... - I moved the hard drive further up the cage away from another drive, worrying about heat - Replaced the SATA cable with new one, as suggested elsewhere - Changed the power connector for another but on the same trunk (the only spare) of the Corsair PSU (which I assume would not make much difference if there is an issue with the PSU). - Observed that drive 2 is on a dual SATA controller card along with another drive but not witnessing any errors with that drive. The 2nd rebuild on the WD Green lasted less than an hour this time and failed again. I would really appreciate if anyone could lend a hand and help figure this out. My hope is that both the Red and Green drives may be salvageable, and could expand my array, or at least save me forking out for a third drive? I attach the most recent syslog and smart report on the Green WD below. Many thanks, Jasper smartctl_sda.txt