Gragorg

Did this but port 3000 no longer loads the GUI. If I enter the API (9001 in my case) port the gui comes up. Any Ideas how to fix this?

I am currently running mealieV1. Did the repository change from hkotel to ghcr.io? Can I just change my current repository from "hkotel/mealie:omni-nightly" to "ghcr,io/mealie-recipes/mealie:nightly"? I assume I dont have to do a migration as it already is V1?

There some confusion from Crucial documentation. Sometimes it is Percentage Lifetime Remaining and some time it is Percentage Lifetime Used. Other users have reported that is usually listed as Percentage Lifetime Remaining while actually it is displaying Percentage Lifetime Used. Here is someone posting the issue it also links to more information on the Crucial site. Are your MX500 the exact same model running the same firmware version?

In addition to trurl post here is a easy step by step video if you need some additional help.

Yes its not an issue.

Add the disk to a pool. Setup primary and secondary storage on system and appdata shares. Mover action will be array to cache. Disable docker engine and run the mover. It will move your appdata and docker image to the cache drive.

Did you copy over the .ovpn, .crt, and .pem file from PIA? You can also use wireguard instead of Open VPN by changing the VPN_CLIENT in the template.

Diese Karte sollte gut funktionieren. Es handelt sich um einen unterstützten Chipsatz und eine anständige Marke.

I have a new drive coming tomorrow. I have a backup copy of the data on that disk. I was thinking that after I rebuild it I should overwrite the contents back to the drive to eliminate any corruption that may have happened. Can I mount the backup copy to UD and copy the files to directly to the disk5 after the rebuild using Dynamix file manager? Thanks

So I have a drive with read errors is this a disk or connection issue? What is the best way to resolve this? tower-diagnostics-20240501-0019.zip

Next time it happens and you are powered down cycle the power switch on the back of your power supply and then try the front power button again.

Does your unraid server use a static ip or DCHP? If you use static is possible the new router has already assigned the ip your server used if you have not reserved it. If you look in attached device on your router is the IP only assigned once?

Wireguard is built into unraid and is my go to for accessing my server from a phone or another computer. It also allows you access other machines on the same network.

Look like something is filling your docker image. If you hit the "container size" button on docker tab is there anything obvious? Also turn on the advanced view switch on the docker tab and see if you have any orphans at the bottom of the screen.

Did you login to https://www.plex.tv/ or your local ip webgui for your server?

If you login to plex.tv website can you select a movie? If so Hit the "..." and select "get info". In the bottom left corner of the window hit "View XML". Take a look in the address bar of your browser and the the token should be at the end. You can copy this for your docker template.

You should post your diagnostics. It sounds like you put the 3 drives in the array. Typically SSDs are not recommended for the array as there is no TRIM support. If this is the case I would put the 2TB in the array and use the SSD in a pool for testing.

Yes you can remove the trial key and reboot. I would make a copy of it just in case something goes south.

Is your docker image showing full on the dashboard? Also post your diagnostics.

You can do the parity swap procedure.

Currently my parity is by far my largest drive and I agree it should skip the portion after the largest data drive. However there is no way to skip. Would be a good new feature thou.

Here is the list of approved controllers. JMB585 and Asmedia are both on the approved list. Just be sure they do not use port multipliers. So a JMB585 should be a 5 port card and an Asmedia ASM 1166 is a 6 port. Both chipsets should work well.

So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal. When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec". In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history. Yesterday I went to address the drive that was resetting connection but since I had a warm spare already in my machine I just used it to rebuild. The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time. In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history. It seems to be sending the previous time. Is this a known bug?

The requirement for an array device is going to be removed in a future release. The ZFS zpool has higher performance but drives do not spin down. The array allows you mix and match hard drive sizes and expand one drive at a time when needed. It also spins down unused drives to save power but performance is limited to the performance of a single drive as data is not striped. If you lose one drive your data is covered in both cases (array and raidz). If you lose two drives the raidz pool you would lose your data while the array would only lose the two failed disks and all remaining data would be intact. You can add a second parity to the array to have a two disk fault tolerance.

Update went smoothly. Thanks for all your hard work.