Messed up officially. Linux related.

[pillage2001]

I know this is off topic but I figure I would get help the fastest here.....Mods please don't move it...

Here's the situation, I have a server running a software RAID and I made a new kernel and updated it. When I rebooted, it showed this:

Uncompressing linux...

...ran out of input data.

-- System halted.


I tried running the old images but it wouldn't run due to the software RAID. It said something about not able to mount the root and went into the kernel panic.

Need steps to work around this problem and I'm running out of ideas. I'm not really linux incline...

Update:

Got to mount the root onto /dev/hda1 but it said it could not open an initial control.

I tried init=1 but gave the same crap. It asked me to use the init= option but it did not budge.

 

[Pepsi90919]

I'm not really linux incline...

and your avatar?

 

[IEC]

He probably wanted to be Linux-inclined... and it's just an avatar anyways...

 

[SacrosanctFiend]

Originally posted by: Pepsi90919

I'm not really linux incline...

and your avatar?

Is a penguin.

 

[monzi]

Hummmmmmmmmm,


google it.

 

[KeyserSoze]

Googled for ya, sorry, can't be much more help than this.





KeyserSoze

 

[hevnsnt]

Might have more luck in the OS forum

 

[jonnyfin]

Ouch! I've run into a similar problem but my error got past the uncompressing linux state, and held me up at an out of loopback addresses message.

Sorry I can't help further, but that's how I realized it's a VERY good idea to install the new kernel rather than upgrade the existing kernel. You can always rpm -e the old kernel once you've tested out the new kernel.

You may want to try doing an upgrade installation, and just changing the boot loader to say lilo/grub, (whatever you're not currently using), make sure to keep all existing filesystems. That should reinstall the original kernel.

 

[Pepsi90919]

Originally posted by: SacrosanctFiend

Originally posted by: Pepsi90919

I'm not really linux incline...

and your avatar?

Is a penguin.

OMG!@at

 

[Platypus]

Without knowing any specifics of what you did, I would suggest reading this document:
http://www.tldp.org/HOWTO/Boot+Root+Raid+LILO.html

If you're using something like lilo as your bootstrap, you can point towards root on the lilo command line if you know where it's supposed to be.
( root=/dev/md0) as a stab in the dark?

If you have grub, I can figure out how to acheive similar results or something

 

[pillage2001]

Originally posted by: CorporateRecreation
Without knowing any specifics of what you did, I would suggest reading this document:
http://www.tldp.org/HOWTO/Boot+Root+Raid+LILO.html

If you're using something like lilo as your bootstrap, you can point towards root on the lilo command line if you know where it's supposed to be.
( root=/dev/md0) as a stab in the dark?

If you have grub, I can figure out how to acheive similar results or something

Yeah, I'm using lilo as my bootstrap.

Thing is, would lilo even see my RAID array?? I'm usign a software RAID and was told that I need to load the drivers before I can access the drive.

I looked up google.

If I use a rescue disk, can I access the partition on my software RAID??

edit: I used root=/dev/md0 and it still went into kernel panic. Can't mount root. I'm pretty sure it's md0.

 

[skyking]

Rescue disks should be able to see into software raid arrays.
do you recall what distro you are using, and what kind of array?

 

[Platypus]

Originally posted by: pillage2001

Originally posted by: CorporateRecreation
Without knowing any specifics of what you did, I would suggest reading this document:
http://www.tldp.org/HOWTO/Boot+Root+Raid+LILO.html

If you're using something like lilo as your bootstrap, you can point towards root on the lilo command line if you know where it's supposed to be.
( root=/dev/md0) as a stab in the dark?

If you have grub, I can figure out how to acheive similar results or something

Yeah, I'm using lilo as my bootstrap.

Thing is, would lilo even see my RAID array?? I'm usign a software RAID and was told that I need to load the drivers before I can access the drive.

I looked up google.

If I use a rescue disk, can I access the partition on my software RAID??

edit: I used root=/dev/md0 and it still went into kernel panic. Can't mount root. I'm pretty sure it's md0.

I'll try to look into it if I have some time tomorrow

 

[pillage2001]

Check updates.