Dash----

Members
  • Posts

    5
  • Joined

  • Last visited

Dash----'s Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Allright, I'll post to that topic. I did have mirroring to flash enabled, but that was all that was in the log I pulled of USB.
  2. The thing is that in no logs I can find any reference to macvlan and I have not assiged any custom IPs to docker containers. I also have not been using br0 in docker (I have host/bridge/custo network). In this thread there is still no conclusion on what is causing this it seems, but most of the people are seeing something in their logs. It seems that in my logs the crash is actually missing which would indicate the system totally locked up.
  3. Hey, sorry for not understanding what is happening here but I have noticed in the last few weeks that my Unraid instance running on HP Microserver Gen 8 has been randomly crashing. Every few days or so. This first started after upgrading the processor from stock intel celeron to Xeon E3-1220L V2, but it might have been just a coincidence. I have enabled syslog storage to USB and am attaching it here (the last day of it - the crash happened around 17:35 ish together with diagnostics and what I see via remote console at the crash time. Happy to provide more info. p.s. I see a topic that has to do with NAT and crashing but not sure if it is related. syslog.txt atlas-diagnostics-20210620-1740.zip
  4. Hey guys quick question on what to expect with first parity sync. I have 2x4tb ironwolf drives from before in my hp gen8 microserver - both for data + 1TB cache ssd. I now added 2x8tb smr (seagate barracudas). Over the night I transferred my media to the new 8tb drive (cca 2tb in 14h) and today I added a parity drive. Now, I do understand (or thought I do) problems of SMR drives, but creating of the parity is going extremely slow - it made 215GB in last 3 and a half hours. Transfer speeds started with 100MB/s+ and are now between 3-15. Am I doing something wrong? Going through the forums I understood that sequential writes should not have such a penalty. I did extended smart test during the night before and both of them looked fine as well... When I first encountered the issue, I cancelled the parity sync after an hour and changed bios setting to sata ahci and enabled cache in bios, but it does not seem to have done any difference . Adding diagnostics here if someone catches anything. Again, I understand the speed limitations of re-writing the data in daily use, but this seems excessive. atlas-diagnostics-20210429-2012.zip