Jump to content

wesman

Members
 View Profile  See their activity

  • Posts

    130

  • Joined

  • Last visited

 Content Type 

Posts posted by wesman

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by wesman

    Hi there, 

     

    I am attempting to mount a share on a different unraid system. I installed the latest (as of 28 Aug 2020) Version on UD, and the UD Addon. Added the Share, Got the Success lcon, but the share will not mount.  

     

    618001452_ScreenShot2020-08-28at8_30_21AM.thumb.png.70cd321da3845228bbbce0afa63aeace.png

     

    I tried, Searching for the System (Found and added by name), as well as, deleting it and adding it by IP (Seen above).

     

    When I try to mount it, I get  

    Aug 28 06:04:09 Eyrie kernel: CIFS VFS: \\HARDHOME failed to connect to IPC (rc=-13)
Aug 28 06:04:09 Eyrie kernel: CIFS VFS: cifs_mount failed w/return code = -13
Aug 28 06:04:09 Eyrie unassigned.devices: Mount of '//HARDHOME/Media' failed. Error message: 'mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.
Aug 28 06:05:39 Eyrie unassigned.devices: Removing configuration '//HARDHOME/Media'.
Aug 28 06:09:38 Eyrie ntpd[4558]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Aug 28 06:13:08 Eyrie unassigned.devices: Mount SMB share '//192.168.29.34/Media' using SMB3 protocol.
Aug 28 06:13:08 Eyrie unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Media' '//192.168.29.34/Media' '/mnt/disks/192.168.29.34_Media'
Aug 28 06:13:08 Eyrie kernel: CIFS: Attempting to mount //192.168.29.34/Media
Aug 28 06:13:08 Eyrie kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Aug 28 06:13:08 Eyrie kernel: CIFS VFS: \\192.168.29.34 Send error in SessSetup = -13
Aug 28 06:13:08 Eyrie kernel: CIFS VFS: cifs_mount failed w/return code = -13
Aug 28 06:13:08 Eyrie unassigned.devices: Mount of '//192.168.29.34/Media' failed. Error message: 'mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.

     

    Again, this is the lasted version of UD, Diagnostics attached, Thanks for the advice/assist!

     

    eyrie-diagnostics-20200828-0835.zip

     

    Continued Crashes and parity rebuilds

    in General Support

    Posted

    26 minutes ago, trurl said:

    Probably unrelated, but why do you have 200G allocated to docker.img? Have you had problems filling it? 20G should be more than enough and if it grows you likely have some application writing to a path that isn't mapped. Making docker.img large will not fix that problem, it will just make it take longer to fill.

     

     

    Only becuase in one of the errors (a week ago), it implied that the Docker Image was converted to read only, and I read somewhere that can happen if you run out of space. I have no idea how true that is but, I set it to 200.

    Continued Crashes and parity rebuilds

    in General Support

    Posted

    Yet another crash, attached syslog and Diagnostic

     

    Log Starts to indicate a problem around this point. Then appears to going around and around on this. Any Ideas?

     

    Is this a hardware issue? 

    Aug 20 19:32:35 Hardhome kernel: ------------[ cut here ]------------
