Jump to content

wesman

Members
  • Content Count

    112
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wesman

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Do I need an HDMI Headless plug? I have two unraids, and one old TV that plugs into the one I want to get onto (if I need to directly connect). but every time I plug in the HDMI, the only way I can get the video feed back is to reboot the system, would a HDMI Headless plug prevent that?
  2. Or, is it simplier to just do my orginal though? Or do I assign the new drive as an "Unassigned Device" copy the content of the Data Drive to it with a simple "cp /*" I just don't want to mess up a Bitwarden, and a couple other dockers
  3. @trurl DO you mean while using the CA Backup? I was thinking just onto the NVMe. I was thinking. 1.) Keep the config as it is, using CA, to backup the flash and appdata (to the vmne - Data Drive) 2.) Do - New Config, Keep nothing 3.) Start the new Config with Just the New 1TB Drive, and add the NVMe as "Unassigned" 4.) Copy the backups, restore backups. Confirm its working properly 5.) Then add the NVMe as the parity and let it clear it out.
  4. @johnnie.black Do i need to do CA Backup, first, backup the Flash, Appdata? I don't have any actual data on the drive, just, dockers and the Flash configuration, but i do need to keep the docker, like the self hosted BitWarden, etc.
  5. I've had an old NUC sitting around with a 1TB NVMe as a test Unraid for a while as the only Data Drive - No Parity. I decided to add a 1TB SSD 2.5FF into the NUC as a Parity, but apparently, the new drive is apparently bigger. Is a Parity Swap the right procedure for this? Or do I assign the new drive as an "Unassigned Device" copy the content of the Data Drive to it with a simple "cp /*" Then do a new config?
  6. Well, I created a second user without the special characters, and it worked. THANKS! Although, I am surprised that doesn't work
  7. Yep, double and triple checked, both with Hostname and IP, its right
  8. 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. 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
  9. 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.
  10. 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