romain

This is just a thought I had this morning: It would be nice if Unraid would make a post on here or a page on the official docs with a walkthrough on how to best use the diagnostics zip folder so that we can troubleshoot ourselves a bit before posting them up on here. Or if one/some of the admins on here who are constantly looking at other people's diagnostics would make a post explaining what they look for first. I'd like to be able to diagnose my server's issues myself a little better, but the diagnostics folder has quite a bit of info in there and I'm usually not sure what to look at first or where to look next if I check out the syslog text files and don't notice anything strange. This might save some time in the long run for the mods as well. I'm sure many of us would like to be more active in our own troubleshooting than posting a zip and waiting for suggestions. I couldn't find anything like this in my searching this morning, if it already exists, someone please send me a link so I can bookmark it!

@JorgeB thank you. Do you have any ideas or suggestions on anything to try next to resolve the issue?

@JorgeB I had my VM turned off when I booted into safe mode and everything was working well, so I turned on the VM and the server immediately locked up. Here are the diagnostics from before I rebooted. unraid-diagnostics-20241023-1135.zip

@JorgeB sounds good. I guess I'll give it 3 to 7 days before checking back in unless it crashes sooner.

@JorgeB Thanks for taking a look. I rebooted into safe mode and got new diagnostics, attached here.unraid-diagnostics-20241022-0928.zip

Hi everyone, hoping someone can help diagnose this issue. I have logs attached from the last time it happened just now. This has happened 2 or 3 times in the last week or 10 days where the GUI stops loading. Any docker containers that were already running are available and I can SSH into the server to grab logs or try to "powerdown" gracefully. It's hit or miss whether or not server actually powers down gracefully or not though. I ran the diagnostics command and wound up with 2 different zip files from within 10 minutes of each other, I'm not sure what the difference is so I'm attaching both here. unraid-diagnostics-20241021-1252.zip unraid-diagnostics-20241021-1246.zip

Thanks for taking a look. I mounted the array yesterday and was able to browse through files on the array disk through the webui. I wound up starting the "Rebuilding a drive onto itself" process last night, so just hoping that works: https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself I ran the quick smart test on each drive and the tests reported back that everything is fine.

Messing with the cables didn't do anything. Any & all input is appreciated!

Hi everyone, it's been a bad day for the server. I powered down this morning to install a GPU and when I powered up the 2 NICs built into my motherboard didn't seem to be working, so I spent half the day rebooting and removing and adding hardware back and forth and changing BIOS settings. Ended up just using a PCIe NIC. After all that I get the server turned back on and the drives mounted and I have a red X next to one of my parity drives and one of my data drives. I rebooted the server one more time hoping that that might help somehow but no luck there. My diagnostics are attached, if anyone can tell me if I have a bad drive or what to try or troubleshoot further I'd appreciate it! The server is a Dell T630 so all the drives are plugged into a backplane connected to a Dell RAID card. Maybe I should power down and unplug/plug the cable and see what happens..will try that now. unraid-diagnostics-20241010-1632.zip

Thanks @JorgeB I will wait. This has been happening since late 6.11.x releases but I've also reconfigured a pool and added a pool so wasn't sure what was going on.

I tried stopping a docker container that was unresponsive this morning and was getting an error so I tried to stop the array and now it looks like it's having trouble unmounting a zfs cache pool. I ended up restarting the server manually. These lines are repeating in the log: Jan 8 12:07:12 unRAID root: rmdir: failed to remove '/mnt/user': Device or resource busy Jan 8 12:07:12 unRAID emhttpd: shcmd (6600): exit status: 1 Jan 8 12:07:12 unRAID emhttpd: shcmd (6602): rm -f /boot/config/plugins/dynamix/mover.cron Jan 8 12:07:12 unRAID emhttpd: shcmd (6603): /usr/local/sbin/update_cron Jan 8 12:07:12 unRAID emhttpd: Retry unmounting user share(s)... Jan 8 12:07:17 unRAID emhttpd: shcmd (6604): /usr/sbin/zfs unmount -a Jan 8 12:07:17 unRAID root: cannot open 'trash': pool I/O is currently suspended Jan 8 12:07:17 unRAID root: cannot open 'trash/media': pool I/O is currently suspended Jan 8 12:07:17 unRAID root: cannot unmount '/mnt/cache': pool or dataset is busy Jan 8 12:07:17 unRAID emhttpd: shcmd (6604): exit status: 1 Jan 8 12:07:17 unRAID emhttpd: shcmd (6605): umount /mnt/user Jan 8 12:07:17 unRAID root: umount: /mnt/user: target is busy. Jan 8 12:07:17 unRAID emhttpd: shcmd (6605): exit status: 32 Jan 8 12:07:17 unRAID emhttpd: shcmd (6606): rmdir /mnt/user This happens on and off, I've googled and searched the forum before for answers but am not sure what is going on. I ran diagnostics before forcing the reboot, they're attached here. Hopefully someone can point me in the right direction to fix whatever is causing this. unraid-diagnostics-20240108-1152.zip

I've been able to bulk upload photos to Immich manually through the command line by going to my Docker tab, finding the Immich container, clicking ">_ Console" and running the command: immich upload --key HFEJ38DNSDUEG --server http://192.168.1.216:2283/api --recursive directory/ This works fine, but I'd like to automate this using userscripts so that it runs automatically from time to time. I don't know much about writing scripts though - I've tried a few things but haven't gotten it to work. If I click the ">_" button at the top of my GUI for the UNRAID terminal, and run: docker exec -it immich bash I can get into the docker container, so my userscript looks like this: #!/bin/bash docker exec -it immich bash immich upload --key HFEJ38DNSDUEG --server http://192.168.1.216:2283/api --recursive directory/ When I run that though I get the error: I've also tried running: docker exec -it immich upload --key HFEJ38DNSDUEG --server http://192.168.1.216:2283/api --recursive directory/ but get an error message telling me that the upload command is not found. I'm pasting in the generic 'immich upload' command from the Immich website, the command that I'm running has my correct API key, IP address & upload source directory. Can anyone suggest a way to set up my user script so that I can run it on a schedule to grab any photos that I put into the upload source directory? Another item that I'm concerned about once I get the first part running - when I run the immich upload command through the docker console, there is a message that says something like 'you're about to upload ### photos, are you sure?' and then I have to enter y/n. Is there a way to make sure that the user script can confirm 'y' for me?

That did it, thanks!

@Djoss thanks for writing back. For some reason I was thinking that I couldn't see photos but I just checked again and you're right it works the same in the container as it does with the desktop version. I tried double clicking on some .mp4 and .mov files that it found and could not watch the videos. Is there anything extra that I might need to do to allow czkawka to show video?

I'm curious if there's a way to view photos & videos through this container?