search for: systemboard

...its status, > although from what I remember from previous posts, it's better to just > let the BIOS think it's a JBOD and use the linux software RAID tools > directly. > I see, thank you. Right now I am running off one of the disks because of the mishap, I am also waiting for a systemboard replacement at which time I can decided whether to go with Linux software RAID, ie mdadm, or back to the Intel BIOS RAID. The latter lacks any progress indicators in BIOS when rebuilding an array which took around 20 hours for a 256 GB RAID 1 setup and it is annoying not to know the status of the...

I have recently upgraded to 2.6.18-194.3.1.el5 and within several days the machine crashed with the following error (repeating in mcelog): MCE 0 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 2 BANK 8 MISC 41 MCG status: MCi status: Error overflow Uncorrected error MCi_MISC register valid Processor context corrupt MCA: MEMORY CONTROLLER AC_CHANNEL0_ERR

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.

Very strange and as you suggested delete the ifcfg-eth0 file and recreate, specify your settings. I suspect your wireless device and or systemboard is faulty. Is there a BIOS hardware self-test you could perform to check the integrity of your hardware? On Sun, Feb 9, 2020, at 8:10 AM, Nicolas Kovacs wrote: > Hi, > > I've done my fair share of CentOS 7 installations, but this is the first time I > have this kind of weird pro...

...ough from what I remember from previous posts, it's better to just > > let the BIOS think it's a JBOD and use the linux software RAID tools > > directly. > > > I see, thank you. Right now I am running off one of the disks because of the mishap, I am also waiting for a systemboard replacement at which time I can decided whether to go with Linux software RAID, ie mdadm, or back to the Intel BIOS RAID. > > The latter lacks any progress indicators in BIOS when rebuilding an array which took around 20 hours for a 256 GB RAID 1 setup and it is annoying not to know the stat...

...f there was one, this should have been captured. >> There are a lot of clients behind this system so getting the right >> filter syntax >> might be difficult. >> >> This Problem seems to be on all HP Proliant DL380Gen9 and DL360Gen9 >> which have in fact the same systemboard. >> >> >> MfG / regards, >> Holger Baust >> >> -- >> freenet Datenkommunikations GmbH >> Ein Unternehmen der freenet Group >> Willst?tterstra?e 13 >> D-40549 D?sseldorf >> >> Tel.: +49 (0) 211 53087 519 >> Fax: +49 (0) 21...

Hello. We are using pxelinux for years to boot Linux via PXE since years. Since EFI is spreading, I changed configuration to be able to boot EFI systems. The "Client": - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), FW: 5719-v1.38 The Server: - ISC-DHCP with tfpd-hpa running on Debian 6.x -

I have been having some problems with hardware RAID 1 on the motherboard that I am running CentOS 7 on. After a BIOS upgrade of the system, I lost the RAID 1 setup and was no longer able to boot the system. Testdisk revealed that the partition tables had been damaged and because I had earlier saved information from fdisk, I was able to recreate the partitions. However, booting into the BIOS and

...e difficult. tftpd and dhcp are on the same system. If there was one, this should have been captured. There are a lot of clients behind this system so getting the right filter syntax might be difficult. This Problem seems to be on all HP Proliant DL380Gen9 and DL360Gen9 which have in fact the same systemboard. MfG / regards, Holger Baust -- freenet Datenkommunikations GmbH Ein Unternehmen der freenet Group Willst?tterstra?e 13 D-40549 D?sseldorf Tel.: +49 (0) 211 53087 519 Fax: +49 (0) 211 5381573 Mobil: +49 (0) 170 4930127 holger.baust at freenet.ag www.freenet.de mobil.freenet.de www.mobilcom-de...

On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > Hello. > > We are using pxelinux for years to boot Linux via PXE since years. > Since EFI is spreading, I changed configuration to be able to boot EFI > systems. > > The "Client": > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > - NIC used for booting: HP Embedded LOM 331i

...t I remember from previous posts, it's better to just >>> let the BIOS think it's a JBOD and use the linux software RAID tools >>> directly. >>> >> I see, thank you. Right now I am running off one of the disks because of the mishap, I am also waiting for a systemboard replacement at which time I can decided whether to go with Linux software RAID, ie mdadm, or back to the Intel BIOS RAID. >> >> The latter lacks any progress indicators in BIOS when rebuilding an array which took around 20 hours for a 256 GB RAID 1 setup and it is annoying not to know...

Hello, I''ve looked around Google and the zfs-discuss archives but have not been able to find a good answer to this question (and the related questions that follow it): How well does ZFS handle unexpected power failures? (e.g. environmental power failures, power supply dying, etc.) Does it consistently gracefully recover? Should having a UPS be considered a (strong) recommendation or

I''m not sure if this is a problem with the iscsitarget or zfs. I''d greatly appreciate it if it gets moved to the proper list. Well I''m just about out of ideas on what might be wrong.. Quick history: I installed OS 2008.05 when it was SNV_86 to try out ZFS with VMWare. Found out that multilun''s were being treated as multipaths so waited till SNV_94 came out to