swells

Ok. So I ran the post read portion of the preclear and it was fine. So I trusted the new 8TB disk and wanted to replace that failed 2TB disk asap. I did the swap and everything went fine. After the swap I started a nocorrect parity check and so far, at 27% complete (2.2TB or so), there are 4201 sync errors. My first thought is to let this run and then do it again and see if it is the same. If it is, do I correct it? How should I proceed at this point?

I have about 700GB left I think. So maybe 100-200GB tops on any given disk.

Yeah, honestly this drive may have been bad for a while. Who knows. It is one of the oldest in there and who knows how often it is accessed. I will preclear again and go from there. Thanks for your help!

Alright, i'll run with that then. Should I do a full preclear again or just a post read? Thats where it was when it disconnected from the controller last night. As far as I can tell, everything was ok with the preclear up to that point. With the plug in it looks like I can just do the post read and save a couple days, but I have no problem doing it all again if need be. Just not sure about leaving that bad disk there a while longer.

You can't do that and just not utilize the extra disk space? hmm, well crap.

Nothing I can't afford to lose on this server. Entirely media. I would however rather be safe than sorry, so will probably try to replace that disk before I do anything else. I do however wish to continue with my move to bigger 8TB drives. Any problems with the below plan? With the last couple steps, is there a way to expand the file system once the larger parity drive is in place or do I need to remove it and put it back in like a new disk to utilize the space? My current plan is something like: 1) Ensure 8TB disk is fine 2) Rebuild bad 2TB disk onto precleared 8TB disk. 3) Order another 8TB disk and preclear it. 4) Replace current 3TB disk with new 8TB disk. 5) Replace 8TB data disk previously used to replace failed 2TB disk with 3TB former parity disk. 6) Utilize full 8TB of original 8TB disk in array.

Ok, thanks! I guess I was just looking at the part that said passed up top. Any way for me to do this according to my original plans without purchasing another drive?

Here is a new one after a reboot and reseating cables. I didnt have time before work to do a complete rip apart and check but I can if I need to later tonight. Nothing sticks out to me in the logs. tower-diagnostics-20160225-1036.zip

I just ran an extended. It still passes. Has a current pending sector count of 1 and offline uncorrectable count of 1. Otherwise no errors.

Ok, here you go. tower-diagnostics-20160225-0847.zip

Ok, I need some help. I picked up a new 8TB Seagate drive to serve two purposes. I have a few 2TB WD20EARS drives still in play and one of them has 1 sector pending relocation. I also am getting low on space and need to expand soon. The 8TB drive will become my new parity drive to replace a 3TB drive in use currently and the 3TB parity drive will replace this 2TB WD drive so I can retire it (it has been in use for ~5 years in this server). So that is the background. The drive was finishing up a single pass of preclear on the post read phase and was about 70% complete last night. I was about to go to bed and figured I would kick off a parity check and make sure all was well before the preclear finished and I could continue on. I woke up to the preclear complete, but the 8TB disk was spun down and would not spin up. It was basically not available any longer. I checked the logs and it was full of errors. Looks like two drives had some issues, ATA12 is the 2TB WDEARS drive I would like to replace, it reconnected to the controller and is fine now from what I can tell. And ATA15 (sdn) is the 8TB Seagate and it did not and is offline. I have no idea what I should be looking at. Is there a huge problem here? Did i over stress something by running a parity check while running the preclear? If someone could please take a look at the logs you will see everything of relevance I believe. I have removed a bunch of crap that was spamming the logs, which I have also never seen before, but it was basically thousands of lines of this: Feb 24 23:47:49 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Errors.txt

Awesome. Got it working. Appreciate you doing this. Thanks a lot!

I don't see it in the list from your private repo. Am I missing something? I do have a section for Sparkly-Private.

Hey guys, Having some issues getting PlexWatch going. I converted my Plex Media Server from a plugin to docker which had some road bumps but I have it looking like its 100% good now. Then I installed the PlexWatch docker. When I load the WebUI, it has my stats from plex there, but every other tab is blank. If I go to the settings tab right when i first launch the app, I can play with settings there, but if I go to any other tab first before settings, it doesnt show anything in settings either. I initially had a message that it could not find the DB, but I had the setting in the docker settings wrong and got that fixed, no longer have that error. Any ideas what is going on now?

There is a guide on their site for installing it under any OS without a raspberry pi. That led me to believe you did not need a raspberry pi to run it. http://bernerbits.github.io/ras-pints-without-pi/

