LimeB

I recently replaced my UNRAID system, and for the time being I had it running on a wireless NIC — everything was working fine until I tried setting up a new Windows VM (it’s been a while since I last ran any VMs). I know having both wired and wireless enabled at the same time can cause problems, so I went ahead and disabled the wireless adapter. However, I can’t get the wired NIC to work and probably hasn’t been since setting this up. Any time I change settings for eth0, they don’t seem to save. I also notice that the NIC and my route both show a link light, but the router doesn't show it is providing IP to the NIC. I see this as it is physically connected, but logistically no. I’ve checked through the usual network settings and can’t find anything obvious causing this issue. Has anyone seen this before or know what I should check next?

It is my understanding that if the array isn't stopped, the power button doesn't stop it. Have I been wrong in that it will stop the array cleanly before it will power down?

Looks like I am resolved. Another set of removing/deleting and installing it is up and running now.

I am also seeing this, which I don't understand because in docker, the user exists. 2025-02-16 21:28:16.818 PST [100] FATAL: password authentication failed for user "postgres" 2025-02-16 21:28:16.818 PST [100] DETAIL: Role "postgres" does not exist. Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"

I am trying to get Immich set up, which I have tried a few different ways, but I keep running into 2 issues. The latest setup I tried is Spaceinvader One's walkthrough. The first issue is perhaps being caused by the second issue, but the first trying to access the UI I received: This site can’t be reached 192.168.1.30 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED The second is I am receiving this error, which I have copied and pasted unique a username/password but also used the defaults as well: [Nest] 1264 - 02/16/2025, 8:58:56 PM ERROR [ExceptionHandler] error: password authentication failed for user "postgres" at Parser.parseErrorMessage (/app/immich/server/node_modules/pg-protocol/dist/parser.js:283:98) at Parser.handlePacket (/app/immich/server/node_modules/pg-protocol/dist/parser.js:122:29) at Parser.parse (/app/immich/server/node_modules/pg-protocol/dist/parser.js:35:38) at Socket.<anonymous> (/app/immich/server/node_modules/pg-protocol/dist/index.js:11:42) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:561:12) at readableAddChunkPushByteMode (node:internal/streams/readable:512:3) at Readable.push (node:internal/streams/readable:392:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) { length: 104, severity: 'FATAL', code: '28P01', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'auth.c', line: '323', routine: 'auth_failed' } api worker exited with code 1 Starting api worker

I have had a few Windows VMs over the years which always have worked fine. I needed to wipe and reset the drive I had my VMs on so I am trying to get a new VM started from scratch. I went through the guide from Spaceinvader One, and I was able to get to the install of Windows 11 but when it got to the updating part, basically the console screen became black. Now if I tell the VM to shutdown, it will, so it seems as if Windows is running but the screen is not. If I boot it up, it looks like Windows is loading, I see the "UNRAID" logo and will see the Windows loading circle under it, but then it sits on with the "UNRAID" logo. Any ideas on what I might need to check?

Just to confirm. I can do this by just copying everything off, for mat, than copy it back over?

After my last post, system booted up and went into a bad state probably within minutes but I didn't notice for a few hours. I went ahead and ran a memtest and no errors with 9 passes. I have moved the memory into dual channel, and I am still having issues. Now what I am seeing is within minutes of the array being started, my docker containers will crash, and can't start. I am seeing my cache drive being unmountable as per my other post. I can run the command you suggested, it gets me running again. Maybe I am running into multiple issues here because I'm not seeing the initial UI problem anymore but now more just docker keeps failing because of my cache drive. Attached is a diag after the latest boot and crash. This last time I did disable docker, started the array, then enabled docker. diagnostics-20240204-0119.zip

Maybe the macvlan inadvertently got changed when I was then messing with some other settings for working on something else. I felt like it was staying stable after I initially changed to ipvlan but thinking back, it must have got changed back and I became unstable again. Now it is changed again and I'll see how it holds up, along with running a memtest.

I think I am still having related issues, or maybe it is something else. I again had hard reset the box, and after that I had an issue which I created another post about with my cache drive which it is working again. Twice though docker containers were not running, stopped I guess at some point, and wouldn't start until I rebooted. Currently this was happening, I am trying to stop the array but it is not stopping. Attached is the current diag and I have tried physically rebooting it yet. Maybe this is a separate issue from before but i'm not certain. diagnostics-20240127-2005.zip

Awesome. I am back in business! Thank you.

I had an unclean shutdown and coming back up, my cache drive is not mountable. Attached are my diags. Unmountable disk present: Cache • Samsung_SSD_970_EVO_Plus_2TB_S59CNM0RA30351D (nvme0n1) btrfs check with -n [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with no modifier [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with -L [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 While it is not critical if I have to format the drive but hate to do it. Any thoughts on what I can try to fix it? diagnostics-20240124-0800.zip

Appreciate the suggestion. Yesterday the UI died on me a few times, once while stopping docker. I made the change and so far it has been holding since yesterday. It is possible that maybe docker wasn't failing on me except that one time which I posted this 2 days ago but I was assuming it also had been.

A few times since upgrading my parity drive to a larger one, I am having issues with my server going into a bad state. I feel like this is similar to what I initially saw happening when I switched from Intel to AMD but the issues went away after I change some recommended settings but I think I recall I even changed the BIOS back to defaults. It has been fine for a few years now. It seems like if I have to hard reset the system, it will boot up, run file while parity check is happening, but then later in the day, or next, the UI becomes unresponsive. I am able to SSH in and reset the UI. And say right now, I see that my docker containers are all but 1 stopped and the stopped ones are throwing an error. VMs will throw an error if I try to start them. Attached is my diags. diagnostics-20240108-1437.zip

I ended up stumbling on this video and went with using the -L flag. After doing so, all is well again it seems. I also just realized I ran into corruption a few years ago and read through that thread as well. That one I also went through the repair with -L.