Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Try redoing the flash drive, backup the config folder, re-do it using the USB tool, restore the config folder.
  2. That might not be the only problem but you need to check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  3. This is a problem, you should be able to use the invalid slot command but don't remember if it was working correctly with that release, nor the steps needed for that particular release since it's been many years, maybe you can find something in the forum, if you don't post back I see if I can get 5.0.6 to boot on my test server.
  4. Cache disk is failing and needs to be replaced, if you need to repair the fs to recover data best bet is to clone it first with ddrescue.
  5. For RJ45 NICs look for Aquantia based NICs, like the Asus XG-C100C and similar, you can also look for used Intel NICs, if you want SFP+ Mellanox Connect-X 2 and 3 work great and can be found cheaply on ebay, Intel also a good option.
  6. Btrfs is fine with stable hardware, better with ECC RAM (but no required), it can be easily corrupted by bad hardware, especially bad RAM, in some cases devices dropping can also cause issues, and having a UPS is always good to avoid unclean shutdowns, some pool monitoring info here.
  7. Samba aio was enable for -beta30, it won't be for future releases since it can cause low read speeds with some devices, see if this makes any difference: -stop array -go to Settings -> SMB -add to SMB extras: aio read size = 0 -start array and retest
  8. Yep, that's only for -beta30 (and future releases).
  9. You search for the HBA model, not the chip used.
  10. Looks like this issue is finally going to be fixed with smartmontools 7.2: https://www.smartmontools.org/ticket/1336
  11. It means the filesystem is good and the data is available. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  12. Disk looks healthy, the emulated disk is mounting so if contents look correct you can rebuild on top. Good idea to update the LSI firmware since it's very old.
  13. blkdiscard /dev/sdX P.S.: -beta30 requires -f to force if there's an existing filesystem.
  14. You can try v6.9-beta, if that doesn't help contact LT and ask for v6.7.x
  15. Scrub is only done on the data/metadata, if you're moving the data not much point in scrubbing after, you could (and should) wipe them completely with blkdiscard before adding them to the other pool.
  16. Then only if you have a backup, 6.7.x is no longer available for download, best bet is to try and resolve the VM issue, you don't want to get stuck on an old release anyway.
  17. Diags after rebooting won't be much help, also don't forget to try safe mode.
  18. Try getting the diags on the console by typing "diagnostics", also make sure to see if it still happens if you boot in safe mode.
  19. If you upgraded with the GUI there's also an option to go back (Tools -> Update OS -> Restore).
  20. Both x8 slots are connected to the chipset, though it's still an older FSB design, still much better than the PCI 4 slot that uses the DMI. Also make sure the HBA and expander are connected using dual link (two cables). Restarting from the beginning using a x8 PCI 2.0 slot with dual link should be be faster than waiting 3 days, should...
  21. 8, any storage device counts, except optical drives, empty card reader also doesn't count.
  22. Currently the pool is only using 3 devices.
×
×
  • Create New...