falsenegative
Members
-
Joined
-
Last visited
-
that was it I guess. I installed a piKVM together with the ATX-Board a few days prior. I don't know if this could affect the power rails itself, as it should not interfere, but when removing the ATX-Board 2 hours ago, i also removed an old power splitter y-cable I had installed. after removing it, the errors are gone and the new parity is currently being built on the new disk. Thanks for holding my hand! :) I hope that was really the root cause.. thanks again!
-
Hi all, I ran out of ideas and need some input please.. I run unraid 7.1.4 with a pool of currently 3 disks. 2 weeks ago, my parity disks began to throw errors so I ordered a wd red pro 10TB to replace the parity disk. ~25% into building the new parity, the new disk began to throw errors as well. my disks are attached to an PCI-Express-SATA Port Extender (https://www.amazon.de/dp/B08F56WKW7?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3&th=1). the 3 pool disks attached to it have no issues so far. I switched the SATA Cable for the new parity disk and attached it to an onboard SATA Port (my Cache-Pool is attached on the onboard ports as well). The issue persisted. So i sent the wd red pro disk back and ordered a different disk (Toshiba MG10 20TB). This disk had issues too, it would start to spin up, give a high pitched noise and then i would hear the disk slow down and spin up again. I did all sorts of cross checks (switch cables, power cable, onboard/extender SATA Ports..) but the problem remained. I ordered another replacement for the Toshiba MG10 which just arrived. Installed it, started preclear and after I few seconds I again see errors as seen in the screenshot. please advise. Thanks in advance and best regards. Frank
-
the satisfactory container really runs well, thanks for your work @ich777 Together with a buddy of mine, I am playing on my server and we progressed to Tier4 so far. a few hours ago we noticed, that conveyor belts that had been placed became invisible. the belts from conveyor elevators were suddenly running below or above the actual elevators. working links suddenly stopped working between belts, elevators, containers and so on. anyone experienced something similar? I guess it's due to the experimental status of the server and has nothing to do with the container implementation itself?
