Fedora 2 Kernel updates kill my machine...

[marcusI]

I am fairly new with Linux and I am having a problem that I just can't figure out... if anybody could lend a hand it would be very much appreciated...

I installed Fedora 2 about a week back, played around with it and it seemed to be working fine. I then ran a redhat update, got a new kernel, and rebooted back into the old kernel (2.6.5-1.358) and it worked fine. I decided to give a new kernel a try, rebooted into the new kernel and it crapped out on me... rebooted and tried to go into the old kernel again and that crapped out on me too.... I rebulit my comp from scratch again, a coworker of mine said it can't be the kernel, just try it again... sure enough it tanked on me again...

So far, I have rebuilt my machine from scratch 3 times, it happened each time I tried the new kernel but the last time this happened I wrote down all that I saw....

-

Red Hat nash version 3.5.22 starting

**** this takes a few mintues ****

INIT: version 2.85 booting
Setting default font [OK]

Welcome to Fedora Core
Press I to enter interactive startup

i\i/Configuring kernel parameters: [OK]
Setting Clock [OK]
Loading default keymap [OK]
Setting hostname mifedora01 [OK]
Initializing USB controller (uhci-hcd): [OK]
Mounting USB filesystem [OK]
Checking root filesystem
/: clean, 157522/2101152 files, 793373/4194973 blocks

Remounting root filesystem in read-write mode [OK]
EXT3-fs error (device sda2) in ext3_dirty_inode: Journal has aborted ext3_abort called
EXT3-fs abort (deveice sda2): ext_journal_start: Detected aborted journal
Remounting filesystem read-only

***** takes about 10 minutes, then continues on to black screen where it hung up (or seemed to)
Rebooted the system and tried to go back into the old kernel (2.6.5-1.358) where I received the following…

Root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
Kernel /vmlinuz-2.6.5-1.358. img [Linux-initrd @ 0x1fe72000, 0x4d74b bytes]

Uncompressing Linux … Ok, booting the kernel.
Audit(0087474723.4294935408:0) : initialized
Red Hat nash version 3.5.22 starting
EXT3-fs: error (device sda2): ext3_check_descriptors: Block bitmap for group 80 not in group (block 0)!
EXT3-fs: group descriptors corrupted!
Mount: error 22 mounting ext3
Pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed: 2
Umount /initrd/proc failed: 2
Kernel panic: No init found. Try passing init= option to kernel

-

Just to note, I am running a SCSI drive in case that may be related.... I would appreciate any help to avoid this problem in the future... Thanks

[SuperNu]

Just to let you know, I have been having one hell of a time with my scsi cd-rw and cdrom with Fedora Core 2. I believe that there is some major problems with the scsi modules in the 2.6 kernel. I have made posts regarding my problem here and here. So far, the only solution I have found is to upgrade to the very latest kernel version, 2.6.6-1.435 at the time of this writing. I would try to compile your own kernel and see if that helps you out. You could also go back to 2.4 if you have to.

--SN

[marcusI]

just an update in case anybody has a problem like mine....

I replaced the SCSI controller and HD with an IDE drive. Works fine now....
seems like something is wrong with the newer kernels in supporting one or both of my devices. Just for a reference, I was using an Adaptec SCSI card 29160N and a Quantum Atlas V SCSI drive.

[Picomp314]

you need to recompile a custom kernel to enable scsi support

[Thetargos]

Originally Posted by Picomp314

you need to recompile a custom kernel to enable scsi support

Now that's what I call careless kernel building!! Why did the FC2 folks suddenly decided NOT to enable SCSI support in their stock kernels? (that paired with the inability to use the libata with the official kernels, unless you recompile them, for that matter, you'd better compile the latest vanilla, and you'd be set anyway!)...