Topic: 7.1 failed at boot after updates

[vk7krj]

I have a reasonably new installation of 7.1 here, working well for the last couple of months- until tonight. I ran updates from the web gui, all seemed to go ok (lots of updates- about 2 or 3 pages full) until it asked to reboot to finish configuring. Now the server gets as far as


  Booting 'SME Server (2.6.9-42.0.10.Elsmp)'

root (hd0,0)
 Filesystem type is ext2fs, partition type )xfd
kernel /vmlinuz-2.6.9-42.0.10.Elsmp ro root=/dev/main/root
   [Linux-bzImage, setup=0x1400, size=0x15f56e]
initrd /initrd-2.6.9.42.0.10.Elsmp.img
   [Linux-initrd @ 0x1dedb00, 0x104be0 bytes

Uncompressing Linux... Ok, booting the kernel.


and just stops.

As a newcomer to linux, I am completely stuck- and with a LOT of data on the H/D  (around 80gig) I would REALLY appreciate not having to reload it all..
I have searched the forum with various search terms but couldn't find anything similar- is there anything I can do short of reinstalling and having to reload all my data. I am running raid1 with two, 340gig H/D's

Thanks, Ken Johnson

[byte]

I have a reasonably new installation of 7.1 here, working well for the last couple of months- until tonight. I ran updates from the web gui, all seemed to go ok (lots of updates- about 2 or 3 pages full) until it asked to reboot to finish configuring. Now the server gets as far as

Please report bugs and potential bugs in the bug tracker. Thanks.

[vk7krj]

Byte- how have you identified that this is a bug?  How am I, as a newbie and linux noephyte supposed to identify this as a bug and not finger trouble on my part?
I would have thought that until the same or a very similar problem occurs a number of times, it is merely a problem to be discussed in a general forum- as I said in my original post, I could not find anything similar in my searches of the forums so I presumed that the problem was an error on my part.
I really would appreciate some help with the problem, not just a smack on the wrist for daring to ask for help on SME in an SME forum.

Ken Johnson.

[bpivk]

Byte- how have you identified that this is a bug? How am I, as a newbie and linux noephyte supposed to identify this as a bug and not finger trouble on my part?

Did you mess With SME? If not: "Post a bug".

I would have thought that until the same or a very similar problem occurs a number of times, it is merely a problem to be discussed in a general forum

No. People use different computers so someone can have a clean install and won't have any problems and another user will have to constantly report issues with his server.

Do what byte told you and post a bug. Developers will help you and tell you what you have to do and you'll solve your problem.

[byte]

Byte- how have you identified that this is a bug?

I haven't and haven't even identified this as a bug, but because you updated server it could be a "potential" bug therefore gave normal response of opening a bug.

How am I, as a newbie and linux noephyte supposed to identify this as a bug and not finger trouble on my part?

You've not. that's why as a "potential bug" I've pointed you to the bug tracker for

I really would appreciate some help with the problem, not just a smack on the wrist for daring to ask for help on SME in an SME forum.

My post (as I always post) was not intended as a smack on the wrist, it's normal procedure, if I saw your post and thought I could help then I would but because it could be a "potential" bug we need to move this over to the bug tracker.

[okepc]

The most read line on this forum is:

Please report bugs and potential bugs in the bug tracker. Thanks.

And it becomes very annoying!

vk7krj needs help here.
So please help him out.

My 2 cents

Dirk

[byte]

The most read line on this forum is:

Please report bugs and potential bugs in the bug tracker. Thanks.

And it becomes very annoying!

You may well do...But I don't get annoyed repeating, because otherwise nothing would get fixed, if you read before you post you will see in red "Don't report problems here" then I/others would not have to post saying exactly that.

vk7krj needs help here.
So please help him out.

And if he needs help he will need to help us by posting a bug report, if this wasn't a potential bug I/others would help.

[okepc]

So what are you suggesting to post in this forum?

Don't report problems here

Might as well take everything to the bug tracker as all i see are problems in these forums that people want to be solved.

My idea is let the community try and solve the problem first and if everything else fails, then report it to the bug tracker.

Another 2 cents

Dirk

[okepc]

You can hit a button on the splash screen and choose the previous kernel and see what happens.

Dirk

[byte]

So what are you suggesting to post in this forum?

Don't report problems here

Ok let me put the full sentence in case anyone else is misunderstood before you post you will see...

Don't report problems here - Please report bugs and potential bugs in the bug tracker.

That is what is suggested.

My idea is let the community try and solve the problem first and if everything else fails, then report it to the bug tracker.

That's fine, but my idea is if it's "potential bug" then I shall redirect to bug tracker, if I know it's not a potential bug then I'll read thread and see if it's something I can help.

Let's stick to topic as all of us will have different views and we could have a never ending thread.

[okepc]

Did you try this?

You can hit a button on the splash screen and choose the previous kernel and see what happens.

[manankanchu]

@vk7krj

Ken,

I had exactly the same issue after fresh installation with 7.1 ... I came across it by selecting the second entry on the splash screen (that's the white screen with GNU GRUB headline) instead of just letting it run with the first line "SME Server (2.6.9-42.0.3.ELsmp)"

So selecting "SME Server-up (2.6.9-42.0.3.EL)" made it boot properly.

Don't ask me the difference ... I'm running SME since years happily without really knowing the details ... might make some of the experts shiver

Maybe it helps ...

Rgds

  M.

[psdata]

Hello,

I have here the same problem, only after a upgrade (yum) and whith a newer kernel version

Booting 'SME Server (2.6.9-55.0.02.Elsmp)'

root (hd0,0)
Filesystem type is ext2fs, partition type )xfd
kernel /vmlinuz-2.6.9-55.0.02.Elsmp ro root=/dev/main/root
[Linux-bzImage, setup=0x1400, size=0x15f56e]
initrd /initrd-2.6.9.55.0.02.Elsmp.img
[Linux-initrd @ 0x1dedb00, 0x104be0 bytes

Uncompressing Linux... Ok, booting the kernel.


and just stops.


I have al ready tried to make a update from CD and to select the old kenale version vmlinuz-2.6.9-42.0.03.Elsmp

But then whith booting it says file is missing.

How can I reinstall the kernal whithout lossing the data and user information.

On this moment I make a disk backup so I play later whith a copy off the data.
Strange This server install is all ready running for 5 year's no problems, after hardware upgrade's, disk upgrades and a lot off yum upgrade's

I need some help to reinstall the only the kernal.

Regards

John