December 29, 201312 yr Hi guys, Running 5 RC 14. Trying to preclear a 3TB internal Toshiba drive. My first hard drive to be added to the array larger than 2TB. Was looking to switch out the old 2TB parity drive with this 3TB one. Seems to hang up during the post read process repeatedly. In full disclosure I am streaming from the unraid box while this disk is preclearing. Not sure if that is a no no or if it should be ok. If that is not the issue is it a bad communication between the hard drive and the mobo or is the hard drive bad possibly. Here is the error message i am receiving from the sys log repeatedly (sys log shows this error over and over so I didnt post the entire log)... Dec 29 09:15:16 Tower kernel: end_request: I/O error, dev sdh, sector 5860530232 (Errors) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code (Errors) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 (System) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 98 38 00 00 00 08 00 00 (Drive related) Dec 29 09:15:16 Tower kernel: end_request: I/O error, dev sdh, sector 5860530232 (Errors) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code (Errors) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 (System) Dec 29 09:15:16 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 98 38 00 00 00 08 00 00 (Drive related) Dec 29 09:15:16 Tower kernel: end_request: I/O error, dev sdh, sector 5860530232 (Errors) Thanks for any ideas you guys may have
December 29, 201312 yr Author Was trying to run preclear on a different 3TB toshiba hard drive (bought two of them and apparently I am a glutton for punishment) and during pre-read the speed has slowed to a crawl (2.6 MB/s). Seeing this error so far in the syslog... Dec 29 14:42:49 Tower kernel: [<c1307570>] ? start_secondary+0xad/0xaf (Errors)
December 29, 201312 yr Author Syslog attached. Thank you for looking! I also just noticed the below in Main View of unmenu on the hard drive I am attempting to clear... /dev/sdi TOSHIBA_DT01ACA300_X3T7LU0KS /dev/sdi1 TOSHIBA_DT01ACA300_X3T7LU0KS Not sure why the single hard drive is appearing as two partitions maybe (sdi and sdi1) or if that is an issue. Thanks again syslog-2013-12-29.zip
December 29, 201312 yr Syslog attached. Thank you for looking! I also just noticed the below in Main View of unmenu on the hard drive I am attempting to clear... /dev/sdi TOSHIBA_DT01ACA300_X3T7LU0KS /dev/sdi1 TOSHIBA_DT01ACA300_X3T7LU0KS Not sure why the single hard drive is appearing as two partitions maybe (sdi and sdi1) or if that is an issue. Thanks again /dev/sdi is the device name for the entire RAW drive. /dev/sdi1 (with trailing "1") is the name of the first partition on the disk. This is entirely normal and expected on a disk that has been partitioned. If there was a second partition you'd see /dev/sdi2. Just a reminder, the /dev/sdX drive letter is assigned upon bootup and will change frequently depending on which drive spins up first upon booting. Make sure when performing disk operations you use the model number/serial number to verify you have the correct disk name. You can type ls -l /dev/disk/by-id to see all the disk model/serial number and their affiliated /dev/sdX device names. You will see all unRAID disks have a first partition (with the trailing "1" on their name) Normally, you will never use the /dev/sdX or /dev/sdX1 names... instead you'll use the /dev/mdX names of the unRAID device names.
December 30, 201312 yr Author Thanks guys. I have upgraded to 5.0.4 and will again give pre-clearing the drive a shot overnight and see how things look in the am. To be continued... Thanks again
Archived
This topic is now archived and is closed to further replies.