Topic: YUM didn't kill my Server TWICE (SMEv7p1) (EDIT)

[AaronG]

Hi,

I have reported this as a bug in bugzilla - BUG 538.

This has happend on two occasions. The first time I did a Manual YUM update and after doing a "signal-event post-upgrade" and "signal-event reboot" my server would not boot.

Code: [Select]

Unable to find volume group
ERROR: /bin/lvm exited abnormaly ( pid192)

mount: error 6 mounting ext3
mount: error 2 mounting none

switchroot: mount failed:22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init


After unsucessfully performing an "upgrade" re-install I tried doing it again but this time through the server-manager and then I did a RECONFIGURE reboot and it again failed... (I am not 100% sure it is the same error as I am working remotely, I will find it tomorrow) but i think it will be the same problem.

My hardware is a Intel Pentium 2.8, 2GB RAM, RAID 1 (Hardware) Adaptec SATA 1210SA Raid Card, 2 x 200GB Western Digital SATA drives.

I REALLY like the YUM update feature but I am now scared to use it.

Is there anyway i can fix this problem and get it to boot up again without reinstalling???

PLEASE HELP

[AaronG]

I might have jumped the gun too quickly in blaming YUM for my problem.

I have noticed that my server now has (maybe its always been there) a GRUB loader - it now displays a graphical background with TUX on it.

I have never interrupted this screen before but this morning I did. I noticed 4 operating system choices.

CentOS (2.6.9-22.0.2.EL)
CentOS (2.6.9-22.0.2.ELsmp)
SME Server (2.6.9-22.0.1.ELsmp)
SME Server Up (2.6.9-22.0.1.EL)

It appears that my server was defaulting the 2nd CentOS option. Thus causing the error outlined in my previous post.

I have subsequently tried to boot using each option. BOTH of the CentOS options give me the error however SME Server options boot up fine.

My next questions now are - is this normal?? Which option should I choose? What is the difference between the 2 SME options?? Should the CentOS ones be there?

I understand that SME is built on the core of CentOS.

Is there a bug that has caused my server to suddenly default to the CentOS option after a signal-event reboot ???

I apologise for being a typical noob and jumping to conclusions before thoroughly investigating the problem. I have been working mostly remotely with this server so my troubleshooting has been somewhat hindered.


Cheers
Aaron

[cc_skavenger]

did you have centos loaded previously?  If not, I would raise this as a bug.

[gordonr]

I apologise for being a typical noob and jumping to conclusions before thoroughly investigating the problem. I have been working mostly remotely with this server so my troubleshooting has been somewhat hindered.

No need to apologise for being a 'noob', but this is precisely why we want bugs reported in the bug tracker, and only there. Thanks.

[AaronG]

I haven't had CentOS installed previously.

Yes this has been reported as a bug in Bugzilla. My original Bug report has been updated to reflect the actual problem.

If i report this as a bug in bugzilla, is it inappropriate to discuss the problem here also???

[gordonr]

I haven't had CentOS installed previously.

Yes this has been reported as a bug in Bugzilla. My original Bug report has been updated to reflect the actual problem.

If i report this as a bug in bugzilla, is it inappropriate to discuss the problem here also???

Many thanks for keeping Bugzilla up-to-date - not everyone does

But please don't raise it in the forums as well, as it wastes a precious resource - developer time:

- We need to look in two places - Bugzilla and the forums - and merge the information
- We need to respond to the same issue in multiple threads
- We can't merge duplicate forum threads - we can merge duplicate Bugzilla items
- We need to respond to inappropriate advice
- Some advice provides fixes which causes later breakage
- The forum posts disappear into history without the issue being tracked
- People get into the habit of posting bugs to the forums, so the cycle continues

Please help us by keeping issues in Bugzilla. It is the quickest way to resolution, for all of us. Thanks.

[AaronG]

Ok..

Point Taken  

Thanks!!!