Jump to content

JorgeB

Moderators
  • Posts

    67,662
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Use UEFI tools instead, or use Free DOS with and older board without a UEFI BIOS.
  2. Yes. Expander is using an old firmware, though most likely that is not the problem, it should still be updated as mine improved performance considerably with the latest one, mostly when using a lot of devices, but if those errors persist after updating then there are other issues, I updated mine with Windows, easier since it didn't require installing anything else, instructions are included in a txt that comes with the download. Also a month ago you posted this in another thread: What hardware changed between then and now? Or was that an assumption? At the time I understood you already had that combo.
  3. This time is was a controller problem, it affected all disks: Jul 8 02:25:02 NAS kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0007 address=0xccebc000 flags=0x0000] Jul 8 02:25:02 NAS kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0007 address=0xccebc480 flags=0x0000] This is quite common with some Ryzen boards, look for a BIOS update or use an add-on controller.
  4. If there's nothing logged about the crash it suggests a hardware issue, you can try running the server in safe mode without dockers/VMs for a few days, if it crashes like that it's likely a hardware problem, if it doesn't start turning the services on one by one.
  5. Yes, it's IT mode only. Yep, though kind of unusual by that much.
  6. It is, and running Ryzen with overclock RAM is known to cause data corruption, see here for more info.
  7. This is likely the problem, though it should still be usable if you create individual raid0 volumes for all disks, but ideally you want to use a HBA, not a RAID controller with Unraid,lkike the LSI 9211-8i, 9207-8i, etc.
  8. Disk dropped offline so there's no SMART report, but looks like a controllers problem there are ATA errors in multiple disks, that Asmedia controller is just a 2 port controller with SATA port multipliers and they are known to have issues with Unraid/Linux, you should replace it with a recommended controller.
  9. You should start by posting the diagnostics: Tools -> Diagnostics.
  10. If you mean run without parity yes. Yes.
  11. Parity protection will only be added when you add a disk to the parity slot. Entire disk. Parity needs to be the same size or larger than the largest data drive drive.
  12. That's not unusual for files than end up on lost+found, you need to check one by one and rename.
  13. Likely gone, the result of the filesystem corruption. Yep. No, it would rebuild the same contents as now, parity can't help with filesystem corruption, also you should always have backups of anything important.
  14. Don't hand understand the question, but Unraid will partition and format the disk before use, full disk capacity will be used.
  15. Yes, assign it as data disk, but it will need to be formatted before use.
  16. What setting are you using for eht1? It can't be in the same subnet and you should leave the gateway blank.
  17. Looks like a RAM problem, you can also test the current DIMMs by using one at a time.
  18. It's showing at 30% used, so it wasn't formatted, could be the result of filesystem corruption, check the lost+found folder, there could be something there.
  19. This means a problem with the flash drive, make sure you're using a USB 2.0 port, and if it keeps happening try a different flash drive.
  20. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  21. That's the one I'm using, is the expander on the latest one also?
  22. Cache pool(s) only work with user shares.
  23. And forgot to mention, you don't, the other parity could remain as is, since no data drive would be larger than 16TB.
×
×
  • Create New...