every reboot caues unraid to do parity check and says unsafe shutdown


96 posts in this topic Last Reply

Recommended Posts

ever since i upgraded to 6.9    everytime i need to reboot unraid  

it runs parity check and tells me i did an unsafe shutdown

[TOWER] Automatic unRaid Non-Correcting Parity Check will be started Unclean shutdown detected

 

is there something wrong i needed to change  so each time i do a reboot it will display it and run parity check

 

tower-diagnostics-20210407-2200.zip

Link to post
  • Replies 95
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Put flash in PC and let it checkdisk. While there make a backup.

 

Do you have any VMs running or have a command line open when you try to reboot?

Link to post

ok i can do that..

 

as for VMS  ya  i run 

VM of windows, ubunutu, volumio, Home Assistant,.. 

 

and no command line open..  but in past i know i had VMs running and if i reboot it just shuts them down normally doesnt it?  as all i do is just do a reboot i never shut the VMs down  first    least i didnt know that..

 

Link to post

ah ok  so its a bug in unraid..  ill give that change setting.. maybe the fix it in next release or unraid..  but ill give that a test 

change from 90 seconds to 100 seconds

and ill try once parity done.. takes 21 hours  so i got several hours to go.. i know this happened right out of the gate when i upgraded to 6.9  darn partiy check...

 

but ill give that a try..

Link to post

so i gave it a shot  the settings the Shutdown to 100 seconds  but  it failed... i also did the upgrade to 6.9.2  

so not sure if it caused it

 

so it didnt fix it.. which bites...  what else can i set so i gotta wait another 24 hours before i can reboot  since parity is running..

this issue only came up since i upgraded to 6.9    6.8 had no issues... and i see alot of people having this bug issue so its just not me.. but it seems it worked for them

to go from 90 seconds to 100 seconds..

 

so what else can i do?  

i also know VMBackup  is having issues to back up 2 vms  that run  could it be those 2 vms   and why cant VM backup  work    

i posted  the log in that plugin forum  but no reply  yet 

Link to post

Those are not unclean shutdown logs, at least there's no shutdown logged, opened the same file twice, and only one shows an unclean shutdown, see reply below by trurl.

Link to post
Apr  9 10:02:10 Tower emhttpd: shcmd (4416): umount /mnt/user
Apr  9 10:02:10 Tower root: umount: /mnt/user: target is busy.
Apr  9 10:02:10 Tower emhttpd: shcmd (4416): exit status: 32
Apr  9 10:02:10 Tower emhttpd: shcmd (4417): rmdir /mnt/user
Apr  9 10:02:10 Tower root: rmdir: failed to remove '/mnt/user': Device or resource busy
Apr  9 10:02:10 Tower emhttpd: shcmd (4417): exit status: 1

You don't have a command line open to a user share somewhere do you?

Link to post

You should see if you can successfully stop the array even when not issuing a shutdown.  If that does not stop cleanly then that might be a bit easier to investigate why as the system is still running.

Link to post

ah ok  no  command line  i not verry good at command line  

 

as for the logs those were both from the "flash log "   folder i posted the last couple  from that directory  so i cant tell if the are shut down logs or not  i just posted the last couple 

 

as for shutting down array.. guess ill have to wait till parity checking is done then  only at 6.9%  so wont be done till tomorrow morning..

i also only thought maybe its my vm backup issue causing this cuz couple of them wont back up  so i figured that might be causing these unclean shut downs.. 

 

but ill re try i guess tommorow morning   just a Stop   and then start

 

when you do a Stop And Start array... does it create Log Files  if its unclean too

 

and how will i know if the array will  shut down start up successfully  will it also report as i dont remember in past  

but its been a while since i did a start and stop more then a year  its just been restart the server  more then anything  other then being up time more then 100 days at a time

well in the past anyways

 

Link to post

If you simply issue the Stop option then if the array stops successfully it was clean.    If it does not stop you can then investigate what is stopping it from stopping.

Link to post
22 minutes ago, comet424 said:

as for the logs those were both from the "flash log "   folder

Any diags manually downloaded on the console will also be saved there.

Link to post

so should i wait till tommorow to stop the array as its doing parity check?  or should i try it now??

 

when you mentioned  any diagnostics manually downloaed on the console be saved there..  

does that mean if i save  anynomomis Diagnostic  download from tools  is saved there too? 

Link to post
1 hour ago, comet424 said:

does that mean if i save  anynomomis Diagnostic  download from tools  is saved there too? 

No, it does when you type "diagnostics" on the console.

Link to post

oh ok    ya i dont use the command prompt  for anything  other then rsync to learn

 

which reminds me fix common issues telling me to change my go file for my keys thing

 

 

as for stoping and starting array do i just wait till tommorow to try again.. since its running sitll parity check as i dont like interrupting but i never know when its ok to stop it

 

so i guessing wait till tommorow   and then hit stop start array...

 

Link to post

i actually dont know..  i know  i get the browser  saying VM Backup  has started  and then it craps out

 

i posted the logs in the VMBackup Plugin  but no one replied so i figured no one knows the answer or the guy that wrote the program.

 

