OK, so I did a motherboard swap and now when trying to get linux to boot I get a error

mount error 6 reiserfs
pivotroot pivot_root (/sysroot, /sysroot/initrd)
kernal panic no init found


so this is about as cryptic as MS windows blue screen

Can someone offer an idea on how to recover from this.

aparently something isn't getting mounted properly, but aside from the motherboard swap the machine is the same.

Since I have work that I don't really want to lose, I move the drives back to the old machine. I'm going to try a different set of drives, 1 ide 2 scsi and see if Fedora likes the new board.

But that aside, is there a way to make linux recover from this or re-initialize so it will detect the hardware change and adjust.

Interesting note, when running the install/upgrade, the disk part. app doesn't see the boot drive, nor does rescue see any linux partitions.

lastly sorry if I sound a but dumb, 1 year newbie here

fyi

Fedora,
old box pIII 1 ghz, 3 scsi drives on adaptec 2940 512 memory
new p4-celeron 2.5 ghz intel 848 chip set, all else same.

TIA

"mount error 6 reiserfs
pivotroot pivot_root (/sysroot, /sysroot/initrd)
kernal panic no init found"

initrd loads modules that you need in order to boot. The most likely error is that one of the modules is for your ide controller (or possibly scsi if you are booting a scsi drive). The hard drive controller is chipset dependent. If your new motherboard has a different IDE controller chipset than the old motherboard then the wrong hard drive chipset driver is being loaded by initrd and things start to crap out.

"But that aside, is there a way to make linux recover from this or re-initialize so it will detect the hardware change and adjust."

The hardware detection was done by the Fedora installer which set up the initrd. I suppose that you could add an alternate initrd with the correct drivers and then set up a dual boot with two entries in grub to the same kernel with different initrds.

A better way to solve this problem would be to do a Fedora install on the new machine. Install to a new partition and set up a dual boot until you get the new systm working.

"Interesting note, when running the install/upgrade, the disk part. app doesn't see the boot drive, nor does rescue see any linux partitions."

This statement is a little cryptic. You may have the problem that your new hardware configuration is not actually working 100% yet.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites