Hi.

I am still a noob. I shut down my Unraid server end of July, because of houserenovations, and fired it up again today, and I got shot in the face by the following. I am sorry  that I really don't understand how this happened at all. Only think I can think of is that I moved the server physically from one location in the house to another. But I have not touched anything, and it seems everything is alright on the inside.

 

 

Can anybody point me in the right direction to help myself here?

PS: Both cache disks are quite new, before this happened, as I setup Unraid fall of -23.

Please post the diagnostics.
 

tower-diagnostics-20241210-1047.zipHere they are.

Type:

 

btrfs rescue zero-log /dev/nvme0n1p1

 

Then restart the array, but even if the pool mounts post new diags because there may be other issues, since btrfs is also detecting data corruption.

tower-diagnostics-20241210-1323.zipSeems like something happened in a positive way, but I can see Docker service "failed to start".

First, there's a 2TB WD with apparent cables issues spamming the log, replace cables for that disk and post new diags.

Hi @JorgeB. That 2tb disk had serious issues a while ago. I thought I had removed it from Unraid as I don't need that disk anymore. 

 

Could you really see that the issue was cables? In that case I will throw away the cables if I put in a new disk. 

 

Anyways, the disk is now removed, not the cables I expect that does not matter?

tower-diagnostics-20241210-2009.zip

13 hours ago, tormi said:

Could you really see that the issue was cables?

It could, but could also be disk, you can replace them or swap cables with a different one and retest.

 

Regarding the pool, run a correcting scrub and post the results.

Should I remove thoose cables to, or can I just leave them now that I removed the drive?

 

Scrub Result (I did not choose to correct anything)

UUID: 1fd1ba22-3954-4321-82d8-d7dac32a05c6 Scrub started: Wed Dec 11 04:59:24 2024 Status: finished Duration: 0:00:11 Total to scrub: 23.88GiB Rate: 2.17GiB/s Error summary: csum=2 Corrected: 0 Uncorrectable: 0 Unverified: 0

If they are not connected to any drive, you can leave them for now.

 

Run a correcting scrub.

Seem like something is "Uncorrectable"... I did a reboot after and took a new diag report.

 

UUID: 1fd1ba22-3954-4321-82d8-d7dac32a05c6 Scrub started: Wed Dec 11 11:21:57 2024 Status: finished Duration: 0:00:09 Total to scrub: 23.88GiB Rate: 2.65GiB/s Error summary: csum=2 Corrected: 0 Uncorrectable: 2 Unverified: 0

tower-diagnostics.zip

Look in the syslog for the corrupt files list after the scrub and delete them/restore from a backup, then another scrub to confirm no more errors.

Checked the syslog. No referece to corrupt files but this is repeating:

Dec 12 04:44:29 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:31 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:31 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:33 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:35 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:36 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:37 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:39 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:41 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:41 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:43 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:45 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:46 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:47 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:49 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:51 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:51 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:53 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:55 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:56 Tower upsmon[2640]: Poll UPS [[email protected]] failed - Data stale
Dec 12 04:44:57 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:59 Tower usbhid-ups[2632]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec 12 04:44:59 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update

Considering removing the Network UPS tool for UNRAID, but don't know if that would fix anything. (I am scared of doing changes.)

You can just disable the UPS service and retest.

Hmm, I restarted the server again, now the NUT Tool is working, and the errors are gone. I send you the syslog again in PM. Still no dockers start though.

 

 

There are plugins that need an update, but I don't know if it is safe to install plugins before dockers is up and running:

Just now, tormi said:

There are plugins that need an update, but I don't know if it is safe to install plugins before dockers is up and running:

Plugins are independent of docker containers so I would recommend updating them.

I did update them, but it says "not available". Still at least I can see the NUT plugin is working...

This is my Docker settings:

 

 

Latest diagtower-diagnostics-20241212-2007.zip

Try recreating the docker image:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

I will certainly try this.

Just one question before I continue. In the docker settings this is what it looks like now, I put no on "enable docker".

Notice the vDisk location.

 

I find the docker file at 22,5GB in disk2/system/docker which is a array disk. Is the directory location the same in the settings? When I choose the path manually I get to /mnt/disk2/system/docker/docker.img

Just wondering if the path somehow has got distorted? Should I try to point it directly to that path myself?

 

If so can you verify that the appdata storage folder is correct?

 

Also I notice the Docker vDisk size is set to 20GB while mine is actually 21,5... Could this be an issue?

Edited December 13, 20241 yr by tormi

34 minutes ago, tormi said:

find the docker file at 22,5GB in disk2/system/docker which is a array disk. Is the directory location the same in the settings? When I choose the path manually I get to /mnt/disk2/system/docker/docker.img

Since that location is part of the /mnt/user location then nothing wrong with that.   Ideally, however, you want all of the 'system' share on the 'cache' pool for best performance, but running Mover with the Docker and VM services disabled should achieve that.   After that is done you could set the 'system' array to be cache only.

 

36 minutes ago, tormi said:

Also I notice the Docker vDisk size is set to 20GB while mine is actually 21,5... Could this be an issue

Likely the difference between displaying the size in decimal and binary units.

So all I do is click the "move" button at the "Main" tab, then I set the "System" array to cache only. After this I rebuild the docker container if needed? 

Do I need to make any path alterations in any other places?

This is the settings for the "system" data btw:

 

Should I not include a secondary storage?

Edited December 13, 20241 yr by tormi

6 minutes ago, tormi said:

So all I do is click the "move" button at the "Main" tab, then I set the "System" array to cache only. After this I rebuild the docker container if needed? 

Do I need to make any path alterations in any other places?

Yes.

 

Paths should be fine.

So i have gone forward with the process. A bunch of the dockers/apps have been installed from "previous apps", but it seems it is stuck at my "TandoorReciepes" app. It has been "pulling fs layer" for at least 1 hour now on this app... 

 

Just leave or do something else?