i did today in the mean time of  my last reply  here  i did delete some VMs  that i didnt need anymore just tried cleaning up  figured maybe this problem is caused by the VMs

 

but i dont know if VM Backup ever completes??  i just get the starting   if i remember and then i get error twice  it shows  but the logs really say nothing.

 

what i can try to do before i turn off the array and back on.

 

i could Run the VM Backup  force it and see if i get the errors..  ill post in here..  and  then ill take Off The Array then back On  to see if i get the Parity coming on  due to unsafe shut down and then ill try a reboot and post info

 

i guesss maybe i shouldnt have deleted the VMs i not using  i just trying to think of different ways to clean up to see if it cures things

 

 

Link to post
10 minutes ago, comet424 said:

Take Off The Array then back On  to see if i get the Parity coming on  due to unsafe shut down

Not entirely sure what you mean by "Take Off The Array".

 

3 hours ago, itimpi said:

If you simply issue the Stop option then if the array stops successfully it was clean.    If it does not stop you can then investigate what is stopping it from stopping.

There won't be an unclean shutdown if you stop the array without shutting down, since you won't be shutting down. If the array doesn't stop after some reasonable amount of time then post new diagnostics without shutting down or rebooting.

Link to post
Posted (edited)

take off the Array..  Click Stop..  cuz  either the Array is "ON"   to use it   or your Take it "Off"   take it offline so you cant use it

sorry my dislexia   i dont explain things right 

 

and ok ill do that..  how long is a reasonable amount of time  for shutting down an array as i havent done it in so long and in past it varys  

i have noticed i had issues  using  Space Invaders  Icon Copy thing he made. it corrupts  Unraid  and not sure if his program damaged it..  

he needs a disclaimer that you can not use his program  if your using a Folder with a Space...   so if you use his setup   and use "test" or say "temp"   that works but 

if you use what i have  "Temp Files"    hes program corrupts unraid  i had a hell of time to figure it out.. how to fix it..  it would be stuck in  "starting services"   and it makes unraid un usable.. i had to copy a certain folder  from a backup  for the flash directory..  back to the flash drive  because   it buggers up unraid to the point its unsable and a reboot doesnt fix it..   so i tried to fix his code to make it work for "spaces"   but i couldnt so i just changed  my  "Temp Files"  to "Temp"  to get his icons thing to work.

 

and i not sure if that has also caused  reaccuring issue. of the array

 

do you think that could be the issue too??    would the diaganostic files show anything?  here is the current one this is just from now  after i did a reboot  after updating  so i dunno if it would say anything.. but would it say  a while ago working on the spacemans VM Icons   program  could it caused it???

 

so dunno if the current diagnostics will say anything at the moment    but ill try what you guys said tommorow when parity is done

tower-diagnostics-20210409-1641.zip

Edited by comet424
Link to post

so i stopped and started the array  did not show any issues

 

i stopped array then rebooted  server.. and that didnt show any errors 

 

so i did a diagnostic file  after i did a turn off the array and then back on..

then i turned off the array  rebooted  unraid  and then took a 2nd diagnostic file

 

so hopefully it tells you something..

 

tower-diagnostics-20210410-1311.zip tower-diagnostics-20210410-1257.zip

Link to post

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 you in the 2 i posted..  or the first 2 i posted...

 

i figured my next try  tommorow ill do

 

is turn off all the VMS    then reboot  unraid  and see if anything happens.. and try 1 VM at a time then a reboot.. to see if thats the issue

 

or is there a better test to test the issue?

 

 

Link to post
8 minutes ago, comet424 said:

the diaganostic files never showed

You can see these in syslog yourself, right after plugins finish loading then the go script runs:

 

Apr  7 21:55:51 Tower root: Starting go script
Apr  7 21:55:51 Tower root: Starting emhttpd
Apr  7 21:55:51 Tower emhttpd: Unraid(tm) System Management Utility version 6.9.1
Apr  7 21:55:51 Tower emhttpd: Copyright (C) 2005-2021, Lime Technology, Inc.
Apr  7 21:55:51 Tower emhttpd: unclean shutdown detected

 

Apr  9 10:04:14 Tower root: Starting go script
Apr  9 10:04:14 Tower root: Starting emhttpd
Apr  9 10:04:14 Tower emhttpd: Unraid(tm) System Management Utility version 6.9.2
Apr  9 10:04:14 Tower emhttpd: Copyright (C) 2005-2021, Lime Technology, Inc.
Apr  9 10:04:14 Tower emhttpd: unclean shutdown detected

 

Apr 10 13:02:16 Tower root: Starting go script
Apr 10 13:02:16 Tower root: Starting emhttpd
Apr 10 13:02:16 Tower emhttpd: Unraid(tm) System Management Utility version 6.9.2
Apr 10 13:02:16 Tower emhttpd: Copyright (C) 2005-2021, Lime Technology, Inc.
Apr 10 13:02:16 Tower emhttpd: shcmd (3): /usr/local/emhttp/webGui/scripts/update_access

 

No unclean shutdown after latest reboot.

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.