Ok update: I borrowed a SATA USB caddy from my neighbor and took out disk6 and plugged it into my computer.

Windows explorer does not display the drive (probably because it's xfs), but it is displayed in Windows Disk Management Tool as 'healthy partition'.

I don't understand. I've replaced the power cable and SATA cable for that drive in my Unraid box.
How come it suddenly won't detect it?

What do I do now? :(

Edited May 24, 20251 yr by Corvus

Hard Disk Sentinel reports zero errors under a random seek test.

S.M.A.R.T. reports no errors.

Short self test successful.


Furthermore, an app called 'Linux reader' seems to be able to browse the directory structure just fine on Windows (albeit with a minute or so of loading from the drive, not sure if normal).

When plugging it back into my Unraid box, I thought to check 'system devices', and it looks like it appears there. Is this good news?

I have no idea where to go from here. I'd really appreciate any help!

Edited May 24, 20251 yr by Corvus

So I've been reading other threads, and I ran xfs_repair -v /dev/sdd

This is what it spits out:

Apparently this means the filesystem is corrupted.

Is this fixable? If so, how?

Update:

I stopped the array, then I removed the disk from the array, started the array again, and then it appeared in my unassigned devices (with an option to mount). I then stopped the array again and assigned the same disk back to the array, however there's a message saying 'All existing data on this device will be OVERWRITTEN when array is Started'. If the data is erased, will it be restored via parity? I just want to make sure because I don't want to permanently lose the data on the disk.

To be clear, I haven't changed or written any files to the disk manually when I attached it to the SATA caddy.

Am I safe to continue?

Edited May 24, 20251 yr by Corvus

18 hours ago, Corvus said:

xfs_repair -v /dev/sdd

This command is not correct, but first, unassign disk6 and post new diags after array start.

Before you replied, I had already started the array with the drive re-added.
Here are the diags.

I managed to recover my docker.img. I also have my appdata folder. How do I restore my docker containers with all of their previous settings once the rebuild is finished?
Your thoughts/advice are greatly appreciated.

nas-diagnostics-20250525-2232.zip

Edited May 25, 20251 yr by Corvus

Anyone?

18 hours ago, Corvus said:

How do I restore my docker containers with all of their previous settings once the rebuild is finished?

This is normally done via Apps->Previous Apps.

That assumes that your appdata share has been restored to its original location (if required).

1 minute ago, itimpi said:

This is normally done via Apps->Previous Apps.

That assumes that your appdata share has been restored to its original location (if required).

Ok, I've copied across my appdata backup to cache/appdata.
So all I have to do is reinstall the apps themselves from the app store?

Does having access to my previous docker.img do me any favors here or make the process any faster?

Just now, Corvus said:

So all I have to do is reinstall the apps themselves from the app store?

Yes - but by the Previous Apps section so that settings are retained.

7 minutes ago, itimpi said:

Yes - but by the Previous Apps section so that settings are retained.

I have over 20+ dockers.

Does having my previous docker.img file make this process any easier/faster?

Edited May 26, 20251 yr by Corvus

Just now, Corvus said:

I have over 20+ dockers.

Does having my previous docker.img file make this process any easier/faster?

No.

However you can simply tick off all the dockers you want reinstalled from the Previous Apps section and then let the system install all the selected ones in one operation.

18 minutes ago, itimpi said:

No.

However you can simply tick off all the dockers you want reinstalled from the Previous Apps section and then let the system install all the selected ones in one operation.

Ok so I recreated my docker in docker settings. I pointed the appdata to mnt/cache/appdata, and the docker.img to /mnt/cache/system/docker/docker.img

After it ran, I expected to see a blank 'docker' tab, but NO. ALL MY DOCKERS ARE THERE ALREADY!

I'm pleasantly surprised, although I don't know how this could've happened.

However, when I try to access the web UI for any of them, I notice that it doesn't resolve.
I never had any custom networks set for any of them. What could be preventing this from working?

EDIT: One thing that's weird is that some of these dockers have unusual IP address on them that I would have never assigned to them. My server has the local IP 192.168.x.x, and all of my dockers previously used that address prefix. However some of them have 172.17.x.x.
All the ports seem correct though.

Any ideas?

Edited May 26, 20251 yr by Corvus

UPDATE:
I went back into docker settings, deleted the docker img, then reenabled docker. As expected this time, no dockers appear.
Went into app store, ticked all the previous dockers I want to install, and let it run.

But again, same problem. I cannot get the WebUI to show for any of them. I've made zero network changes to my LAN/router, and for some reason, the weird LAN IP shows for most of the dockers container IP. However, if I try to access the docker UI from within Unraid by clicking on the icon and selecting 'WebUI', my browser all of a sudden wants to go to the correct IP address - still no UI shows though.

What am I doing wrong?

Edited May 26, 20251 yr by Corvus

Guys, can someone help me? I really don't want my Plex users to wait another 24 hours until this problem is fixed. First one to successfully help me restore Plex functionality within 2 hours gets a round of beers delivered by me to their Paypal account. I'm dead serious.

Edited May 26, 20251 yr by Corvus