Jump to content

JorgeB

Moderators
  • Posts

    67,556
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. If want to export the pool (not the share(s) inside it) you need to en enable disk shares, need to be aware of the disk to share or share to disk copy issues.
  2. SMART looks fine, difficult to say if the vibration is a real problem or not without any SMART or device errors.
  3. Cache is currently a single device, so it can't be converted to raid1: Data Metadata System Id Path DUP DUP DUP Unallocated -- --------- --------- --------- -------- ----------- 1 /dev/sdb1 328.00GiB 2.00GiB 64.00MiB 135.70GiB -- --------- --------- --------- -------- ----------- Total 164.00GiB 1.00GiB 32.00MiB 135.70GiB Used 163.59GiB 616.27MiB 48.00KiB For some reason you are using the DUP profile for data, convert to single.
  4. One thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  5. Pool has dual data profiles, run balance to single again, if it fails post new diags.
  6. Not necessary, but an option to make sure all went well.
  7. If you have email reports enable you'll get a more detailed report.
  8. There's no link detected on eth0, there is on eth2, eth0 is the main NIC used by Unraid, you can change which on is eth0 on Network Settings -> Interface Rules (reboot required), also if you want to use the onboard NIC you need to update to v6.9-rc1.
  9. I believe that's normal for UD devices, they will show correct usage on the MAIN page.
  10. If you know thew assignments yes, you can then check "parity is already valid" before array start, just make sure no data drive is assigned to a parity slot.
  11. Please post the diagnostics: Tools -> Diagnostics
  12. When there's nothing on the log it's usually a hardware issue, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  13. It might help if you mention what error you're getting, array looks fine to me.
  14. UD where the docker device is is almost full: Filesystem Size Used Avail Use% Mounted on /dev/mapper/UASSD1 239G 231G 8.2G 97% /mnt/disks/UASSD1 That could be a problem, suggest freeing up some space and recreating the docker image, don't let it go above 90%.
  15. It is, but if the movie folders already exist on disk6 it will go there, check for those.
  16. You'd need to ask in the plugin support thread.
  17. Looks more like a power/connection problem, if you already replaced the SATA cable do the same for power, if it keeps happening after that it could be the disk.
  18. Correct, as far as Unraid is concern they are both the same drive. Unless you can change the ID in the RAID controller not much else you can do, this is one of the reasons we don't recommend RAID controllers.
  19. Strange, don't see any mention of the LSI in the log, like it's not there, try a different slot if available.
  20. According to the diags it's completely stuck at the moment, but can't the see the reason for it, reboot in safe mode, start array in maintenance mode and start over, also there is some log spam from CA backup and an unassigned disk, see if you can fix that.
  21. If you have the space you can convert back to raid1 and then remove a device, both procedures are in the FAQ pinned on this sub-forum.
×
×
  • Create New...