Lime Technology - unRAID Server Community
September 07, 2010, 04:03:11 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: What does this error mean: hdk: drive_cmd: error=0x04  (Read 2101 times)
teamhood
Sr. Member
****
Posts: 340


View Profile Email
« 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


View Profile WWW Email
« 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


View Profile Email
« 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!!!!  Roll Eyes
Logged
erwin.zeez
Newbie
*
Posts: 1


View Profile Email
« Reply #3 on: March 26, 2010, 10:35:33 PM »

GOOD ONE DUDE.
LIKE  Grin
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!