[CentOS] LSI driver and SSD status error in IPMI
Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other) After boot the status for the SSDs changing in ERROR The same thing happen when boot with the install CD Otherwise everything works fine. Is this hurt? Can I do something? Also I tried to install the latest LSI driver (06.809.18.00), but seems it is not loaded after restart: As the official driver install guide say, before the driver install, I installed the dkms from the epel repo. /var/log/messages: systemd-modules-load: Failed to find module 'override megaraid_sas 3.10.* weak-updates/megaraid_sas' /etc/modules-load.d/megaraid_sas.conf: override megaraid_sas 3.10.* weak-updates/megaraid_sas #modinfo megaraid_sas filename: /lib/modules/3.10.0-229.14.1.el7.x86_64/kernel/drivers/scsi/megaraid/megaraid_sas.ko description:LSI MegaRAID SAS Driver author: megaraidli...@lsi.com version:06.805.06.01-rh2 license:GPL rhelversion:7.1 srcversion: C0124BBE9453A621D4086DB alias: pci:v1000d005Fsv*sd*bc*sc*i* alias: pci:v1000d005Dsv*sd*bc*sc*i* alias: pci:v1000d002Fsv*sd*bc*sc*i* alias: pci:v1000d005Bsv*sd*bc*sc*i* alias: pci:v1028d0015sv*sd*bc*sc*i* alias: pci:v1000d0413sv*sd*bc*sc*i* alias: pci:v1000d0071sv*sd*bc*sc*i* alias: pci:v1000d0073sv*sd*bc*sc*i* alias: pci:v1000d0079sv*sd*bc*sc*i* alias: pci:v1000d0078sv*sd*bc*sc*i* alias: pci:v1000d007Csv*sd*bc*sc*i* alias: pci:v1000d0060sv*sd*bc*sc*i* alias: pci:v1000d0411sv*sd*bc*sc*i* depends: intree: Y vermagic: 3.10.0-229.14.1.el7.x86_64 SMP mod_unload modversions signer: CentOS Linux kernel signing key sig_key: E9:9F:C4:37:BD:9C:BF:B4:F1:B1:DA:87:C1:57:FF:66:56:9B:EE:66 sig_hashalgo: sha256 parm: lb_pending_cmds:Change raid-1 load balancing outstanding threshold. Valid Values are 1-128. Default: 4 (int) parm: max_sectors:Maximum number of sectors per IO command (int) parm: msix_disable:Disable MSI-X interrupt handling. Default: 0 (int) parm: msix_vectors:MSI-X max vector count. Default: Set by FW (int) parm: allow_vf_ioctls:Allow ioctls in SR-IOV VF mode. Default: 0 (int) parm: throttlequeuedepth:Adapter queue depth when throttled due to I/O timeout. Default: 16 (int) parm: resetwaittime:Wait time in seconds after I/O timeout before resetting adapter. Default: 180 (int) parm: smp_affinity_enable:SMP affinity feature enable/disbale Default: enable(1) (int) Can somebody tell me how to get the driver to work? Thanks, -- Levi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
On Thu, Oct 15, 2015 at 5:50 PM, wrote: > Mike - st257 wrote: > > Hello List, > > > > I'm ironing out details to upgrade a few systems to CentOS7. > > > > My servers have BMC with Serial over LAN support. In C5 and C6, I > determined how to have BIOS/POST, kernel, and serial console access. I'm > reading up on the method to accomplish the pieces with C7. > > > > Presently SoL output works, so I see BIOS/POST messages and the GRUB > boot list. > > My changes to enable serial redirection for the kernel do not appear to > work. > > > > I've made the following changes to GRUB2's /etc/grub/default config > file: -- removed rhgb > > You did take out "quiet", too? > I did not. I would expect what shows up on the VGA console to be identical on the serial console. I'll give that a shot today. To make matters more complex, this is an offsite box for which I've implemented full disk encryption. And if I don't get the LUKS passphrase prompt on the serial console, well I'm in a bind... > > mark > > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
On 10/16/2015 08:23 AM, Mike - st257 wrote: On Thu, Oct 15, 2015 at 5:50 PM, wrote: You did take out "quiet", too? I did not. I would expect what shows up on the VGA console to be identical on the serial console. ... To make matters more complex, this is an offsite box for which I've implemented full disk encryption. And if I don't get the LUKS passphrase prompt on the serial console, well I'm in a bind... For the LUKS prompt to show in text mode you do have to remove the quiet. I'd be interested in finding out if the /etc/default/grub that I posted works for you (with the proper change in UUID's of course). The key things for me to get this working was getting the bit rate correct (the GRUB serial port settings do not propagate to the kernel; you have to set all the serial port settings on the kernel command line); you have to make sure the bit rate of the kernel's serial console and your SoL BMC are the same (and your original problem description made it sound like they were not set up the same); the documentation to set this up is found in /usr/share/doc/kernel-doc-3.10.0/Documentation/serial-console.txt which is part of the kernel-doc package. For hardware (RTS) flow control at the kernel (and assuming your SoL uses 115200 for the bit rate, and assuming you want the VGA to still be a console), you might want the parameters: console=ttyS0,115200n8r console=tty0 You don't actually have to keep the VGA as a console, incidentally, for either GRUB or the kernel. I have run a machine that way before. I personally am not a fan of using flow control on a console; I tend to just set the bit rates lower (I have gotten burned before by RTS/CTS flow control on a device console). But that's just my personal preference; the 'r' at the end of the parameters for the serial console selects RTS/CTS flow control. By default the kernel will set up the serial console for 9600n8 operation, regardless of what you set it for GRUB or the serial console redirect in your BMC setup. I'll reiterate that systemd does the Right Thing for the case of a serial console, and spawns a getty with the same parameters as you set on the kernel's console line; you do not need to create a separate .service file for the serial console's getty, in my experience. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
On 10/16/2015 09:14 AM, Lamar Owen wrote: [It is documented that] by default the kernel will set up the serial console for 9600n8 operation, regardless of what you set it for GRUB or the serial console redirect in your BMC setup. Replying to myself with a correction to my statement and a clarification while it is documented this way, I do remember having a bit rate mismatch without specifying a bit rate of 9600, so it's possible the default bit rate was changed upstream. And it's possible I that I am remembering incorrectly, and just put the parameter there anyway. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
I started to compose this message, then got busy with other work... Hopefully I'll have better details by the end of today. Thanks Lamar! On Thu, Oct 15, 2015 at 3:54 PM, Lamar Owen wrote: > On 10/15/2015 03:05 PM, Mike - st257 wrote: > >> Would anyone be so kind as to share their experience? >> What has worked for your BMC/SoL configurations? >> > I have a C7 server with a physical RS-232 console, but the config should > be similar. I did not have to generate a systemd service for this; systemd > saw the console line and automatically started the getty without me having > to generate a .service file (as far as I recall all I had to do was > generate the proper /etc/default/grub, and then run 'grub2-mkconfig -o > /boot/grub2/grub.cfg' and it Just Worked). > > Now, I have the system set for console on both the VGA and on ttyS0, and I > am not using flow-control. Here's what I have that works (again with a > physical ttyS0): > > [root@backup670 ~]# cat /etc/default/grub > GRUB_TIMEOUT=5 > GRUB_DEFAULT=saved > GRUB_DISABLE_SUBMENU=true > GRUB_SERIAL_COMMAND="serial --unit=0 --speed=9600 --word=8 --parity=no > --stop=1" > GRUB_TERMINAL_OUTPUT="console serial" > I didn't have Term Output specified as you do. Probably the biggest problem right there, g'ah! ( will know when I have a moment to test ) > GRUB_CMDLINE_LINUX="rd.md.uuid=long-uuid-string crashkernel=auto > rd.lvm.lv=vg/swap > rd.lvm.lv=vg/root rd.md.uuid=another-long-uuid console=tty0 > console=ttyS0,9600 rd_NO_PLYMOUTH" > I didn't have the option to disable Plymouth. I see you don't have flow control enabled, otherwise you'd have 9600n8r I'll try it without n8r. > GRUB_DISABLE_RECOVERY="true" > > > Also see: http://0pointer.de/blog/projects/serial-console.html > > There should be no need to modify any .service files; simply editing > /etc/default/grub and regenerating grub2's The baud rate I used is not specified in any of the service files systemd generates. But as you've said I should _not need_ a service file (which is much like CentOS6 behaved with serial kernel params). > config should be enough; it was in my case (I verified by looking through > root's .bash_history and finding the lines around editing /etc/default/grub > and not finding any edits of any .service files) > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Debugging Kernel Problems
Not sure if this is the correct subject line but my recently installed Centos build (Linux localhost.localdomain 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Sep 15 15:05:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) periodically just freezes - completely locks up, no activity, nothing in the logs, just stops dead requiring a power off and reboot. I've really looked around to try and find the _best_ way to set up debugging but there is a lot written about it from a lot of parties but I'm not sure who the definitive source is. I did try booting with the 'CentOS Linux (3.10.0-229.14.1.el7.x86_64) 7 (Core) with debugging' option but that really didn't add anything to finding a solution. Dmesg did report this however: dmesg|grep debug [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-229.14.1.el7.x86_64 root=UUID=1928d2da-784c-4b18-868c-f9858bceea6d ro crashkernel=auto rhgb quiet LANG=en_US.UTF-8 systemd.debug [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-229.14.1.el7.x86_64 root=UUID=1928d2da-784c-4b18-868c-f9858bceea6d ro crashkernel=auto rhgb quiet LANG=en_US.UTF-8 systemd.debug [0.940176] ehci-pci :00:12.2: debug port 1 [0.946472] ehci-pci :00:13.2: debug port 1 [1.238335] systemd[1]: Unknown kernel switch systemd.debug. Ignoring. [5.083981] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts [5.206423] systemd[1]: Unknown kernel switch systemd.debug. Ignoring. Which I found interesting. So, can anyone point me to a detailed guide to debugging what's going on with my build that will help me solve my locking problem? BTW, I think it might be my wireless Atheros equipped PCI card (dmesg|grep -i atheros [2.231264] ath5k: phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) but can't be sure because I've not any real proof that's the issue. Thanks in advance for your patience and assistance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
Mike - st257 wrote: > On Thu, Oct 15, 2015 at 5:50 PM, wrote: >> Mike - st257 wrote: >> > My servers have BMC with Serial over LAN support. In C5 and C6, I >> determined how to have BIOS/POST, kernel, and serial console access. I'm >> reading up on the method to accomplish the pieces with C7. >> > >> > Presently SoL output works, so I see BIOS/POST messages and the GRUB >> boot list. >> > My changes to enable serial redirection for the kernel do not appear >> to work. >> > >> > I've made the following changes to GRUB2's /etc/grub/default config >> file: -- removed rhgb >> >> You did take out "quiet", too? > > I did not. > I would expect what shows up on the VGA console to be identical on the > serial console. > > I'll give that a shot today. Do. That hides everything before the o/s switches root. It's *possible* that it's hiding where you're being prompted for the LUKS password. Personally, I'd have left / unencrypted mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Semi-OT: torque, pbs_mom, cpuset, loglevel
We're running the current version of torque. On our small supercomputer (an SGI), no updates to torque since July, but just recently - someone may be trying something new - /var/log/messages is on-and-off being spammed with Oct 15 18:02:04 servername pbs_mom: LOG_INFO::create_job_cpuset, creating cpuset for job 1971[656].york.cit.nih.gov: 1 cpus (12), 1 mems (1) and I mean thousands of lines. I tried to adjust the loglevel of pbs_mom, but it appeared to make *no* change, and their "documentation" and "manpage" simply does not describe what message level each value of loglevel produces. Anyone have a clue? I've been googling, and not finding anything of use. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Debugging Kernel Problems
On Fri, Oct 16, 2015 at 7:33 AM, Tod wrote: > Not sure if this is the correct subject line but my recently installed > Centos build (Linux localhost.localdomain 3.10.0-229.14.1.el7.x86_64 #1 SMP > Tue Sep 15 15:05:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) periodically > just freezes - completely locks up, no activity, nothing in the logs, just > stops dead requiring a power off and reboot. "nothing in the logs"? Have you run memtest for an extended period of time? You might first want to eliminate the possibility that this is a hardware problem. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Debugging Kernel Problems
If you have hardware raid on this machine, try to mount xfs partitions with nobarrier. We had similar freezes and this helped for us. On Fri, Oct 16, 2015 at 9:04 PM, Akemi Yagi wrote: > On Fri, Oct 16, 2015 at 7:33 AM, Tod wrote: > > Not sure if this is the correct subject line but my recently installed > > Centos build (Linux localhost.localdomain 3.10.0-229.14.1.el7.x86_64 #1 > SMP > > Tue Sep 15 15:05:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) periodically > > just freezes - completely locks up, no activity, nothing in the logs, > just > > stops dead requiring a power off and reboot. > > "nothing in the logs"? Have you run memtest for an extended period of > time? You might first want to eliminate the possibility that this is a > hardware problem. > > Akemi > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Marius Vaitiekūnas ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Debugging Kernel Problems
Akemi Yagi wrote: > On Fri, Oct 16, 2015 at 7:33 AM, Tod wrote: >> Not sure if this is the correct subject line but my recently installed >> Centos build (Linux localhost.localdomain 3.10.0-229.14.1.el7.x86_64 #1 >> SMP >> Tue Sep 15 15:05:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) >> periodically just freezes - completely locks up, no activity, >> nothing in the logs, just stops dead requiring a power off and reboot. > > "nothing in the logs"? Have you run memtest for an extended period of > time? You might first want to eliminate the possibility that this is a > hardware problem. Actually, we've had that occasionally, on a number of boxes. I *think* they were all SuperMicros (sold by Penguin), and they become unresponsive - when I plug in the monitor-on-a-stick, there's no response at all on the console, keys do nothing. we have to power cycle them, and nothing ever shows, not in dmesg.old, not messages, nowhere. Never figured it out. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Incoming rsync connection attempts
2015-10-14 20:13 GMT+02:00 Jeff Boyce : > > There is no /etc/rsyncd.conf file present on the system, so I can see why > the connection wasn't successful. Our backups get pushed to this one from > other servers using rsync. > > > Why do you have rsyncd enabled if you don't have rsyncd.conf ? If your pusing backups using rsync over ssh, you don't need rsynd. -- Laurent. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Incoming rsync connection attempts
On 10/14/2015 01:13 PM, Jeff Boyce wrote: This is on a RHEL 3.9 box (Dell PE2600, year 2004) that is primarily used as backup storage within our LAN. You have a RHEL 3.9 box exposed to the Internet? -- Ian Pilcher arequip...@gmail.com "I grew up before Mark Zuckerberg invented friendship" ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Incoming rsync connection attempts
On 10/14/2015 11:13 AM, Jeff Boyce wrote: This is on a RHEL 3.9 box (Dell PE2600, year 2004) that is primarily used as backup storage within our LAN. I will retire it when it dies, until then it runs fairly maintenance free. I do have a public IP address assigned to the WAN because we have a vsftp server running on it for transferring files back and forth to a few clients, and I occasionally access the server remotely. I am wondering if there is anything relatively simple that I can do to address these attempted connections, until I have time to move our vsftp server from it and remove the public IP address from the WAN? Thanks. block all ports except what you need at your firewall. suggestion, retire FTP, and use something like OwnCloud for customer file transfers, this is a dropbox style web based file service. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
