Jump to content

JorgeB

Moderators
  • Posts

    67,870
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Just create a new flash drove, restore the backup and replace the key, more info below: https://wiki.unraid.net/Manual/Changing_The_Flash_Device
  2. Sorry, I didn't read the complete post, no idea about why it's crashing, I've never used NFS, someone else might be able to help.
  3. If you have a backup you just need to restore it, are all the array/pool devices the same since the backup or were there any changes?
  4. This will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk6 -Start array (in normal mode now), ideally the emulated disk6 will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk and/or post new diags. -If the emulated disk mounts and contents look correct stop the array -Re-assign disk6 and start array to begin.
  5. Not my forte, hopefully someone else can help, @ljm42should be able to help you but I believe is out for the week.
  6. See if this helps: https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29
  7. Depends on the switch, there are models with just RJ45 ports (one combo in this case), e.g.: https://www.netgear.com/business/wired/switches/unmanaged/xs508m/
  8. Wait for the parity sync to finish, turbo write won't work properly until it does.
  9. diskFsType.1="fuseblk" Not sure what heppend here but this is not a valid filesystem, click on disk1 and change fs to auto, if it's already auto change to a different one, then back to auto and apply.
  10. Log is showing device issues, but since it already rotated cannot see the beginning of the problem please reboot and post new diags after array start.
  11. Look more like a hardware issue, you are also having flash drive problems.
  12. Yes, that's usually the best bet, though it depends on how the USB enclosure was setting the disk if it will work or not.
  13. All NICs are being detected, the 10GbE is unable to get an IP address: Oct 2 18:19:29 Tower dhcpcd[1201]: br0: probing for an IPv4LL address Oct 2 18:19:34 Tower dhcpcd[1201]: br0: using IPv4LL address 169.254.173.54 It it connected to a DHCP server? The gigabit link is reporting link down, if that's the main internet NIC make sure a cable is connected and set it as eth0 (Settings -> Network Settings -> Interface Rules) then reboot (you can access the GUI buy booting into GUI mode).
  14. Like mentioned it's not possible for Unraid to move data form array to cache with cache=yes, something else is going on, possible with how you have the containers configured.
  15. Best bet is to post in the appropriate docker support thread:
  16. Since array auto start is disabled the array is stopped so it's normal for the shares and docker not to work, did you try accessing the GUI using the IP address? P.S.: LAN cable is connected to eth1, not eth0, while not technically a problem with the default bound you should always use eth0 to avoid future issues.
  17. The syslog is showing a similar error: Oct 2 16:19:58 Tower kernel: Alternate GPT is invalid, using primary GPT. But like mentioned not clear which device is the problem, check the output of: fdisk -l /dev/sdX for all the devices, it should indicate the culprit
  18. It's logged as a disk problem, but since it passed the SMART test the disk is good for now, keep monitoring but any more similar errors you might consider replacing it.
  19. The 10GbE NIC needs a x4 or larger PCIe slot, x1 doesn't have enough bandwidth for a 10GbE NIC.
  20. https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments:
  21. MCE are hardware errors, nothing to do with parity, look for a SEL (system event log) in the BIOS/IPMI, it might have more info.
  22. Yes, just log off from MyServers, internet connection is not required to run Unraid, unless you are using a trial key.
×
×
  • Create New...