February 8, 20233 yr The unraid device didn't shut down early before my home power outage today, and the contents of the share disappeared after booting, and neither Docker nor VMS would start. I tried to reboot the device several times and it didn't solve the problem, here is my diagnostic file. tower-diagnostics-20230208-1820.zip Edited February 10, 20233 yr by tsq456
February 8, 20233 yr Community Expert Your syslog is full of errors on the sdb device (cache2) so that is the likely cause of your problem. Not sure though of the best way to proceed - hopefully @JorgeB as the expert on these things will chime in.
February 8, 20233 yr Author 5 minutes ago, itimpi said: Your syslog is full of errors on the sdb device (cache2) so that is the likely cause of your problem. Not sure though of the best way to proceed - hopefully @JorgeB as the expert on these things will chime in. Thank you for your reply, There was a similar operation before, but this problem did not occur...
February 8, 20233 yr Community Expert Check filesystem on disk1 and post new diags after array start.
February 8, 20233 yr Author 13 minutes ago, JorgeB said: Check filesystem on disk1 and post new diags after array start. this is the new diagstower-diagnostics-20230208-1923.ziptower-diagnostics-20230208-1923.zip
February 8, 20233 yr Community Expert Solution It's still not fixed, you must run xfs_repair without the -n flag or nothing will be done.
February 8, 20233 yr Author 11 minutes ago, JorgeB said: It's still not fixed, you must run xfs_repair without the -n flag or nothing will be done. Just remove the flag, or use another flag? I remove the -n and it reports an error with message:
February 8, 20233 yr Author 2 hours ago, JorgeB said: Use -L I just tried file check with -L flag. After it, I found that SHARES can displayed and VMS could be started ( Docker service still could not be started). Now I tried to stop the array and check it again, but I found that the array is stopped in STOPPING state and can't really stop completely Edited February 8, 20233 yr by tsq456
February 8, 20233 yr Author 26 minutes ago, tsq456 said: I just tried file check with -L flag. After it, I found that VMS could be displayed ( Docker service still could not be started). Now I tried to stop the array and check it again, but I found that the array is stopped in STOPPING state and can't really stop completely The array is actually stopped, but the status is always STOPPING, because vms have prompted "Array must be started to view Virtual Machines" syslog: syslog.txt what can I do with this problem? I can not do file check again because of it. Edited February 8, 20233 yr by tsq456
February 8, 20233 yr Community Expert Still a lot of error on the syslog, type reboot in the console, if it doesn't reboot after 5 minutes force it, then post new diags after array start.
February 9, 20233 yr Author 11 hours ago, JorgeB said: Still a lot of error on the syslog, type reboot in the console, if it doesn't reboot after 5 minutes force it, then post new diags after array start. The reboot goes well and this is the most new diags tower-diagnostics-20230209-1200.zip
February 9, 20233 yr Community Expert Looks good for now, except the docker image, it needs to be recreated.
February 10, 20233 yr Author 20 hours ago, JorgeB said: Looks good for now, except the docker image, it needs to be recreated. It's okay now! thanks a lot for ur help!
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.