• Posts

  • Joined

  • Last visited

Everything posted by AshranPewter

  1. This works for me, but I do want to note that I can't get the logs to save to the flash drive. The syslog server way works though. Cheers, AshranPewter
  2. Ya maybe my bios version is different (mine is SAG5AR21 which you can find with the command 'dmidecode -s bios-version') or the hardware is a different revision? I went through a lot of troubleshooting haha. I even started conversation with QNAP to get a newer bios, though that is still ongoing. J3455 apparently has signal degradation issues over time and fixed with newer bios, down the rabbit hole...
  3. I figured it out. I had used pci=noacpi to get all drives to be recognized but pcie_port_pm=off is a better option per the the bug report here
  4. @Xutho and anyone else that reads this thread later one with questions. pci=noacpi has huge implications on speed in my testing. I was getting a lot of call traces in my logs and was concerned about long term safety of my data. Using pcie_port_pm=off instead is far better per the kernel bug report link from earlier, temps are far better as well for all of my stuff. My processor isn't at 100% on one core consistently and instead of 40MB/s parity checks, I get 190MB/s parity checks. Cheers, Ash
  5. Thanks for the reply @jonp! I installed 6.9 rc1 and no change. When doing a parity rebuild I still get the problems before. Max 40MB/s, faster when downloading large files from a program in Docker and the Traces are still there. I did try a few added things to see if I could fix it but neither of them fixed anything. Tried Booting into Safe Mode Tried Booting with Bios instead of UEFI Additionally I have issues with where the WebGUI is unresponsive when I start the Parity Check
  6. Found this thread: that suggests reducing md_sync_thresh is there somewhere I can change this in the interface? or a place I can see the current value? Thanks! Ash
  7. this is great, docker wasn't restarting when I ran this though. Got caught in an unmountable docker.img file. Hopefully that doesn't happen when array starts, it should create the file pretty quick before docker becomes active I'm guessing.
  8. It's a QNAP machine, getting new CPU/Mainboard will be next to impossible. I'll just deal with slow parity rebuilds if there's no other solution.
  9. I've run a memtest and no issues 100%, i tried a different set of ram. Trace doesn't go away. Not sure what to do.
  10. Nevermind.... the traces you mentioned are back and the speeds are back down to 30-40MB/s...
  11. I think that did it, getting more consistent around 70-80 after reseating. Probably faster when Dockers are down but not fussed about it. Also seeing my processor cores consistently at more utilization whereas before was stuck around 42% overall with one core at 100%. Probably causing issues there. Appreciate the help. Cheers, Ash
  12. Hi All having some issues building my parity, this isn't writes to the server or anything but just parity rebuild. It is at 30MB/s, now I wouldn't usually care that much but this machine was a pre-built QNAP that had very fast transfer times and raid rebuild, it seems weird that I'm stuck at 30MB/s when the tests I run on each of the drives is 150MB/s reads (using the drivespeed docker). 2 * 4TB and the parity drive is 8TB. Note: 2 things to note, It transfers faster with files downloading (from a docker container download) getting speeds up to 60MB/s There is no change with docker enabled or disabled Attached is the diagnostics. Thanks! Ash
  13. Wanted to comment on this thread because I've just gotten everything working on my QNAP as well (TS-453b Mini). I did take it apart and remove the DOM flash storage for fear of QNAP OS booting and taking everything with it if the USB happened to be out or some random thing happened. I'm pretty sure I could put any linux distro on it for that matter but Unraid works very well and was easy to setup and get going in a day or so (most of which was transferring data). Hurray for docker compose and being able to move 2GB of appdata files and images and be up and running the same way I was before in the matter of minutes! Things that are better: Faster Boot Times (10 minutes to 1-2 minutes) Cache drive is easy to setup so all dockers start and stop faster and the programs running on them work faster The interface is less bloated in general, QNAP runs a full on drag-and-drop GUI which although is nice for file management is very slow for everything else Everything is very closed on QNAP and non-standard. Even though Unraid is closed in a sense, it's far more open and easier to do what I want (except run a system wide V2ray client...) Forums are basically dead in QNAP, Unraid forums have tons of people talking about everything Cache drive allows for the drives to spin down when I don't need them so they don't make any noise
  14. Mine is around 50% right now while moving around 4.5TB and I also have Docker running atm. So not sure if mine would look like that later but on the main dashboard 1 core is consistently at 100% which I'll try to resolve with a reboot when my data is across and parity protected.
  15. Looks like it's Dynamix System Statistics you're using got it up and running. My speeds look similar, I do have a cpu core at 100% consistently as well.
  16. I guess that's about the same as mine, I would expect it to be a bit higher but maybe a limitation of the processor or system. What is this plugin you have above? Maybe I can compare using it. Thanks for the reply!
  17. Hope you're still here, I'm wanting to use this. Got everything to boot, but when I'm writing from one drive to another without parity, Unraid is having a ton of issues moving files. Max 50MB/s on a 35GB file. Are you having this issue as well?
  18. How do you tell that it's using it? Besides that it uses less of the processor. Like an official way tell through logs. Thanks! AshranPewter