Aug 20 19:32:35 Hardhome kernel: WARNING: CPU: 2 PID: 16827 at mm/truncate.c:707 invalidate_inode_pages2_range+0x163/0x369
Aug 20 19:32:35 Hardhome kernel: Modules linked in: nvidia_uvm(O) macvlan veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs dm_crypt dm_mod dax md_mod nct6775 hwmon_vid atlantic e1000e nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crc32_pclmul intel_rapl_perf intel_uncore pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd kvm intel_cstate drm_kms_helper wmi_bmof mxm_wmi coretemp drm rsnvme(PO) mpt3sas crct10dif_pclmul intel_powerclamp crc32c_intel syscopyarea sysfillrect sysimgblt x86_pkg_temp_thermal fb_sys_fops agpgart nvme i2c_i801 video pcc_cpufreq raid_class nvme_core wmi scsi_transport_sas i2c_core ahci libahci backlight thermal button acpi_pad fan [last unloaded: atlantic]
Aug 20 19:32:35 Hardhome kernel: CPU: 2 PID: 16827 Comm: mono Tainted: P        W  O      4.19.107-Unraid #1
Aug 20 19:32:35 Hardhome kernel: Hardware name: System manufacturer System Product Name/ROG MAXIMUS XI HERO, BIOS 1502 02/21/2020
Aug 20 19:32:35 Hardhome kernel: RIP: 0010:invalidate_inode_pages2_range+0x163/0x369
Aug 20 19:32:35 Hardhome kernel: Code: 8b 70 20 f6 c1 01 74 04 48 8d 51 ff 48 89 e8 48 29 d0 48 c1 f8 06 48 01 f0 48 39 c3 74 0e 48 c7 c7 79 fc d2 81 e8 a4 1c fa ff <0f> 0b 4c 39 65 18 0f 85 70 01 00 00 48 8b 55 08 48 89 e8 f6 c2 01
Aug 20 19:32:35 Hardhome kernel: RSP: 0018:ffffc9000a4039c8 EFLAGS: 00010246
Aug 20 19:32:35 Hardhome kernel: RAX: 0000000000000024 RBX: 0000000000ab9c11 RCX: 0000000000000000
Aug 20 19:32:35 Hardhome kernel: RDX: 0000000000000000 RSI: ffff88903d8964f8 RDI: ffff88903d8964f8
Aug 20 19:32:35 Hardhome kernel: RBP: ffff888d6570fad8 R08: 0000000000000003 R09: 000000000001c800
Aug 20 19:32:35 Hardhome kernel: R10: 0000000000000000 R11: 0000000000000044 R12: ffff888d6cb41068
Aug 20 19:32:35 Hardhome kernel: R13: 0000000000000000 R14: 000000000000000e R15: ffff888d6cb41070
Aug 20 19:32:35 Hardhome kernel: FS:  000014a9deafc700(0000) GS:ffff88903d880000(0000) knlGS:0000000000000000
Aug 20 19:32:35 Hardhome kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 20 19:32:35 Hardhome kernel: CR2: 0000153c8ac22880 CR3: 00000001fb5e0001 CR4: 00000000003606e0
Aug 20 19:32:35 Hardhome kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 20 19:32:35 Hardhome kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 20 19:32:35 Hardhome kernel: Call Trace:
Aug 20 19:32:35 Hardhome kernel: ? alloc_rt_sched_group+0x108/0x12f
Aug 20 19:32:35 Hardhome kernel: fuse_dentry_revalidate+0x203/0x28e
Aug 20 19:32:35 Hardhome kernel: lookup_fast+0x1fb/0x280
Aug 20 19:32:35 Hardhome kernel: walk_component+0xb6/0x254
Aug 20 19:32:35 Hardhome kernel: path_lookupat.isra.0+0x146/0x208
Aug 20 19:32:35 Hardhome kernel: ? __bpf_prog_run32+0x34/0x54
Aug 20 19:32:35 Hardhome kernel: ? try_to_wake_up+0x2af/0x2d6
Aug 20 19:32:35 Hardhome kernel: filename_lookup+0x7c/0xdf
Aug 20 19:32:35 Hardhome kernel: ? autoremove_wake_function+0x9/0x2a
Aug 20 19:32:35 Hardhome kernel: ? _cond_resched+0x1b/0x1e
Aug 20 19:32:35 Hardhome kernel: ? kmem_cache_alloc+0xdf/0xeb
Aug 20 19:32:35 Hardhome kernel: ? getname_flags+0x44/0x146
Aug 20 19:32:35 Hardhome kernel: do_utimes+0xe5/0x136
Aug 20 19:32:35 Hardhome kernel: do_futimesat+0xad/0xcc
Aug 20 19:32:35 Hardhome kernel: do_syscall_64+0x57/0xf2
Aug 20 19:32:35 Hardhome kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 20 19:32:35 Hardhome kernel: RIP: 0033:0x14a9ebb06b47
Aug 20 19:32:35 Hardhome kernel: Code: 39 c3 75 cf 42 0f b6 14 28 80 fa 3d 77 cb 49 0f a3 d4 73 c5 48 83 c4 08 5b 5d 41 5c 41 5d c3 0f 1f 40 00 b8 eb 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 09 f3 c3 0f 1f 80 00 00 00 00 48 8b 15 09 23
Aug 20 19:32:35 Hardhome kernel: RSP: 002b:000014a9deafa568 EFLAGS: 00000297 ORIG_RAX: 00000000000000eb
Aug 20 19:32:35 Hardhome kernel: RAX: ffffffffffffffda RBX: 000014a9deafa570 RCX: 000014a9ebb06b47
Aug 20 19:32:35 Hardhome kernel: RDX: 0000000000000040 RSI: 000014a9deafa5f0 RDI: 000014a9b87dff60
Aug 20 19:32:35 Hardhome kernel: RBP: 000014a9b87dff60 R08: 0000000000000006 R09: 00000000ffffffff
Aug 20 19:32:35 Hardhome kernel: R10: 0000000000000000 R11: 0000000000000297 R12: 000014a9b87dff60
Aug 20 19:32:35 Hardhome kernel: R13: 000014a9deafa5f0 R14: 0000565545d81d68 R15: 000014a9b8000b20
Aug 20 19:32:35 Hardhome kernel: ---[ end trace 3002143fbf5bb3c3 ]---

     

    syslog-192.168.29.34.log hardhome-diagnostics-20200821-0735.zip

    poweroff and reboot not working

    in General Support

    Posted · Edited by wesman

    Any Help on this? It's happened again. I am trying to get a diagnostic but its not working. I'll have to power it off first. 

     

    I was able to get this syslog

      

    Jul 19 15:53:11 Hardhome kernel: CPU: 9 PID: 377 Comm: khugepaged Tainted: P D W O 4.19.107-Unraid #1 
