wesman

Members
  • Content Count

    112
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wesman

  • Rank
    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. 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:
  8. 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.
  9. 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 nct