Grimbone
Members
-
Joined
-
Last visited
-
Issue Description: The Unraid webGUI footer displays: "Unraid® webGui ©2025 , Lime Technology , Inc."As of the current date (January 05, 2026), this copyright year appears to be outdated. It should likely be updated to ©2026 to reflect the current year. This is visible on every page of the webGUI in the footer. Steps to reproduce: Log in to the Unraid webGUI. Navigate to any page (e.g., Main tab). Observe the footer text showing ©2025. Expected Behavior: The copyright year should automatically update to the current year (2026). Additional Notes: This appears to be a minor cosmetic issue only—no functional impact observed. The system time, uptime, and appear correct elsewhere in the GUI. Attached screenshot for reference shows the footer clearly. Thanks for looking into this!
-
I am looking for a way to stream a mp4 video from Unraid directly to a YouTube channel. I have a pre-recorded video that is stored on the Unraid server that I want to stream to Youtube and loop for 24hrs a day. Does Unraid have a docker application w/ gui interface that can achieve this? Thanks!
-
Finally figured it out. Updated the motherboard bios firmware and now drive is showing. 👍
-
Checked the cables, twice. Drive is not showing in the bios.
-
Running Unraid 6.12.13 Just purchased an 8tb Seagate Ironwolf drive and it is not being recognized. I want to use the drive for my Parity This is the drive that was purchased. https://www.amazon.com/dp/B084ZV4DXB?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 Any suggestions? nas-pc-diagnostics-20241102-1337.zip
-
Seems a reboot solved the errors. I checked the logs and the errors are gone. I also checked the Cache Dirs plugin and the shares are no longer on the list. I also think the original issue I opened this thread was caused by plugging in a sata power cable into my PSU that was by a different manufacture and it fried the drives. Thanks everyone for the help. You guys and gals are awesome! 🙏
-
I checked the 3.3v issue using a different solution by putting a piece of label tape over the third pin since I didn't have an adapter. None of the drives worked so I am pretty sure the drives are dead. I am salvaging what is left in unraid. I removed the old 2 cache drives, moved the data to the array, and and replaced them with a single 1 tb drive and moved the data back over to cache. Everything looks good in the logs except for the following errors. Nov 1 05:38:25 NAS-PC cache_dirs: ERROR: included directory 'bitcoin' does not exist. Nov 1 05:38:25 NAS-PC cache_dirs: ERROR: included directory 'domains' does not exist. Nov 1 05:38:25 NAS-PC cache_dirs: ERROR: included directory 'unRaidLars' does not exist. Nov 1 05:38:25 NAS-PC cache_dirs: ERROR: included directory 'urBackup' does not exist. Anyway to resolve these errors? nas-pc-diagnostics-20241101-0633.zip
-
Hello, Thanks for the speedy reply! Ok, so I tested the three hard drives one at a time by putting them back in the old pc they were taken from and booting into the bios to see if the old machine still recognizes them. The bios did not recognize any of the three drives and I don't think they were spinning. (not 100% sure) Just to make sure I went and tested a brand new drive that i have and the bios did see the brand new drive. For some reason the 3 problem drives aren't even recognized in the old PC now.
-
Hello! Running newest version of unraid. I had unraid running on an old ASUS M5A97 R2.0 motherboard with an AMD FX 8350 with 8gb ram. 2 SSD cache drives 250gb each 1 parity drive 8tb 5 drives 2tb, 2tb, 2tb, 4tb and 8tb I also had an old ASUS M5A97 LE R2.0 with an ASUS FX 8350 with 16gb ram hooked up to a tv as a regular windows pc and just recently replace it. As you can see the motherboards (tho 1 is LE version) and processors are basically the same except one had 8gb ram and the other had 16 gb ram. I decided to swap out the ASUS M5A97 R2.0 motherboard with 8gb ram for the ASUS M5A97 LE R2.0 with 16gb ram. I know i could have just swapped the ram but I tried and it would still only see 8gb so I decided to just swap the motherboards so the server could have 16gb ram. Now for the problem. I completed the swap and when I booted into bios and also unraid it will only show 5 of the 8 drives. 8tb parity missing 8tb regular drive missing 2tb regular drive missing I did some troubleshooting and swapped both power cable and data cable (all drives are sata) from a drive that was working and showing in both bios and unraid to a drive that wasn't showing and the drive still will not show up. I did this to all 3 drives that were not showing and they still will not show up. Its seems odd that removing the drives and then popping them in the new system immediately would cause 3 drives to die. I do not know why these 3 drives will not show when hooked up to the cables that will show the working drives. I am now concerned because one of them is the parity drive. I am planning to hook up the drives that were not showing up to my gaming pc (Asus tuf x570 plus - AMD 5900x – 32gb ram). The plan is to hook them up to my gaming pc and see if the bios will see the drives so at least i know the drives are still good. I know the motherboard is 12 yrs old and I have no issues with buying a new motherboard, processor and ram if that what needs to be done. I am just concerned about losing the drives and data. Anyone know why this may have happened? Any other ideas? Any other way to test these drives? Thanks!
-
Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358077, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) Sep 13 20:03:42 NAS-PC smbd[5414]: PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358117, 0] ../../lib/util/fault.c:173(smb_panic_log) Sep 13 20:03:42 NAS-PC smbd[5414]: =============================================================== Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358133, 0] ../../lib/util/fault.c:174(smb_panic_log) Sep 13 20:03:42 NAS-PC smbd[5414]: INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 5414 (4.17.12) Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358145, 0] ../../lib/util/fault.c:178(smb_panic_log) Sep 13 20:03:42 NAS-PC smbd[5414]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358159, 0] ../../lib/util/fault.c:183(smb_panic_log) Sep 13 20:03:42 NAS-PC smbd[5414]: =============================================================== Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.358170, 0] ../../lib/util/fault.c:184(smb_panic_log) Sep 13 20:03:42 NAS-PC smbd[5414]: PANIC (pid 5414): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.12 Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.368299, 0] ../../lib/util/fault.c:292(log_stack_trace) Sep 13 20:03:42 NAS-PC smbd[5414]: BACKTRACE: 39 stack frames: Sep 13 20:03:42 NAS-PC smbd[5414]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14572c11f64e] Sep 13 20:03:42 NAS-PC smbd[5414]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14572c11f8a9] Sep 13 20:03:42 NAS-PC smbd[5414]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d0fb) [0x14572c53a0fb] Sep 13 20:03:42 NAS-PC smbd[5414]: #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x14572c0c94df] Sep 13 20:03:42 NAS-PC smbd[5414]: #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x14572c547266] Sep 13 20:03:42 NAS-PC smbd[5414]: #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x14572c577c69] Sep 13 20:03:42 NAS-PC smbd[5414]: #6 /usr/lib64/libsmbd-base-samba4.so(+0x5cfc6) [0x14572c549fc6] Sep 13 20:03:42 NAS-PC smbd[5414]: #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d14e) [0x14572c54a14e] Sep 13 20:03:42 NAS-PC smbd[5414]: #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x14572c546099] Sep 13 20:03:42 NAS-PC smbd[5414]: #9 /usr/lib64/libsmbd-base-samba4.so(file_close_user+0x3d) [0x14572c5461dd] Sep 13 20:03:42 NAS-PC smbd[5414]: #10 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff+0x4d) [0x14572c5c2ffd] Sep 13 20:03:42 NAS-PC smbd[5414]: #11 /usr/lib64/libsmbd-base-samba4.so(+0xd6435) [0x14572c5c3435] Sep 13 20:03:42 NAS-PC smbd[5414]: #12 /usr/lib64/libdbwrap-samba4.so(+0x5d18) [0x14572bddad18] Sep 13 20:03:42 NAS-PC smbd[5414]: #13 /usr/lib64/libdbwrap-samba4.so(+0x5f3a) [0x14572bddaf3a] Sep 13 20:03:42 NAS-PC smbd[5414]: #14 /usr/lib64/libdbwrap-samba4.so(dbwrap_traverse+0x7) [0x14572bdd8f67] Sep 13 20:03:42 NAS-PC smbd[5414]: #15 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff_all+0x5b) [0x14572c5c37eb] Sep 13 20:03:42 NAS-PC smbd[5414]: #16 /usr/lib64/libsmbd-base-samba4.so(+0xdca8b) [0x14572c5c9a8b] Sep 13 20:03:42 NAS-PC smbd[5414]: #17 /usr/lib64/libsmbd-base-samba4.so(smbd_reinit_after_fork+0) [0x14572c5ca070] Sep 13 20:03:42 NAS-PC smbd[5414]: #18 /usr/lib64/libsmbd-shim-samba4.so(exit_server_cleanly+0x14) [0x14572c126284] Sep 13 20:03:42 NAS-PC smbd[5414]: #19 /usr/lib64/libsmbd-base-samba4.so(smbd_server_connection_terminate_ex+0x4d6) [0x14572c59f326] Sep 13 20:03:42 NAS-PC smbd[5414]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_timer_handler+0xfe) [0x14572c0e292e] Sep 13 20:03:42 NAS-PC smbd[5414]: #21 /usr/lib64/libtevent.so.0(tevent_common_loop_timer_delay+0x8a) [0x14572c0e2ada] Sep 13 20:03:42 NAS-PC smbd[5414]: #22 /usr/lib64/libtevent.so.0(+0xeed9) [0x14572c0e3ed9] Sep 13 20:03:42 NAS-PC smbd[5414]: #23 /usr/lib64/libtevent.so.0(+0xcef7) [0x14572c0e1ef7] Sep 13 20:03:42 NAS-PC smbd[5414]: #24 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14572c0dcba1] Sep 13 20:03:42 NAS-PC smbd[5414]: #25 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14572c0dce7b] Sep 13 20:03:42 NAS-PC smbd[5414]: #26 /usr/lib64/libtevent.so.0(+0xce97) [0x14572c0e1e97] Sep 13 20:03:42 NAS-PC smbd[5414]: #27 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x14572c590be7] Sep 13 20:03:42 NAS-PC smbd[5414]: #28 /usr/sbin/smbd(+0xb090) [0x55a5d52e7090] Sep 13 20:03:42 NAS-PC smbd[5414]: #29 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14572c0dd8c1] Sep 13 20:03:42 NAS-PC smbd[5414]: #30 /usr/lib64/libtevent.so.0(+0xee07) [0x14572c0e3e07] Sep 13 20:03:42 NAS-PC smbd[5414]: #31 /usr/lib64/libtevent.so.0(+0xcef7) [0x14572c0e1ef7] Sep 13 20:03:42 NAS-PC smbd[5414]: #32 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14572c0dcba1] Sep 13 20:03:42 NAS-PC smbd[5414]: #33 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14572c0dce7b] Sep 13 20:03:42 NAS-PC smbd[5414]: #34 /usr/lib64/libtevent.so.0(+0xce97) [0x14572c0e1e97] Sep 13 20:03:42 NAS-PC smbd[5414]: #35 /usr/sbin/smbd(main+0x1489) [0x55a5d52e4259] Sep 13 20:03:42 NAS-PC smbd[5414]: #36 /lib64/libc.so.6(+0x236b7) [0x14572bee06b7] Sep 13 20:03:42 NAS-PC smbd[5414]: #37 /lib64/libc.so.6(__libc_start_main+0x85) [0x14572bee0775] Sep 13 20:03:42 NAS-PC smbd[5414]: #38 /usr/sbin/smbd(_start+0x21) [0x55a5d52e4b31] Sep 13 20:03:42 NAS-PC smbd[5414]: [2024/09/13 20:03:42.368574, 0] ../../source3/lib/dumpcore.c:315(dump_core) Sep 13 20:03:42 NAS-PC smbd[5414]: dumping core in /var/log/samba/cores/smbd Anyone have an idea why this is happening?
-
Still don't see it this up yet so I used the information in this thread to get the server going. Thanks to @Nodiaque and everyone else for the tips and info on setting this up!
-
Thank you for doing this. Will be keeping an eye out for this to show up! 👍
-
Hi all, My server is running fine and not having any problems at all. I just received a new SAMSUNG FIT Plus 64GB flash drive as a gift and would like to swap out the old flash drive for the new Samsung flash drive. What would be the best way to go about doing this? Thanks!
-
In Settings > NetworkSettings change IPv4 DNS server assignment from Automatic to Static Set IPv4 DNS server to 8.8.8.8 and 8.8.4.4 Now try and see if it works. *EDIT* You will have to disable Docker and VM's in the settings before you can make these adjustments.
-
Update! So I rebooted and the IP came back but I could not access Plex remotely, I couldn't update dockers and I couldn't retrieve new apps. When I went to Apps tab I got a message to use a static dns and it suggested 208.67.222.222 to use. So I went into setting > network settings and changed IPv4 DNS server assignment: to static and IPv4 DNS server: 208.67.222.222 and now everything works. Was this the solution? it seems to be but I just want to make sure and also can I use any DNS IP?
