dilligaf

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

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

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)

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

Hi guys, I posted this in another thread and realized it may not get much attention there as that issue had been "solved" so I am starting a new topic. Hope this is OK. Anyone have any ideas why it appears PMS is running however all of a sudden the webgui always shows "Stopped". Previously it would show "Started" in green as it should and was clickable to access the PMS interface. I have stopped and started the array, rebooted, uninstalled and reinstalled, upgraded to latest PMS version, downgraded back to the version that previously worked, etc and have had no luck getting the status to show as started. I assume PMS is actually running as I can access it at htp://unraidIP:32400/manage. Not sure if there are other issues causing this but it appears coincidentally (or maybe not) that all of a sudden rebooting the server takes much much longer than it ever did before. And waiting for Unmenu and SimpleFeatures to load up and show the correct WebGUI is considerably slower than ever before. I also have noticed an orange light next to my "Applications" share (which is cache only and is the location of my PMS library and temp directories) that may or may not have always been there. Log file below if anyone has the time to review... http://pastebin.com/cuffEkkH Thanks for any help or advice you all may have...

Hi guys, Anyone have any ideas why it appears PMS is running however all of a sudden the webgui always shows "Stopped". Previously it would show "Started" in green as it should and was clickable to access the PMS interface. I have stopped and started the array, rebooted, uninstalled and reinstalled, upgraded to latest PMS version, downgraded back to the version that previously worked, etc and have had no luck getting the status to show as started. I assume PMS is actually running as I can access it at htp://unraidIP:32400/manage. Not sure if there are other issues causing this but it appears coincidentally (or maybe not) that all of a sudden rebooting the server takes much much longer than it ever did before. And waiting for Unmenu and SimpleFeatures to load up and show the correct WebGUI is considerably slower than ever before. I also have noticed an orange light next to my "Applications" share (which is cache only and is the location of my PMS library and temp directories) that may or may not have always been there. Log file below if anyone has the time to review... http://pastebin.com/cuffEkkH Thanks for any help or advice you all may have...

And there was what I missed. I missed enabling it on a couple of shares. So files were not moving to cache but just straight to the shares. Thanks guys for slapping some common sense into me. I figured I had to be missing something silly.

OK guys. I think I am missing the forest for the trees here... Finally added my cache drive (2TB like all of the other drives in my unraid server). So say I normally move a video/TV file from my desktop (over network connection) to a "TV" folder share on unraid (all through Windows 7 network interface). Now that the cache drive is present do I just move the file to the cache drive (not a share) and the mover script will take care of it later (currently at the default 3:40 am setting)? If on my "TV" share on the server the TV files are each in a separate folder for each TV show title. How will the mover script know where to move this particular file? Apologies if I am missing something simple. Or perhaps the mover script does not actually separate files and categorize for me (which is understandable) Thanks in advance for any help or direction.

Just to update for historical purposed i guess... Switching to 5.0 Beta 14 solved the issue apparently. I have run through to completion two parity checks so far (first one to correct the 6 errors found and then a second one that returned 0 errors (predictably and thankfully). I have yet to try the latest RC2 but will at some point in the next few days and hopefully have similar results. Thanks again to mbryanr for all of your help,

Well using a different cable as well as a different port on the SuperMicro card was not the solution. Thanks for the link. i will keep my eyes open for a possible non test RC2 to try. Latest sys log attached. syslogtail2.txt

both ata 6, 7, and 8 are via a single breakout cable from the supermicro card. perhaps that one cable to that specific hard drive is bad. I will move things around and see if I can take that cable out of the equation.

well. it looks like we got about 2 hours from the parity check.correct completing and again lost web gui access and inability to shut server down remotely. Latest syslog attached. To my untrained eye... is ata7/8 an issue in some way again? Thanks syslogtail.txt

thanks. upgrade completed. now running a parity check. fingers crossed. thanks again for your help!

true. i will give it a try. upgrading from a beta to RC2 still the same process (backup current flash and then copying and replacing bzimage and bzroot). just want to make sure im not missing anything

gotcha. unless you recommend otherwise... i think ill look into upgrading to beta 14 and see if that is helpful. thanks again