Sounds like a wierd hardware bug to me, perhaps it could be reproduced using another OS? A dirty hack would be to make cron run ls command on your drive every 5 minutes or so. It will not resolve the underlying problem, but perhaps the symptoms will go away. To do this, you need to issue command
$ crontab -e after which cron will ask you for a string which specifies when and how often you want to run the process. To issue ls every five minutes enter: */5 * * * * /bin/ls /path/to/your/drive > /dev/null Change /path/to/your/drive to the location where the drive is mounted and hopefully there will be no problems. Max Shkurygin. On Fri, May 22, 2009 at 12:35 PM, xe22 <[email protected]> wrote: > Russell Polo wrote: >> >> I have a weird behavior on my AMD64 dual core FC 10 computer. >> >> The machine has both IDE and SATA buses. I have the "old" drive on the IDE >> interface and a new 1GB drive on the Sata, I also have a DVD burner on the >> IDE side. >> >> It seems that sometime after boot, (if they aren't being used) the machine >> will "forget" about the IDE devices. The mounted drive becomes inaccessible >> and the devices can not be read. Not sure on the time, it is probably more >> than 30 minutes so it's hard to test. >> >> I have learned that a silly script that just does a "ls" on the old drive >> every 30 seconds seems to keep it around. >> >> I also seem to get kernel oops reports associated with losing the drives. >> ( I get a "request to send report" ) when I restart. >> >> Once I lose the drives, a reboot is not enough to get them back. It takes >> a full shutdown and restart. >> >> The recent discussion of BIOS problems has got me thinking this might be a >> good place to look for a solution. I had been thinking it was a kernel >> problem that would probably bee fixed by an update, There have been several >> updates and I haven't seen a change in behavior. (I have been dealing with >> this for about 6 months) >> >> I have been out of the hardware side of things for so long I probably have >> been demoted to "newbie" on the issue, I'm not even sure how to tell you >> what motherboard I have installed. Any guidance would be appreciated. >> >> >> --Russell >> _______________________________________________ >> Mid-Hudson Valley Linux Users Group http://mhvlug.org >> http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug >> Upcoming Meetings (6pm - 8pm) MHVLS Auditorium >> Jun 3 - TBD >> Jul 1 - TBD >> Aug 5 - TBD >> > I found GRUB to cause failure on mixed disk systems. SATA/SCSI caused major > damage, and SATA/USB > was causing confusion on bootup. I switched to LILO and the problem is gone. > Just something to try. > > Louis > _______________________________________________ > Mid-Hudson Valley Linux Users Group http://mhvlug.org > http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug > Upcoming Meetings (6pm - 8pm) MHVLS Auditorium > Jun 3 - TBD > Jul 1 - TBD > Aug 5 - TBD > _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 3 - TBD Jul 1 - TBD Aug 5 - TBD
