Jump to content

sonofdbn

Members
  • Content Count

    296
  • Joined

  • Last visited

Community Reputation

5 Neutral

About sonofdbn

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. And now this endpoint has stopped completely for me.
  2. You can always add the variable manually. The option to add variables, ports, etc. is at the bottom of the settings screen.
  3. For me it's working, but speeds fluctuate a lot - sometimes stops altogether, then back up to normal. I'm using Sweden.
  4. Should I let the parity check finish? (The crash came roughly 50% of the way into the previous parity check.) Is there a possibility that the flash drive is corrupted? I did install a docker recently, about the time of the first crash. I haven't started it this time round. Don't want to name it and give it a bad rep when it might have nothing to do with the crashes.
  5. Fortunately I ran the syslog server tool as suggested - the server crashed again. This time I could ping, but no SSH. Also I couldn't see any of the shares, but my Win10 VM was still running. Weird? The GUI timed out with a 500 Internal Server Error. So I shut down the VM and then rebooted. I've attached the syslog, removing entries at the end which came after the reboot. My UPS is down, so those messages are not surprising. 192.168.134 is an Asus router. I have two Asus routers, one is the main one and one is configured as an access point (and also serves as a switch). I believe that internal IP address is the access point. The single Ethernet cable from the server is connected to the access point. unRAID came up again at 00:45 extract-syslog-192.168.1.14.log tower-diagnostics-20200401-0104.zip
  6. Unfortunately the server crashed again. I noticed it when my Win10 VM disconnected (wasn't using the VM, but it was running in an RDP window on my PC). Couldn't SSH in to the server and couldn't ping it. So I've rebooted and parity check started automatically. I've attached the latest diagnostics (after rebooting) and the previous one for easy reference. From what I can tell, on Disk 3 the UDMA CRC Error Count hasn't changed. I'm wondering whether there's anything that can tell what cause the crash. So far, 4.8% into the parity check, there are no errors. tower-diagnostics-20200331-1439.zip tower-diagnostics-20200325-1911.zip
  7. Thanks for all the help. All done and seems to be OK. The disk was connected via a forward breakout cable to a SAS HBA and I was a little worried, having no spare breakout cable. Fortunately I found the last remaining SATA port on the MB and managed to use that with a new SATA cable. I'll watch out for more CRC errors, though.
  8. So should I do another parity check first? Then if that turns out OK, do a rebuild?
  9. Thanks for the quick response. OK, I cancelled the parity check and checked the cables, which seemed to be OK. I restarted but the disk still has an "x" next to it. (Weirdly I get a notification saying the array has turned good, array has 0 disks with read errors. While I get that if the disk is disabled but the array still works, doesn't seem like the state of the array should be termed "good".) If I need to restart the parity check, should I be writing corrections to parity? Diagnostics are attached. tower-diagnostics-20200325-1911.zip
  10. This morning I found my server unresponsive - seemed to be on, but couldn't SSH in and no response from pings. So I switched it off and restarted and it automatically went into a parity check. A few minutes later I got a messages for Disk 3: udma crc error count, then a message saying it was in error state, and warning that the array had errors, 1 disk with read errors. I'm assuming I should replace the disk. Is that correct? (Diagnostics attached.) Also, should I stop the parity check? Finally, if I replace this 4TB disk, can I replace it with an 8TB disk (which is the size of my parity disks)? For the replace, do I just put in the new one in place of the old one and rebuild? tower-diagnostics-20200325-1526.zip
  11. Couldn't get work units from F@Home, so went with RDP-Boinc. It's nice to see so many cores maxed out for once.
  12. Did you also do the last part? I missed that part initially, but after doing that AND clearing cookies, the Web UI worked.
  13. Thanks for the help. All done. Recreating the image was so much easier than I expected. I was worried because I had two instances of some dockers (named them differently of course), and was pleasantly surprised to see both listed in the previously installed apps list. Also took the opportunity to turn on log rotation.
  14. Thanks for looking at this. I'm trying to understand how docker.img works in the cache pool. In my case, docker.img sits inside /mnt/cache and is set to 20GB. So if I free up space by deleting some files in /mnt/cache, and also delete some containers to free up space in the docker image, would I then still have to recreate the docker image?
  15. I was trying to update a docker and got a read-only file system error. On reading around it seems like it might be cache disk error. I am running a two disk btrfs pool as my cache disk, but don't know enough to see whether there is anything significant in the attached diagnostics. I did notice that on my Dashboard Memory log was at 100%. I'm running 6.8.1. Can anyone help? (I subsequently rebooted the server and am now able to update the docker, but would still like to know if there's any preventative maintenance I should be doing.) tower-diagnostics-20200310-1448.zip