On Tue, Dec 3, 2019 at 10:57 AM Heath Nye
wrote:
> please remove from from this list
>
at the bottom of every message is this link...
https://lists.centos.org/mailman/listinfo/centos
there's unsubscribe instructions on there.
___
CentOS mailing list
please remove from from this list
On Tue, Dec 3, 2019 at 4:49 AM Gokan Atmaca wrote:
> Hello
>
> I'm using centos 7. At uncertain times I suddenly get the following
> error. The system is panic. Then it restarts automatically. I have
> updated the package ( pkla-check-auth ) but the problem
Hello
I'm using centos 7. At uncertain times I suddenly get the following
error. The system is panic. Then it restarts automatically. I have
updated the package ( pkla-check-auth ) but the problem persists. My
virtualization environment is KVM. (Host Centos7 , Guest Centos7.
Problem Guest VM)
On 4/11/19 2:21 PM, Jyrki Tikka wrote:
On Wed, 10 Apr 2019 08:38:04 -0700, Benjamin Smith
wrote
I drove to the site, picked up the machine, and last night found that the
problem wasn't anything to do with mdadm, but rather setting a partition to
GPT.
If you want to boot a BIOS based machine
On Wed, 10 Apr 2019 08:38:04 -0700, Benjamin Smith
wrote
>I drove to the site, picked up the machine, and last night found that the
>problem wasn't anything to do with mdadm, but rather setting a partition to
>GPT. For some reason, you *cannot* have a partition of type GPT and expect
>Linux
On Apr 10, 2019, at 9:38 AM, Benjamin Smith wrote:
>
> For some reason, you *cannot* have a partition of type GPT and expect
> Linux to boot. (WT F/H?!?)
I believe you were trying to make use of a facility invented as part of the GPT
Protective Partition feature without understanding it
On Tuesday, April 9, 2019 2:53:55 AM PDT Simon Matter via CentOS wrote:
> > I think it's because you clobbered md0 when you did --zero-superblock on
> > sd[ab]1
> > instead of 2.
As mentioned in another reply, this was a typo in the email, not on the
machine.
I drove to the site, picked up the
> In article <6566355.ijnrhnp...@tesla.schoolpathways.com>,
> Benjamin Smith wrote:
>> System is CentOS 6 all up to date, previously had two drives in MD RAID
>> configuration.
>>
>> md0: sda1/sdb1, 20 GB, OS / Partition
>> md1: sda2/sdb2, 1 TB, data mounted as /home
>>
>> Installed kmod ZFS via
In article <6566355.ijnrhnp...@tesla.schoolpathways.com>,
Benjamin Smith wrote:
> System is CentOS 6 all up to date, previously had two drives in MD RAID
> configuration.
>
> md0: sda1/sdb1, 20 GB, OS / Partition
> md1: sda2/sdb2, 1 TB, data mounted as /home
>
> Installed kmod ZFS via yum,
System is CentOS 6 all up to date, previously had two drives in MD RAID
configuration.
md0: sda1/sdb1, 20 GB, OS / Partition
md1: sda2/sdb2, 1 TB, data mounted as /home
Installed kmod ZFS via yum, reboot, zpool works fine. Backed up the /home data
2x, then stopped the sd[ab]2 partition with:
Ken Smith wrote:
> John R Pierce wrote:
>> On 12/7/2016 12:09 PM, Ken Smith wrote:
>>> Gigabyte Technology Co., Ltd P43-ES3G
>>
>> thtas a rather old motherboard, like circa 2008?my longtime
>> experiences with consumer desktop grade hardware suggest that at 5
>> years, 50% of them go flaky.
John R Pierce wrote:
On 12/7/2016 12:09 PM, Ken Smith wrote:
Gigabyte Technology Co., Ltd P43-ES3G
thtas a rather old motherboard, like circa 2008?my longtime
experiences with consumer desktop grade hardware suggest that at 5
years, 50% of them go flaky. that one is about 8 years old
On 12/7/2016 12:09 PM, Ken Smith wrote:
Gigabyte Technology Co., Ltd P43-ES3G
thtas a rather old motherboard, like circa 2008?my longtime
experiences with consumer desktop grade hardware suggest that at 5
years, 50% of them go flaky. that one is about 8 years old now.
--
john r
Hi All,
This is a Centos 6.4 system used as a home server and Myth backend
machine. It has just suffered a motherboard failure and I have got a
identical replacement.
This machine normally runs in run level 3. It has a NVidia graphics card
and the NVidia driver installed but I found it
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Jonathan Billings
> Sent: den 28 maj 2016 03:02
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-
On May 27, 2016, at 1:42 AM, Sorin Srbu wrote:
> The one I posted a screen dump of earlier.
I don’t see any posts of a screen dump. The mailing list software (mailman) is
set to strip any non-text attachments, so if it was an image, it was probably
stripped.
(The
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of John Hodrien
> Sent: den 26 maj 2016 16:10
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of m.r...@5-cent.us
> Sent: den 26 maj 2016 16:08
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-
On Thu, 26 May 2016, Sorin Srbu wrote:
Uninstalled NFS, as it wasn't needed anyway.
Still got the panic.
Seriously, what panic?
jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Sorin Srbu wrote:
>> Behalf Of Johnny Hughes
>> Sent: den 26 maj 2016 14:30
>>
>> If lockd is failling to start:
>>
>> https://bugs.centos.org/view.php?id=10927
>
> Uninstalled NFS, as it wasn't needed anyway.
>
> Still got the panic.
>
I haven't been following this thread closely, but if it's 7,
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Johnny Hughes
> Sent: den 26 maj 2016 14:30
> To: centos@centos.org
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
> 642.el6.x86_64
>
;
>> Behalf Of Subscriber
>
>> Sent: den 26 maj 2016 13:32
>
>> To: CentOS mailing list <centos@centos.org>
>
>> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
>
>> 642.el6.x86_64
>
>>
>
>> Im
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Subscriber
> Sent: den 26 maj 2016 13:32
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
Hello Sorin,
Thursday, May 26, 2016, 1:58:29 PM, you wrote:
> Hi,
> Of the four machines tested, two failed with a kernel panic.
> At the time, I just rebooted to a previous kernel, as a quick fix.
> I found some of the issues you list already.
> I've run the CR-updates on a few
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Johnny Hughes
> Sent: den 26 maj 2016 12:39
> To: centos@centos.org
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
> 642.el6.x86_64
>
&
On 05/26/2016 03:58 AM, Sorin Srbu wrote:
> Content-Type: text/plain;
>
> charset="us-ascii"
>
> Content-Transfer-Encoding: 7bit
>
>
> Hi all,
>
>
> Just tested the new CentOS 6.8 release on a few VMs and a physical box and
>
> got a kernel panic.
>
>
> Is it just me, or anybody
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of John Hodrien
> Sent: den 26 maj 2016 11:14
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-
On Thu, 26 May 2016, Sorin Srbu wrote:
Hi all,
Just tested the new CentOS 6.8 release on a few VMs and a physical box and
got a kernel panic.
Is it just me, or anybody else as well?
Just fishing for now, will look into the issue more thoroughly later today.
Include the actual kernel panic
Hi all,
Just tested the new CentOS 6.8 release on a few VMs and a physical box and
got a kernel panic.
Is it just me, or anybody else as well?
Just fishing for now, will look into the issue more thoroughly later today.
--
BW,
Sorin
Greetings Max,
> I had previously reported this, and I was told that the reported bug was
> here:
> https://bugs.centos.org/view.php?id=9374
>
> Looking at it now, I see that it is closed.
Wrong. That reports refers to an earlier bug, which appears to be
identical:-
Greetings,
I just tried upgrading one of my CentOS boxes to this kernel.
It crashes; the screen looks like this:
http://www.brama.com/~deckard/P1010308.JPG
So, I'm continuing to run on
kernel-2.6.32-504.23.4.el6.x86_64
I had previously reported this, and I was told that the reported bug was
On Feb 3, 2016, at 5:28 PM, Peter Q. wrote:
>
> probably open bug
I don’t know how you get “probably” out of these two screenshots. Both
machines seem to be crashing in about the same place in the boot, and both seem
to have Intel graphics, but the resulting crashes are
On Feb 3, 2016, at 12:24 PM, Max Pyziur wrote:
>
> When I tried rebooting the machine, none of the kernels would work except for
> the oldest one.
Define “would not work”. Post a photo of the error message somewhere if you
can’t describe it better than that. You might have
On Wed, 3 Feb 2016, Warren Young wrote:
On Feb 3, 2016, at 12:24 PM, Max Pyziur wrote:
When I tried rebooting the machine, none of the kernels would work except for
the oldest one.
Define “would not work”. Post a photo of the error message somewhere if you
can’t describe
probably open bug
https://bugs.centos.org/view.php?id=9374
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Greetings,
Today, I decided to reboot one of my CentOS machines after it had been
running for 219 days.
In this time, I had done yum updates several times. When I tried rebooting
the machine, none of the kernels would work except for the oldest one.
Here are the installed kernels:
...@pari.edu
To: centos@centos.org
Sent: Thursday, 2 April, 2015 06:04:01
Subject: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing
gkrellm.
Just a heads up, since I know gkrellm is in EPEL and not in the main
CentOS repos. However, something fairly fundamental has changed
On 04/02/2015 10:33 AM, Lamar Owen wrote:
That's why I still hope it's local to my machine. But now to try to
reproduce on other hardware. (for reference, hardware on which I saw
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI
Firepro 7820M video, with / on a Samsung
On 02-04-2015 17:05, Lamar Owen wrote:
On 04/02/2015 10:33 AM, Lamar Owen wrote:
That's why I still hope it's local to my machine. But now to try to
reproduce on other hardware. (for reference, hardware on which I saw
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI
On 04/02/2015 07:52 PM, Karanbir Singh wrote:
On 03/04/15 00:18, Lamar Owen wrote:
Ok, I have the vmcore, but the debuginfo for kernel
3.10.0-229.1.2.el7.x86_64 I can't find. Found and installed for
kernel 3.10.0-123.13.2.el7.x86_64 but that doesn't help me
troubleshoot the -229.1.2
On 04/02/2015 04:05 PM, Lamar Owen wrote:
On 04/02/2015 10:33 AM, Lamar Owen wrote:
That's why I still hope it's local to my machine. But now to try to
reproduce on other hardware. (for reference, hardware on which I saw
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI
On 03/04/15 00:18, Lamar Owen wrote:
On 04/02/2015 04:35 PM, Marcelo Ricardo Leitner wrote:
If you can share the original backtraces, it already helps and someone
may even point you to a fix if it's a known issue.
Ok, I have the vmcore, but the debuginfo for kernel
On 04/02/2015 04:35 PM, Marcelo Ricardo Leitner wrote:
If you can share the original backtraces, it already helps and someone
may even point you to a fix if it's a known issue.
Ok, I have the vmcore, but the debuginfo for kernel
3.10.0-229.1.2.el7.x86_64 I can't find. Found and
On 02-04-2015 02:04, Lamar Owen wrote:
Just a heads up, since I know gkrellm is in EPEL and not in the main
CentOS repos. However, something fairly fundamental has changed, as
prior to updating, gkrellm worked fine, but now every time I execute
gkrellm the kernel panics.
I'm going to triage on
On 04/02/2015 07:29 AM, Marcelo Ricardo Leitner wrote:
If it's that easy to reproduce, please grab the panic message or
generate a vmcore through crashdump and report it at
bugzilla.redhat.com against kernel component.
Thanks for the pointer with some details. I see that I have a bit to
I arrived at work this morning to find that my desktop unit
(CentOS-6.6 KVM) halted with a kernel panic. I am not conversant with
any way to save the console display in this case and there was rather
a lot of text. I jotted down a few notes and power-cycled the unit to
restart. which it did and
Just a heads up, since I know gkrellm is in EPEL and not in the main
CentOS repos. However, something fairly fundamental has changed, as
prior to updating, gkrellm worked fine, but now every time I execute
gkrellm the kernel panics.
I'm going to triage on a different machine, as the panic
On Wed, March 18, 2015 10:59, m.r...@5-cent.us wrote:
Hi, James,
James B. Byrne wrote:
Kernel panic - not syncing: Attempted to kill init!
snip
Now, admittedly, a) I really haven't been following this thread, and
b) haven't worked a lot with VMs, and not with KVM, but could you
clarify
I have a cloned kvm (that I can now get started following a shutdown
and reboot of the hypervisor host). When it starts with its original
virtio disk there is no problem. If I create a virtio disk and add it
via virt-manager it also boots without issue, although one cannot see
the new 'physical'
Hi, James,
James B. Byrne wrote:
I have a cloned kvm (that I can now get started following a shutdown
and reboot of the hypervisor host). When it starts with its original
virtio disk there is no problem. If I create a virtio disk and add it
via virt-manager it also boots without issue,
Sorry if you see this twice, I may have goofed:
Hey,
So I was playing around with trying to get a CentOS 6.5 system
FIPS-140 complaint. However, my system panics because it cannot find
the hmac file associated with my kernel. It's basically as what is
going on is described in this bug report:
I don't have expertise on this issue, but it would be interesting if that
bit of shell script there were adjusted to also print out the fstab and
possibly other diagnostic information relevant to the problem. That way,
you might get a clue as to where /boot is coming from. Then again, I'm not
even
I don't have expertise on this issue, but it would be interesting if that
bit of shell script there were adjusted to also print out the fstab and
possibly other diagnostic information relevant to the problem. That way,
you might get a clue as to where /boot is coming from. Then again, I'm not
even
On Apr 20, 2014, at 8:01 PM, Dale Harris rod...@gmail.com wrote:
But that file does exist on the system. I guess the initramfs may not
see the /boot directory on the system? Or is it trying to look for
/boot inside the initramfs? If so that would explain my problem. I
haven't verified
So as usual, I was skipping a step. I did need to include the boot=
kernel parameter since /boot was separate from root. It wasn't
getting mounted. Everything seems to be working now.
On Sun, Apr 20, 2014 at 11:59 PM, Evan Rowley rowley.e...@gmail.com wrote:
I don't have expertise on this
There is apparently a kernel bug that creates a kernel panic when
starting a windows guest in vmware workstation. I have experienced this
bug on two machines, both with workstation 8.0.6 but it has been
reported with other versions as well:
https://communities.vmware.com/message/2318686 .
Hello all:
I just updated yesterday and rebooted when I received this error:
compat: exports duplicate symbol pcmcia_loop_typle (owned by kernel)
FATAL: Error inserting dm_mod
(/lib/modules/2.6.32.-358.2.1.el6.centos.plus.x86_64/kernel/drivers/md/dm-mod.ko):
Invalid module format
compat: exports
On Sun, Mar 17, 2013 at 7:35 AM, Kwan Lowe kwan.l...@gmail.com wrote:
Hello all:
I just updated yesterday and rebooted when I received this error:
compat: exports duplicate symbol pcmcia_loop_typle (owned by kernel)
FATAL: Error inserting dm_mod
On Sun, Mar 17, 2013 at 10:45 AM, Akemi Yagi amy...@gmail.com wrote:
Reported in the bug tracker:
http://bugs.centos.org/view.php?id=6304
Thanks for the quick reply and will follow that discussion.
I'm still getting my head around netconsole... been a while :)
Cc:
Subject: Re: [CentOS] Kernel panic after update to 6.4
On 03/12/2013 01:48 PM, Akemi Yagi wrote:
On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley
emm...@webengineer.com wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I
decided to update the host as well. And it failed
On 2013-03-13, Johnny Hughes joh...@centos.org wrote:
(...)
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted:
On 2013-03-13, Johnny Hughes joh...@centos.org wrote:
(...)
On 03/13/2013 05:17 PM, Johnny Hughes wrote:
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 05:52 PM, Nux! wrote:
On 12.03.2013 20:41, Emmett Culley wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided
to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to
On 03/14/2013 05:17 AM, Liam O'Toole wrote:
On 2013-03-13, Johnny Hughes joh...@centos.org wrote:
(...)
On 03/13/2013 05:17 PM, Johnny Hughes wrote:
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
On 03/12/2013 05:08 PM, Emmett Culley wrote:
On 03/12/2013 04:23 PM, lists-centos wrote:
Original Message
Date: Tuesday, March 12, 2013 04:05:28 PM -0700
From: Emmett Culley emm...@webengineer.com
To: centos@centos.org
Cc:
Subject: Re: [CentOS] Kernel panic after
On 2013-03-14, Johnny Hughes joh...@centos.org wrote:
(...)
Maybe ... try this (everything done as root):
Boot on a kernel that works and do this:
1. Backup you current initrd:
cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img
/boot/initramfs-2.6.32-358.2.1.el6.x86_64.img.bak
OK.
On 03/14/2013 10:33 AM, Liam O'Toole wrote:
On 2013-03-14, Johnny Hughes joh...@centos.org wrote:
(...)
Maybe ... try this (everything done as root):
Boot on a kernel that works and do this:
1. Backup you current initrd:
cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
After yum upgrade --enablerepo=epel on two of five machines, one of which is
the host
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
After yum upgrade --enablerepo=epel on two
On 12.03.2013 20:41, Emmett Culley wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I
decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1
Plus a call
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
After yum upgrade --enablerepo=epel on two
On 03/13/2013 05:17 PM, Johnny Hughes wrote:
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley emm...@webengineer.com wrote:
(...)
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to
update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1
Plus a call trace I couldn't see
Luckily I was able to
On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley emm...@webengineer.com wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to
update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted:
On 03/12/2013 01:48 PM, Akemi Yagi wrote:
On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley emm...@webengineer.com wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to
update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill
On 03/12/2013 04:23 PM, lists-centos wrote:
Original Message
Date: Tuesday, March 12, 2013 04:05:28 PM -0700
From: Emmett Culley emm...@webengineer.com
To: centos@centos.org
Cc:
Subject: Re: [CentOS] Kernel panic after update to 6.4
On 03/12/2013 01:48 PM
Just installed CentOS 6.3 from a minimal install disc. All was well, so
I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don't remember off the
top of my head). Went to reboot the machine and now it won't book up. As
it starts to
On 20.08.2012 18:17, Joseph Koenig wrote:
Just installed CentOS 6.3 from a minimal install disc. All was well,
so
I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don't remember off
the
top of my head). Went to reboot the
Joseph Koenig wrote:
Just installed CentOS 6.3 from a minimal install disc. All was well, so
I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don't remember off the
top of my head). Went to reboot the machine and now it won't
Just installed CentOS 6.3 from a minimal install disc. All was well, so
I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don't remember off the
top of my head). Went to reboot the machine and now it won't book up. As
it starts
Joseph Koenig wrote:
Just installed CentOS 6.3 from a minimal install disc. All was well, so
I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don't remember off the
top of my head). Went to reboot the machine and now it won't
Yes, grub was installed, and it would seem PERC controller is presenting
drives to the system - at least it was. Before I ran a yum update after
installing the system, I could boot it and log in just fine.
Worth reinstalling from the minimal install disc again just to make sure
that still
Joseph Koenig wrote:
Yes, grub was installed, and it would seem PERC controller is
presenting
drives to the system - at least it was. Before I ran a yum update after
installing the system, I could boot it and log in just fine.
Worth reinstalling from the minimal install disc again just to
Odd thought: have you tried a) looking at the drives in the PERC firmware,
or b) booting to linux rescue, and examining the filesystems?
Well, sure enough, it can't seem to find any good superblocks. Even
backups are showing corrupt. Will reinstall and see what happens...
Thanks!
Joseph Koenig wrote:
Odd thought: have you tried a) looking at the drives in the PERC
firmware, or b) booting to linux rescue, and examining the filesystems?
Well, sure enough, it can't seem to find any good superblocks. Even
backups are showing corrupt. Will reinstall and see what
Well, sure enough, it can't seem to find any good superblocks. Even
backups are showing corrupt. Will reinstall and see what happens...
You mean the backup superblocks are bad? And it was a running system before?
Is it still under warranty? You might consider talking to Dell about
checking
I have the same behavior 6.2 vs latest on my Toshiba satellite.
32-220 boots fine (except for the touchpad and power detection)
32-279.2.1 crashes immediately
Glad to forward logs
On Mon, 20 Aug 2012, m.r...@5-cent.us wrote:
Joseph Koenig wrote:
Yes, grub was installed, and it would seem
I am hopelessly trying to debug a new install of 6.2 x86_64. I used the minimal
install with default options. Unfortunately the screen garbles during the kernel
panic. Scroll/Num lock lights are blinking.
1. Where can I find debugging steps? (tried rescue and mount to read /var/log,
but no values
-Original Message-
From: Jason Pyeron
Sent: Thursday, January 05, 2012 19:44
Subject: [CentOS] Kernel panic after install in cento6 before
mounting rootfile system rw
I am hopelessly trying to debug a new install of 6.2 x86_64.
I used the minimal install with default options
-Original Message-
From: centos-boun...@centos.org
[mailto:centos-boun...@centos.org] On Behalf Of Edward Martinez
Sent: Wednesday, December 21, 2011 10:14 PM
To: centos@centos.org
Subject: Re: [CentOS] Kernel Panic
On 12/21/11 17:54, TE Dukes wrote:
-Original
At 2011-12-23 Fri 20:09 -0500,fred smith wrote:
On Sat, Dec 24, 2011 at 01:37:03AM +0100, Ljubomir Ljubojevic wrote:
Vreme: 12/24/2011 01:00 AM, fred smith piše:
On Fri, Dec 23, 2011 at 05:44:11PM -0500, Ross Walker wrote:
Is that sound on-board? If it is disable it in BIOS, if it
On Fri, Dec 23, 2011 at 05:33:07PM -0700, Corey Henderson wrote:
On 12/23/2011 5:00 PM, fred smith wrote:
On Fri, Dec 23, 2011 at 05:44:11PM -0500, Ross Walker wrote:
On Dec 23, 2011, at 2:47 PM, fred smithfre...@fcshome.stoneham.ma.us
wrote:
On Fri, Dec 23, 2011 at 01:02:12PM -0500,
Add the modules to:
/etc/modprobe.d/blacklist.conf
And re-install the kernel. The dracut util that builds the initramfs
includes this file at install time.
at last, I've had the opportunity to pursue this. all I have to do is
blacklist the snd_hda_codec_realtek module, reboot and voila,
Am 23.12.2011 07:41, schrieb Rainer Traut:
It will be in 6.2/updates/
Still building right now.
Are you sure this will help?
It looks to me he's already using RHEL6.2 with latest kernel 220.
Sorry forget my post, he's running 2.6.32-220.el6.x86_64 and the new one
is 2.6.32-220.2.1.el6
On Thu, Dec 22, 2011 at 05:53:13PM -0600, Johnny Hughes wrote:
On 12/22/2011 05:44 PM, fred smith wrote:
On Thu, Dec 22, 2011 at 04:56:42PM -0600, Johnny Hughes wrote:
snip
There is a new kernel building right now that might
fix something ... though I do not see anything specifically
On Fri, Dec 23, 2011 at 01:02:12PM -0500, fred smith wrote:
On Thu, Dec 22, 2011 at 05:53:13PM -0600, Johnny Hughes wrote:
On 12/22/2011 05:44 PM, fred smith wrote:
On Thu, Dec 22, 2011 at 04:56:42PM -0600, Johnny Hughes wrote:
snip
There is a new kernel building right now that might
On Dec 23, 2011, at 2:47 PM, fred smith fre...@fcshome.stoneham.ma.us wrote:
On Fri, Dec 23, 2011 at 01:02:12PM -0500, fred smith wrote:
On Thu, Dec 22, 2011 at 05:53:13PM -0600, Johnny Hughes wrote:
On 12/22/2011 05:44 PM, fred smith wrote:
On Thu, Dec 22, 2011 at 04:56:42PM -0600, Johnny
On Fri, Dec 23, 2011 at 05:44:11PM -0500, Ross Walker wrote:
On Dec 23, 2011, at 2:47 PM, fred smith fre...@fcshome.stoneham.ma.us wrote:
On Fri, Dec 23, 2011 at 01:02:12PM -0500, fred smith wrote:
On Thu, Dec 22, 2011 at 05:53:13PM -0600, Johnny Hughes wrote:
On 12/22/2011 05:44 PM, fred
On 12/23/2011 5:00 PM, fred smith wrote:
On Fri, Dec 23, 2011 at 05:44:11PM -0500, Ross Walker wrote:
On Dec 23, 2011, at 2:47 PM, fred smithfre...@fcshome.stoneham.ma.us
wrote:
On Fri, Dec 23, 2011 at 01:02:12PM -0500, fred smith wrote:
On Thu, Dec 22, 2011 at 05:53:13PM -0600, Johnny
Vreme: 12/24/2011 01:00 AM, fred smith piše:
On Fri, Dec 23, 2011 at 05:44:11PM -0500, Ross Walker wrote:
Is that sound on-board? If it is disable it in BIOS, if it isn't, remove the
card.
See if it breaks after that.
the Bios has only a very few options, and disabling sound isn't
one of
1 - 100 of 219 matches
Mail list logo