trurl

Stop array Unassign disabled disk Start array with disabled disk unassigned Stop array Reassign disabled disk Start array to begin rebuild

Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

I have 2 UPS. The larger one has the USB connection to my Unraid server, but it powers both my Unraid and my desktop. Unraid monitors the UPS status over USB using apcupsd built-in to Unraid. The desktop monitors the UPS status using apcupsd I installed on it, but over the network to the instance of apcupsd on Unraid. They both shutdown after a short period on battery since I don't want to run the battery down. The smaller UPS has all my network on it. The network must stay up one way or another or my desktop can't get the status of the UPS it is on. And I can still use the internet for a while with wifi on laptops and mobile devices even if the power is off.

Another way to get a full-featured, multi-purpose, multi-user Linux with Unraid is to create a VM.

Those few CRC on disk7 are not a concern. It is part of the array currently and will have to stay for the rebuild. 1 pending on disk5 not ideal but we'll just have to live with for now. Do you want to rebuild to the same disk?

Of course this means your array is offline until done and you start normal so many would not want to do it that way. Interesting that I have never seen this done or recommended.

I should have said all disks in the array are needed to rebuild so you are good on that. Looks like a CRC. Usually a connection issue but since it is just the one I would just acknowledge it by clicking on that warning on the Dashboard and it will not warn you again unless it increases.

And might also tell us if you have other issues that might cause problems when you rebuild. Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. The Diagnostics would have given us that SMART you posted and a lot more.

OK, I guess that makes sense. Since the disks aren't mounted nothing can be written to the array, and parity stays the same while the disk rebuilds. At least that is how it seems to me it should work. I just don't know for sure it does work that way. Maybe @johnnie.black will comment on this thread tomorrow and tell us. He seems to have tested everything. Anyway, even if you did allow writes and parity updates during rebuild, you could always put the original disk back and rebuild parity.

system share is all on cache now. You should get rid of it then. Your cache isn't very large and could use the space.

Which disks are these?

And you still have the original disk (I assume) in case something doesn't work out for some reason, so all the files are still on that original disk.

I've never done that or seen anyone else do it when they are trying to rebuild a disk. It might work if you pressed the Sync button (at least according to the description), but I would be more familiar with what is happening if you started it in normal mode. And I don't know why you would want to do it in Maintenance mode anyway. I don't see how that would be any safer than doing it the normal way. Just start it in normal mode and post another screenshot.

Many plugins may not be compatible with your old version. But your plugins are old too. Diagnostics for that old version doesn't have some of the useful information provided by later versions. There have been a number of fixes since that old version also. Possibly your old version even has a broken version of the XFS repair which might bite you if you have to repair the filesystem on a disk.

Assign the disk and start the array. Then post a screenshot of Main - Array Operation.

I meant do ANY of your disks have SMART warnings. ALL disks are needed to rebuild the disabled disk.

No Stop array Unassign disabled disk Start array with disabled disk unassigned Stop array Reassign disabled disk Start array to begin rebuild

I have merged your threads. Please don't crosspost.

Sorry everyone I somehow managed to merge this thread with a completely different thread by accident. I corrected the title (sort of) but the end result is any links to the thread are now broken, including the plugin support link. EDIT OK, I think I now know what happened at least. While I was trying to merge 2 threads (crossposted) from a new user, he apparently deleted one of the threads to be merged, with the result that a different thread (this one) got merged instead. The user only had those 2 posts, and one other, which is in this thread 2 posts up.

Step 2 is not really needed if you are replacing the disk. Assigning a different disk to the same slot should be enough to get it to let you rebuild. Why are you running such an old version? WDC WD80EFAX-68KNBN0 shows up but is not assigned. Is this the disk you intended to rebuild to?

SMART for disk20 looks OK. Maybe a bad connection so you might check that. Syslog resets when you reboot so nothing in the diagnostics that might tell us what happened. You have a lot of small disks, many still ReiserFS. Have you considered upsizing disks to get same capacity with fewer disks? Larger disks perform better and fewer disks are fewer opportunities for problems. You have so many disks that I didn't look at SMART for any of the others. Do you have SMART warnings on the Dashboard for any disks? Do you have a spare to rebuild to? Or you can rebuild to the same disk if you are confident in the rest of your array. Do you know how to rebuild?

No, but there may be nothing wrong with disk20 and you might be able to rebuild to the same disk. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Disk13 looks OK. It seems to have been disabled a couple of days ago when writes to it failed. Maybe just a bad connection so you should check that. It will have to be rebuilt to get it enabled again since it is now out of sync. You can either rebuild to the same disk or to another. If you rebuild to another then you can keep the original as a backup in case there is any problem rebuilding, but it is probably safe to rebuild to the same disk if all of your other disks are OK. Do any have SMART warnings on the Dashboard?

This should have worked assuming you haven't left anything out of your description. You didn't New Config at any point did you? If you remove the original disk it will be emulated, and if you replace it with another disk and start the array, it will still be emulated while it rebuilds. If instead you put the same disk back in, and you never started the array with that original disk unassigned or any other disk assigned to the slot, then it would just take the disk as is since it is the same disk and it was never disabled. I am just trying to suggest possible scenarios to see if it will help you remember anything you left out. The syslog in the diagnostics only goes back to the last reboot, and since you rebooted after whatever you already did, there is nothing in the syslog about that. Was it disk3 you were trying to replace? The last inventory in that syslog has nothing assigned to that slot.