| 1 |
On Wednesday 27 July 2011 17:18:19 James Wall wrote: |
| 2 |
> On Wed, Jul 27, 2011 at 4:03 PM, Dale <rdalek1967@×××××.com> wrote: |
| 3 |
> > Here is a update. Let's see what folks think about this situation. I |
| 4 |
> > mentioned in another thread that I did a from scratch kernel. It was a |
| 5 |
> > .35 version. It seemed to work fine, for a while. When I tell |
| 6 |
> > Seamonkey to download to my desktop, it works fine. The minute I tell |
| 7 |
> > it to save it to my large 750Gb drive, I get a kernel panic. Keep in |
| 8 |
> > mind, there is nothing OS related on that drive. Nothing OS at all. |
| 9 |
> > It is videos, CD ISO's and such as that. |
| 10 |
> > |
| 11 |
> > Here is another thing I just found out. I did download a few videos I |
| 12 |
> > wanted to save. They were on my desktop and who likes desktop clutter. |
| 13 |
> > So, I dragged them over to the large data drive. I did this by |
| 14 |
> > dragging from the desktop to a open Konqueror window. This was not |
| 15 |
> > downloading or anything, just a straight move operation. It copied a |
| 16 |
> > few Mbs and panic. This had nothing to do with Seamonkey either. |
| 17 |
> |
| 18 |
> This looks like a drive/cable issue, since it only occurs on the one |
| 19 |
> drive. If both drives are SATA, I would try swapping the cables to |
| 20 |
> rule out a bad cable. If the problem stays with the drive I would |
| 21 |
> first try a different SATA port to see if that clears up the issue. |
| 22 |
|
| 23 |
I would also check that all the cables are plugged in properly and that there |
| 24 |
is nothing conductive (like metal) touching the drive where it really |
| 25 |
shouldn't. |
| 26 |
Maybe open the case, take the drive out and put it on a big sturdy cardboard |
| 27 |
box to avoid possible shorts. |
| 28 |
> |
| 29 |
> > So, did this issue just move from a Seamonkey sort of problem to |
| 30 |
> > completely something else? Hmmmmm. After the crash, I boot to single |
| 31 |
> > user mode. I ran resierfsck --fix-fixable on the drive. Not one |
| 32 |
> > error. |
| 33 |
|
| 34 |
Did you do that on a mounted drive? I would first try a filesystem check before |
| 35 |
using that command. |
| 36 |
|
| 37 |
> > I ran the smart thingy and not one error there either. |
| 38 |
|
| 39 |
Did you force the short and long tests to be run and waited for them to be |
| 40 |
finished? On a large drive, the long test can easily take several hours |
| 41 |
(without any indication of how far it actually is) |
| 42 |
|
| 43 |
> > Thinking file system is bad in the kernel, well my /home directory is |
| 44 |
> > on reiserfs too. It is the one that works. |
| 45 |
|
| 46 |
If it were the reiserfs implementation, the issue would be more common. |
| 47 |
|
| 48 |
> > Now, what the heck is this about? Does this make sense to anyone? |
| 49 |
|
| 50 |
It does, there is something wrong with that drive. |
| 51 |
|
| 52 |
Another thing you could try is to plug that drive into a different machine (I |
| 53 |
believe you still have your old one?) and see if the same issue occurs there. |
| 54 |
Also, now would be a good time to have backups of the data on that drive :) |
| 55 |
|
| 56 |
-- |
| 57 |
Joost |
Archives