According to Tom Taylor: While burning my CPU.
>
> I'm having an unusual problem. I installed SuSE 6.1 several times testing
> different configurations without experiencing problems until early this
> week. Something is now causing a problem with not being able to read the
> SCSI drives in my system. My boot drive, an IDE, is still working properly.
> The message (see bottom of page) indicates a bad superblock.
>
> Using the Rescue floppy from one of the previous installs, I am able to
> boot completely and run without problems, including access to both of the
> SCSI hard drives.
>
> This is the displayed message (as much of it as I can see) when the problem
> occurs:
>
> insmod: /lib/modules/2.2.5/scsi/sd_mod.o; insmod block-major-8 failed
> fsck.ext2; Operation not supported by device while trying to open
> /dev/sdb1 /dev/sdb1:
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock is
> corrupt, and you night try running 32fsck with an alternate superblock:
>
> e2fsck -b 8193 <device>
>
> after remounting / as rw, that attempt results in:
>
> (none): ~ # e2fsck -b 8193 /dev/sdb1
>
> e2sfck 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
> insmod: /lib/modules/s.s.5/scsi/sd_mod.o: insmod block-major-8 failed
> insmod: /lib/modules/s.s.5/scsi/sd_mod.o: insmod block-major-8 failed
> insmod: /lib/modules/s.s.5/scsi/sd_mod.o: insmod block-major-8 failed
> insmod: /lib/modules/s.s.5/scsi/sd_mod.o: insmod block-major-8 failed
> e2fsck: Operation not supported by device while trying to open /dev/sdb1
>
>
> The same results occur when I try to use the rescue disk from the
> re-install but not from my original rescue disk.
>
> I don't think that the superblock is corrupt or I would have the same
> problem from my original rescue disk. I've loaded RedHat 6.0 after the
> failed SuSE install and it worked without a problem but I prefer to be able
> to reload SuSE and use it without a floppy.
The problem is possably being caused by using a module from another kernel
version.
'insmod' cannot load the module sd_mod.o or so it seems.
>
> Any ideas?
>
> I'm attaching the (I think) appropriate log files.
>
> System info:
>
> M/B ASUS P5T2P4
> CPU AMD K5-100
> MEM 64MB
> HD1 WD 31000 IDE hdax
> (/,/boot,/root,/home,/usr,/var as separate partitions)
> HD2 Conner CFP 1080S sda (ID0)
> (/stuff)
> HD3 Conner CFP 1080S sdb (ID1)
> (/opt)
> Adaptec 2940 controller (ID7) V1.16 bios
> FD1 Teac FD235HF
> VGA Diamond Stealth S3 Vision 868 bios V1.02
> NET Clone PCI ethernet 10Mbps (NE-2000 mode)
> SB AWE32 CT3900 (IDE port disabled)
> TAPE Colorado Jumbo250
> TAPE CTRL: Colorado FC-20
> CD-ROM NEC CDR-1610A SCSI (ID=4)
> MOUSE Logitech FirstMouse M-C43
>
> This has all been in the system and working from early May until this week.
>
>
>
> THIS MESSAGE HAS ALSO BEEN SENT TO [EMAIL PROTECTED]
>
> Tom
>
> -----------------------------------------------------------
> Tom Taylor Sr. Development Technician
> Telemedic Systems, Inc. 253.529.0526
> Member: PSLUG http://sealinux.itsite.com
> email: [EMAIL PROTECTED], [EMAIL PROTECTED]
> -----------------------------------------------------------
> When you get to the point where you really understand your
> computer, it's probably obsolete.
> ------------------------------------------------------------
>
--
Regards Richard.
[EMAIL PROTECTED]
