Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I just started having the following errors on my WD 80gig HD since upgrading to Slackware 9.1 and compiling a custom kernel for it. I've had the drive for about a year and have not had a problem with it till now.
If you still got warranty on the hdd head over to http://sourceforge.net/projects/va-ctcs/ install it,read the warning and run the hdd test for about a day or two.I had the same warning various times on one hdd about a year ago and also got data corruption but after I changed file systems it worked fine.
# IDE, ATA and ATAPI Block devices
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
Looking over this config, it looks like I should try and compile a new kernel and clean up the IDE section abit (lose CMD640, etc)
Ok, I think I found a few things that might have been causing the errors, but as far as which exact one, I'll never know.
1. ext3: I'm mounting the partitions as ext2 to avoid the corrupt journal. Trying to figure out how to fix it.
2. I have $CFLAGS and $CXXFLAGS sourced at login. They might have borked up the kernel.
3. ACPI: I did have it working with 2.4.19 and had to dump it when moving to 2.4.21. I re-enabled it for 2.4.22, and it seemed to make my system flaky.
1. Switching to a different journaling filesystem at next hardware upgrade. Ext3 worked good for a few years, but I can't afford to lose my /home partition, too much valuable info. (yes I back up, but one day can really screw me).
2. Compile flags will be exported only when I actually compile a program, not at login.
3 ACPI is nice, but not too stable at this point, hopefully 2.6 will make it more solid.
Thanks for the help guys. Off to search the forums about journaling FS opinions.
Last edited by larrystorch; 11-03-2003 at 08:20 PM.
In the end, the hard drive was on it's last leg. It was a Maxtor that was only 2 years old. I bought a new Western Digital, and was able to copy over my important data before taking a sldgehammer to the Maxtor.
For some reason, I have had 3 Maxtor drives of different sizes and purchased at different times all die prematurely. On the other hand, some of my friends have never had a problem with Maxtor.
If you have another hard drive around, hook it up to the same IDE channel to see if it's kernel or IDE channel giving you problems. I went thru a bunch of kernel, IDE channel and drive combos till I was certain it was hard drive.