Hi,

I have Redhat 9 installed and running just fine. My PC performed an unusual shutdown during the Blackout, however I wasn´t running any programs or doing anything. It was probably just in screensaver mode or the screen was blank.

Now, when I boot the system it boots fine. However when I ask it to shut down, I get the following Code: Bad EIP Value. This massage appears after it kills several procceses, after unmounting file system, after Halting System.

I don´t know what to do.

I checked the log files for Boot and everything logs as successful

Under system log I get these unusual logs
Aug 16 15:02:35 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:02:35 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 16 15:02:35 localhost gconfd (root-3809): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Aug 16 15:02:35 localhost gconfd (root-3809): Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Aug 16 15:02:35 localhost gconfd (root-3809): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Aug 16 15:03:45 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:03:45 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 16 15:04:26 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:04:26 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 16 15:07:31 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:07:31 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 16 15:13:16 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:13:16 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }


Thats all I know...Iḿam a bit new to Linux so I may be making a big thing out of nothing...

Please help.
Regards,
C.

PS Let me know if I can provide more info.

Hope you shut down the box to possibly prevent corruption. If hdb is a harddisk, then back up if you need to and run "badblocks" on the drive. About gconfd, verify the rpm and reinstall if necessary. IMHO ain't worth worrying about.

hdb is my slave drive on the first ide channel...this is where I have my linux partitions.

I am unsure how to use badblocks but I did try fsck. I ran it in single user mode, unmounted hdb and then I did fsck /dev/hdb and it told me that the superblock did not recognize a valid ext2 partition or drive.

I also tried setting my bios to pio instead of dma.

I also tried switching cables and nothing has worked.

hopefully I can figure out how to use the badblocks command.

Do you have any other suggestions

one more thing...i was unable to shutdown correctly....the blackout happened when I was outside....when i came back everything was down.

C

*Before you start, if you have important data you definately need to recover, then first make a backup of the partitions (or if unsure of the whole disk) to another medium or another drive. if you don't want to use a proprietary solution, or Partimage, then just do "dd if /dev/hdbX of=/mnt/anotherharddisk/somefileX" (where X is a partition number) .

"fdisk -l /dev/hdb" should show the partition table.

If you don't recognize any of it, or if it shows plain wrong info, try testing your disk (and recovering your partition table if necessary) with Testdisk and
Gpart.

If it does show a correct partition table, then "mke2fs -n /dev/hdbX" should give you the locations where the backup superblocks are. Run "e2fsck -b <backupsuperblock> -n /dev/hdbX" for a testdrive (answers "no" to all questions and nothing will be changed) if you need to see what e2fsck will be doing before it actually does it. Now run "e2fsck -b <backupsuperblock> -c /dev/hdbX".