magnumpraw

Few hours in and data rebuild seems good so far. Will report back with final results, but thanks in advance for the extremely quick response and help!

My bad, I meant rebuild Data. I tried rebuilding data with old Disk 5, but got the error that the disk was too small (since new disk 5 was larger) I have put new Disk 5 back in and started Data rebuild. Hopefully that does the trick.

Ok, so I shutdown, re-seated the cables, replaced the original Disk 5, and booted the server back up. It does appear that both Disk 4 and 5 are functioning. Is putting back old Disk 5 OK? If so, Should I do a parity rebuild or a new config with old Disk 5 in? If not, do I put new Disk 5 back in and do a parity rebuild? mediaserver-diagnostics-20200801-1419.zip

ok, will do. My disks are all in a front slide-out Icy-Dock backplane, so I never open the case when replacing disks. But I will open it up, re-seat the cables, and boot up again

I had shutdown my Unraid while we were gone for vacation and upon rebooting, Drive 5 was labelled as missing. I purchased a new drive, replaced drive 5 and started a parity rebuild. Almost immediately, drive 4 started having read errors and eventually dropped off. What are my options at this point and what are suggestions to proceed? Thanks! mediaserver-diagnostics-20200801-1102.zip

that did the trick. Thank you!!!

sorry about that. Here is a new diag file after accessing the plugins tab a couple times and trying to install a couple plugins. mediaserver-diagnostics-20190611-1639.zip

I have come across an issue where all my plugins show status 'unknown' and will not update. I can browse new plugins, but they will not install. After combing the forum I have taken these steps with no change in result. -in network, ensured the gateway was set to my router's address -in network, ensured the DNS entries were 8.8.8.8 and 8.8.4.4 -I have telneted in and successfully pinged 8.8.8.8 and google.com -have restarted my server and router multiple times. Any other ideas to try? mediaserver-diagnostics-20190610-2222.zip

I'm not sure. I only have 2 users set up and both have R/W. I've never (to my knowledge) changed those permissions from when they were first set up. Kinda stumped on this one especially since I've had no trouble with the 9 other drives.

I have been slowly converting my 13 disk array from reiserfs to xfs. I have 4 disks left, but have run into an issue with unBalance. When I run the "Plan" stage to move files from any of the 4 remaining reiserfs disks to an xfs disk, unBalance warns me that I have permissions error with folders (anywhere from 4 to 22 depending on the disk). I have tried running Docker Safe New Permissions several times, but it does not fix the issue. I have also tried just going ahead and hitting the "move" button in unBalance. When I do, it goes to the transfer page and I see the list of folders like normal, but the process finishes in seconds with yellow checks next to each folder in the list and when I look at the contents of the destination drive, nothing was actually transfered. Any ideas on what's going on and how to fix it? Thanks!!!! mediaserver-diagnostics-20190214-0123.zip

I ended up putting back the original disk 6 (2TB disk) and did a New Configuration. Everything is back properly. Thanks for the advice.

Here's what's happened so far. I bought a couple WD Red 4TB disks on a black Friday deal to preemptively replace a couple of the aging 2TB disks I have in my array. -Wed. I did a parity check on my system which came up with 0 errors. -I replaced disk 1 (2TB disk) with one of the new 4TB disks that had been successfully precleared -after unRaid rebuilt the disk, the array was fine. -I ran another parity check that night and the next day disk 6 showed several hundred thousand errors. -Since I had another 4TB disk, I decided just to replace disk 6 and rebuild again. -Today after the rebuild finished, disk 7 now shows 128 errors, and my main shares are all EMPTY. If I view the contents of each disk individually I can see my files, but the main shares (ie: Movies) show 0 folders and 0 files In addition, now "Fix Common Problems" shows disk 1 and disk 6 (the 2 new 4TB disks) have a warning: "Unable to write to disk 1" "suggested fix: Drive mounted read-only or completely full" Man! what did I screw up. My unRaid has been working flawlessly for a long time now and all of a sudden everything is exploding. Any insight on how I can right this would be appreciated. Thanks!!! My diagnostics: mediaserver-diagnostics-20181130-2257.zip

OK, so...here's what's happened over the last several days and I my undying appreciation ahead of time if anyone can help me out of this mess. I confess ahead of time, I am not super knowledgable and likely caused some problems. -On Thurs. I ordered a new parity disk as Johnnie.black suggeted. -to get disk7 going again I stopped the array, selected "none" for disk7, started the array, stopped it again, selected disk7 (now with a blue square icon), started the array and let it data-rebuild -the process completed on Sat morning. I received my new disk later that day and went to shut down the server, but now disk 10 was red-X'd. -I repeated the same process for disk10 as the above mentioned disk7 -The rebuild was only moving at a few kB/s and saying it would take months to rebuild. I decided to give it a day, but when I looked yesterday, disk10 then showed green, but now disk9 is showing red. -I tried the same process again for disk9 just wanting to get the array to a green status so I can replace the parity drive. -The interface was unresponsive yesterday however, and the array would not stop, shutdown or reboot. -I tried a hard power down (with the power button on my machine) and a reboot. -Now the array gets to disk7, but won't mount anything past that. Knowing I probably screwed things up, what would be the next suggestion for action? Thanks! mediaserver-diagnostics-20180319-1054.zip

