UNRAID 6.10.0-rc2 Failed Disk and Docker Apps Disappeared

[trurl]

I assume neither have been tested. Only need one for now to rebuild disk2. I guess rebuild will be a good test of the disk and its connections. Plug it in and post new diagnostics just so we can see its SMART report before proceeding.

[evans.family.mike]

See attached

unraid-smart-20220927-1718.zip

unraid-diagnostics-20220927-1727.zip

Edited September 27, 2022 by evans.family.mike
Added new diagnostics report

[trurl]

Diagnostics already includes SMART for all attached disks so no need to attach it separately.

 

SMART for new disk looks fine. I guess we can let rebuild test the disk and its connections.

 

Follow these instructions carefully. If things don't seem to work as described, or you have questions, let us know. We will check some things along the way to see how well things are working.

1. Go to Tools - Diagnostics, Retain All, Apply
2. Reassign disk1, assign new disk as disk2
3. Check BOTH parity valid box AND maintenance mode box

Then start the array and post new diagnostics and a screenshot of Array Devices

 

Those steps will get disk1 back into the array, a new disk in disk2 slot, all other disks as is, and without actually mounting anything so parity and all disks are unchanged.

 

The next steps (after we get diagnostics and screenshot) will disable disk2 so it can be rebuilt on the new disk.

[ChatNoir]

3 hours ago, trurl said:

• Go to Tools - Diagnostics, Retain All, Apply
• Reassign disk1, assign new disk as disk2
• Check BOTH parity valid box AND maintenance mode box

I guess you mean Tools / New Config ?

[evans.family.mike]

Those were some stressful steps :-D  See the attached diagnostics

unraid-diagnostics-20220928-0929.zip

[JorgeB]

Now unassign disk2, start the array in normal mode and post new diags.

[evans.family.mike]

See attached

unraid-diagnostics-20220928-1007.zip

[JorgeB]

Stop the array, click on disk2 and change the filesystem from "auto" to "xfs", then check filesystem on the emulated disk2.

[evans.family.mike]

I stopped the array and clicked on Disk 2 to change the filesystem to xfs and clicked Done.  But I don't get an option to check the filesystem, I assume since there isn't a disk assigned?  And the File system type doesn't stay as xfs and reverts back to auto

Edited September 28, 2022 by evans.family.mike
added additional info

[JorgeB]

It should stick, but do this instead:

 

-start array in maintenance mode:

-in the console type

xfs_repair -v /dev/md2

If and only if it asks for -L type

xfs_repair -vL /dev/md2

When done start the array in normal mode and post new diags.

[evans.family.mike]

Is this what you meant by "If and only if it asks for -L"?

[JorgeB]

Yep.

[evans.family.mike]

See attached

unraid-diagnostics-20220928-1131.zip

[evans.family.mike]

I just realized the last diagnostic report was done with the array still in Maintenance Mode.  Attached is a new report with the array started normally

unraid-diagnostics-20220928-1438.zip

[JorgeB]

Emulated disk is mounting now, check that contents look correct, also look for a lost+found folder and any lost files inside. 

[evans.family.mike]

It looks like everything is there and I'm not seeing any lost+found folders in any of the shares

[JorgeB]

Then you can rebuild, just stop the array, re-assign the disk and start the array to begin.

 

[evans.family.mike]

Started

Total size:12 TB

Elapsed time:less than a minute

Current position:6.05 GB (0.1 %)

Estimated speed:159.3 MB/sec

Estimated finish:20 hours, 55 minutes

 

Should I wait until this completes to re-enable Docker?

[JorgeB]

You can do it now, though if containers will be doing a lot of reading or writing to the array it will affect rebuild time.

[evans.family.mike]

Fair enough, I'll leave it disabled until this is finished.  From what you guys have seen in the diagnostics does Disk 1 look like it is ok or should I proceed with my initial plan of replacing it as well?

[JorgeB]

Disk1 look OK for now, though it should be kept cooler.

[evans.family.mike]

Parity Sync just completed with no errors.  This looks very promising.  I was able to start docker and my apps were there.  I guess I need to understand how I make them utilize the SSD or NVMe disk pools I have.  I thought I had them configured to utilize them correctly but I guess I was wrong.  Regarding upgrading UNRAID itself from an RC release to a normal release, is there a particular procedure I need to follow?

unraid-diagnostics-20220930-1121.zip

[JorgeB]

32 minutes ago, evans.family.mike said:

Regarding upgrading UNRAID itself from an RC release to a normal release, is there a particular procedure I need to follow?

Just go to Tools -> update OS select "stable" branch and then "check for updates"

[evans.family.mike]

I think I am all good now.  Thank you so much @JorgeB @trurl and @ChatNoir for all of your help and guidance in getting my array back in working order.  I truly appreciate every bit of it.  

[trurl]

7 hours ago, evans.family.mike said:

I was able to start docker and my apps were there.  I guess I need to understand how I make them utilize the SSD or NVMe disk pools I have.  I thought I had them configured to utilize them correctly but I guess I was wrong.

On 9/24/2022 at 12:14 PM, trurl said:

You don't seem to have a pool named cache, but some of your user shares are configured to use that pool. In particular, appdata, domains, system are configured to prefer a pool named cache, and since it doesn't exist, all those shares have been created on the array

You need to go to the settings for each of those shares and designate a pool that exists. Then

 

 Nothing can move open files. You have to disable Docker and VM Manager in Settings then run Mover to get these moved to their designated pools.