VernGraner

I ran into this problem this morning on my 7.0.0 unRAID server. I had rebooted and it hung with this error message: waiting up to 30 sec for device with label unraid to come online ... scsi umount: /: not mounted. not found - press enter key to reboot..._ Being as how I had this Mediasonic 8-bay external USB/eSATA drive case w/8 sata drives in it*** connected to the server: https://mediasonicstore.com/products/mediasonic-8-bay-hard-drive-enclosure-usb-3-0-esata-h82-su3s2 I unplugged its USB cable and rebooted. The server then came up. 👍🙂 I then upgraded from 7.0.0 to 7.0.1 and rebooted to verify the server upgraded correctly (it had) I then reattached the external USB drive case and rebooted once more. The server came up normally, so Bottom line: Upgrading to 7.0.1 fixes the issue for me ***And, before any more people start yelling about usb drives on unraid being "abnormal!" and "unsupported!" and "not recommended!", for the record- I don't plan to use this box for an array or storage! I use it as an easy way to add/remove a bunch of old small drives to format/pre-clear & get SMART stats before the drives get recycled or repurposed. 👍🙂

I've noticed similar errors in my log- though not nearly as many as you are having. It would appear mine is related to a Macrium backup process running from my Windows 11 machine to my unraid server "Defender". The log entries are here: Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.214128, 0] ../../source3/smbd/close.c:312(close_remove_share_mode) Nov 3 08:31:46 Defender smbd[363]: close_remove_share_mode: Could not get share mode lock for file backups/Macrium PACMANsr/macrium_test.dat Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226669, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) Nov 3 08:31:46 Defender smbd[363]: PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226690, 0] ../../lib/util/fault.c:173(smb_panic_log) Nov 3 08:31:46 Defender smbd[363]: =============================================================== Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226707, 0] ../../lib/util/fault.c:174(smb_panic_log) Nov 3 08:31:46 Defender smbd[363]: INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 363 (4.17.10) Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226720, 0] ../../lib/util/fault.c:178(smb_panic_log) Nov 3 08:31:46 Defender smbd[363]: 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 Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226733, 0] ../../lib/util/fault.c:183(smb_panic_log) Nov 3 08:31:46 Defender smbd[363]: =============================================================== Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.226746, 0] ../../lib/util/fault.c:184(smb_panic_log) Nov 3 08:31:46 Defender smbd[363]: PANIC (pid 363): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.10 Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.227086, 0] ../../lib/util/fault.c:292(log_stack_trace) Nov 3 08:31:46 Defender smbd[363]: BACKTRACE: 32 stack frames: Nov 3 08:31:46 Defender smbd[363]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x1523bb2a364e] Nov 3 08:31:46 Defender smbd[363]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x1523bb2a38a9] Nov 3 08:31:46 Defender smbd[363]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d0fb) [0x1523bb6850fb] Nov 3 08:31:46 Defender smbd[363]: #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x1523bb2524df] Nov 3 08:31:46 Defender smbd[363]: #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x1523bb692266] Nov 3 08:31:46 Defender smbd[363]: #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x1523bb6c2a99] Nov 3 08:31:46 Defender smbd[363]: #6 /usr/lib64/libsmbd-base-samba4.so(+0x5cfc6) [0x1523bb694fc6] Nov 3 08:31:46 Defender smbd[363]: #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d112) [0x1523bb695112] Nov 3 08:31:46 Defender smbd[363]: #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x1523bb691099] Nov 3 08:31:46 Defender smbd[363]: #9 /usr/lib64/libsmbd-base-samba4.so(file_close_conn+0x44) [0x1523bb691104] Nov 3 08:31:46 Defender smbd[363]: #10 /usr/lib64/libsmbd-base-samba4.so(close_cnum+0x67) [0x1523bb6ddc77] Nov 3 08:31:46 Defender smbd[363]: #11 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_tcon_disconnect+0x4e) [0x1523bb710fde] Nov 3 08:31:46 Defender smbd[363]: #12 /usr/lib64/libsmbd-base-samba4.so(+0xbbb42) [0x1523bb6f3b42] Nov 3 08:31:46 Defender smbd[363]: #13 /usr/lib64/libtevent.so.0(tevent_common_invoke_immediate_handler+0x17a) [0x1523bb265e2a] Nov 3 08:31:46 Defender smbd[363]: #14 /usr/lib64/libtevent.so.0(tevent_common_loop_immediate+0x16) [0x1523bb265e46] Nov 3 08:31:46 Defender smbd[363]: #15 /usr/lib64/libtevent.so.0(+0xebfb) [0x1523bb26bbfb] Nov 3 08:31:46 Defender smbd[363]: #16 /usr/lib64/libtevent.so.0(+0xcef7) [0x1523bb269ef7] Nov 3 08:31:46 Defender smbd[363]: #17 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1523bb264ba1] Nov 3 08:31:46 Defender smbd[363]: #18 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1523bb264e7b] Nov 3 08:31:46 Defender smbd[363]: #19 /usr/lib64/libtevent.so.0(+0xce97) [0x1523bb269e97] Nov 3 08:31:46 Defender smbd[363]: #20 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x1523bb6dba37] Nov 3 08:31:46 Defender smbd[363]: #21 /usr/sbin/smbd(+0xb090) [0x5564f265a090] Nov 3 08:31:46 Defender smbd[363]: #22 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x1523bb2658c1] Nov 3 08:31:46 Defender smbd[363]: #23 /usr/lib64/libtevent.so.0(+0xee07) [0x1523bb26be07] Nov 3 08:31:46 Defender smbd[363]: #24 /usr/lib64/libtevent.so.0(+0xcef7) [0x1523bb269ef7] Nov 3 08:31:46 Defender smbd[363]: #25 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1523bb264ba1] Nov 3 08:31:46 Defender smbd[363]: #26 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1523bb264e7b] Nov 3 08:31:46 Defender smbd[363]: #27 /usr/lib64/libtevent.so.0(+0xce97) [0x1523bb269e97] Nov 3 08:31:46 Defender smbd[363]: #28 /usr/sbin/smbd(main+0x1489) [0x5564f2657259] Nov 3 08:31:46 Defender smbd[363]: #29 /lib64/libc.so.6(+0x236b7) [0x1523bb06c6b7] Nov 3 08:31:46 Defender smbd[363]: #30 /lib64/libc.so.6(__libc_start_main+0x85) [0x1523bb06c775] Nov 3 08:31:46 Defender smbd[363]: #31 /usr/sbin/smbd(_start+0x21) [0x5564f2657b31] Nov 3 08:31:46 Defender smbd[363]: [2023/11/03 08:31:46.227338, 0] ../../source3/lib/dumpcore.c:315(dump_core) Nov 3 08:31:46 Defender smbd[363]: dumping core in /var/log/samba/cores/smbd Nov 3 08:31:46 Defender smbd[363]: For what its worth, the Macrium backup does not report it had failed, so it would appear these errors did not stop the backup from completing 🤔 As this seems to happen when I run a Macrium backup, It would seem I can recreate this error on demand. If someone has any guidance on next steps on troubleshooting this, I would love to hear it! :) Vern

Could someone please link a walk-through or provide the steps to do this roll back function mentioned above?

I've also got this issue happening when I copy large files from the unRAID box down to my Windows 10 machine. I've tried this on two different physical Windows 10 boxes and got the same error. unRAID is V6.7.2 Windows 10 is 1803 Build 17134.885