Hey guys. I have a request and I know this is a shot in the dark. I have no experience with docker and thought maybe I could ask here for something specific. One of my hobbies is home brewing. I recently stumbled upon an app (raspberry pints http://raspberrypints.com/) that i find interesting and would like to play with. Any way someone could put together a docker container for this for me?

So to resolve the issue with my empty share, I renamed the share from Media to Media2. I then Created a new Media share and copied all of the data from Media2 to Media one disk at a time. Once this was complete I was unable to delete the trouble Media2 share via the webgui so i deleted the Media2 folders from each drive. When I got to disk9 it failed to delete. This lead me to believe there was an issue with this disk. I ran reiserfsck which found one issue. I then ran the --rebuild tree as it recommended. After this, everything is good, I was able to remove the troubled share and I probably could have used it again if I wanted but didnt need to. My new issue is my new Media share is showing double the free space it should have. Should be 1.44TB and it shows 2.88TB. I get this figured out and im set. Any ideas?

The drive is fine now. Im working on the upgrade aspect now. Still have a share showing as Empty. Trying a base 5.0 install now.

Here is a pastebin link to my most recent reboot. http://pastebin.com/bhexNFsm

Got my issue with the disk resolved. Rebuilt onto spare drive and multiple parity checks show all is good. I am trying my upgrade again and having the same issue. I have tried renaming share.cfg to share.old and even removed it completely. my Media share is still empty. Anyone have any ideas at all on this?

So I have been having some issues since attempting to upgrade to 5.0.5. I was using 5.0rc11a. Since I had always done upgrades and had several packages and plugins I no longer used, I wanted to do a fresh install. So i backed up my thumb drive and wiped it. I put a fresh install of 5.0.5 on there and copied over everything from the config folder. When I booted up, everything seemed fine at first glance. I setup Plex, SABnzbd, nzbdroid, and went on my way. It wasn't until i attempted to browse my 'Media' share from my windows desktop that I discovered a problem. The share showed empty, no matter what I did. If i opened a terminal window and went to /mnt/user/Media, and did an ls, nothing was returned. Every other share was fine. In the webgui, the share was also present but empty. The strange part is that plex would play everything from the path I use with the share, so for example plex would play a movie at /mnt/user/Media/Movies/Godzilla... or whatever. So I knew the data was there, I could also see it on the physical disks. So i shut everything down and went back to my backup and copied it back and started up. Now I had a disk showing as unformatted. Hmm... ok. Stop array, shut down. Restart, now its there, but shows 3 write errors which I can see in my syslog and shows 38 pending sectors. This is one of my original drives to the server, has been in there for over 4 years and is well out of warranty. I have a spare 3TB drives sitting here and have no problem rebuilding to it. Just seems strange that this happens in the middle of this upgrade nightmare. So my questions are, do i replace the drive? Any reason this could be a case where the drive is fine? What do I need to do to upgrade to 5.0.5 without this issue with my shares happening? I attached my syslog that shows the errors reading from this disk. Thanks for any help you guys can give! Errors.txt.txt

I just upgraded to 5.0.5 from a 5.0RC11. As part of this, i wanted a fresh install since i have been upgrading and adding and removing addons for quite some time. I copied the config directory to a fresh install. One of my shares shows it is empty. In Windows, my "Media" share is empty and shows 1.77TB available. My Software share has 400GB available and is fine. I have looked at the share.cfg settings for both shares and everything looks fine. In the webGUI, it also shows empty if i click on the browse share button. Even in command line an 'ls' returns nothing for the share. The strange part is all of this content is in Plex and I can play all of it. I can browse the individual disks and all the content is there under the Media folder. Any ideas what went wrong here? EDIT: Oops, wrong forum. Can someone move this for me?

Ok, I got home from work, opened up the server and verified that the 3 drives with problems are all connected to the same card via the same breakout cable. Could use some guidance here please. Since i know my original drive is fine, i kind of trust the data on that one more than the new one. How does one go about placing that drive back into the array and going back? SAB may have grabbed a few shows last night that would be the only thing new since this started. No problem replacing those. Please someone with more experience than me help me out here. I should also note that when i stopped the array, Disk9 says not installed, disk7 says missing and disk0 also says missing.

What would I look for in the log to see if those drives with errors are the ones attached to the SASLP card? Im sure theres somewhere that the drivers are installed and all that stuff happens? Or is that not possible to determine without opening the case and checking cables and serial numbers?

Ok, i replaced the drive, did the rebuild, which ended fine and then I started a parity check. Same disk number went to disabled. I actually checked the syslog this time and it looks like there are tons of read errors on 3 disks. Im not home to confirm this, but if i had to guess, the 3 that have errors are all on my SASLP-MV8, and are the only 3 drives attacked to it, which narrows down my problem. Im attaching my syslog, can someone take a look and confirm if what I saw is correct? (this is from just after I started the parity check and when the errors begin, log was too big. If you need more I have it) Thanks syslog1.txt