OK, thank you. I will do that.

I received a Call Traces error which instructed me to post my diags here and ask for help. Any insight would be appreciated. Thanks in advance. mediaserver-diagnostics-20180315-1136.zip

of course, sorry. Here is the Diagnostics. mediaserver-diagnostics-20160730-1251.zip

I'm using Unraid 6.2-rc2 and the Preclear Disks Beta plugin version 2016.06.23. When I run a clear using the plugin, it starts for a 4 or 5 seconds and then ends and says "Preclear finished successfully" but obviously it hasn't. Here's what the plugin window looks like. There are some suspicious lines towards the bottom. Any ideas what's going on? ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdc # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-Read in progress ... # # # # # # # # # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 0:00:01 | Total elapsed time: 0:00:02 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 12038 - # # 194-Temperature_Celsius 35 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ###########################################################################################################################? /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh: line 597: 21233664 + dd: : syntax error in expression (error token is ": ") --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh: line 1302: /boot/preclear_reports/preclear_report_WD-WMAY01461783_2016 .07.29-02:00:58.txt: Invalid argument root@MediaServer:/usr/local/emhttp#

After placing the plexmediaserver.64bit.plg file in /boot/config/plugins, When I do a installplg /boot/config/plugins//plexmediaserver.64bit.plg I get a ------------------------------ Warning: simplexml_load_file(): I/O warning : failed to load external entity "boot/config/plugins/plexmediaserver.64bit.plg" in /usr/local/emhttp/plugins/plgMan/plugin on line 125 plugin : warning : no name attribute, installing anyway Warning: simplexml_load_file(): I/O warning : failed to load external entity "boot/config/plugins/plexmediaserver.64bit.plg" in /usr/local/emhttp/plugins/plgMan/plugin on line 125 plugin:xml parse error ------------------------------- any ideas on what i'm doing wrong? Thanks!!

will do. I'll let you know thanks

Sorry it's been a while since getting back. The rebuild appeared to go normally. md10 still showed up as unformatted so I just reformatted md10 and rebuilt it. Interestingly enough md3 then appeared as unformatted. Though I ran a reiserfsck --check on it which told me to to run a --rebuild-tree which I did and it seemed to be ok. There was nothing in the lost+found directory. The array appears to be normal on the interface and on boot up. I can browse files, but as soon as I try to write to it, windows explorer stops responding and I can no longer access the server. I'm not sure if this is a new problem or a continued result of what I had done before. I'm so confused, lol. I've attached a new syslog. Thanks! 2011-5-12.txt

Thanks for the incredibly snappy responses guys! I tried your suggestion, lionel, and moved disk 10 to a different slot. The rebuild on disk 6 looks very normal now and is completing at a rate consistent with what I've experienced in the past (4hrs roughly). The web interface is responding normally as well. Disk 10 is no longer listing any errors during the rebuild process. Everything would be completely normal if only disk 10 didn't still say Unformatted. I guess I will let the disk 6 rebuild finish and see where we are in the morning.

Sry, I adjusted my post for better wording. The array wasn't rebuilding the parity, it was rebuilding the the files on the new disk. But yeah, I think I am in trouble with 2 disks not functioning. The old disk I was replacing had gone bad so it's of no use unfortunately. I will be getting a UPS.

So I may have really messed something up. My array has been running great for months now and yesterday I upgraded one of my disks (md6): Shut down the system, put the new disk in, checked format and then it started to rebuild. Everything was going well till the power went out. When it came back on, I rebooted the system. Here's where the problems began. I saw the option to format again and pressed it without thinking assuming it was just repeating the same process as before the power outage. I went to bed and when I got up in the morning, the rebuild had only progressed 1%. This was an obvious red flag and then I realized that on the main page, disk /md10 (a disk which has been in the array for months) was showing that it was unformatted although it's light was green and the page said the array was valid. I did some forum searching and found people had had success simply restarting the system. I did so (though the main web interface page was taking a looong time to respond now). When the system rebooted, it started automatically into the parity rebuild, but /md10 was still showing unformatted (but green) and was logging up thousands of errors. Did something happen to /md10 during the power failure to mess it up? When I pressed the format button after the power outage, it very well could have been md10, not md6 that was showing unformatted. Can I save my data? Because now I have a new disk (md6) that hasn't been rebuilt and a disk with problems (md10). After more forum searching, I ran -reiserfsck --check on md10 and got a bad block error: bread: Cannot read the block (22): (Input/output error) In any other case, I would just replace the disk, but I can't because of course I have the other new disk in the system. Any thoughts? Thanks in advance!!!! Here's my syslog https://files.me.com/apatrickrose/x1br5j