On Wed, Jul 27, 2011 at 4:03 PM, Dale <rdalek1...@gmail.com> wrote: > > Here is a update. Let's see what folks think about this situation. I > mentioned in another thread that I did a from scratch kernel. It was a .35 > version. It seemed to work fine, for a while. When I tell Seamonkey to > download to my desktop, it works fine. The minute I tell it to save it to > my large 750Gb drive, I get a kernel panic. Keep in mind, there is nothing > OS related on that drive. Nothing OS at all. It is videos, CD ISO's and > such as that. > > Here is another thing I just found out. I did download a few videos I > wanted to save. They were on my desktop and who likes desktop clutter. So, > I dragged them over to the large data drive. I did this by dragging from > the desktop to a open Konqueror window. This was not downloading or > anything, just a straight move operation. It copied a few Mbs and panic. > This had nothing to do with Seamonkey either.
This looks like a drive/cable issue, since it only occurs on the one drive. If both drives are SATA, I would try swapping the cables to rule out a bad cable. If the problem stays with the drive I would first try a different SATA port to see if that clears up the issue. > So, did this issue just move from a Seamonkey sort of problem to completely > something else? Hmmmmm. After the crash, I boot to single user mode. I > ran resierfsck --fix-fixable on the drive. Not one error. I ran the smart > thingy and not one error there either. Thinking file system is bad in the > kernel, well my /home directory is on reiserfs too. It is the one that > works. > > Now, what the heck is this about? Does this make sense to anyone? > > Dale > > :-) :-) > > -- No trees were harmed in the sending of this message. However, a large number of electrons were terribly inconvenienced.
