kysdaddy Posted November 20, 2020 Share Posted November 20, 2020 Parity check is running, Smart log: Diagnostic attached. I have no idea what to do next, the disk is not disabled, the server seems to be running fine. Thoughts? tower-diagnostics-20201120-0715.zip Quote Link to comment
JorgeB Posted November 20, 2020 Share Posted November 20, 2020 Those are normal, one thing to keep an eye on for SAS devices is this: Elements in grown defect list: 0 It should be 0 or a low number and stable, large number and/or it keeps rising it's a very bad sign. Quote Link to comment
kysdaddy Posted November 20, 2020 Author Share Posted November 20, 2020 Sorry for the stupid question but... What do I do about this, will this error go away once the parity check completes or is there something else that I should do? Thx Chas Quote Link to comment
JorgeB Posted November 20, 2020 Share Posted November 20, 2020 25 minutes ago, kysdaddy said: will this error go away once the parity check completes It will if it's a parity sync, parity is invalid until the sync is done. Quote Link to comment
kysdaddy Posted November 20, 2020 Author Share Posted November 20, 2020 It's a parity check? Quote Link to comment
JorgeB Posted November 20, 2020 Share Posted November 20, 2020 Are you asking me? If it's a parity check then please post diags. Quote Link to comment
kysdaddy Posted November 20, 2020 Author Share Posted November 20, 2020 No, again Sorry for the confusion. It says that it is a parity check. But then again I have proven my ignorance quite well when it come to this system. Dropped a new diagnostics just in case. tower-diagnostics-20201120-1352.zip Quote Link to comment
JorgeB Posted November 20, 2020 Share Posted November 20, 2020 There were read errors on disk15, those should be visible in the GUI, you should also have received a notification about that. Run an extended SMART test on that disk. P.S. There's also filesystem corruption on the cache pool, you should backup and re-format. Quote Link to comment
kysdaddy Posted November 20, 2020 Author Share Posted November 20, 2020 Yes I was aware of the read errors, that was the initial question that I posted. I didn't know if there was something that I should do to deal with disk 15 and the errors. Are there directions on completing the backup and reformat anywhere? Just to be sure that I don't foul it up? Should I wait for the parity check to complete? Or is that a priority? I have a history of putting the cart before the horse and screwing things up even more. Thx Quote Link to comment
JorgeB Posted November 20, 2020 Share Posted November 20, 2020 7 minutes ago, kysdaddy said: that was the initial question that I posted. You only mentioned the SMART errors, not the same thing. 7 minutes ago, kysdaddy said: Are there directions on completing the backup and reformat anywhere? Basically just copy everything anywhere else, format and copy back, you can use this to help. 9 minutes ago, kysdaddy said: Should I wait for the parity check to complete? If there's been no more errors and it's going at a normal speed you can wait for the check to finish. Quote Link to comment
kysdaddy Posted November 22, 2020 Author Share Posted November 22, 2020 Hey JorgeB, I must be completely blind. I have followed the instructions up to the point of " Basically just copy everything anywhere else, format" I just don't have an option to format? What am I missing I see both drive as unassigned drives but no option to format. Chas Quote Link to comment
kysdaddy Posted November 22, 2020 Author Share Posted November 22, 2020 I had to do single drive first and then add the second to the pool. Chas Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 Hello, Twice now I have woken up to a "frozenish" server with no access to download a diagnostic and no way to properly shutdown and restart the machine, Dashboard blank and bottom half of main tab blank. Even reboot on cli wouldn't work. Tried via ssh and both terminal links via gui. Both times I had to do a hard shutdown via hardware power button. The first time this happened, things continued to spiral on restart. Dockers failed to load , the restart didn't change anything. A day and a half later after much appreciated help from JorgeB, I reformatted my cache and started trying to rebuild. I got everything setup the way I wanted it, all was good. I walked into my office this morning and dejavu! Today I had no docker access, Dashboard and no access to restart,. Today after I did a hard restart, the machine is back to normal. Here is the diagnostic pulled immediately after the machine restarted. Any help understanding what is happening is appreciated. Chas tower-diagnostics-20201126-0851.zip Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 I just remembered something that I changed yesterday. I enabled mover logging in schedule, and had not seen the "fix common problems" warning, I just disabled that. Yesterday I also enabled SSD Trim Settings set to run daily at 3 am, I have disabled that as well With my history, I am guessing that those two changes are what killed me this time, please correct me if I'm wrong. Chas Quote Link to comment
JorgeB Posted November 26, 2020 Share Posted November 26, 2020 Unfortunately diags after rebooting are not much help, you can try this. Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 I followed the directions. I created a syslog1 share, set it up as preffercache and set the local syslog to that folder. I set the local ip as the server and clicked apply. the directions say that I should find a file in the folder immediately called syslog-192.168.1.2.log. I check the share and it is empty. What did I miss this time. Thanks again Quote Link to comment
JorgeB Posted November 26, 2020 Share Posted November 26, 2020 I forgot there's currently a problem with the beta and this, it should be fixed on the next one. Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 Thanks, I'll remove those settings. And keep my fingers crossed. Is it just option 3 or is syslog not working on the beta? I could setup on a remote if that still works? Chas Quote Link to comment
JorgeB Posted November 26, 2020 Share Posted November 26, 2020 I believe remote still works. Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 Does the remote server have to be local, can I use my remote machines swag address? server.xxxxx.net? Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 I downloaded kiwi syslog and dropped it onto my windows desktop, set it up and tested the folder, it passed the test. I setup syslog in unraid But nothing is populating in the external folder. This is the latest accessing system log via tools menu Nov 26 11:15:23 Tower ool www[16725]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Nov 26 11:15:25 Tower rsyslogd: invalid or yet-unknown config file command 'UDPServerAddress' - have you forgotten to load a module? [v8.2002.0 try https://www.rsyslog.com/e/3003 ] Nov 26 11:15:25 Tower rsyslogd: invalid or yet-unknown config file command 'UDPServerRun' - have you forgotten to load a module? [v8.2002.0 try https://www.rsyslog.com/e/3003 ] Nov 26 11:15:25 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="18067" x-info="https://www.rsyslog.com"] start Did I do something wong, or does the beta problem extend to remote as well. Chas Quote Link to comment
JorgeB Posted November 26, 2020 Share Posted November 26, 2020 Sorry, never needed to use it so idea if it's well configured, maybe someone else can help, according to Tom remote server is still working. Quote Link to comment
kysdaddy Posted November 26, 2020 Author Share Posted November 26, 2020 Thanks for trying! Chas 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.