dbrowne

Colour me thick. Thanks for highlighting that. Doing what it says only works if I take in what is said after the big bold bit that says NOTE. Feeling a bit sheepish. Nonetheless, thanks all for your patience and forbearance. Resolved.

Odd, it doesn’t show as ticked as an included disk in any of my shares. Parity checks out as valid; wouldn’t a missing disk corrupt the parity data? Anyhow, I am where I am; is the suggested course of action that I should add a disk 7, create a new array that now includes the disk, tick it to be included in the desired shares and then rebuild parity?

Thx for the quick responses. @ New Zealand No. I could add an extra disk to the array; I do have two precleareds sitting in reserve. Though I am wondering why it is being asked for, as didn't I create it to include a seventh disk. @itimpi Please see included attachment. tower-diagnostics-20200610-1138.zip

Unraid 6.8.3 This pops up in alerts. "Fix Common Problems - Tower: 08-06-2020 12:43 Errors have been found with your server (Tower). Investigate at Settings / User Utilities / Fix Common Problems" So I do so, and... "Share Media has disk7 set in its included disk settingsdisk7 is not defined / installed in the array. This will cause errors when writing to the array. Fix it here: NOTE: Because of how the UI works, disk7 will not appear in on this page. You will need to make a change (any change), then revert the change and hit apply to fix this issue" This is not the case; Share Media only includes disks 1 to 6. I recently rebuilt my array with newer, fewer, larger capacity drives, as my old one was littered with lots of smaller ones that were getting on a bit. None of my shares include a disk 7 and parity checks out fine. Need I be concerned, and if so, what should I do about it (short of adding a disk 7 to the array - which I suppose I could do)? Thanks for any advice.

Thanks for that. It worked a charm.

Without wanting to go into the details of a really boring sob story, I have finally reached the fourth stage of grief and accepted that the data on my disk twelve is irrecoverably corrupted, so time to move on. Even with the drive removed, replaced, location swapped, rebuilt and the array run in emulation, and all permutation thereof, the files are visible, but read/write is impossible. New permissions change nothing, and those files are undeletable. What I would like to do is just yank the drive, lose the files on that disk, and rebuild the array, while also not affecting the files on the other disks. How might I go about this?

That was it. I was on 6.6.7. All better now. Thanks.

I do. When I type "fix" in the search box all that shows up is "malfurious roundcube postfixadmin". Fix common problems pulls up a blank. And when I type in Andrew Zawadzki, who I believe is its author, 12 other plugins list, but not that one.

Can't find the fix common problems plugin shown in Spaceinvader One's video. Is it still available?

Thanks. Time to go shopping.

So, I can reboot and and select any of the options on the launch page, but all the unraids types result in the same above screen. At that point it becomes unresponsive to keyboard entries and I have to reboot. For lack of other options, I decided to do the memtest, and at present I see the following. Is this likely to be the culprit? If so, odd that it chose to manifest just as I invoked the Move function. Is it really likely to be just a case of swapping out the memory?

Yes, the following. It is however unresponsive to keyboard entries.

I just upgraded my parity drive from a 12 to 16TB one. I intended to repurpose the 12 TB drive to replace a smaller one in the build. But before doing that, and invoking another 6 day parity rebuild, I had 3.8 TB sitting in the cache that I decided to move onto the raid array first. I pressed the move button and lost the gui, neither can I telnet in. I can see that the indicator light on my cache drive is a solid hard working blue, while the rest of my drives are running as dimmer, but constantly flickering, blue as well, leading me to believe that they are likely all being written to. I am loathe to do a hard reboot for fear of losing or corrupting the data, but how long is it unreasonable to leave this running in the hope that the data transfer reaches some sort of conclusion before deciding to do so? It has so far been five days. Unraid 6.something; as I'm locked out, so I can't check which version. 72TB on 16 drives + cache and parity. Parity rebuild speeds vary from 20MB/s to 60MB/s. Any advice, however uninformed, is gratefully appreciated.

First answer did the trick. Thanks.

The Wiki https://wiki.unraid.net/UnRAID_6/Upgrade_Instructions tells me that in order to upgrade to the latest version I must first upgrade my 6.1.6 version to 6.2 by installing the following plug-in https://raw.githubusercontent.com/limetech/unRAIDServer-6.2/master/unRAIDServer.plg. This achieves nothing, and when I try to look at the link's location, it's 404: not found. Can anyone please advise on what I should be doing that I'm missing. Many thanks.