Jul 19 15:53:11 Hardhome kernel: Hardware name: System manufacturer System Product Name/ROG MAXIMUS XI HERO, BIOS 1502 02/21/2020 
Jul 19 15:53:11 Hardhome kernel: Call Trace:

     

    UPDATING WITH DIAGNOSTICS

    hardhome-syslog-20200719-2255.zip

    hardhome-diagnostics-20200719-1844.zip

    poweroff and reboot not working

    in General Support

    Posted · Edited by wesman
    update

    My Server stopped responding a while back, when I ssh to it, i can issue the commands (poweroff or reboot) and nothing happens. 

    I went to this link
    https://wiki.lime-technology.com/Console#To_cleanly_Stop_the_array_from_the_command_line

    but, just starting this and I get. 
     

    root@Hardhome:~# /root/samba stop

    -bash: /root/samba: No such file or directory

     

    Am I doing something wrong here?

    I searched for and found  

    /etc/rc.d/rc.samba stop

      (not sure if that is the same samba command or not, but after running it, my shares disappeared).  

    /etc/rc.d/rc.docker stop

      (just hangs - its actually the docker that "seemed" to hang first)

     

    looking at the docker (since the system is not shutting down, I see)

    4146e136835a        bitwardenrs/server        "/start.sh"         2 days ago          Up 2 days (unhealthy)  

    I tried 

    docker stop 4146e136835a

    just hangs.  

    umount /dev/md*

      - says that disk is already unmounted 

    umount: /dev/md1: not mounted.

      

    /root/mdcmd stop

    -bash: /root/mdcmd: No such file or directory 

    mdcmd stop

    seems to work, is this the same command? but I get

    /usr/local/sbin/mdcmd: line 11: echo: write error: Device or resource busy

     

    I can't think of anything to do except forceable power cycle the system, any help?

    UPDATE: Forced Power Cycle, attached Diagnotics

    hardhome-diagnostics-20200714-1147.zip

    Disk that wont show up after failing

    in General Support

    Posted

    I had a second parity start getting disabled in unraid, I removed it from my main system and replaced it with another.

     

    Then placed it in my backup system, ran preclear on it for 3 cycles,  zero errors, no smart errors. nothing. 

     

    double checked all my cables and put the disk back in the original system, but it will not show up in unassigned devices or under /mnt/disks/

     

    is it locked out or something?

     

    Best options in 2019 for Plex on Unraid with hardware acceleration?

    in General Support

    Posted

    I am sure others have noted that you can:
    Run Plex in a Docker with any NVIDIA Card
    Using LinuxServer's Plex and Unraid build (video below)

     

    Also, I would recommend the 1660, it is the cheapest card that can do both

     

    I got this one, it can both Encode (4K - which plex doesn't do yet) and Decode 4K H.265 (HEVC) 4:4:4   
    This means if you have 4K movies in your library (which I do) Plex (in a docker) can decode it (in hardware) and 
    Encode it into what ever your uses wants (in hardware). 
    https://www.amazon.com/gp/product/B07ZHWQ81N/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

     

    This shows what all the different cards can do

    https://developer.nvidia.com/video-encode-decode-gpu-support-matrix

     

     

×
×
  • Create New...