Re: [CentOS] Centos 7 and backup solution
On 27/01/2019 11:56, Alessandro Baggi wrote: Hey there, what type of backup solution do you use on C7? Thanks in advance ___ I've been using Duplicati along with backblaze B2 + local storage, and using it on both my windows and 2 Centos boxes I was using Crashplan for years until they shut it down for home users, and it's a great replacement cheers Dunc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM not activating on reboot
On 05/10/2017 12:10, Anthony K wrote: It might require a vgexport then vgimport to fix. On 03/10/2017 21:28, Gordon Messmer wrote: Is /etc/mdadm.conf up to date? Run "mdadm --detail --scan" to get the information you need, and either replace the lines in mdadm.conf or add the one that's missing. You might need to rebuild the initrd afterward (dracut --force). I'm unclear on why any of that would be necessary, though. I don't usually add pre-existing arrays to running systems, so I'm a bit out of my experience here. Thanks for the replies both I'd already tried both those ideas before posting, I should have mentioned In the end what fixed it was copying over the lvm.conf from the old system backup, and rebuilding the initrd I didn't think to diff the two before hand so not sure what it was that changed, but sorted now anyway! thanks again Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM not activating on reboot
On 30/09/2017 17:49, Gordon Messmer wrote: On 09/30/2017 08:30 AM, Duncan Brown wrote: However on a reboot, boot fails if I add that entry to fstab: 'Timed out waiting for device dev-mapper-vg03\x2dstorage.device' I then have to activate it again with vgchange. I'm guessing I'm going to need a grub option, or do something with dracut but I'm a bit stuck here You can add the kernel option "rd.lvm.lv=vg03/storage" but that *should* only be necessary if that mount point is needed in the early boot process. What does your fstab entry look like? Thanks for the reply No joy after adding the kernel option, exactly the same issue As for the fstab entry: # cat /etc/fstab UUID=84cb3521-4722-4993-8f8d-07289d6486cb / xfs defaults 0 0 UUID=3f7c32cd-49bb-4fda-8dc1-db88d2912786 /boot xfs defaults 0 0 UUID=a36c7e69-67d6-4ad2-b4c5-01228b168c4b swap swap defaults 0 0 /dev/vg03/storage /mnt/storage xfs defaults,sunit=1024,swidth=2048,inode64 1 2 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] LVM not activating on reboot
Hi I've recently rebuilt my home server using centos 7, and transplanted over the main storage disks It's a 3 disk raid5, with an lvm storage group (vg03) on there Activating and mounting works fine: # vgscan Reading volume groups from cache. Found volume group "vg03" using metadata type lvm2 # vgchange -ay 1 logical volume(s) in volume group "vg03" now active # lvscan ACTIVE '/dev/vg03/storage' [<1.82 TiB] inherit I can then mount /dev/vg03/storage as expected However on a reboot, boot fails if I add that entry to fstab: 'Timed out waiting for device dev-mapper-vg03\x2dstorage.device' I then have to activate it again with vgchange. I'm guessing I'm going to need a grub option, or do something with dracut but I'm a bit stuck here Thanks Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Nvidia related kernel panic on boot, *unless* the keyboard is tapped
On 01/03/2017 16:32, Denniston, Todd A CIV NAVSURFWARCENDIV Crane, JXVS wrote: -Original Message- From: Duncan Brown [mailto:cent...@duncb.co.uk] Sent: Wednesday, March 01, 2017 5:49 AM To: CentOS@centos.org Subject: [CentOS] Nvidia related kernel panic on boot, *unless* the keyboard is tapped So here is an odd one Ever since the upgrade to 7.3, when using the el-repo kmod-nvidia, boot hangs around the 'mounted /boot' point. If left it then kernel panics However at that point, tapping the keyboard gets it going again. As I'm using a wireless keyboard, even the act of switching the keyboard on gets it going again This doesn't happen without the kmod, and I'm in the process of capturing the panic to file the bug report with el-repo, but for the sake of conversation has anyone seen anything like this before, or have any idea why that could happen? cheers Dunc I have not checked to see if elrepo has kicked out all the new drivers to fix it since then, but apparently RH changed some kernel 'pointers' in 7.3 which kind of messes up some of the kmods: https://elrepo.org/bugs/view.php?id=715 https://elrepo.org/bugs/view.php?id=710 I am betting that you installed the kmod-nvidia before the upgrade to 7.3 and thus did not get the kind of warning that those folks did. Perhaps even related to this issue: https://elrepo.org/bugs/view.php?id=693 which kmod-nvidia do you have? At the bottom of 693, pperry indicates: "kmod-nvidia-367.57-2.el7.elrepo.x86_64 is for EL7.3". The most recent, I did obviously get the brief error where the centos kernel release hadn't quite caught up, but that was a while ago. Once booted the driver itself works perfectly, Its just so odd I get the kernel panic unless I tap the keyboard during boot ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Nvidia related kernel panic on boot, *unless* the keyboard is tapped
So here is an odd one Ever since the upgrade to 7.3, when using the el-repo kmod-nvidia, boot hangs around the 'mounted /boot' point. If left it then kernel panics However at that point, tapping the keyboard gets it going again. As I'm using a wireless keyboard, even the act of switching the keyboard on gets it going again This doesn't happen without the kmod, and I'm in the process of capturing the panic to file the bug report with el-repo, but for the sake of conversation has anyone seen anything like this before, or have any idea why that could happen? cheers Dunc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] update clamav to 0.99.2
On 09/07/2016 14:15, Walter H. wrote: On 09.07.2016 14:39, Pete Geenhuizen wrote: I don't see it either. On 07/09/16 08:36, Walter H. wrote: On 07.07.2016 22:19, Helmut Drodofsky wrote: Helo, update is in EPEL repository. strange, here it isn't ... the reason: at the moment clamav 0.99.2 is only EL7, EL6 ist at 0.99.1 https://dl.fedoraproject.org/pub/epel/6/x86_64/ https://dl.fedoraproject.org/pub/epel/7/x86_64/c/ so OP has installed at CentOS 7 it's in testing for el6 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 07/12/2015 18:35, Akemi Yagi wrote: On Mon, Dec 7, 2015 at 10:18 AM, Duncan Brown wrote: On 07/12/2015 14:40, Akemi Yagi wrote: This bug report: https://bugs.centos.org/view.php?id=9860 and its upstream (RH) reference: https://bugzilla.redhat.com/show_bug.cgi?id=1285235 might possibly be related to the kernel panic the original poster reported. There is a workaround that may be worth a try: Boot with the kernel parameter : initcall_blacklist=clocksource_done_booting Akemi Thanks Akemi, that worked perfectly That is indeed good news. Now, this is only a workaround. As seen in the RH bugzilla, the patch is in the z-series kernel and the target is set to "7.3". That will be CentOS 7 (1605) [or later]. At any rate it's several months from now. If we are able to identify the patch, it will be possible to include it in the centosplus kernel. Akemi ___ Thats great, thank you I'll keep an eye on the bug report ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 07/12/2015 14:40, Akemi Yagi wrote: On Mon, Dec 7, 2015 at 4:45 AM, Johnny Hughes wrote: On 12/06/2015 10:11 PM, Greg Lindahl wrote: (bit snip) Oh, wait: CentOS, love it or leave it. Correct. In fact, I would prefer you leave. No, I would prefer ALL of you leave. All of you who are not addressing the OP's issue should leave the thread. Just start a new thread, not here. Enough is enough (/me saying in the same tone as President Obama referring to the gun violence in the US). Now back to the topic... This bug report: https://bugs.centos.org/view.php?id=9860 and its upstream (RH) reference: https://bugzilla.redhat.com/show_bug.cgi?id=1285235 might possibly be related to the kernel panic the original poster reported. There is a workaround that may be worth a try: Boot with the kernel parameter : initcall_blacklist=clocksource_done_booting Akemi Thanks Akemi, that worked perfectly I've managed this twice in a week now, a simple question on the mythtv-users list ended up turning into a huge debate about 4k TV's http://lists.mythtv.org/pipermail/mythtv-users/2015-December/383441.html Still got the problem sorted though so all good I guess! cheers Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 06/12/2015 01:12, Marcelo Ricardo Leitner wrote: Em 05-12-2015 05:35, Duncan Brown escreveu: On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote: Em 03-12-2015 14:46, Duncan Brown escreveu: Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? Of some. It's failing on ftrace initialization while allocating memory, but can't know the real reason. It can be just lack of memory or any other bug. Probably by that stage of the boot, framebuffer is already loaded. Use vga=0x317 boot option to get a bigger resolution and more lines on it, then send another pic. I hope it fits this time. If not, pick 0x31A, if your monitor allows. (kernel src, Documentation/fb/vesafb.txt) | 640x480 800x600 1024x768 1280x1024 +- 256 | 0x3010x3030x3050x307 32k | 0x3100x3130x3160x319 64k | 0x3110x3140x3170x31A 16M | 0x3120x3150x3180x31B Marcelo ___ Hi Marcelo Thanks for the suggestion I've worked through a decent selection and cant get any to show a higher resolution than it's currently at, in fact most just leave me with a blank screen Note I can change the resolution all I want if I boot via the previous kernel Damn :-( Serial cable then? heh Cheers, Marcelo Yeah I've got a nice little usb one I can hook directly into a raspberry pi on the way I'm totally expecting this to get fixed in a kernel update before the thing even arrives, but it'll be a good learning experience and will probably be useful in the future! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 04/12/2015 12:03, Karanbir Singh wrote: On 03/12/15 16:47, Duncan Brown wrote: Did you rebuild initrd after removing the kmod packages? Yes, and no change is it possible to get a bug report at bugs.centos.org with as much detail as possible, so we can try to reproduce ( and atleast document and manage it that way ). thanks I'm seeing if I can get a decent copy of the kernel panic Would the bug report be much use without it? thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote: Em 03-12-2015 14:46, Duncan Brown escreveu: Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? Of some. It's failing on ftrace initialization while allocating memory, but can't know the real reason. It can be just lack of memory or any other bug. Probably by that stage of the boot, framebuffer is already loaded. Use vga=0x317 boot option to get a bigger resolution and more lines on it, then send another pic. I hope it fits this time. If not, pick 0x31A, if your monitor allows. (kernel src, Documentation/fb/vesafb.txt) | 640x480 800x600 1024x768 1280x1024 +- 256 | 0x3010x3030x3050x307 32k | 0x3100x3130x3160x319 64k | 0x3110x3140x3170x31A 16M | 0x3120x3150x3180x31B Marcelo ___ Hi Marcelo Thanks for the suggestion I've worked through a decent selection and cant get any to show a higher resolution than it's currently at, in fact most just leave me with a blank screen Note I can change the resolution all I want if I boot via the previous kernel cheers Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 19:48, m.r...@5-cent.us wrote: Duncan Brown wrote: On 03/12/2015 17:00, m.r...@5-cent.us wrote: Duncan Brown wrote: On 03/12/2015 14:29, Leon Fauster wrote: Am 03.12.2015 um 15:06 schrieb Duncan Brown : On 03/12/2015 13:54, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 01:44:47PM +, Duncan Brown wrote: The last message before it is "switching to clocksource hpet" Then the panic scrolls by I've no idea if that counts as later or not It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. The content of the panic is really the only thing that can help. That's what I figured, but how do I go about getting a copy of it? Most of it has scrolled by when it's finished start for example with a photo (or video and grab the frame where the panic occurs) and - disable grub options like rhgb or quit ... Here is a couple of pictures, ^^ should be are.* http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? I'm just guessing here, but it looks to me as though it's looking at inodes - so filesystem, and kernel modules, maybe video - notice the blacklist. Wonder if this is a grub2 issue, and it's not finding the filesystem. This isn't, by chance, a secure boot, not BIOS, system? No nothing that exciting, BIOS, and xfs on lvm2. Pretty much the standard options anaconda gives you And it boots fine in 3.10.0-229.20.1.el7.x86_64 A thought: did you say you'd rebuilt the ramfs, making sure both xfs and lvm drivers were included? As far as I know yes, I'm just doing a standard dracut rebuild. There's not reason they wouldn't I did also try a yum --reinstall on the kernel with no luck either ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 17:19, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 04:46:10PM +, Duncan Brown wrote: Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? So, both of those are just the end of the kernel call trace, unfortunately, it doesn't show what function actually caused the panic. That'd be above that text, something you could get from an attached console. The first one looks like its in the middle of allocating an inode for a file, the second in looking up some dentry during init (just guessing though), although both seem to be in an allocation event at the end of an interrupt (EOI), but that's probably just coincidence. I had a feeling that would be the case It's installed on an SSD so it goes past instantly I've taken a video and can just about make out "Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu" ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 17:00, m.r...@5-cent.us wrote: Duncan Brown wrote: On 03/12/2015 14:29, Leon Fauster wrote: Am 03.12.2015 um 15:06 schrieb Duncan Brown : On 03/12/2015 13:54, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 01:44:47PM +, Duncan Brown wrote: The last message before it is "switching to clocksource hpet" Then the panic scrolls by I've no idea if that counts as later or not It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. The content of the panic is really the only thing that can help. That's what I figured, but how do I go about getting a copy of it? Most of it has scrolled by when it's finished start for example with a photo (or video and grab the frame where the panic occurs) and - disable grub options like rhgb or quit ... Here is a couple of pictures, ^^ should be are.* http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? I'm just guessing here, but it looks to me as though it's looking at inodes - so filesystem, and kernel modules, maybe video - notice the blacklist. Wonder if this is a grub2 issue, and it's not finding the filesystem. This isn't, by chance, a secure boot, not BIOS, system? mark No nothing that exciting, BIOS, and xfs on lvm2. Pretty much the standard options anaconda gives you And it boots fine in 3.10.0-229.20.1.el7.x86_64 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 16:17, Fred Wittekind wrote:
On 12/3/2015 5:40 AM, Duncan Brown wrote:
On 03/12/2015 10:06, Leon Fauster wrote:
Am 03.12.2015 um 10:53 schrieb Duncan Brown :
On 03/12/2015 09:40, Bernard Lheureux wrote:
On 12/03/2015 10:29 AM, Duncan Brown wrote:
initramfs is missing...
check if /boot/initramfs-{kernelversion}.img is correctly there,
if not do a "yum reinstall kernel-{version}" and it should be ok !
Hi All
After upgrading to 7.2, I'm getting an immediate kernel panic on
boot
Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots
fine
How can I go about diagnosing the problem here?
thanks
Duncan
No joy unfortunately, the correct initramfs is there
I tried reinstalling just in case, but no change
any additional kernel modules installed?
--
LF
Hi Leon
I'm running kmod-nvidia and kmod-forcedeth from elrepo
The nvidia-kmod had an update to work with the new kernel, the
forcedeth did not but as far as I can tell it didn't need one. (also
why on earth the forcedeth module has gone from the stock kernel in 7
I have no idea)
The first thing I tried however was uninstalling both, but I'm still
getting the same panic
Is there any way of logging it so I can see exactly what the panic says?
thanks all
Duncan
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Mine booted successfully after update to 7.2 CR. I am also using a
Nvidia kmod from elrepo, no forcedeth though.
kernel-3.10.0-327.el7.x86_64
kmod-nvidia-340xx-340.96-1.el7.elrepo.x86_64
Did you rebuild initrd after removing the kmod packages?
Yes, and no change
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 14:29, Leon Fauster wrote: Am 03.12.2015 um 15:06 schrieb Duncan Brown : On 03/12/2015 13:54, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 01:44:47PM +, Duncan Brown wrote: The last message before it is "switching to clocksource hpet" Then the panic scrolls by I've no idea if that counts as later or not It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. The content of the panic is really the only thing that can help. That's what I figured, but how do I go about getting a copy of it? Most of it has scrolled by when it's finished start for example with a photo (or video and grab the frame where the panic occurs) and - disable grub options like rhgb or quit ... -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 13:57, Akemi Yagi wrote: On Thu, Dec 3, 2015 at 5:44 AM, Duncan Brown wrote: On 03/12/2015 13:33, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 09:29:21AM +, Duncan Brown wrote: Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? It'd probably help if you could give us more details on the kernel panic. Can you see where it is panicking? Does it happen during the kernel/initrd stage or later during boot? I suggest installing the kdump service if it is panicking later in boot, you might be able to capture a kernel dump which makes debugging these things a lot easier. Otherwise, I suggest trying to capture the panic message some other way. The last message before it is "switching to clocksource hpet" Then the panic scrolls by Maybe an issue with X. Look into /var/log/Xorg.0.log for hints. Or, does it boot fine in single user mode? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos The same thing happens in single user mode too ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 13:54, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 01:44:47PM +, Duncan Brown wrote: The last message before it is "switching to clocksource hpet" Then the panic scrolls by I've no idea if that counts as later or not It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. The content of the panic is really the only thing that can help. That's what I figured, but how do I go about getting a copy of it? Most of it has scrolled by when it's finished ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 13:33, Jonathan Billings wrote: On Thu, Dec 03, 2015 at 09:29:21AM +, Duncan Brown wrote: Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? It'd probably help if you could give us more details on the kernel panic. Can you see where it is panicking? Does it happen during the kernel/initrd stage or later during boot? I suggest installing the kdump service if it is panicking later in boot, you might be able to capture a kernel dump which makes debugging these things a lot easier. Otherwise, I suggest trying to capture the panic message some other way. The last message before it is "switching to clocksource hpet" Then the panic scrolls by I've no idea if that counts as later or not ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 11:28, Leon Fauster wrote: Am 03.12.2015 um 11:40 schrieb Duncan Brown : On 03/12/2015 10:06, Leon Fauster wrote: Am 03.12.2015 um 10:53 schrieb Duncan Brown : On 03/12/2015 09:40, Bernard Lheureux wrote: No joy unfortunately, the correct initramfs is there I tried reinstalling just in case, but no change any additional kernel modules installed? I'm running kmod-nvidia and kmod-forcedeth from elrepo The nvidia-kmod had an update to work with the new kernel, the forcedeth did not but as far as I can tell it didn't need one. (also why on earth the forcedeth module has gone from the stock kernel in 7 I have no idea) The first thing I tried however was uninstalling both, but I'm still getting the same panic Is there any way of logging it so I can see exactly what the panic says? was the "init-ram-disk" regenerated (yum reinstall kernel-x.y.z) -- LF It was, and just to check I've regenerated using dracut too with no change ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 11:24, Karanbir Singh wrote:
On 03/12/15 09:40, Bernard Lheureux wrote:
On 12/03/2015 10:29 AM, Duncan Brown wrote:
initramfs is missing...
check if /boot/initramfs-{kernelversion}.img is correctly there, if not
do a "yum reinstall kernel-{version}" and it should be ok !
You might want to also check there is enough diskspace for the initrd to
be built and hosted in the right place..
The boot partition is half empty, and as far as I can tell it is there OK:
[root@gobbla boot]# ls -lah
total 252M
dr-xr-xr-x. 4 root root 4.0K Dec 3 11:43 .
drwxr-xr-x. 18 root root 4.0K Dec 3 11:23 ..
-rw-r--r-- 1 root root 121K Sep 15 16:14 config-3.10.0-229.14.1.el7.x86_64
-rw-r--r-- 1 root root 121K Nov 3 19:18 config-3.10.0-229.20.1.el7.x86_64
-rw-r--r-- 1 root root 124K Nov 19 22:20 config-3.10.0-327.el7.x86_64
drwxr-xr-x. 2 root root 26 Oct 9 07:20 grub
drwx--. 6 root root 104 Dec 3 11:20 grub2
-rw-r--r--. 1 root root 39M May 21 2015
initramfs-0-rescue-00095717eba54050b81e403ded5ee369.img
-rw--- 1 root root 45M Dec 3 11:43
initramfs-3.10.0-229.14.1.el7.x86_64.img
-rw--- 1 root root 24M Sep 18 06:33
initramfs-3.10.0-229.14.1.el7.x86_64kdump.img
-rw--- 1 root root 35M Dec 3 11:19
initramfs-3.10.0-229.20.1.el7.x86_64.img
-rw--- 1 root root 17M Dec 2 13:38
initramfs-3.10.0-229.20.1.el7.x86_64kdump.img
-rw--- 1 root root 8.8M Dec 3 11:43
initramfs-3.10.0-229.20.1.el7.x86_64.tmp
-rw--- 1 root root 29M Dec 3 11:17
initramfs-3.10.0-327.el7.x86_64.img
-rw-r--r--. 1 root root 20M Dec 2 13:40 initrd-plymouth.img
-rw-r--r-- 1 root root 235K Sep 15 16:16
symvers-3.10.0-229.14.1.el7.x86_64.gz
-rw-r--r-- 1 root root 235K Nov 3 19:21
symvers-3.10.0-229.20.1.el7.x86_64.gz
-rw-r--r-- 1 root root 247K Nov 19 22:22 symvers-3.10.0-327.el7.x86_64.gz
-rw--- 1 root root 2.8M Sep 15 16:14
System.map-3.10.0-229.14.1.el7.x86_64
-rw--- 1 root root 2.8M Nov 3 19:18
System.map-3.10.0-229.20.1.el7.x86_64
-rw--- 1 root root 2.9M Nov 19 22:20 System.map-3.10.0-327.el7.x86_64
-rwxr-xr-x. 1 root root 4.7M May 21 2015
vmlinuz-0-rescue-00095717eba54050b81e403ded5ee369
-rwxr-xr-x 1 root root 4.8M Sep 15 16:14
vmlinuz-3.10.0-229.14.1.el7.x86_64
-rw-r--r-- 1 root root 171 Sep 15 16:14
.vmlinuz-3.10.0-229.14.1.el7.x86_64.hmac
-rwxr-xr-x 1 root root 4.8M Nov 3 19:18
vmlinuz-3.10.0-229.20.1.el7.x86_64
-rw-r--r-- 1 root root 171 Nov 3 19:18
.vmlinuz-3.10.0-229.20.1.el7.x86_64.hmac
-rwxr-xr-x 1 root root 5.0M Nov 19 22:20 vmlinuz-3.10.0-327.el7.x86_64
-rw-r--r-- 1 root root 166 Nov 19 22:20
.vmlinuz-3.10.0-327.el7.x86_64.hmac
thanks for the reply
Duncan
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 10:06, Leon Fauster wrote:
Am 03.12.2015 um 10:53 schrieb Duncan Brown :
On 03/12/2015 09:40, Bernard Lheureux wrote:
On 12/03/2015 10:29 AM, Duncan Brown wrote:
initramfs is missing...
check if /boot/initramfs-{kernelversion}.img is correctly there, if not do a "yum
reinstall kernel-{version}" and it should be ok !
Hi All
After upgrading to 7.2, I'm getting an immediate kernel panic on boot
Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine
How can I go about diagnosing the problem here?
thanks
Duncan
No joy unfortunately, the correct initramfs is there
I tried reinstalling just in case, but no change
any additional kernel modules installed?
--
LF
Hi Leon
I'm running kmod-nvidia and kmod-forcedeth from elrepo
The nvidia-kmod had an update to work with the new kernel, the forcedeth
did not but as far as I can tell it didn't need one. (also why on earth
the forcedeth module has gone from the stock kernel in 7 I have no idea)
The first thing I tried however was uninstalling both, but I'm still
getting the same panic
Is there any way of logging it so I can see exactly what the panic says?
thanks all
Duncan
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/2015 09:40, Bernard Lheureux wrote:
On 12/03/2015 10:29 AM, Duncan Brown wrote:
initramfs is missing...
check if /boot/initramfs-{kernelversion}.img is correctly there, if
not do a "yum reinstall kernel-{version}" and it should be ok !
Hi All
After upgrading to 7.2, I'm getting an immediate kernel panic on boot
Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine
How can I go about diagnosing the problem here?
thanks
Duncan
No joy unfortunately, the correct initramfs is there
I tried reinstalling just in case, but no change
thanks for the reply
Duncan
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] 7.2 kernel panic on boot
Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? thanks Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] atrpms.net repo
On 20/06/2015 15:13, Leon Fauster wrote: Does anyone known whats going on with atrpms.net ? I see an unreachability since some days ... -- LF Not sure what the problem is this time, and I hope its just temporary, but its been on its way out for a long time. I've taken this opportunity to move stuff to the nux repository. I've found everything I was getting from atrpms on there so far. A shame, as it used to be such a great repo, and Axel was always so quick to help or ask questions. I guess with all the problems in Greece at the moment, it's fairly low on his list of priorities. cheers Dunc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] One nice thing about upstream 7
On 23/07/2014 20:05, m.r...@5-cent.us wrote: > Lamar Owen wrote: >> On 07/22/2014 04:54 PM, m.r...@5-cent.us wrote: >>> My manager took the "binary DVD" and dd'd it onto a flash drive... and >>> it booted. No problems at all. >> This works for CentOS 7, too. > Haven't needed to try it, but I was assuming it did. > >mark > > It worked for 6.5 too.. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Expunge Old Email
On 27/09/2011 13:31, John Hinton wrote:
> For those of you running mailservers on CentOS 6, what are the
> suggestions for programs to expunge old email? For instance, deleting
> email from a Spam folder that is 2 weeks old or older.
>
> I see that Dovecot does have a solution, but was wondering about what
> others have landed on.
>
> My systems are basically Postfix, Dovecot using Maildir.
>
> Thanks,
> John Hinton
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
I just use a daily cron job with regex, never had much luck with
dovecots method:
# delete 30 day old mails from Trash
find /var/mail/ -regex '.*/\.\(Trash\|Junk\)\(/.*\)?\/\(cur\|new\)/.*'
-type f -ctime +30 -exec rm '{}' \;
# delete 200 day old mails from mailinglists
find /var/mail/ -regex
'.*/\.\(Fedora\|Atrpms\|Centos\|Mythtv\)\(/.*\)?\/\(cur\|new\)/.*' -type
f -ctime +200 -exec rm '{}' \;
cheers
Dunc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
