hda Kernel error!!!
Hello All,
When today I checked the server logs with logwatch I found under kernel
section a very long messages about the kernel .
I am usuall checking the logs daily,but I didn;t see the kernel sction so
long before.
In that I found warning about kernel error!!
WARNING: Kernel Errors Present
hda: drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)
What is this error?
Dose this indicate error on hda?
Should I replace hda?OR it's different from all these? Please help thank you...
Quoted 11 lines · system
Hello All,
In that I found warning about kernel error!!WARNING: Kernel Errors Present
hda:drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda:drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)What is this error?
Dose this indicate error on hda?
Should I replace hda?OR it's different from all these? Please help thank you...
Mayby I'm not kernel expert yet, but IMVHO it looks like hardware (hard drive) problem.
You could do some tests on this drive using programs like badblocks or similar. I have problem like that and in this case it was hardware problem (drive had guarantee, and manufactor replaced it, so it had to be broken). So AFAIK this type of error indicates serious problem with hardware, unfortunately.
Is there in logs any other similar messages in the neighbourhood of these, you write here?
Best Regards,
Jan Meizner
[email protected]
Quoted 9 lines · Jan Meizner
Quoted 8 lines · system
Hello All,
In that I found warning about kernel error!!WARNING: Kernel Errors Present
hda:drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda:drive_cmd: status=0x51 { DriveReady SeekComplete Error }...:
1Time(s)
Quoted 7 lines
Quoted 4 lines
What is this error?
Dose this indicate error on hda?
Should I replace hda?OR it's different from all these? Please help thank you...Mayby I'm not kernel expert yet, but IMVHO it looks like hardware (hard drive) problem.
Quite the opposite. It only means that command was aborted.
This frequently happens on older devices under 2.4 and is usually harmless. [ This issue was discussed few times already. ]
Quoted 4 lines · system
hda: drive_cmd: error=0x04 { DriveStat...: 1Time(s) hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)What is this error?
You need to tell us:
- kernel version
- make and model of the hard disk
- make and model of the controller (or chipset)
If you are using kernel 2.6.6 and a Maxtor disk, then it's a known problem. Search the LKML archives and look at the post-2.6.6 changes to drivers/ide/ide-disk.c.
Signature · 1 line
Ciao, Flavio
Quote from Jan Meizner <[email protected]>:
Quoted 11 lines · system
Quoted 8 lines
Hello All,
In that I found warning about kernel error!!WARNING: Kernel Errors Present
hda:drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda:drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)
Quoted 7 lines
Quoted 4 lines
What is this error?
Dose this indicate error on hda?
Should I replace hda?OR it's different from all these? Please help thank you...Mayby I'm not kernel expert yet, but IMVHO it looks like hardware (hard drive) problem.
It means the disk received a command it didn't support. It's easy to trigger by disabling S.M.A.R.T. and then requesting S.M.A.R.T. data, for example.
Quoted 5 lines
You could do some tests on this drive using programs like badblocks or similar. I have problem like that and in this case it was hardware problem (drive had guarantee, and manufactor replaced it, so it had to be broken). So AFAIK this type of error indicates serious problem with hardware, unfortunately.
It does not necessarily indicate a serious problem. Are you sure your error messages were exactly the same?
John.
Quoted 3 lines
It does not necessarily indicate a serious problem. Are you sure your error messages were exactly the same?
while we are at it. some days ago i got this:
hdi: task_in_intr: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
hdi: task_in_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=280923064991615, high=16744319, low=8355711, sector=1130361
ide4: reset: success
maxtor 200gb disk (2x100gb partitions, both reiserfs 3.6) on highpoint hpt374. i wasn't able to access the disk anymore until reboot and lost data. also got a kernel bug message regarding to reiserfs.
end_request: I/O error, dev hdi, sector 199201724 Buffer I/O error on device hdi2, logical block 7498 lost page write due to I/O error on hdi2 journal-601, buffer write failed
------------[ cut here ]------------ kernel BUG at fs/reiserfs/prints.c:339! invalid operand: 0000 [#2] CPU: 0 EIP: 0060:[<f1134388>] Not tainted EFLAGS: 00210286
EIP is at reiserfs_panic+0x38/0x70 [reiserfs]
eax: 00000024 ebx: eeea3800 ecx: 00000001 edx: c0314cd8
esi: f127a1e8 edi: 00000000 ebp: 00000000 esp: db62fe00
ds: 007b es: 007b ss: 0068
Process umount (pid: 31023, threadinfo=db62e000 task=dc6f0660)
Stack: f114c446 f11522e0 f127a1e8 eeea3800 f113ff0e eeea3800 f114a240 00000000
00001000 00000002 00000005 00000003 00000000 d9db61dc 00000110 00000004
eeea3800 00000000 f114480d eeea3800 f127a1e8 00000001 00001000 e2e52d00
Call Trace:
[<f113ff0e>] flush_commit_list+0x2ee/0x480 [reiserfs]
[<f114480d>] do_journal_end+0x9dd/0xcb0 [reiserfs]
[<f1140d09>] do_journal_release+0x89/0x100 [reiserfs]
[<f1143048>] journal_mark_dirty+0x158/0x2e0 [reiserfs]
[<f1131b8b>] reiserfs_destroy_inode+0x1b/0x20 [reiserfs]
[<f1140d9f>] journal_release+0x1f/0x30 [reiserfs]
[<f1131a15>] reiserfs_put_super+0x25/0x150 [reiserfs]
[<c0152f15>] generic_shutdown_super+0xf5/0x110
[<c015381d>] kill_block_super+0x1d/0x50
[<c0152d58>] deactivate_super+0x48/0x80
[<c0166fef>] sys_umount+0x3f/0x90
[<c0142704>] sys_munmap+0x44/0x70
[<c0167057>] sys_oldumount+0x17/0x20
[<c0108cbb>] syscall_call+0x7/0xb
Code: 0f 0b 53 01 4c c4 14 f1 c7 04 24 60 8c 14 f1 c7 44 24 08 e0the weird thing is, S.M.A.R.T doesn't show any current problems with the disk and there's nothing in the S.M.A.R.T error log...? can't remember exactly which kernel i was running, i've tried too many lately because of this error (either 2.6.2 or some 2.6.6), currently i have 2.6.6-mm3.
thx,
JG
Quote from JG <[email protected]>:
Quoted 6 lines
--Signature=_Sat__22_May_2004_18_53_54_+0200_tMfzaYq4HdZNA_y9
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Quoted 7 lines
Quoted 2 lines
It does not necessarily indicate a serious problem. Are you sure your error messages were exactly the same?
while we are at it. some days ago i got this:
hdi:task_in_intr: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
hdi:task_in_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=280923064991615, high=16744319, low=8355711, sector=1130361
ide4: reset: success
Look at the LBAsect requested - this is far beyond the end of the disk, which explains why it returned address mark not found - the sector doesn't exist.
John.
Quoted 5 lines · Flavio Stanchina
Quoted 4 lines · system
hda: drive_cmd: error=0x04 { DriveStat...: 1Time(s) hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)
Quoted 8 lines
Quoted 1 line
What is this error?
You need to tell us:
- kernel version
- make and model of the hard disk
- make and model of the controller (or chipset)If you are using kernel 2.6.6 and a Maxtor disk, then it's a known problem. Search the LKML archives and look at the post-2.6.6 changes to
drivers/ide/ide-disk.c.
There are hundreds, if not thousands of ways to get a 0x5104 response from an IDE drive. Without more information on what was going on at the time, it's tough to say whether this is the same issue.
Only a few Maxtor drives (relatively) were affected with this most recent issue, and the original author didn't post a drive model number.
--eric
Signature · 2 lines
Eric D. Mudama [email protected]
Quoted 7 lines · John Bradford
Quote from Jan Meizner <[email protected]>:
Quoted 6 lines
Quoted 6 lines
WARNING: Kernel Errors Present
hda:drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda:drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)
[...]
Quoted 5 lines
Quoted 2 lines
So AFAIK this type of error indicates serious problem with hardware, unfortunately.
It does not necessarily indicate a serious problem. Are you sure your error messages were exactly the same?
Probably you're right. I should rather say it might be an error. I had similar error (i couldn't found log now) but it may differ a bit, and I also get some additional errors (I/O errors).
BTW maybe somebody have similar problem. Unfortunately it's not my machine so I cannot do any test other then looking at dmesg. There is kernel 2.4.26. When my friend try to use put there his hard drive (old Segate 8GB) it get during boot, or while trying to acces drive (depend on which computer he tries) 4 times CRC Error and machine complitly freeze (don't react on anything, no opps, no panic).
When I tried to use my Segate (3.2GB) i got lost interupt errors at boot time.
Both drives are ok (I've checked them).
If somebody have any idea what the problem is, I would be very grateful for advice. I could provide specyfic drive types later if it makes any sens.
Best Regards
Jan Meizner