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

hmmm. looks similar? smart2.2.txt

last one... smart8.txt

syslogs smart4.txt smart5.txt smart6.txt smart7.txt

Gotcha. I will check on the newer betas. SO I shut down the server and re checked the cabling to and from the hard drives and the SuperMicro card. Restarted and at that point was able to get the smart tests to run on those 3 drives (#6, 7, 8 attached to the SuperMicro card). I ran the smart test for those 3 without starting the array. So not sure if the smart tests ran this time due to that, due to my possibly re-seating a loose cable or just coincidence. Anyhoo, I will post the Smart reports for you to glance over if you have time. As I review them (if I am looking at numbers correctly which it is quite likely I am not) the reallocation sector #'s might be concerning? Again not sure. I go cross-eyed looking at these syslogs. Thanks again for your willingness to help. I really appreciate it. smartparity.txt smart1.txt smart2.txt smart3.txt

interesting. as for some reason I am unable to obtain a smart report nor run a smart test for my Disc 6 and Disc 7. I enter the command via putty and it just sits there forever with no reply. I am certain one of those is likely assigned to ata7. Probably via the one Supermicro AOC-SASLP-MV8 8-Port SAS SATA add-on Card i have in the server. I will need to open up the case to make certain.

Thanks for the reply. Sylogs attached. Working on the smart testing/reports now. I struggle to make sens of the syslogs so if anyone sees anything glaringly obvious please educate me. syslog-2012-05-03.txt syslogtail.txt

Hi everyone, Server has thrown a new one at me this last couple of days. In running the monthly parity check with correction the web GUI seems to hang and become inaccessible about 4 hours into the parity check run. The server is still accessible as a network drive and via putty however the web based GUI no longer responds. To be able to re-access the web GUI the only remedy so far appears to be to reboot the server via the power button. I can access the server via putty but a shutdown command (assuming I am issuing the correct one) does not shut down the server. Putty tells me the server is going down for reboot but it does not actually happen on the machine. So I assume something is hanging up somewhere. Not sure what logs I can access since I have to restart the system to get back into the web-GUI. I cannot locate on the flash drive where any new logs are being written when all of this fun happens. The interesting thing is if I restart the server and cancel the automatic parity check it performs early (before the web GUI becomes inaccessible) and uncheck the "correct parity" option the check will run through to completion (each time finding 6 sync errors). However if I try to run the parity check and correct these 6 errors this is when the system seems to hang (at lest access to the web GUI and ability to shut down the server remotely hangs). Anyone have a direction to point me toward to try to troubleshoot? Thanks so much in advance.

Thanks for the reply Joe. I was finally able to delete the log files from the flash drive directly. I also ran a checkdisk on the drive as one of the files would not delete as it came back as corrupted. The drive appears fine as of now but I am beginning to wonder if this particular drive is slowly going bad. As far as the parity checks. I believe I do stop the array before rebooting or powering down. I may be confused but I do not think the reboot and powerdown buttons in the web gui are available until the array is stopped? I made sure to stop the array this time, then power down, and then I removed the flash drive from the server (in order to delete those pesky log files). Upon reboot, I restarted the array and all appeared well. I then noticed it running a parity check again. Was this again an unexpected shutdown you think? or did it detect changes to the flash drive maybe and run a parity check?

Hi all, Well I finally have a question I could not locate the answer to among all of the great information around here. If this issue has been posted and answered and I missed it via the search I apologize in advance. Is it normal to have a log file that is very large on my boot/flash drive? I have one showing around 1.85GB. Yikes! That is a decent size .txt file I do believe. Perhaps it has been there all along (although the date of the file is last week when I added two new drives to the array). I just happened to notice that an awful lot of my 4GB flash drive is being used up. It is located in \\TOWER\flash\logs. Every other file in that folder is a more reasonable 200KB or so. I first thought well maybe after some time UNRAID deletes older log files automatically? I am unable to open the file in any program so far (notepad, wordpad, and even MS Word.) to try to see what it contains. I cannot seem to delete the file via explorer over the network. Well, I delete it and then it shows right back up it seems. I have not yet shut down the server and tried to manually delete the file from the jump drive. Is this a sign of something going wrong? Again so far I am unable to even see what is within the log for error checking. Should I attempt to delete the file directly from the jump drive after shutting down the server? What is safe to try. Or am I worried about nothing? Edit/Update: I decided to reboot the server and upon reboot it is now running an (as far as I know) unscheduled parity check. More to worry about or see what happens? Thanks for any advice you can provide.