cinereus

fs-diagnostics-20221004-2321.zip

Thanks. So I will be okay going from 6.11.0 to 6.9.x?

I have all drive set to spin down after 1 hour. I have checked with the File Activity plugin and nothing is showing up. But having left my server for 12+ hours several times the drives never seem to spin down. What else can I check to find out what's going wrong here?

Thanks for this. Why do you need to reassign cache pool?

1. How do I roll back to pre 6.11.0? 2. How do I find which packages I was using with NerdPack so I can manually install them? EDIT, solved 2: cat /boot/config/plugins/NerdPack/NerdPack.cfg

EDIT: Solved the issue. Removed exec zsh from .bash_profile using a userscript And the issue occurs because NerdPack is silently disabled even though release notes don't mention it no longer works and the plugin remains installed.

After installing the update I'm getting this on eth0: Oct 4 01:57:51 fs kernel: tun: Universal TUN/TAP device driver, 1.6 Oct 4 01:57:54 fs ntpd[1467]: Listen normally on 4 eth0 192.168.0.250:123 Oct 4 01:57:54 fs ntpd[1467]: Listen normally on 5 eth0 [fe80::ec4:7aff:fe59:76ee%5]:123 Oct 4 01:57:54 fs ntpd[1467]: new interface(s) found: waking up resolver Oct 4 02:04:12 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Oct 4 02:04:13 fs ntpd[1467]: Deleting interface #4 eth0, 192.168.0.250#123, interface stats: received=40, sent=40, dropped=0, active_time=379 secs Oct 4 02:04:13 fs ntpd[1467]: 216.239.35.0 local addr 192.168.0.250 -> <null> Oct 4 02:04:13 fs ntpd[1467]: 216.239.35.4 local addr 192.168.0.250 -> <null> Oct 4 02:04:13 fs ntpd[1467]: 216.239.35.8 local addr 192.168.0.250 -> <null> Oct 4 02:04:13 fs ntpd[1467]: 216.239.35.12 local addr 192.168.0.250 -> <null> Oct 4 02:04:13 fs ntpd[1467]: Deleting interface #5 eth0, fe80::ec4:7aff:fe59:76ee%5#123, interface stats: received=0, sent=0, dropped=0, active_time=379 secs Oct 4 02:04:15 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX Oct 4 02:04:16 fs ntpd[1467]: Listen normally on 6 eth0 192.168.0.250:123 Oct 4 02:04:16 fs ntpd[1467]: Listen normally on 7 eth0 [fe80::ec4:7aff:fe59:76ee%5]:123 Oct 4 02:04:16 fs ntpd[1467]: new interface(s) found: waking up resolver Oct 4 02:04:22 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Oct 4 02:04:24 fs ntpd[1467]: Deleting interface #6 eth0, 192.168.0.250#123, interface stats: received=4, sent=4, dropped=0, active_time=8 secs Oct 4 02:04:24 fs ntpd[1467]: 216.239.35.0 local addr 192.168.0.250 -> <null> Oct 4 02:04:24 fs ntpd[1467]: 216.239.35.4 local addr 192.168.0.250 -> <null> Oct 4 02:04:24 fs ntpd[1467]: 216.239.35.8 local addr 192.168.0.250 -> <null> Oct 4 02:04:24 fs ntpd[1467]: 216.239.35.12 local addr 192.168.0.250 -> <null> Oct 4 02:04:24 fs ntpd[1467]: Deleting interface #7 eth0, fe80::ec4:7aff:fe59:76ee%5#123, interface stats: received=0, sent=0, dropped=0, active_time=8 secs Oct 4 02:04:25 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX Oct 4 02:04:27 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Oct 4 02:04:35 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Oct 4 02:04:36 fs ntpd[1467]: Listen normally on 8 eth0 192.168.0.250:123 Oct 4 02:04:36 fs ntpd[1467]: Listen normally on 9 eth0 [fe80::ec4:7aff:fe59:76ee%5]:123 Oct 4 02:04:36 fs ntpd[1467]: new interface(s) found: waking up resolver Oct 4 02:05:30 fs vnstatd[6518]: Detected bandwidth limit for "eth0" changed from 1000 Mbit to 100 Mbit.

I used to install zsh by running the following script: # Install Oh My ZSH! HOME="/root" sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" "" --unattended chsh -s $(which zsh) However when I run this now I get Zsh is not installed. Please install zsh first. And now I can't even open a terminal either through web gui or via ssh. I get -bash: exec: zsh: not found Connection to fileserver closed. Why isn't zsh installing like it used to?

It seems ASRock Z690 PG Riptide is now end of life. Is there a similar mobo that people can recommend? Even better if it has 12 SATA instead of only 8.

Thanks. If my NICs are "going bad" is there anything I can do? I think I'd need to replace the whole motherboard?!

