September 07, 2010, 04:03:11 AM
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Home
Help
Search
Login
Register
Lime Technology - unRAID Server Community
>
Support
>
unRAID Server 3.0
>
What does this error mean: hdk: drive_cmd: error=0x04
Pages: [
1
]
« previous
next »
Print
Author
Topic: What does this error mean: hdk: drive_cmd: error=0x04 (Read 2101 times)
teamhood
Sr. Member
Posts: 340
What does this error mean: hdk: drive_cmd: error=0x04
«
on:
May 22, 2007, 03:20:36 PM »
Running parity and its crawling....
May 22 17:28:23 Tower kernel: md(9,8):can't shrink filesystem on-line
May 22 17:28:26 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:26 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:26 Tower emhttp[1051]: smart ioctl: Input/output error
May 22 17:28:26 Tower kernel: hdl: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:26 Tower kernel: hdl: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:26 Tower emhttp[1052]: smart ioctl: Input/output error
May 22 17:28:26 Tower kernel: hdf: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:26 Tower kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:26 Tower emhttp[1056]: smart ioctl: Input/output error
May 22 17:28:50 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:50 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:50 Tower emhttp[1078]: smart ioctl: Input/output error
May 22 17:28:50 Tower kernel: hdl: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:50 Tower kernel: hdl: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:50 Tower emhttp[1079]: smart ioctl: Input/output error
May 22 17:28:50 Tower kernel: hdf: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:50 Tower kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:50 Tower emhttp[1083]: smart ioctl: Input/output error
May 22 17:28:53 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:53 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:53 Tower emhttp[1090]: smart ioctl: Input/output error
May 22 17:28:53 Tower kernel: hdl: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:53 Tower kernel: hdl: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:53 Tower emhttp[1091]: smart ioctl: Input/output error
May 22 17:28:54 Tower kernel: hdf: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:28:54 Tower kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:28:54 Tower emhttp[1095]: smart ioctl: Input/output error
May 22 17:29:03 Tower kernel: reiserfs: replayed 63 transactions in 201 seconds
May 22 17:29:04 Tower kernel: md(9,10):Using r5 hash to sort names
May 22 17:29:04 Tower kernel: md(9,10):Removing [14063 14069 0x0 SD]..done
May 22 17:29:04 Tower kernel: md(9,10):There were 1 uncompleted unlinks/truncate
s. Completed
May 22 17:29:04 Tower emhttp[1014]: remount: /dev/md10
May 22 17:29:04 Tower kernel: md(9,10):can't shrink filesystem on-line
May 22 17:29:05 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:29:05 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:29:05 Tower emhttp[1102]: smart ioctl: Input/output error
May 22 17:29:05 Tower kernel: hdl: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:29:05 Tower kernel: hdl: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:29:05 Tower emhttp[1103]: smart ioctl: Input/output error
May 22 17:29:05 Tower kernel: hdf: drive_cmd: status=0x51 { DriveReady SeekCompl
ete Error }
May 22 17:29:05 Tower kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
May 22 17:29:05 Tower emhttp[1107]: smart ioctl: Input/output error
May 22 17:29:05 Tower emhttp[982]: shcmd (9): killall -w smbd nmbd
May 22 17:29:05 Tower nmbd[978]: [2007/05/22 17:29:05, 0] nmbd/nmbd.c:terminate(
Logged
limetech
Administrator
Hero Member
Posts: 2066
Re: What does this error mean: hdk: drive_cmd: error=0x04
«
Reply #1 on:
May 23, 2007, 12:31:02 PM »
Looks like a PCI controller might have died, or perhaps loose cable, or perhaps power issue. Please attach the entire syslog.
Logged
teamhood
Sr. Member
Posts: 340
Re: What does this error mean: hdk: drive_cmd: error=0x04
«
Reply #2 on:
May 24, 2007, 07:43:24 AM »
Well.. I powered down the server and unplugged and replugged all cables, cards, and power cords... seems to be back to normal... interesting!!!!
Logged
erwin.zeez
Newbie
Posts: 1
Re: What does this error mean: hdk: drive_cmd: error=0x04
«
Reply #3 on:
March 26, 2010, 10:35:33 PM »
GOOD ONE DUDE.
LIKE
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General
-----------------------------
=> Announcements
=> Applications
=> Good Deals!
=> Forum Feedback
=> Lounge
===> Newsflash Discussion
===> Weekly Polls
-----------------------------
unRAID Server 5.0-beta Support
-----------------------------
=> webGui Design
=> Security Model
=> Plugin Design
=> Other
-----------------------------
Support
-----------------------------
=> unRAID Server 4.5
=> Active Directory issues
=> unRAID Server 4.4
=> unRAID Server 4.3
=> unRAID Server 4.2
=> unRAID Server 4.0/4.1
=> unRAID Server 3.0
=> Motherboards
=> Hardware
=> Software
=> Feature Requests
=> User Customizations
-----------------------------
Bilge
-----------------------------
=> webGui
Loading...