comet424 Posted April 14, 2021 Author Share Posted April 14, 2021 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???? Quote Link to comment
comet424 Posted April 14, 2021 Author Share Posted April 14, 2021 (edited) 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?? Edited April 14, 2021 by comet424 Quote Link to comment
trurl Posted April 14, 2021 Share Posted April 14, 2021 1 hour ago, comet424 said: and no parity check started but no reboot either It won't start an unclean shutdown parity check except when it thinks you have booted up from an unclean shutdown. Quote Link to comment
trurl Posted April 14, 2021 Share Posted April 14, 2021 1 hour ago, comet424 said: stay with btrfs or go with xfs Changing filesystems reformat the disk. Quote Link to comment
comet424 Posted April 14, 2021 Author Share Posted April 14, 2021 (edited) 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 Edited April 14, 2021 by comet424 Quote Link to comment
comet424 Posted April 14, 2021 Author Share Posted April 14, 2021 (edited) 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 Edited April 14, 2021 by comet424 Quote Link to comment
John_M Posted April 14, 2021 Share Posted April 14, 2021 1 hour ago, comet424 said: and how you clear that stat that the other guy said btrfs dev stats -z /mnt/disk3 Quote Link to comment
JorgeB Posted April 15, 2021 Share Posted April 15, 2021 7 hours ago, comet424 said: Error summary: no errors found This means those are old errors and the files have been deleted/replaced since, more info on that here. Quote Link to comment
comet424 Posted April 15, 2021 Author Share Posted April 15, 2021 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 tower-diagnostics-20210415-1252.zip tower-diagnostics-20210415-0817.zip Quote Link to comment
JorgeB Posted April 15, 2021 Share Posted April 15, 2021 1 hour ago, comet424 said: so here is the log before the reboot and a diagnostic after the reboot Those don't help to diagnosing an unclean shutdown, the only ones that can help are the diags saved by Unraid in the logs folder. Quote Link to comment
comet424 Posted April 15, 2021 Author Share Posted April 15, 2021 (edited) 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 tower-diagnostics-20210415-0817.zip tower-diagnostics-20210415-0819.zip unbalance.log tower-diagnostics-20210415-1252.zip tower-diagnostics-20210414-1359.zip tower-diagnostics-20210414-1405.zip Edited April 15, 2021 by comet424 Quote Link to comment
JorgeB Posted April 16, 2021 Share Posted April 16, 2021 We just need the last diags created automatically by Unraid when you last rebooted, do you which ones are those? Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 (edited) 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 whats confusing these are really noy Flash logs they are "diagnostic" download files it seems there is no difference from "flash logs" and "manual down" maybe log files should be saved as tower-diagnostic(Reboot) somethiong to show whats a pre reboot and whats and after reboot file in flash logs unless there is something i can change so it makes it easier for me to distinguish reason i said i gave the last 2 days diag nostics is to look in there what keeps causing this bug that other people are having and that the 100 second from 90 seconds trick didnt fix it... as i also make sure to check fix common issues too to try to solve those too Edited April 16, 2021 by comet424 Quote Link to comment
JorgeB Posted April 16, 2021 Share Posted April 16, 2021 Delete all the diags from the flash drive, do another reboot, post the diags saved there. Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 do i wait till after parity check is done? Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 i at 92.7% so another hour or so to go Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 (edited) ok so i waited till was done.. i made sure Fix Common issues had 0 errors i rebooted and it started parity check again.. i canceled it i didnt wanna do another one i just finished one a few min ago and here is the 2 log files from the flash folder unbalance.log tower-diagnostics-20210416-0857.zip Edited April 16, 2021 by comet424 Quote Link to comment
JorgeB Posted April 16, 2021 Share Posted April 16, 2021 Shutdown timeout is not being honored, did you try changing to a different number and re-applying? Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 just the 90 seconds to the 100 seconds that was from the other forum that fixed the issue for other people i havent tried different numbers as trul was giving me other tests to do... i dunno how high to go? or what number is too high Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 ok so i set it to 150 from 100 and ill try a reboot.. Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 ok the 150 seconds fixed it.. it didnt take a new log file did the log files tell you what caused the timeout from not being honored? is it the VMS? more so Windows VMs? does it say like windows does These Files are still open do you wish to force closer... does the diagnostics tell ya what was still open at the time of the timeout? Quote Link to comment
JorgeB Posted April 16, 2021 Share Posted April 16, 2021 2 hours ago, comet424 said: did the log files tell you what caused the timeout from not being honored? It appears to be an Unraid bug, it's not respecting the set timeout, you had the timeout set to 100 secs, and Unraid was forcing the shutdown after less than 30 secs had elapsed, changing the setting usually makes it stick, same thing happened to a handful of users after upgrading to v6.9. Quote Link to comment
comet424 Posted April 16, 2021 Author Share Posted April 16, 2021 oh ok.. as its was set to 90secs i guess thats the default.. and then i set it to 100 and i just in the earlier post set it to 150 so i figured it was a Windows VM thing you know how it hangs ro how you cant shut down Windows VMS using Stop you always gootta use the Force Stop as it wont shut downin the VM section.. be nice if they could fix that too that the STOP would shut it down.. or i had to click STOP 2-4 times to get ot to shut down .. so least i not going crazy.. so then will this happen again in the next reboot or will it stick.. i didnt try a 2nd reboot i was also thinking maybe my hard drives are failing and unraid knows something Quote Link to comment
JorgeB Posted April 16, 2021 Share Posted April 16, 2021 7 minutes ago, comet424 said: ro how you cant shut down Windows VMS using Stop you always gootta use the Force Stop as it wont shut downin the VM section. You can try hibernating the VMs instead, that's what I do, much faster. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.