I don't get why it would have worked for years with no issue before though? syslog keeps repeating this what does it mean? Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: Detected Tx Unit Hang Oct 3 17:56:14 fs kernel: Tx Queue <20> Oct 3 17:56:14 fs kernel: TDH, TDT <0>, <2> Oct 3 17:56:14 fs kernel: next_to_use <2> Oct 3 17:56:14 fs kernel: next_to_clean <0> Oct 3 17:56:14 fs kernel: tx_buffer_info[next_to_clean] Oct 3 17:56:14 fs kernel: time_stamp <115869ae9> Oct 3 17:56:14 fs kernel: jiffies <11586a9c0> Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: tx hang 17692 detected on queue 20, resetting adapter Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: initiating reset due to tx timeout Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: Reset adapter Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: RXDCTL.ENABLE for one or more queues not cleared within the polling period Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1 eth1: TXDCTL.ENABLE for one or more queues not cleared within the polling period Oct 3 17:56:14 fs kernel: ixgbe 0000:05:00.1: master disable timed out Oct 3 17:56:18 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX Oct 3 17:56:24 fs kernel: ixgbe 0000:05:00.1 eth1: Detected Tx Unit Hang

eth1 is going up and down constantly again even after a reboot. Any idea what the issue is that's causing it to crash every other day? fs-diagnostics-20221003-1735.zip

Thanks. I have now rebooted and will see how it goes. Where do you see the eth1 crash?

Clearer diagnostics after reboot: And here's the system log: Sep 29 14:29:34 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/ TX Sep 29 14:29:34 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:29:40 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:29:40 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:29:46 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:29:47 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:29:56 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:29:56 fs kernel: ixgbe 0000: 05:00.0 eth0: NIC Link is Down Sep 29 14:30:20 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:30:20 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:30:35 fs emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/showLog.php dropbox and drive sync Sep 29 14:30:44 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:30:45 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:30:57 fs kernel: ixgbe 0000:05: 00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX Sep 29 14:30:57 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Sep 29 14:31:14 fs kernel: ixgbe 0000 :05:00.0 eth0: NIC Link is Up 100 Mbps, Flow Control: RX/TX fs-diagnostics-20220929-1434.zip

I just rebooted my server. It took about 5 minutes to reboot but Web GUI is not loading. I have been able to ping on both interfaces and the machine responds to ping. I can access it by SSH. I can see the login prompt on IPMI. However none of my dockers have loaded and I can't even access the login page of the webui. EDIT: resolved, it finally came up a whole 25 minutes later!

Managed to log in long enough to get diagnostics: fs-diagnostics-20220929-1325.zip

I have two interfaces eth0 and eth1. eth0 goes directly to the router and provide and internet connection eth1 goes directly to my PC Last night I noticed that eth0 had dropped. I unplugged and replugged the ethernet cable and all was fine. I had to do this one more time later in the evening. When I woke up this morning I found that eth0 had dropped to 100 Mbps. I unplugged and replugged and it reconnected instantly at 1000 Mbps. A couple of hours later I noticed that eth1 wasn't working. I unplugged and replugged which did nothing. Now eth1 is flickering between connecting and disconnecting. It stays connected for long enough to go to "unidentified network" but doesn't have time to resolve an IP before it says "interface down" and my PC says "not connected". As I was trying to diagnose this it seems eth0 has gone down completely and won't connect at all. This means I can't even get diagnostics. On the outside it seems that the onboard ethernet is just dying! Is this possible? Could I see anything in diagnostics to show whether this is the case? The hardware is Supermicro SuperChassis CSE-826 with a X9DRH-7TF V1.02 motherboard.

Loading pnacl program… done. Connecting to root@servername… OpenSSH_8.8p1, OpenSSL 1.0.2k 26 Jan 2017 debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling debug1: Connecting to servername [x.x.x.x] port xxxx. debug1: Connection established. debug1: getpeername failed: Function not implemented debug1: identity file /.ssh/identity/id_rsa type -1 debug1: identity file /.ssh/identity/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.4 debug1: compat_banner: match: OpenSSH_8.4 pat OpenSSH* compat 0x04000000 debug1: Authenticating to servername:port as 'root' debug1: load_hostkeys: fopen /.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen //etc/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen //etc/ssh_known_hosts2: No such file or directory debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-ed25519 SHA256:wdRRHRK0r5xP5rwNdoqrt0UYA2WLXnV3UXkU6nVKQvk debug1: load_hostkeys: fopen /.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen //etc/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen //etc/ssh_known_hosts2: No such file or directory debug1: Host '[servername]:port' is known and matches the ED25519 host key. debug1: Found key in /.ssh/known_hosts:1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /.ssh/identity/id_rsa explicit debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<redacted> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /.ssh/identity/id_rsa debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: keyboard-interactive Any ideas?

Nothing about my config has changed but it's stopped working as of this morning. I still have ~/.ssh/authorized_keys set up correctly. I'm still using the same id_rsa file But it's not attempting to use it and goes straight to a password prompt every time. This has been working for two years without issue before.

Mapped network drive.

64GB RAM. Try as I might I've never got Windows 10 to use more than 25 GB at a time.

Afraid I'm still getting the same issue. Sometimes even moving the mouse over folders is enough to crash it.

I wasn't doing any file transfer or reading/writing to the disk at all. It seems to have stopped now finally but it was going on for several hours.

Thanks. I'll try that and see if it helps...

Any ideas?