• Posts

  • Joined

  • Last visited

Everything posted by DuzAwe

  1. I have almost all Seagate drive and have had no issues.
  2. Welp, Thanks for your help again. I guess Ill be back at some point.
  3. Well I feel like a fool. Ok Looks clean. Opening filesystem to check... Checking filesystem on /dev/nvme1n1p1 UUID: cdb12f2a-8005-48a1-b8f7-bd0e1fc9fd43 [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) found 266705154048 bytes used, no error found total csum bytes: 225909672 total tree bytes: 698073088 total fs tree bytes: 379420672 total extent tree bytes: 46546944 btree space waste bytes: 119030509 file data blocks allocated: 2601829400576 referenced 262717333504
  4. Comes back with: root@thelibrary:~# btrfs check /dev/sdX1 Opening filesystem to check... ERROR: mount check: cannot open /dev/sdX1: No such file or directory ERROR: could not check mount status: No such file or directory
  5. Anything in the logs to point at what it is? The disk have run fine for months the rc for 6.9 is when this stuff started.
  6. A reboot seems to have put everything back to normal? Scrub came back with nothing. Should a reboot have done that?
  7. Howdy, New ECC ram installed after my last two issues. Woke up this morning to more errors. Looks like the first error was just cache then loop2 later? thelibrary-diagnostics-20210327-0921.zip
  8. btrfs errors on device loop2 Cache drive goes read only - General Support - Unraid We have been there and have done that. Its been running fine since I took the other two dimms out.
  9. I have returned. Getting this error now, Still BTRFS but no corruption that I can see. I was unable to scrub and could not gracefully shut down either. Put my drives in my windows machine to get smart results. Both are at 87% health with no errors on short or long. thelibrary-diagnostics-20210318-0813.zip
  10. Not to jinx it but..........the next set of ram dimms seem to have everything stable...........logs attached just because. I have ordered ECC replacement sticks to hopefully rule this issue out permanently. Hopefully this is the end of this issue. Thanks for all the help. Ill report back should anything happen once I start using the system properly again. thelibrary-diagnostics-20210314-1533.zip
  11. Got a lovely 503 for web gui on my reboot thelibrary-diagnostics-20210314-1427.zip
  12. So new vdisk created and its immediately corrupt thelibrary-diagnostics-20210314-1413.zip
  13. Its worth noting in that case that this issue started with 6.9-RC2. My set up has not changed since it was built in Jan 2020 (better times) Its run stable up to the xmas period. With a few lock ups I'm starting to believe is related to logs filling the ram up. But Im not sure. Anyway I have caught the device loop2 issue and hope to help get to the bottom of it.
  14. 24 hours no fails. 6 full passes. Running dim tests now.
  15. 3.5 hours left on the test and its all clear. What should I gear up for next?
  16. Nineish hours of testing three complete passes with no errors so far.
  17. Have been thinking. Since all this started I haven't been able to get the smart tests to run on the cache drives. Is that more indicative of the drives failing then the RAM being an issue? Memtest is two passes down with no errors.
  18. Anything wrong with taking two sticks at a time to another machine to test?
  19. Too rule out ram issues? How long should I leave it run?
  20. Ok here we go, It happened again. I reformatted the Cache disks after my post here. thelibrary-diagnostics-20210313-0116.zip
  21. Docker deleted (had to reboot, that kills all the logs and what not right?) and rebuilt. I guess now we wait.
  22. Syslog attached. Detail of build is in my sig. Motherboard BMC chip died and has been replaced. Other than that and the upgrade to 6.9. Nothing out of the norm. Also has UPS if that makes any difference. thelibrary-syslog-20210311-0928.zip
  23. Unsure if this error is to be expected or not? Trying to overclock and when I use nvidia-settings I get the below. No issues using smi.