Jump to content

JorgeB

Moderators
  • Posts

    67,108
  • Joined

  • Last visited

  • Days Won

    703

Everything posted by JorgeB

  1. You can only connect one cable (single link) or two cables (dual link and max link speed for best performance) to the backplane, hence why no point in having an HBA with more ports.
  2. That backplane has a bultin expander, you just need an HBA with 2 miniSAS connectors, like 9300-8i, no point in buying anything with more ports.
  3. No, I was just giviing some examples of the most common ones, the 9305-24i will also work fine, you can always google Unraid + HBA model you want and are likely to get some hits
  4. Any LSI with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc
  5. Both images are corrupt, you'll need to recreate them, libvirt should be restored from a backup if available or you'll lose the XML for the VMs , corruption most likely caused by one of you cache drives (cache1) dropping out in the past: Jun 26 15:38:58 unraid kernel: BTRFS info (device sdk1): bdev /dev/sdk1 errs: wr 469514164, rd 255940664, flush 10036587, corrupt 0, gen 0 These are read and writes errors, and a lot of them so it dropped out for some time, or multiple times, see here for more info on how to better monitor a pool.
  6. Not at this time, sorry, but I believe the HBA should work normally if you just use one of the standard PCIe slots, not the storage slot.
  7. Check the VM config and make sure "Initial Memory" and "Max Memory" are set to the same value.
  8. If current cache is btrfs you can do an online replacement, and can even continue to use it normally during it.
  9. I would run a few days in safe mode with all docker disable, if stable try turning on the dockers on by one, if still unstable it's likely a hardware problem, like PSU, etc.
  10. There are known issues with Ryzen and Linux, there are workarounds that work for most users, they are discussed here:
  11. OK, I see that: Jun 15 03:02:51 Tower root: Creating new image file: /mnt/user/system/libvirt/libvirt.img size: 1G Unraid is trying to create libvirt.img but it never gets created, there aren't also any errors or reason why it's failing to do it, weird issue, if possible I would try connecting the disk to the onboard controller and trying again, or make sure libvirt is created on a device using the onboard controller, like a cache device.
  12. Disk1 is mounting correctly: Filesystem Size Used Avail Use% Mounted on /dev/mapper/md1 3.7T 25G 3.7T 1% /mnt/disk1 Is is not available on the shares or what is exactly the problem?
  13. You need to check/swap connections for the missing disks, check if they are detected in the bios, very unlike two disks would die at the same time. A new config would allow you to start the array but by losing the data on both missing disks.
  14. Would need the diags to confirm but they are likely being detect with a different size, one of the possible issues when using a RAID controller.
  15. This happened recently to a user and I just confirmed it's a bug, starting on v6.7.0 when for example removing a device from a 2 device raid1 pool, the command changed from: balance start -f -dconvert=single -mconvert=single /mnt/cache && /sbin/btrfs device delete /dev/sde1 /mnt/cache & to balance start -f -dconvert=single /mnt/cache && /sbin/btrfs device delete /dev/sde1 /mnt/cache & The metadata isn't being convert to single profile, so the device delete will fail, and Unraid will keep trying every array start.
  16. Those call traces during parity check (and related bad performance) can usually be solved by lowering the md_sync_thresh value, though the current value is pretty low already.
  17. The error is unrelated to the email, and no idea waht's causing that, I only meant you should always replace a failing disk.
  18. It will work with SSDs that support read zeros after trim.
  19. Any pool requires btrfs, you can have multiple pools with some limitations and the help of UD, until Unraid supports them.
  20. Please post the diagnostics: Tools -> Diagnostics
  21. That's definitely not a Dell H310, looks like a SAS2LP, possibly a RocketRAID, there's at least one model that looks identical on the device list to the SAS2LP, but the missing drives issues appears to be limited to the Marvell 9230
  22. Dell H310 uses an LSI chipset and will work fine.
×
×
  • Create New...