applesauce9

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by applesauce9

  1. Yup that was the issue for me too. I thought I had it set up properly because it was working for months. Thanks
  2. I too can't access the web UI anymore. I was on the old testdasi version this morning and I noticed the web UI wasn't working. Went to the support thread and found this one. Updated to it and it still wasn't working. Deleted the image and my appdata and tried to install a fresh one, and still no web UI. My log looks exactly the same as the one above. Anything else I can try to help diagnose?
  3. Rearranged all my drives (didn't take as long as I feared). Instead of the two parity drives sharing a molex-to-two-sata adapter, I made each one share with an SSD instead. I'm not using regular sata power cables because they're shucked from WD externals that don't like the 3.3v pins or something like that. So far so good but it will take a day to rebuild parity and be sure. It was failing pretty quickly before, though, so I'm optimistic. Thanks again.
  4. Tried to add a second parity disk. Parity writing worked for several hours then I started getting errors. Parity device disabled, and Disk in error state. As I was trying to start and stop the array in maintenance mode, I noticed that those disks were disappearing and reappearing, and I believe the device names were changing (sdm and sdl at one point, later sde and sdk). My only thought is that the power for these two disks is dropping so they're getting disconnected, but I'm unsure of how to confirm this in the diagnostic logs. These two happen to be running off a molex-sata adapter. I'm just hoping for help confirming the error before I go rewiring everything and replacing sata cables (my case is a mess). I also tried going back to one parity disk. Stays in error state. Original parity: WDC_WD80EMAZ-00WJTA0_7SJG85KW New Parity: WDC_WD80EZAZ-11TDBA0_7SJ3MU5U Thanks server-diagnostics-20190811-1422.zip Edit: noticed my two parity devices weren't being detected when I created the diagnostics zip so there's no SMART report for them. Added those. WDC_WD80EZAZ-11TDBA0_7SJ3MU5U-20190811-1437 (sdk).txt WDC_WD80EMAZ-00WJTA0_7SJG85KW-20190811-1437 parity (sde) - DISK_DSBL.txt