Les Mikesell wrote:
> On Mon, Mar 11, 2013 at 1:22 PM, wrote:
>>
>> Finally, if you can see it running via linux rescue, I'd go with Les'
>> thought: boot that way, chroot to /mnt/sysimage, and first do a
>> grub-install. If that doesn't solve it, then try the rebuild of initrd.
>>
>
> Is there a
On Mon, Mar 11, 2013 at 1:22 PM, wrote:
>
> Finally, if you can see it running via linux rescue, I'd go with Les'
> thought: boot that way, chroot to /mnt/sysimage, and first do a
> grub-install. If that doesn't solve it, then try the rebuild of initrd.
>
Is there a simple way to tell yum to re-
Les Mikesell wrote:
> On Sun, Mar 10, 2013 at 10:45 PM, Frank Cox
> wrote:
>>
>> The most maddening part of this is that all of the files and the
>> filesystems appear to be present -- I can boot off of a rescue CD and
mount the
>> whole works under /mnt/sysimage and browse to my hearts content.
On Sun, Mar 10, 2013 at 10:45 PM, Frank Cox wrote:
>
> The most maddening part of this is that all of the files and the filesystems
> appear to be present -- I can boot off of a rescue CD and mount the whole
> works
> under /mnt/sysimage and browse to my hearts content. I just can't boot the
> d
On Sun, 10 Mar 2013 23:27:25 -0400
Gerry Reno wrote:
> Do you know if this grub file was rewritten?
>
> Can you check it against a backup copy?
I don't have a backup copy of the grub.conf file since it's always been
automatically managed and updated by grub and friends and I've never really had
On Sunday 10 March 2013, Frank Cox wrote:
> Interesting. How can I check that? I have another almost-identical
> system that's still working and I compared grub.conf between the two
> of them and didn't notice any significant differences. Nothing that
> immediately jumped up and down and screa
On 03/10/2013 11:23 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 23:16:10 -0400
> Gerry Reno wrote:
>
>> Boot to rescue mode and see if you can mount the device containing the root
>> filesystem readonly and see all the files on it.
>>
>> Then check that the kernel root option is looking at the same
On Sun, 10 Mar 2013 23:16:10 -0400
Gerry Reno wrote:
> Boot to rescue mode and see if you can mount the device containing the root
> filesystem readonly and see all the files on it.
>
> Then check that the kernel root option is looking at the same device.
I can indeed see all of the files on tha
On 03/10/2013 11:09 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 20:24:55 -0400
> Gerry Reno wrote:
>
>> It seems like maybe it cannot find the root filesystem.
>>
>> Kernel panics just like this when it cannot find it.
> Interesting. How can I check that? I have another almost-identical system
>
On Sun, 10 Mar 2013 20:24:55 -0400
Gerry Reno wrote:
> It seems like maybe it cannot find the root filesystem.
>
> Kernel panics just like this when it cannot find it.
Interesting. How can I check that? I have another almost-identical system
that's still working and I compared grub.conf betwe
On 03/10/2013 07:40 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 19:29:56 -0400
> Gerry Reno wrote:
>
>> Did you try booting a rescue disk and reinstalling the bootloader?
> I booted the "Centos 6.4 minimal iso", told it to "upgrade an existing
> installation", and to install the bootloader. About a
On Sun, 10 Mar 2013 17:40:39 -0600
Frank Cox wrote:
> The bootloader seems to be fine -- grub itself boots up. I get a kernel panic
> after that,
I just had a thought: Is it possible to just reformat and reinstall the /boot
partition? I wonder if that would solve the problem
--
MELVILLE
On Sun, 10 Mar 2013 19:29:56 -0400
Gerry Reno wrote:
> Did you try booting a rescue disk and reinstalling the bootloader?
I booted the "Centos 6.4 minimal iso", told it to "upgrade an existing
installation", and to install the bootloader. About all that it appeared to do
was install the bootload
On 03/10/2013 07:29 PM, Gerry Reno wrote:
> On 03/10/2013 07:00 PM, Frank Cox wrote:
>> On Sun, 10 Mar 2013 11:04:37 -0600
>> Frank Cox wrote:
>>
It may be easier to restore from backup and then attempt to do the update
again.
>>> Perhaps, but since everything seems to still be in place o
On 03/10/2013 07:00 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 11:04:37 -0600
> Frank Cox wrote:
>
>>> It may be easier to restore from backup and then attempt to do the update
>>> again.
>> Perhaps, but since everything seems to still be in place on those hard
>> drives,
>> and since my last "yum
On Sun, 10 Mar 2013 11:04:37 -0600
Frank Cox wrote:
> > It may be easier to restore from backup and then attempt to do the update
> > again.
>
> Perhaps, but since everything seems to still be in place on those hard drives,
> and since my last "yum update" completed without any errors being repor
On 03/10/2013 01:04 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 12:26:51 -0400
> Gerry Reno wrote:
>
>> The "yum update" that was running in your lost VNC session was in all
>> likelihood still running.
> If yum was indeed still running, it wasn't using any significant CPU. I did
> run top in my lo
On Sun, 10 Mar 2013 12:26:51 -0400
Gerry Reno wrote:
> The "yum update" that was running in your lost VNC session was in all
> likelihood still running.
If yum was indeed still running, it wasn't using any significant CPU. I did
run top in my login terminal to see if anything significant was goi
On 03/10/2013 12:12 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 12:14:14 +0100
> Reindl Harald wrote:
>
>> use "screen" if you update over WAN connections
>> yes, i know it is too late but thats the way to go
> I was doing it through VNC, thinking that would be more-or-less equivalent to
> screen, w
On Sun, 10 Mar 2013 12:14:14 +0100
Reindl Harald wrote:
> use "screen" if you update over WAN connections
> yes, i know it is too late but thats the way to go
I was doing it through VNC, thinking that would be more-or-less equivalent to
screen, which it apparently isn't. Somehow my vnc session (
On 03/09/2013 09:36 PM, Frank Cox wrote:
> During today's big Centos 6 update I lost my connection to a machine during
> the
> "yum update" and when I logged back in and ran yum update again it told me to
> run yum-complete-transaction. When I ran yum-complete-transaction I got
> screen after scr
For whatever it's worth - I yum update'd two VMs without any trouble
whatsoever (from 6.3 to 6.4) and am in the process of updating a laptop...
Not that it should matter but they are both guests running on a CentOS 5.9
Xen host.
I'm in the process of updating a laptop - I'm hoping it works too.
On 03/10/2013 07:47 AM, Frank Cox wrote:
> Well, this is interesting. I have three systems, all of which now have the
> same problem.
>
> I was running "yum update" on these machines via a vnc connection (running a
> vnc desktop on one of them, and logging into the others with a a
> gnome-terminal
Well, this is interesting. I have three systems, all of which now have the
same problem.
I was running "yum update" on these machines via a vnc connection (running a
vnc desktop on one of them, and logging into the others with a a
gnome-terminal on my vnc desktop), when my vnc desktop suddenly "w
During today's big Centos 6 update I lost my connection to a machine during the
"yum update" and when I logged back in and ran yum update again it told me to
run yum-complete-transaction. When I ran yum-complete-transaction I got
screen after screen of "x is a duplicate with x" where x consists of
25 matches
Mail list logo
