ds123

Members
  • Posts

    47
  • Joined

  • Last visited

Recent Profile Visitors

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

ds123's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Hi, I switched to safe mode lasy friday and disabled all docker containers and VMs. About 5 days later, the server crashed. This time the server didn't restart by itself - I found the server off and had to press the power button to start it again. Nothing relevant was logged to the local syslog file, in fact there are no logs from the day the crash occurred. Does this mean it's a hardware problem? What is the next step?
  2. What capabilities are affected by switching to safe mode? will the array be inactive? If it's a hardware issue, how to identify the faulty hardware?
  3. It configured correctly, there is a syslog file in the share and logs are written, it just don't have any log from the crash
  4. Hi, I enabled the syslog server logging to a local cache share (to avoid a lot of writes to the flash drive). Today, a week after, the server crashed again and started a parity checl again. However, the local syslog file doesn't have logs prior to the crash (the last log before the crash was written an hour earlier). Two questions- 1. Is using a local file for the syslog server problematic to catch crash issues? If so, will writing to the flash drive help? 2. Is it safe to stop the parity check? it's the third time over the past 3 weeks the system runs a parity check due to this issue.
  5. Hi, My server crashes randomly every once in a while (twice already this month) causing multiple parity checks. This started happening recently even though no new containers or plugins were installed. Attaching diagnostics taken after the last crash. What could be the issue and what is the best way to find the root cause? tower-diagnostics-20231124-0040.zip
  6. Thanks. Changed to ipvlan, so far no issues.
  7. Thanks for the quick reponse. Will I be able to keep the same network settings in each of my docker containers? including my user-defined network, br0 and host? Or should something change?
  8. Hi, After upgrading from 6.11.5 to 6.12.1 I received the following error from the Fix Common Problem plugin - I never had this error before 6.12.x. For now, the server is working properly so there is currently no impact. Can someone please help in understanding this error? Should I change to ipvlan? What are the implications of doing this? In terms of my docker network types - I created a custom network for most of my containers. In addition to that, I have one container that uses br0 (pi hole) with fixed ip address and another containers that use host network (plex and duckdns). Wanted to make sure nothing breaks if I change the docker custom network type to ipvlan. Thanks,
  9. So after about a year that this problem occured relatively rarely, in the last few weeks Disk 1 (the same disk) disappears every few days and even several times a day (until restart), so now I'm worried and looking into it more deeply. I switched both the SATA and power cables of Disk 1 with another disk in the array to see if the problem recurs with another disk. To my surprise, today the problem occurred again with the exact same disk - Disk 1. The log is the similiar to the log JorgeB referred above (this time with ata6) - Since it always happens with the disk, even with different SATA and power connectors, does that mean there is a problem with the disk itself? or maybe 7 disks are too much for the MB/PSU (still unclear why it's always the same disk). should I replace it and activate warranty in this case? other than disappearing, the disk is healthy.
  10. Happened again, attaching diagnostics (before reboot) - tower-diagnostics-20220322-1339.zip
  11. I have attached the diagnostics of my system after rebooting. I currently don't have the diagnostics when the problem occurs, but I will try to download next time it happens. tower-diagnostics-20220310-2128.zip
  12. Over the past few weeks, in two different cases Disk 1 was missing and the array was stopped. Restarting the system solved the problem. The SMART test is ok, and parity check has passed without issues. What could be the problem? this is a new disk (about 5 months old).
  13. Could you please elaborate how you migrated to MySQL? I have thousands of records and I don't want to rebuild the DB from scrtach.