Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Zandor300

  • Rank
    Advanced Member
  • Birthday 12/17/1999


  • Gender
  • URL
  • Location
    The Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @jonathanm Yes, I realized that I hadn't changed that one and tried that too after my last post, but it produced the same result...
  2. @jonathanm Update: I've set my settings to the ones you can see below, but it still initiated shutdown immediately after the UPS lost power:
  3. @jonathanm Yes, sorry, I meant the server stays on and starts shutting down immediately. I did try to set the "Runtime left to initiate shutdown (minutes)" value to 0, but that also immediately initates a shutdown. Didn't try the "Time on battery before shutdown (seconds)" though. Will do right away.
  4. Hi, I have a Digitus DN-170091 UPS with a Mega System HDL801 NetAgent 9 network card running firmware 3.7.DL530. I've configured it in unRAID like so: But for some reason, it is reporting that the UPS has 0.0 minutes of runtime left, so when the UPS loses power, my unRAID servers instantly shutdown. I can't find the runtime counter anywhere in the webinterface for the network card. What am I doing wrong? - Zandor
  5. Hi, I have a server that is 4U and has vents as the front of the case, but I am missing an icon for it. I would love to have an icon for it though. Thanks!
  6. @johnnie.black Okay thanks! Let's hope it stays up!
  7. @johnnie.black Power cycle did nothing: platinum-diagnostics-20190429-1635.zip Replaced SATA cable with a brand spanking new one + using a different port on mobo again: It showed up again. platinum-diagnostics-20190429-1649.zip Why would two SATA cables die so short after each other? I think the first replacement was also brand new.
  8. @johnnie.black I haven't checked the cables/power cycled yet but I did find this in Fix Common Problems: Is this related to the issue? platinum-diagnostics-20190429-1613.zip
  9. @johnnie.black Here is a new diagnostics file after reboot. platinum-diagnostics-20190420-1243.zip
  10. Hi, My parity disk got disabled a couple of weeks ago because of read errors, rebooted; entire disk missing. I shut down my server, replaced the sata cable and connected the drive with a different port on mobo. Now, last Monday, the disk got disabled again because of read errors. Is my disk dead? Thanks in advance! platinum-diagnostics-20190418-1843.zip
  11. I meant, physically, I thought the parity drive was my data drive but I found out even before booting into Unraid. Additionally, I always check serial numbers of the drives before changing array configurations. Also, don’t know if you know this, but if anyone would swap around drives, physically, Unraid doesn’t care and still correctly mounts the drives. Disk 1 has been rebuilt. Will change topic to solved for now.
  12. While I unplugged the parity drive (as I later found out I mixed up the drives), I might have accidentally nudged the Disk 1 SATA cable because after I started the machine, the drive showed up again in the boot menu. It is currently rebuilding Disk 1... If the disk goes down again I will replace the SATA cable. The other available SATA 3 port is broken and only have a SATA II port left so if the SATA port doesn't have a reliable connection, it might be a good excuse to replace it along with the memory and CPU. I've read that the AMD Athlon 64 X2 5000+ isn't very power efficient and the board doesn't have Gigabit ethernet. It's running on a PCIe nic.
  13. The server has been restarted and the disk isn't found by the bios. When going into the boot selection menu, the disk was not showing up. My parity was and my boot drive too. This is what I got to see after Unraid started up: This is a diagnostics file before starting the array. oxygen-diagnostics-20181224-0945.zip I will return tonight so I will check on the wiring tomorrow, swap some cables or connect it with a different port.
  14. Hi, This morning, I woke up with a notification on my phone because a disk has gone into disabled state. I'm far from home (London) and only get back on Tuesday (The Netherlands) but when I downloaded diagnostics remotely, I found a bunch of write errors in a bunch of different sectors on Disk 1. So my question: Did my disk die, has the cable gone bad (again), did my port go bad, or has something else gone wrong? I had someone which is at the place of my server send me pictures from the outside and external cables and all that is fine. Also note, I just found out about all the bruteforce attacks the server has been getting, but that is a thing for when I get back. Kind regards, Zandor Smith oxygen-diagnostics-20181223-0943.zip