taros14

Thanks Squid. They aren't Docker Apps, they were all installed using the PhaZe plugins. I don't have a backup, but am going to look in that Appdata thing you mentioned for future. I'm thinking at this point I have to start over. This of course is after i hit my friend over the head repeatedly ....

So an odd thing happened the other day. A friend was playing around looking at the WebUI to see if he liked unraid for himself and he ran the New Permissions Tool "by accident". Now I am running into problems all over unraid. Plex won't play anything, SABnzbd has no permission to run python scripts, etc. Does anyone have any suggestions on how to restore the permissions for the entire server and its contents? I'm hesitant to just run a chmod 777 on everything for fear it might mess everything up more. I appreciate the suggestions! EDIT: Running unraid 6.3.3 x64

I truly appreciate all the help and advice you have given me Rob, not just in this post, but in prior posts! I did upgrade to 6.2.0-beta23 before I replied to your comment so that is why some of the log shows 6.1.9 and other parts show the new version (I didn't fully start everything because of the errors generated) I figured out that my "side drive" that I use to hold SickBeard, SAB, and Plex was failing so I have replaced that with a new SSD (just having trouble getting that working now ) I did a lookup for my BIOS and I have the latest version, it is just an old motherboard so the BIOS is going to be outdated I tried to change the emulated IDE made to AHCI, but it said I would lose all the data so I did not do that change as I can't afford to lose the data now The bonding mode is an oversight on my part and I will change that on my next reboot. To sum up, my drive I refer to as Xfiles that is not part of the array or cache seems to be failing and I have replaced it with a 480GB SSD. My problems aren't over yet though as now I'm having issues getting everything working with the new drive as when I mount the drive to /mnt/Xfiles it is only showing 7GB available, so I have to figure out why. Again, I appreciate all the help and advice you have provided to me!

My apologies RobJ. I have attached the ZIP file now. Thanks for the heads-up, I'll remember that for the future. tower-diagnostics-20160622-2202.zip

So recently I was looking at the log files for my unraid as Plex started to run very slowly and transcoding was having a hard time. I noticed that the log file kept repeating this sequence over and over: Jun 21 22:26:09 Tower kernel: mptbase: ioc0: LogInfo(0x31120200): Originator={PL}, Code={Abort}, SubCode(0x0200) cb_idx mptbase_reply Jun 21 22:26:08 Tower kernel: mptbase: ioc0: LogInfo(0x31120200): Originator={PL}, Code={Abort}, SubCode(0x0200) cb_idx mptscsih_io_done I am really not sure what the above means and any help would be greatly appreciated so I can get to the bottom of why my server is starting to run sluggish. Thank you community! EDIT: Running Unraid 6.1.9 syslog.txt

I noticed 4 items, but cannot say if any of them are directly related. I can confirm what you have said, preclear of sdg is apparently successful, but is not identified as cleared. I suspect the problem with the Parity drive is 'confusing' UnRAID. * BIOS is a little old, from 2010. Syslog shows a number of ACPI workarounds, a little more than normal. If you can find a newer BIOS for that board, it *might* help. * You have IDE emulation turned on for 2 of your SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. Performance to Disk 3 and your Cache drive should be slightly faster, and a little safer. * You have stations all over the web attempting to connect to your machine, so I have to assume you have it set in the router's DMZ (sic?). Most failed, but some telnet attempts appeared successful, both local and from outside your net. A serious sniffing attempt was made from 42.116.99.53, using various user names and ports. I'm not an expert here, but this sounds incredibly dangerous! * Parity drive (sdh) is not configured correctly. It is a 4tb drive but is configured for 2.1tb, as if >2tb support was not available when drive was prepared. Usable space on it is 1.99tb, usable space on the true 2tb drives is 1.81tb. On array start (each time), the system appears to recognize that something is wrong, and rewrites the GPT entries to the Parity drive, reports unknown partition on it, but does NOT proceed to build parity, apparently accepts it as correct! When you added the new drive as Disk 9, the GPT entries were again written to sdh (the Parity drive), then an MBR written to sdg (new Disk 9). It's possible the GPT writing to sdh caused an execution path that bypassed the already precleared test for sdg. Perhaps the discovery of unknown partition on sdh set a flag that affected the testing of sdg. You might email Tom and link this post. Rob, first most, thank you so much for all the information you have provided! I had no clue that the server was enabled through DMZ, so firstly I disabled that (stupid roommates). I will see if there is a BIOS update and get that updated. I will also do everything else you mentioned and report back, though it'll take some time to get all that completed (especially redoing the parity). Thank you so much for taking the time to read through my syslog!

I am uploading a new syslog and preclear results. If someone believes I should move this question back to a general thread of it's own let me know. Just trying to solve thislong problem so I can add more space Thanks in advance! Archive.zip

Sounds like you may have a third party add-on installed that is interfering with setting up the new disk. Try booting in safe mode and try the operation again. Good idea. I tried this last night and into today. I renamed my /boot/extra and /boot/config/pulgins folder (don't have a /boot/plugin folder) to something else and did a reboot. I then had unRaid go through the clearing of the disk. When it completed, it said "Found new erased disk" and asked if I wanted to start array. So I did, but then it asked that the disk be cleared again. So back to where I started, but appreciate the suggestion.

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array. I did not see in your syslog any evidence of you actually adding the disk to the array. Did you press the button to actually add the disk, or just stop because it says it will clear the disk? Joe L. I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive. Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6 SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do? It is pretty obvious... Does the disk still test as "precleared" when you invoke: preclear_disk.sh -t /dev/sdX (where X = your drive letter) If that test says it is pre-cleared, it is... and you can add the disk to your array and let unRAID do as it wants, regardless of what the screen seems to say. If I'm right, it will skip the step of writing zeros to the entire drive and add it to your array. If I'm wrong, it will write zeros to the drive and then add it to your array. Either way, it ends up added to your array. Joe L. The problem is the array never lets me add it. Here are the steps I have done IN ORDER: Ran Preclear_disk.sh Verified disk has been precleared Stop Array Add drive as Disk 9 Go to start array with newly added disk unRaid says it needs to clear Let clear run unRaid then says it needs to clear it again Let clear run unRaid then says it needs to clear it again It's an endless loop and it never allows me to start the array with the newly added disk.

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array. I did not see in your syslog any evidence of you actually adding the disk to the array. Did you press the button to actually add the disk, or just stop because it says it will clear the disk? Joe L. I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive. Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6 SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do?

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array. I did not see in your syslog any evidence of you actually adding the disk to the array. Did you press the button to actually add the disk, or just stop because it says it will clear the disk? Joe L. I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive.

Anyone have any idea for my issue yet of not being able to add a successfully precleared HDD to the array? Been happening on any new HDD I try to add. Preclear is successful, but the array says it needs to be cleared still when I try to add it. Attached is my syslog after preclearing a disk again. Thanks! syslog.txt.zip

Attached is my syslog after preclearing again. Your help is appreciated! syslog.txt.zip

I will try that Rob. Though won't be until new year as away for the holidays. I'll post back the results when I have them. Thanks!

Can you attach a zip file of all the preclear reports? I'm afraid I won't have time until evening, but someone else may. Hi Rob! Thanks for getting back to me. Attached are the pre_clear reports. Some are older. The drive I was trying to clear is /dev/sde Thanks again! preclear_reports.zip