Howboys

Members
  • Posts

    105
  • Joined

  • Last visited

Posts posted by Howboys

  1. 16 hours ago, wiliamggs said:

    Did anyone figure this out? I have a HP Elite Mini 600 G9 i5 12600, 64GB ram DDR5. It wont boot Unraid. I tried 4 different brand name drives. Hiren's, Parted Magic and other bootable OS will boot, same USB. If imaging with UNRAID tool it wont boot. It works on HP 600 G6 Mini, not on G9.

    I think this was because of USB3 (or more accurately because unraid doesn't officially support USB3). Most modern computers don't have USB2 ports and mist flash drives are USB3. So you're kinda screwed.

     

    My solution was to just move to using snapraid and mergerfs. Much less headache and I use vanilla Ubuntu. I was getting tired of unraid's limitations like these.

  2. I'm also seeing this with 2 different enclosures. Each drive is recognized and the Identity part of the disk reads the correct serial/model/smart. But the Main page only shows drives like JMicron_Generic_0123456789ABCDEF-0:0.

     

    This is mostly fine except preclear freaks out (clicking preclear only seems to kick off the operation on the first drive regardless of which button you press).

     

    I would really love a solution to this.

  3. Did you ever figure this out?

     

    I just got a 800 G4 Mini and I'm seeing very similar symptoms. I've tried booting EFI and legacy, similar results. Basically, half my boots are okay. The other half result in Boot device not found error.

     

    Occasionally, I'll see the blue unraid screen without and text (but the boot would hang). I've messed around with BIOS settings but nothing helped.

     

    I'm using a Samsung 32GB flash drive. I've tried all USB ports on the computer (none are USB 2.0).

     

    Basically, I just can't get unraid to boot reliably on this system.

  4. I'm seeing this too:

     

    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320191,  0] ../../source3/smbd/close.c:312(close_remove_share_mode)
    Jun 15 16:47:34 Tower  smbd[5524]:   close_remove_share_mode: Could not get share mode lock for file Vault/stff/file.mp4
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320283,  0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor)
    Jun 15 16:47:34 Tower  smbd[5524]:   PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD)
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320297,  0] ../../lib/util/fault.c:173(smb_panic_log)
    Jun 15 16:47:34 Tower  smbd[5524]:   ===============================================================
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320310,  0] ../../lib/util/fault.c:174(smb_panic_log)
    Jun 15 16:47:34 Tower  smbd[5524]:   INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 5524 (4.17.3)
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320318,  0] ../../lib/util/fault.c:178(smb_panic_log)
    Jun 15 16:47:34 Tower  smbd[5524]:   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
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320327,  0] ../../lib/util/fault.c:183(smb_panic_log)
    Jun 15 16:47:34 Tower  smbd[5524]:   ===============================================================
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320335,  0] ../../lib/util/fault.c:184(smb_panic_log)
    Jun 15 16:47:34 Tower  smbd[5524]:   PANIC (pid 5524): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.3
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320686,  0] ../../lib/util/fault.c:292(log_stack_trace)
    Jun 15 16:47:34 Tower  smbd[5524]:   BACKTRACE: 38 stack frames:
    Jun 15 16:47:34 Tower  smbd[5524]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x1476341fc64e]
    Jun 15 16:47:34 Tower  smbd[5524]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x1476341fc8a9]
    Jun 15 16:47:34 Tower  smbd[5524]:    #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d10b) [0x1476345dd10b]
    Jun 15 16:47:34 Tower  smbd[5524]:    #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x1476341ac4df]
    Jun 15 16:47:34 Tower  smbd[5524]:    #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x1476345ea2e6]
    Jun 15 16:47:34 Tower  smbd[5524]:    #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x14763461ad49]
    Jun 15 16:47:34 Tower  smbd[5524]:    #6 /usr/lib64/libsmbd-base-samba4.so(+0x5d046) [0x1476345ed046]
    Jun 15 16:47:34 Tower  smbd[5524]:    #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d1ce) [0x1476345ed1ce]
    Jun 15 16:47:34 Tower  smbd[5524]:    #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x1476345e9119]
    Jun 15 16:47:34 Tower  smbd[5524]:    #9 /usr/lib64/libsmbd-base-samba4.so(file_close_user+0x3d) [0x1476345e925d]
    Jun 15 16:47:34 Tower  smbd[5524]:    #10 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff+0x4d) [0x14763466600d]
    Jun 15 16:47:34 Tower  smbd[5524]:    #11 /usr/lib64/libsmbd-base-samba4.so(+0xd6445) [0x147634666445]
    Jun 15 16:47:34 Tower  smbd[5524]:    #12 /usr/lib64/libdbwrap-samba4.so(+0x5d18) [0x147633eded18]
    Jun 15 16:47:34 Tower  smbd[5524]:    #13 /usr/lib64/libdbwrap-samba4.so(+0x5f3a) [0x147633edef3a]
    Jun 15 16:47:34 Tower  smbd[5524]:    #14 /usr/lib64/libdbwrap-samba4.so(dbwrap_traverse+0x7) [0x147633edcf67]
    Jun 15 16:47:34 Tower  smbd[5524]:    #15 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff_all+0x5b) [0x1476346667fb]
    Jun 15 16:47:34 Tower  smbd[5524]:    #16 /usr/lib64/libsmbd-base-samba4.so(+0xdca0b) [0x14763466ca0b]
    Jun 15 16:47:34 Tower  smbd[5524]:    #17 /usr/lib64/libsmbd-base-samba4.so(smbd_reinit_after_fork+0) [0x14763466cff0]
    Jun 15 16:47:34 Tower  smbd[5524]:    #18 /usr/lib64/libsmbd-shim-samba4.so(exit_server_cleanly+0x14) [0x147634201284]
    Jun 15 16:47:34 Tower  smbd[5524]:    #19 /usr/lib64/libsmbd-base-samba4.so(smbd_server_connection_terminate_ex+0x4d6) [0x1476346424c6]
    Jun 15 16:47:34 Tower  smbd[5524]:    #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x1476341bf791]
    Jun 15 16:47:34 Tower  smbd[5524]:    #21 /usr/lib64/libtevent.so.0(+0xec87) [0x1476341c5c87]
    Jun 15 16:47:34 Tower  smbd[5524]:    #22 /usr/lib64/libtevent.so.0(+0xcd77) [0x1476341c3d77]
    Jun 15 16:47:34 Tower  smbd[5524]:    #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1476341beb61]
    Jun 15 16:47:34 Tower  smbd[5524]:    #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1476341bee3b]
    Jun 15 16:47:34 Tower  smbd[5524]:    #25 /usr/lib64/libtevent.so.0(+0xcd17) [0x1476341c3d17]
    Jun 15 16:47:34 Tower  smbd[5524]:    #26 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x147634633ce7]
    Jun 15 16:47:34 Tower  smbd[5524]:    #27 /usr/sbin/smbd(+0xb090) [0x55d319c56090]
    Jun 15 16:47:34 Tower  smbd[5524]:    #28 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x1476341bf791]
    Jun 15 16:47:34 Tower  smbd[5524]:    #29 /usr/lib64/libtevent.so.0(+0xec87) [0x1476341c5c87]
    Jun 15 16:47:34 Tower  smbd[5524]:    #30 /usr/lib64/libtevent.so.0(+0xcd77) [0x1476341c3d77]
    Jun 15 16:47:34 Tower  smbd[5524]:    #31 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1476341beb61]
    Jun 15 16:47:34 Tower  smbd[5524]:    #32 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1476341bee3b]
    Jun 15 16:47:34 Tower  smbd[5524]:    #33 /usr/lib64/libtevent.so.0(+0xcd17) [0x1476341c3d17]
    Jun 15 16:47:34 Tower  smbd[5524]:    #34 /usr/sbin/smbd(main+0x1489) [0x55d319c53259]
    Jun 15 16:47:34 Tower  smbd[5524]:    #35 /lib64/libc.so.6(+0x23177) [0x147633fc9177]
    Jun 15 16:47:34 Tower  smbd[5524]:    #36 /lib64/libc.so.6(__libc_start_main+0x85) [0x147633fc9235]
    Jun 15 16:47:34 Tower  smbd[5524]:    #37 /usr/sbin/smbd(_start+0x21) [0x55d319c53b31]
    Jun 15 16:47:34 Tower  smbd[5524]: [2023/06/15 16:47:34.320857,  0] ../../source3/lib/dumpcore.c:315(dump_core)
    Jun 15 16:47:34 Tower  smbd[5524]:   dumping core in /var/log/samba/cores/smbd

     

    From what I can tell, this only happens from Cx File Manager from.

  5. 24 minutes ago, grants169 said:

     

    My "solution" was to quit NFS and use SMB solely.  Haven't had a problem since. It's pretty scary when it happens because literally all your data just POOF vanishes and I don't like it one bit.   I haven't figured out the cause or a real solution.

    Ugh.. even samba has issues for me (performance and locking related). That's why I switched to nfs.

  6. On 11/20/2022 at 1:42 AM, JorgeB said:

    It appears to be a Samba issue, problem started after Unraid updated Samba to 4.7.x, note that the files should still be deleted despite the error, though program might abort after deleting the first one due to the error.

     

    From https://bugzilla.samba.org/show_bug.cgi?id=15247:

     

    Quote

    Sorry. It looks like your vendor has messed up the port of 4.17 (especially as smbd is crashing). You'll have to contact them directly. If you can reproduce with a "stock" Samba 4.17 then I'll take a look again but in the meantime I'm going to have to close this.

     

    Looks like maybe this is isolated to unraid.

  7. Happened twice today. The first time, I just shutdown the server and made sure all disks were properly cabled. Everything was fine.

     

    A few hours later (just now), the server is unresponse and I see this in the syslog:

     

    Mar 25 09:36:37 Tower elogind-daemon[1352]: Removed session c33.
    Mar 25 09:57:29 Tower kernel: shfs[10680]: segfault at 10 ip 00001480d2ee85c2 sp 00001480d27dcc20 error 4 in libfuse3.so.3.12.0[1480d2ee4000+19000]
    Mar 25 09:57:29 Tower kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee
    Mar 25 09:57:29 Tower kernel: ------------[ cut here ]------------
    Mar 25 09:57:29 Tower kernel: nfsd: non-standard errno: -103
    Mar 25 09:57:29 Tower kernel: WARNING: CPU: 14 PID: 10307 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd]
    Mar 25 09:57:29 Tower kernel: Modules linked in: rpcsec_gss_krb5 xt_mark tcp_diag udp_diag inet_diag nf_tables nvidia_uvm(PO) veth tun xt_nat xt_tcpudp ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm nvme i2c_piix4 edac_mce_amd edac_core kvm_amd kvm gigabyte_wmi wmi_bmof crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel backlight crypto_simd cryptd mpt3sas rapl r8169 i2c_core nvme_core raid_class k10temp syscopyarea ccp ahci scsi_transport_sas sysfillrect sysimgblt realtek fb_sys_fops libahci wmi thermal button acpi_cpufreq unix
    Mar 25 09:57:29 Tower kernel: CPU: 14 PID: 10307 Comm: nfsd Tainted: P S         O      5.19.17-Unraid #2
    Mar 25 09:57:29 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F63a 02/17/2022
    Mar 25 09:57:29 Tower kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd]
    Mar 25 09:57:29 Tower kernel: Code: e9 f3 bc 0c de 48 ff c0 48 83 f8 26 75 e0 80 3d bb 47 05 00 00 75 15 48 c7 c7 17 54 b6 a3 c6 05 ab 47 05 00 01 e8 42 57 ce dd <0f> 0b b8 00 00 00 05 e9 c2 bc 0c de 48 83 ec 18 31 c9 ba ff 07 00
    Mar 25 09:57:29 Tower kernel: RSP: 0018:ffffc90000adfd58 EFLAGS: 00010282
    Mar 25 09:57:29 Tower kernel: RAX: 0000000000000000 RBX: ffff8881b3448030 RCX: 0000000000000027
    Mar 25 09:57:29 Tower kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff
    Mar 25 09:57:29 Tower kernel: RBP: ffffc90000adfda0 R08: 0000000000000000 R09: ffffffff828653f0
    Mar 25 09:57:29 Tower kernel: R10: 00003fffffffffff R11: ffff88843f3427b6 R12: ffff8881b3448108
    Mar 25 09:57:29 Tower kernel: R13: ffff8882ba3eb0c0 R14: 0000000000000080 R15: ffff8882ba3eb400
    Mar 25 09:57:29 Tower kernel: FS:  0000000000000000(0000) GS:ffff88842eb80000(0000) knlGS:0000000000000000
    Mar 25 09:57:29 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Mar 25 09:57:29 Tower kernel: CR2: 000015284b7418a8 CR3: 00000001f97a0000 CR4: 00000000003506e0
    Mar 25 09:57:29 Tower kernel: Call Trace:
    Mar 25 09:57:29 Tower kernel: <TASK>
    Mar 25 09:57:29 Tower kernel: fh_getattr+0x43/0x61 [nfsd]
    Mar 25 09:57:29 Tower kernel: fh_fill_post_attrs+0x55/0xa4 [nfsd]
    Mar 25 09:57:29 Tower kernel: fh_unlock+0x12/0x3b [nfsd]
    Mar 25 09:57:29 Tower kernel: nfsd_unlink+0x13a/0x1b9 [nfsd]
    Mar 25 09:57:29 Tower kernel: nfsd4_remove+0x4f/0x76 [nfsd]
    Mar 25 09:57:29 Tower kernel: nfsd4_proc_compound+0x437/0x56c [nfsd]
    Mar 25 09:57:29 Tower kernel: nfsd_dispatch+0x1a9/0x262 [nfsd]
    Mar 25 09:57:29 Tower kernel: svc_process+0x3f1/0x5d6 [sunrpc]
    Mar 25 09:57:29 Tower kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd]
    Mar 25 09:57:29 Tower kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd]
    Mar 25 09:57:29 Tower kernel: nfsd+0xd5/0x155 [nfsd]
    Mar 25 09:57:29 Tower kernel: kthread+0xe7/0xef
    Mar 25 09:57:29 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b
    Mar 25 09:57:29 Tower kernel: ret_from_fork+0x22/0x30
    Mar 25 09:57:29 Tower kernel: </TASK>
    Mar 25 09:57:29 Tower kernel: ---[ end trace 0000000000000000 ]---

     

    WebUI works, SSH works. However shares are not found:

     

    root@Tower:~# ls /mnt/user
    /bin/ls: cannot access '/mnt/user': Transport endpoint is not connected

     

    Diags attached.

     

    tower-diagnostics-20230325-1002.zip

     

  8. I'm currently running a array rebuild (replaced a drive yesterday) and preclearing the old drive. For some reason now my flash drive seems to not be accessible. I have backups that I can try loading on to a new one later but I'm curious:

     

    1. Should I interrupt the array rebuild or let it run entirely before messing around with the flash drive?

    2. Why did my flash drive fail? Is there anything in the logs that shows any indication?

     

    Thank you

    tower-diagnostics-20230301-1413.zip