When you can, could you confirm what my next steps need to be?

On 1/18/2024 at 1:20 PM, trurl said:

Since emulated disk6 is mountable, it should be safe to format disk5. On the array operation page, it will show you which disks it thinks need formatting. You can format if disk5 is the only one listed.

 

And you can rebuild only parity2, or rebuild parity2 and also rebuild disk6 to a spare disk at the same time.

 

Original disk6 B5SX can be read as an Unassigned Device to help recover some of that lost+found.

 

You could rebuild disk6 to that original disk B5SX if you are sure you don't need to recover any files from it.

 

Format disk5

https://docs.unraid.net/unraid-os/manual/storage-management/#creating-a-file-system-format

 

Rebuild to replacement

https://docs.unraid.net/unraid-os/manual/storage-management/#normal-replacement

 

Rebuild to same disk

https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

 

Do you want to do both parity2 and disk6 at the same time?

On 3/4/2024 at 12:19 PM, trurl said:

Do you want to do both parity2 and disk6 at the same time?

 

I'll do it whichever way you think is safest and gets me back into having some parity protection.

 

Breaking down and clarifying the steps:

 

#1 - Format Disk 5

I understand this as being WFL5W6LK

I can see this disk listed under Array Operations as you suggested I would. 

I simply tick the box that says Yes, I want to do this and proceed with the format.

Then complete step #5 from "Rebuild to replacement" guide, namely "Assign the replacement disk(s) using the Unraid webGui."

 

I note this guide states:

Quote

It is worth emphasizing that Unraid must be able to reliably read every bit of parity PLUS every bit of ALL other disks in order to reliably rebuild a missing or disabled disk. This is one reason why you want to fix any disk-related issues with your Unraid server as soon as possible.

 

I don't think any of my disks are emulated any more, but I know one certainly was for a time. Am I ok to proceed with the above steps at this point in time?

All unmountable disks will be listed for formatting. If disk5 is the only disk listed for formatting then you can format it. You don't want to format if other disks are in the list. There is no need to rebuild disk5 since it isn't disabled or missing (or emulated).

 

Disk6 is of course emulated. Last diagnostics said emulated disk6 was mountable. So it should be OK to rebuild.

 

If you start the array with parity2 unassigned, then it will rebuild it when you start the array with it assigned. In this case, you would assign the same parity2 disk.

 

If you start the array with disk6 unassigned, then it will rebuild it when you start the array with it assigned. In this case, you would assign the replacement disk.

 

You can do both at the same time.

 

Stop the array. Unassign parity2 and disk6. Start the array with both parity2 and disk6 unassigned. Stop the array. Assign the same parity2 and the replacement disk6. Start the array to begin rebuilding both.

 

Hi @trurl,

 

Ok, I've formatted Disk 5 and it's back in the array.

 

Then, I stopped the array to unassign Parity 2 and Disk 6.

I then started the array and let the rebuild commence. However, it's just paused itself.

 

Diagnostics attached.

lucindraid-diagnostics-20240308-0759.zip

Looks like connection problems with both rebuilding disks. All of your array disks are on this controller, correct?

03:00.0 RAID bus controller [0104]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
	Subsystem: Fujitsu Technology Solutions HBA Ctrl SAS 6G 0/1 [D2607] [1734:1177]
	Kernel driver in use: mpt3sas
	Kernel modules: mpt3sas

How are these 2 disks powered? Any splitters?

Quote

All of your array disks are on this controller, correct?

 

Correct

 

 

Quote

How are these 2 disks powered? Any splitters?

 

That I can't remember. I'll have to check. I have been wondering whether a larger PSU / a PSU with more built-in cables would be necessary. Until I can get the cabling checked, am I right in thinking I'm still running with at least one parity drive? 

23 hours ago, siege801 said:

am I right in thinking I'm still running with at least one parity drive?

No. The one parity drive is emulating disk6, so can't emulate another.

Alright, that looks much better. I pulled out the existing PSU, and upgraded to a unit with enough SATA points to not need splitters. It's also a more powerful PSU. So, whether it was an underpower issue, or a splitter issue, I may never know. But for now it looks good.

 

Looking at the diagnostics attached, what other cleanup is required?

lucindraid-diagnostics-20240317-1749.zip

Looks good!

On 1/18/2024 at 12:44 AM, trurl said:

Unrelated, your appdata has files on the array. Just wanted to make a note so we can come back to this after your system is stable.

 

Thanks @trurl

 

Can you advise if this needs to be addressed?

Looks like mover must have taken care of that for you.

Ok, great to know.

 

Next step for me (likely outside the scope of this thread) is to identify the cause of the FixCommonProblems alert about /mnt. This had been spamming my unRAID emails and meant I missed the more critical errors pertaining to the disks/array.

 

@trurl, I can thank you enough. I've sent a small token via your donate link. It's minuscule in comparison, but hopefully it can in some way support you in being the helping soldier to others. Thank you thank you. I'll scan back through this thread and try and find out which of your posts should be marked as the Solution. Any thoughts on which would be most appropriate?

On 3/8/2024 at 8:54 AM, trurl said:

Looks like connection problems with both rebuilding disks. All of your array disks are on this controller, correct?

03:00.0 RAID bus controller [0104]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
	Subsystem: Fujitsu Technology Solutions HBA Ctrl SAS 6G 0/1 [D2607] [1734:1177]
	Kernel driver in use: mpt3sas
	Kernel modules: mpt3sas

How are these 2 disks powered? Any splitters?

I'm thinking this post as Solution.

6 hours ago, siege801 said:

I've sent a small token via your donate link

Thanks

 

Mar 17 04:40:02 LucindRAID root: Fix Common Problems: Warning: Share FETCHSHARE set to not use the cache, but files / folders exist on the cache drive

To fix this one, you either need to move the files for that share off of cache yourself, or let Mover do it for you by setting the share to use cache.

Primary: cache; Secondary: array; Mover action: cache->array.

 

Mar 17 04:40:02 LucindRAID root: Fix Common Problems: Warning: Docker Application MariaDB-Piwigo has an update available for it
Mar 17 04:40:02 LucindRAID root: Fix Common Problems: Warning: Docker Application OpenVPN-jackett-42805 has an update available for it
Mar 17 04:40:02 LucindRAID root: Fix Common Problems: Warning: Docker Application OpenVPN-sonarr-42802 has an update available for it

These are self-explanatory.

 

Mar 17 04:40:04 LucindRAID root: Fix Common Problems: Error: Invalid folder share contained within /mnt ** Ignored

I don't see /mnt/share, but you shouldn't ignore it. Maybe it has been fixed. Set it to not ignored in FCP and rescan. If it still finds it post the results of this command:

ls -lah /mnt

The usual cause would be a docker host path set to /mnt/share

 

Mar 17 04:40:07 LucindRAID root: Fix Common Problems: Warning: Missing DNS entry for host

I think this must be because you only have one DNS specified. I always set all three. For one, your gateway is probably also a DNS. Others are google and OpenDNS. I use the google DNS because they are easy to remember, 8.8.8.8 and 8.8.4.4