• Content Count

  • Joined

  • Last visited

Everything posted by comet424

  1. heck if i know whats automaticlly created.. you guess is good as mine i guess it be ubalance.log and the 8am file you guys are smarter then me at log files. if i took a guess it be 8:19am file its confusing as tower-diagnostics-xxxx is labled the same as a manual download so you cant even tell between the 2 either be nice if the Flash logs wrote tower-diaganostics(flash)-xxxx and manual tower-diaganostics(manual)-xxxx but you guys are the experts. hopefully you can figure it but
  2. ok here are the logs from yesterday and today if i have to go further back let me know from the flash\logs folder... if you need me to go further back more dates i can attach them too unbalance.log
  3. ok so i deleted those old errors u think it would fix it alright so i did a Reboot and Parity error checking is back so here is the log before the reboot and a diagnostic after the reboot i just took whats next test
  4. so i ran that scrub on disk 3 no errors... i running a balance on disk 3 whatever that does UUID: 610be969-2e97-4e51-adeb-39267e01779c Scrub started: Wed Apr 14 16:07:03 2021 Status: finished Duration: 3:22:51 Total to scrub: 1.47TiB Rate: 126.91MiB/s Error summary: no errors found
  5. ah ok.. so whats the next test? i doing a scrub i dunno what i really does and i was asking a question i should have added ? so it was a question "stay with btrfs or go with xfs?" so what next test i do before i do a reboot? and how you clear that stat that the other guy said
  6. i clicked disk 3 and it says UUID: 610be969-2e97-4e51-adeb-39267e01779c no stats available Total to scrub: 1.47TiB Rate: 0.00B/s Error summary: no errors found didnt click the scrub button and i dont know how to clear the btrfs scrub stats??
  7. how do i know if its old or new? i dunno anything about errors all i know is the history tab and i showed no parity errors so what does the scrub do? and how do i know if i fixed the error? and is BTRFS a good system i choose it because when i first installed unraid and gave me options i googled it and they said btrfs was good over xfs but i really dont know and if i should stay with btrfs or go with xfs etc but ya i not sure how to know if i fixed the error????
  8. so i did 2 diagnostic files.. and is it normal it takes a long time to mount disks? is it the bigger the HDs the longer it takes? or the more full it is the longer it takes? so what i did was 1. uninstalled VM Backup Disable Vm Manager Shut down Array. Restart Array Took Diagnostic then i did 2. renabled VM Manager Start 4 of my VMS waited min Shut Down Array Restarted Array Took Diagnostic hopefully you see something.. and no parity check started but no reboot either tower-diagn
  9. were you able to find anything in the diaganostic file? what be the next thing to test?
  10. so i havent found out yet why the 2 Windows VMs cant be backed up.. is it because there running at the same time.. and now if it fails you cant run Backup again.. tells me can not run default but why cant it back up windows vms?
  11. alright its done the correcting parity here is image .. so whats the next step to test why reboots cause parity checking.. and anything to do with why vm backup as you can see wont backup.. from image from a couple posts ago
  12. ah ok so then what i get is fine wasnt 100% sure figure i should got 200+ anywhere on the drive lol well learn something new everyday.. i guess thats why people do Raid 0 is it or Raid 1 to get the maximum speed.. i just cant afford enough drives to do it also reason i like unraid i dont need all the same drives same size and need to buy them all same time. i can add 1 at a time..
  13. what i noticed from those screen shots i not getting over 200mb/s but all my drives are 7200rpms is unraid slow at times.. i know i read that freenas is a faster data transfers then unraid but i like unraid its user friendly.. but i noticed shouldnt i be getting over 200mb/s always?
  14. here is last 3 pages of the array history hope it helps well i might as well let this parity correction run since i started it let it go till tommorow
  15. oh ok so the automatic parity checking after a reboot does nothing then? as for scheduled parity i have it set for ever 3 months to run.. to do thid paritiy correcting thats what that check box is for correct? so i just click start ... and then report back here for the next step how come the other parity checks show no errors? so its 2:02pm and i just clicked the check so around 3pm tommorw show be done
  16. so i been trying to find this correcting parity check in settings etc.. but i dont have anything least i not seeing it i only have the Parity Check on the main page that is in the image.. so then i can try doing a correcting parity check instead of doing a standard parity check every reboot
  17. how do i do that? is the correcting partiy check what i been doing that i done 4 in the past week that take 25 hours to complete is that a correcting parity check or is a correcting parity check something else? so far no failed disk's nothing but what you mean correcting parity check and ill go from there but if a correcting partity check is what i do after every reboot where it starts partity check i already doing those
  18. oh and i re turned on Dockers but not VMS before this reboot.. should i be turning off Dockers again and perform a new reboot?
  19. it was running.. i also tried to fix my go file i figured maybe it is the problem???/ since Fix common issues?? so i remmebed out my go file i tried reading the documenation about it.. i guess it does everything thats remmed out automaticlly?? # Copy SSH files back to /root/.ssh folder and set permissions for files #mkdir -p /root/.ssh #cp /boot/config/ssh/tower_root /root/.ssh/id_rsa ##cat /boot/config/ssh/*.pub >> /root/.ssh/authorized_keys ##cat /boot/config/ssh/ >> /root/.ssh/authorized_keys ##cat /boot/config/ssh/backupserver
  20. i didnt take a diagnostic when i shut the VMs and Dockers off in Settings because i just followed Turls instructions and there was no errors on the screen the last 4 log files from the Flash\Logs mqybe it tell you something? unbalance.log
  21. so shutting down VM MAnager and Disabled Docker.. and rebooting unraid with the Array Up has no effect it still causes Parity Check.. i guess its something to do with the array?? i thought it was the VM Backup but that issue says it creates a log but i never can find it thats where i mentioned it vm backup issues so i guess VMS and Dockers arent the problem.. here is the diagnostic file too..
  22. what i ment by "the diagnostic files never showed" as you seen it says unclean shut down detected but it didnt really you anything.. it didnt tell you exactly specificly the exact file that caused this.. the program application like Windows operating systems will do a memory dump and when you give it in they know exactly what file caused the crashed but "unclean shutdown detected" still didnt help me.. it didnt say this file caused the problem .. or these 2 files caused the problem so how do i fix it? thats what i men
  23. ya thats what i ment sorry i didnt explain it right ya so when it was done i did STOP then START array.. no parity check no errors then i did STOP array and then did a reboot .. and no parity checking no errors so i havent tried another reboot of parity i wanted to give drives a rest today as its been doing parity checking 3 times in last few days each time takes 25 hours so i guess its like other ppl experiencing when you do a reboot thats when it tells u unsafe shut down... i guess the diaganostic files never showed yo