May 16, 201016 yr Just trying to add a new drive to my array. The drive is a 2TB EARS WD drive. It's the 5th drive in my system that also includes a cache drive. I've been banging my head against a wall all weekend trying to get this thing going. I saw a mention of setting jumpers 7-8 on an EARS drive, and when I did that, it did seem to initialize longer, but it still crapped out. When I initially tried to start the array with the new drive, nothing happened, and I found that jumpers 7&8 should be set on an EARS drive, so I did that. It seemed to make it a bit further, but same result, it eventually craps out. When I start the array, it goes for a while, and then eventually it says I can't access the server. And when I look at the syslog, the most current area looks like this: May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351414967 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351414999 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351415025 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351415069 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351415106 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351415159 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351413015 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 May 16 00:55:35 fileserver kernel: end_request: I/O error, dev sdc, sector 351413111 May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Unhandled error code May 16 00:55:35 fileserver kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 I've added drives before and never had a problem. This is really turning me off of unRAID. Hopefully it's USER error.
May 16, 201016 yr Some of the EARS drives had buggy firmware and didn't work well with the jumper. People who RMA-ed such drives reported that the replacement drives worked well.
Archived
This topic is now archived and is closed to further replies.