August 23, 200619 yr This is odd. The last few drives that I have stuck into the system seem to just be taking forever to clear and format. Also, when copying files over from my PC to the server it is also taking much longer. I started noticing this once the HD's got down to the promise cards... how long does it take you all to clear a 300 gb hd? Things were running sooo smooth on my system and no things have really started to slow down! What gives? On the newest software as an FYI! Thank you, Mike
August 23, 200619 yr Author Here is the system log Tower login: root Linux 2.4.31. root@Tower:~# tail -f /var/log/syslog Aug 23 03:51:14 Tower kernel: md: import hdl ST3200826A 5ND274LX offset: 63 size: 195360952 Aug 23 03:51:17 Tower kernel: md: import hde HDS722525VLAT80 VN693ECFV03RAD offset: 63 size: 244198552 Aug 23 03:51:18 Tower kernel: md: import hdf ST3300631A 5NF1K71E offset: 63 size: 293036152 Aug 23 03:51:18 Tower kernel: md9: new disk Aug 23 03:51:18 Tower kernel: md: blkdev_get error: -6 Aug 23 03:51:18 Tower kernel: md: blkdev_get error: -6 Aug 23 03:51:19 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Aug 23 03:51:19 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError } Aug 23 03:51:19 Tower kernel: hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Aug 23 03:51:19 Tower kernel: hde: drive_cmd: error=0x04 { DriveStatusError } So, what do you all think??
August 23, 200619 yr Author I just got back from a really annoying day of work... guess what, drive is still clearing?!?! WTF? Nothing new in the system log as I left my telnet session open all day. Currently at 84% Any ideas? JoeL???
August 24, 200619 yr Author here is new to the system log Aug 23 16:41:20 Tower kernel: md9: new disk Aug 23 16:41:37 Tower kernel: md: blkdev_get error: -6 Aug 23 16:41:47 Tower kernel: md: blkdev_get error: -6 Aug 23 16:41:47 Tower kernel: hdk: drive_cmd: status=0x51 { DriveReady SeekCompl ete Error } Aug 23 16:41:49 Tower kernel: hdk: drive_cmd: error=0x04 { DriveStatusError } Aug 23 16:41:57 Tower kernel: hde: drive_cmd: status=0x51 { DriveReady SeekCompl ete Error } Aug 23 16:41:57 Tower kernel: hde: drive_cmd: error=0x04 { DriveStatusError } Aug 23 16:58:00 Tower smbd[1569]: [2006/08/23 16:58:00, 0] lib/util_sock.c:get_p eer_addr(1000) Aug 23 16:58:00 Tower smbd[1569]: getpeername failed. Error was Transport endp oint is not connected Aug 23 16:58:00 Tower smbd[1569]: [2006/08/23 16:58:00, 0] lib/util_sock.c:write _socket_data(430) Aug 23 16:58:01 Tower smbd[1569]: write_socket_data: write failure. Error = Co nnection reset by peer Aug 23 16:58:01 Tower smbd[1569]: [2006/08/23 16:58:01, 0] lib/util_sock.c:write _socket(455) Aug 23 16:58:01 Tower smbd[1569]: write_socket: Error writing 4 bytes to socke t 5: ERRNO = Connection reset by peer Aug 23 16:58:01 Tower smbd[1569]: [2006/08/23 16:58:01, 0] lib/util_sock.c:send_ smb(647) Aug 23 16:58:01 Tower smbd[1569]: Error writing 4 bytes to client. -1. (Connec tion reset by peer) Aug 23 17:30:01 Tower smbd[1572]: [2006/08/23 17:30:01, 0] lib/util_sock.c:get_p eer_addr(1000) Aug 23 17:30:04 Tower smbd[1572]: getpeername failed. Error was Transport endp oint is not connected Aug 23 17:30:11 Tower smbd[1572]: [2006/08/23 17:30:11, 0] lib/util_sock.c:get_p eer_addr(1000) Aug 23 17:30:11 Tower smbd[1572]: getpeername failed. Error was Transport endp oint is not connected Aug 23 17:30:11 Tower smbd[1572]: [2006/08/23 17:30:11, 0] lib/util_sock.c:write _socket_data(430) Aug 23 17:30:11 Tower smbd[1572]: write_socket_data: write failure. Error = Co nnection reset by peer Aug 23 17:30:11 Tower smbd[1572]: [2006/08/23 17:30:11, 0] lib/util_sock.c:write _socket(455) Aug 23 17:30:11 Tower smbd[1572]: write_socket: Error writing 4 bytes to socke t 22: ERRNO = Connection reset by peer Aug 23 17:30:11 Tower smbd[1572]: [2006/08/23 17:30:11, 0] lib/util_sock.c:send_ smb(647) Aug 23 17:30:11 Tower smbd[1572]: Error writing 4 bytes to client. -1. (Connec tion reset by peer) Aug 23 18:02:36 Tower smbd[1598]: [2006/08/23 18:02:34, 0] lib/util_sock.c:get_p eer_addr(1000) Aug 23 18:02:38 Tower smbd[1598]: getpeername failed. Error was Transport endp oint is not connected Aug 23 18:02:45 Tower smbd[1598]: [2006/08/23 18:02:45, 0] lib/util_sock.c:get_p eer_addr(1000) Aug 23 18:02:46 Tower smbd[1598]: getpeername failed. Error was Transport endp oint is not connected Aug 23 18:02:46 Tower smbd[1598]: [2006/08/23 18:02:46, 0] lib/util_sock.c:write _socket_data(430) Aug 23 18:02:46 Tower smbd[1598]: write_socket_data: write failure. Error = Co nnection reset by peer Aug 23 18:02:46 Tower smbd[1598]: [2006/08/23 18:02:46, 0] lib/util_sock.c:write _socket(455) Aug 23 18:02:46 Tower smbd[1598]: write_socket: Error writing 4 bytes to socke t 22: ERRNO = Connection reset by peer Aug 23 18:02:46 Tower smbd[1598]: [2006/08/23 18:02:46, 0] lib/util_sock.c:send_ smb(647)
August 24, 200619 yr Author WEll... parity check taking forever.. started it this morning before I left for work and it has been about 12 hours.... Total size: 390,711,352 KB Current position: 49,623,552 (12.7%) Estimated speed: 1,117 KB/sec Estimated finish: 5075.7 minutes Sync errors: 0 I don't have any errors, but something is just killing my system... Tom, any help???
August 25, 200619 yr teamhood, You really have a problem! My system starts out at 16 MB/sec and finishes at 32 MB/sec. You definitely either have a bad IDE controller card or one or more of your drives has a veryyyyyyyyyyyyyyy slow or defective IDE interface. Regards, TCIII
August 25, 200619 yr Author teamhood, You really have a problem! My system starts out at 16 MB/sec and finishes at 32 MB/sec. You definitely either have a bad IDE controller card or one or more of your drives has a veryyyyyyyyyyyyyyy slow or defective IDE interface. Regards, TCIII TCIII Thank you for responding. My system has been very fast until the last 2 drives I have installed. I am wondering if maybe it is IDE cables or what... I am going to try and start trouble shooting to see if I can figure it out. It seems the last 2 drive I installed were both like this!!! Thank you for your input. I have emailed Tom my problem and a link to this post... I hope he comes back and helps!!! thank you, Mike
August 26, 200619 yr Author Just to talk to myself a few more posts I figured out the problem. My icy dock is bad. I plugged both the HD's that I thought were giving me problem directly into the the promise cards.... started a parity check and it is now going at about 20 KB/sec. Sheeshh... the things that go wrong are often the easiest things to fix....
August 26, 200619 yr teamhood, Glad to hear that you solved your problem. I know that Tom feels that the Kingwin KF-101 mobile docks are not very reliable and recommends those made by others, but I have over 18 of the Kingwind docks and have not had any problems with them. Just a thought. Regards, TCIII
Archived
This topic is now archived and is closed to further replies.