Hi All, About once a week, I get a this strange error on bash command line. Running any command on the command line results in " Input/output error". Only way to get back to normal operation is to hard reboot the machine. I suspect this is something to do with my file system. I am using RH7.3 with ext3 file system on IBM Travelstar drives. I use dd to duplicate the drives. The source and the target drives are identical (same make, model) .I am not sure, but I suspect this error message comes up only on the duplicated drives. (I have never seen this message on my desktop which has a different drive). Any pointers on what is causing this problem would be great Thanks Rahul
Rahul,>About once a week, I get a this strange error on bash command line. >Running any command on the command line results in " Input/output >error". Only way to get back to normal operation is to hard reboot the >machine. I suspect this is something to do with my file system. I am >using RH7.3 with ext3 file system on IBM Travelstar drives.Sounds like a hardware issue. Like the Travelstar drives are failing or something more insidious (hardware-wise) is happening. I had a similar issue and it turned out that the Processor was giving up the ghost. (Later, I found out that the *CENSORED* that had built the server had Overclocked the CPU "for kicks".)>I use dd to duplicate the drives. The source and the target drives are >identical (same make, model) .I am not sure, but I suspect this error >message comes up only on the duplicated drives. (I have never seen this >message on my desktop which has a different drive).If it only happens to one of the drives, it is also possible that the one drive is failing. I am far from an expert on 'dd'. However, I can say that I have never come across a hard drive kicking out an error only due to being a duplicate of another drive. If you want to confirm that, wipe the suspect drive, rebuild the file system and then copy everything with a more mundane 'cp' command. If the drive is bad, it will likely fail when you are wiping it. It is also possible that you have an IDE channel issue. So, it would be best to further test the 'bad' drive in another PC for final confirmation.>Any pointers on what is causing this problem would be greatI can only point at hardware problems with the information you have provided. Regards, Robert Adkins IT Manager/Buyer Impel Industries, Inc. 586-254-5800
I have the same input/output error on my dell server. I emailed stephen c tweedie and alan cox about it. I believe its a hardware failure in my case. I had /var/log/ mounted to another disk not on the scsi card that was causing problems, and the driver reported that it was unable to contact the scsi card (or something like that). so I will have to have dell ship me out a new board. You should try moving your /var/log to another drive not on your scsi card and next time you get those errors, look at /var/log/messages for clues. Adam
Rahul, I just start experiencing the exact same problems on one of my RedHat 7.3 servers. So far it has been about once a week. The first time this happened, I was lucky enough to get an error in the error log, and it turned out to be from an old kernel bug (kernel BUG at journal.c:406!) I upgraded from 2.4.18-3smp to 2.4.18-27.7.xsmp, but the problem came back, this time with no errors in the log. I thought it might be hardware related (the system would not boot with hda in the system after the 1st crash), so I replaced a harddrive, rebuilt the array, ran e2fsck on /dev/md*, and so far, everything has been fine. It has only been 3 days though, I am afraid the problem might come back. I don't know if any of this helps, but I would like to get to the bottom of this too. I'm running: RH 7.3 with ext3 the rh kernel 2.4.18-27.7.xsmp And raid 1 on dual WDC 120 GB harddrives. /dev/md0 4.8G 1.1G 3.4G 24% / /dev/md2 45M 19M 24M 43% /boot /dev/md1 99G 8.0G 86G 9% /home none 1008M 0 1008M 0% /dev/shm /dev/md3 4.8G 464M 4.1G 10% /var -= END =- ========================================================== Hi All, About once a week, I get a this strange error on bash command line. Running any command on the command line results in " Input/output error". Only way to get back to normal operation is to hard reboot the machine. I suspect this is something to do with my file system. I am using RH7.3 with ext3 file system on IBM Travelstar drives. I use dd to duplicate the drives. The source and the target drives are identical (same make, model) .I am not sure, but I suspect this error message comes up only on the duplicated drives. (I have never seen this message on my desktop which has a different drive). Any pointers on what is causing this problem would be great Thanks Rahul _______________________________________________ Ext3-users mailing list Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
On Mon, Apr 21, 2003 at 12:52:07PM -0400, Rahul Kalaskar wrote:> Hi All, > > About once a week, I get a this strange error on bash command line. > Running any command on the command line results in " Input/output > error". Only way to get back to normal operation is to hard reboot the > machine. I suspect this is something to do with my file system. I am > using RH7.3 with ext3 file system on IBM Travelstar drives.Quite possibly. Check your system logs --- i.e., check out /var/log/messages, and/or the dmesg command. That should give you more information. You might also want to force an fsck check on the partition ti make sure you don't have any hidden corruptions hiding in your filesystem. - Ted
I've no idea what the problem is, but I use the same approach, and have never had trouble with Linux or Windows 98. The only problem I've had with this scheme is that duplicating Windows 2000 (in a partition on the same drive) kills Windows 2000 - even the original (??! - it won't allow login anymore). dd if=/dev/hda of=/dev/hdc bs=16384k (I've tried many values for bs. All seem to work.) Maybe that's helpful for helping eliminate possibilities. How often do you use this? Does the problem only occur once a week because you only back it up once a week, or is there less of a correlation? Cheers, Bret Rahul Kalaskar wrote:> >Hi All, > >About once a week, I get a this strange error on bash command line. >Running any command on the command line results in " Input/output >error". Only way to get back to normal operation is to hard reboot the >machine. I suspect this is something to do with my file system. I am >using RH7.3 with ext3 file system on IBM Travelstar drives. > >I use dd to duplicate the drives. The source and the target drives are >identical (same make, model) .I am not sure, but I suspect this error >message comes up only on the duplicated drives. (I have never seen this >message on my desktop which has a different drive). > >Any pointers on what is causing this problem would be great > >Thanks >Rahul > > > > > >_______________________________________________ >Ext3-users mailing list >Ext3-users@redhat.com >https://listman.redhat.com/mailman/listinfo/ext3-users >