PhreakShow
Dabbler
- Joined
- Sep 16, 2020
- Messages
- 17
Hi.
I have two HP Microserver Gen10, X3418, 8 GB RAM, Intel X540-T2 in the bigger slot. Also, there's four 8TB WD Red drives, but I don't think they matter for now.
BIOS is at ZA10A380, it used to be ZA10A360 and I tried updating it to resolve the issue, no change. I am using FreeNAS-11.3-U4.1 on both units, they have the same problem.
At first I noticed failed backup jobs that run over night. I have a windows server 2019 that copies files to mapped smb shares on the freenas machines.
Mid-backup robocopy complained about a network drive that is no longer reachable. In this state, I cannot reach the machine via ping, ssh, browser, share.
Furthermore, if I plug a monitor in this state, no image appears. Pressing the power button seems to trigger a shutdown (sudden HDD activity on the LED), but it does not appear in the "last" log of shutdowns.
Then I paid more attention to the network devices and the boot process. During startup, either both or one NIC port fail to get recognized.
With this message, both ix0 and ix1 fail to get recognized by the OS. No link, no ping, and no status in ifconfig.
Sometimes, only one port fails, showing:
The issues is the same for both machines. 8GB is plenty of RAM for a single PCI resource.
I am thinking of abandoning FreeNAS and switching back to windows, because even dynamic drives with a software raid5 seem to be more reliable than this.
Any ideas on how to resolve that, or even grasp the actual issue here?
I have two HP Microserver Gen10, X3418, 8 GB RAM, Intel X540-T2 in the bigger slot. Also, there's four 8TB WD Red drives, but I don't think they matter for now.
BIOS is at ZA10A380, it used to be ZA10A360 and I tried updating it to resolve the issue, no change. I am using FreeNAS-11.3-U4.1 on both units, they have the same problem.
At first I noticed failed backup jobs that run over night. I have a windows server 2019 that copies files to mapped smb shares on the freenas machines.
Mid-backup robocopy complained about a network drive that is no longer reachable. In this state, I cannot reach the machine via ping, ssh, browser, share.
Furthermore, if I plug a monitor in this state, no image appears. Pressing the power button seems to trigger a shutdown (sudden HDD activity on the LED), but it does not appear in the "last" log of shutdowns.
Then I paid more attention to the network devices and the boot process. During startup, either both or one NIC port fail to get recognized.
Code:
Sep 16 13:46:20 freenas02 ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xfffa00000-0xfffbfffff,0xfffe00000-0xfffe03fff irq 35 at device 0.1 on pci3 Sep 16 13:46:20 freenas02 ix0: Using MSI-X interrupts with 5 vectors Sep 16 13:46:20 freenas02 ix0: Hardware initialization failed Sep 16 13:46:20 freenas02 device_attach: ix0 attach returned 5
With this message, both ix0 and ix1 fail to get recognized by the OS. No link, no ping, and no status in ifconfig.
Sometimes, only one port fails, showing:
Code:
Sep 15 17:37:06 freenas02 ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xf0c00000-0xf0c03fff irq 35 at device 0.1 on pci3 Sep 15 17:37:06 freenas02 ix1: 0x200000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). Sep 15 17:37:06 freenas02 ix1: Unable to allocate bus resource: memory Sep 15 17:37:06 freenas02 ix1: Allocation of PCI resources failed Sep 15 17:37:06 freenas02 device_attach: ix1 attach returned 6
The issues is the same for both machines. 8GB is plenty of RAM for a single PCI resource.
I am thinking of abandoning FreeNAS and switching back to windows, because even dynamic drives with a software raid5 seem to be more reliable than this.
Any ideas on how to resolve that, or even grasp the actual issue here?