"An error was detected on device \Device\Harddisk6\D during a paging operation."
in [Asus]
|
Prev: P4S8X beeps Hi-Lo-Hi-Lo
Next: M2A-VM with Firewire
From: R on 20 Dec 2008 21:15 On Thu, 18 Dec 2008 20:02:20 -0000, "Oldish Git" <noone(a)nowhere.noway.con> wrote: > >"Paul" <nospam(a)needed.com> wrote in message >news:gidig2$j94$1(a)news.motzarella.org... >>R wrote: >>> Motherboard: P5K-E Wifi. Several drives, mostly Seagate. >>> >>> Recently a new bug has started up. No change of hardware or software >>> that I can imagine would cause this: >>> >>> The system locks up for a minute (or several). No keyboard response, >>> no mouse moves. Then comes back for a few seconds, but locks up >>> again. Rebooting fixes this temporarily. >>> >>> Event viewer has a ton of error logs. Two that alternate: >>> >>> "The device, \Device\Scsi\JRAID1, did not respond within the timeout >>> period." >>> >>> followed by: >>> "An error was detected on device \Device\Harddisk6\D during a paging >>> operation." ......... >> It sounds like something caused the machine to freeze, such that >> some disk I/O timed out without completing. So the error messages >> are a side effect of whatever happened. It is even possible, that >> in the middle of doing some I/O, that the kernel sat there >> waiting for some operation to complete, which means other >> important activities timed out in the intervening period. >> (The kernel is not supposed to do that, by the way.) >> If you're jammed up for five seconds, that might be >> enough for some disk I/O to fail and get logged. And >> the logging can only work, if it becomes unstuck again. > >I agree, something interrupting the dataflow from a drive, it seems. >I've seen bad/loose SATA cables cause similar issues, which rather >surprised me. A dry joint on a drive or mobo SATA connector possible, >too, especially if it seems temperature dependent. >OP could try swapping the SATA cables over and see if the fault moves >or changes, as a quickie. Thanks for the replies, Paul and OG. This one is tough cause it's difficult to reproduce or predict. I've got no idea what sets this off. Good point about cables. SATA cables are just a bad design. Not sure how they ended up with those connectors--very flimsy and prone to loosening.
From: RobV on 21 Dec 2008 01:39
R wrote: > On Thu, 18 Dec 2008 20:02:20 -0000, "Oldish Git" > <noone(a)nowhere.noway.con> wrote: > >> >> "Paul" <nospam(a)needed.com> wrote in message >> news:gidig2$j94$1(a)news.motzarella.org... >>> R wrote: >>>> Motherboard: P5K-E Wifi. Several drives, mostly Seagate. >>>> >>>> Recently a new bug has started up. No change of hardware or >>>> software that I can imagine would cause this: >>>> >>>> The system locks up for a minute (or several). No keyboard >>>> response, no mouse moves. Then comes back for a few seconds, but >>>> locks up again. Rebooting fixes this temporarily. >>>> >>>> Event viewer has a ton of error logs. Two that alternate: >>>> >>>> "The device, \Device\Scsi\JRAID1, did not respond within the >>>> timeout period." >>>> >>>> followed by: >>>> "An error was detected on device \Device\Harddisk6\D during a >>>> paging operation." > ........ >>> It sounds like something caused the machine to freeze, such that >>> some disk I/O timed out without completing. So the error messages >>> are a side effect of whatever happened. It is even possible, that >>> in the middle of doing some I/O, that the kernel sat there >>> waiting for some operation to complete, which means other >>> important activities timed out in the intervening period. >>> (The kernel is not supposed to do that, by the way.) >>> If you're jammed up for five seconds, that might be >>> enough for some disk I/O to fail and get logged. And >>> the logging can only work, if it becomes unstuck again. >> >> I agree, something interrupting the dataflow from a drive, it seems. >> I've seen bad/loose SATA cables cause similar issues, which rather >> surprised me. A dry joint on a drive or mobo SATA connector >> possible, too, especially if it seems temperature dependent. >> OP could try swapping the SATA cables over and see if the fault moves >> or changes, as a quickie. > > Thanks for the replies, Paul and OG. This one is tough cause it's > difficult to reproduce or predict. I've got no idea what sets this > off. > > Good point about cables. SATA cables are just a bad design. Not sure > how they ended up with those connectors--very flimsy and prone to > loosening. It's hard to believe that the early (and cheap) SATA connectors are so poorly made. There are now available many SATA cables with metal latches that lock the cable into place. They're not that expensive and a good investment. This is one of many examples: http://www.newegg.com/Product/Product.aspx?Item=N82E16812123170 ----------------- www.Newsgroup-Binaries.com - *Completion*Retention*Speed* Access your favorite newsgroups from home or on the road ----------------- |