March 16, 20179 yr Similar to other threads, I am experiencing an issue where the Web GUI and shares are not accessible. I opened up the console and notice that a shfs process is pegging the cpu at 100%. I tried to run "diagnostics" and it will not complete (remains on "starting ..."), I tried to kill the PID for the shfs process and it does not respond (hangs the console), and I tried "powerdown" which also hangs on the initial shutdown warning. System is an AMD X4 CPU @ 2.8 GHz with 16 GB RAM. Using a Dell PERC H310 RAID controller with eight drives attached (1 parity + 7 data) in IT mode. I have not had any issues with unRAID previously and nothing that I can think of has changed to cause this issue. Running unRAID 6.3.2. Any suggestions on how to proceed?
March 16, 20179 yr What do you mean when you say 'I have not had any issues with unRAID previously'? What has changed between now and previously?
March 16, 20179 yr The autostart setting is in config/disk.cfg and you can edit it. Try setting it to not autostart, boot in SAFE mode, and see if you can get a diagnostic.
March 16, 20179 yr The Fix Common Problems plugin has a special Troubleshooting Mode, that if enabled will constantly monitor and save diagnostics and syslogs to the flash drive, until you reboot. You don't want to run it normally, because it bloats the syslog hugely, but it's perfect for this kind of issue, when the machine can't be instructed to save a last diagnostics and syslog. First, let the plugin run its tests and see if it notes anything that might be causing trouble.
March 16, 20179 yr Author 2 hours ago, ashman70 said: What do you mean when you say 'I have not had any issues with unRAID previously'? What has changed between now and previously? I have not experienced this issue with unRAID before; in fact, I have not experienced any show stopping issues like this. I am not aware of anything that has changed between yesterday and today - I did not change any config, hardware, etc.
March 16, 20179 yr Author 2 hours ago, trurl said: The autostart setting is in config/disk.cfg and you can edit it. Try setting it to not autostart, boot in SAFE mode, and see if you can get a diagnostic. 2 hours ago, RobJ said: The Fix Common Problems plugin has a special Troubleshooting Mode, that if enabled will constantly monitor and save diagnostics and syslogs to the flash drive, until you reboot. You don't want to run it normally, because it bloats the syslog hugely, but it's perfect for this kind of issue, when the machine can't be instructed to save a last diagnostics and syslog. First, let the plugin run its tests and see if it notes anything that might be causing trouble. In order to get to SAFE mode and / or run Fix Common Problems (which I already have installed and was not reporting issues previously), how do I reboot the server? It is not responding to powerdown from the terminal.
March 16, 20179 yr But you did an upgrade right? I assume things were fine before the upgrade and you started experiencing problems after the upgrade?
March 16, 20179 yr 30 minutes ago, autumnwalker said: In order to get to SAFE mode and / or run Fix Common Problems (which I already have installed and was not reporting issues previously), how do I reboot the server? It is not responding to powerdown from the terminal. poweroff is the correct command. If that doesn't work after about 2 minutes you may have to do it the hard way by holding the power button.
March 16, 20179 yr Author 37 minutes ago, ashman70 said: But you did an upgrade right? I assume things were fine before the upgrade and you started experiencing problems after the upgrade? I did, but things have been running fine since the upgrade until today. I have been running 6.3.2 since February 22.
March 16, 20179 yr Author 9 minutes ago, trurl said: poweroff is the correct command. Ah! Thank you. I will try poweroff.
March 16, 20179 yr So nothing has changed as far as you can tell, and all of a sudden, things just stopped working?
March 16, 20179 yr Author 5 minutes ago, ashman70 said: So nothing has changed as far as you can tell, and all of a sudden, things just stopped working? So far as I can tell, nothing has changed. The only thing that may have changed (without my intervention) is a hardware failure (no previous indications) or a Docker update.
Archived
This topic is now archived and is closed to further replies.