Jump to content

JorgeB

Moderators
  • Posts

    67,435
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Difficult to say what exactly is the problem, sometimes the device resets, others there's a fault with the HBA, best bet would be to use the AMD onboard SATA ports, though I believe they are still from Asmedia they are not x1 like the extra Asmedia controllers, so performance should be normal.
  2. Easiest way is to clear it with blkdiskcard (after the backup is done) -stop array blkdiscard /dev/nvme0n1 -start array -there will be an option to format the cache
  3. Cache filesystem is corrupt, best bet is to backup, re-format and then restore the data.
  4. Without parity you need to do a new config. (tools -> new config)
  5. Please post the diagnostics: Tools -> Diagnostics
  6. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  7. Both disks are failing the extended SMART test so they need to be replaced.
  8. Please post the diagnostics: Tools -> Diagnostics (ideally after the problem and before rebooting)
  9. You're overclocking the RAM, known issue, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  10. Usually the parity just needs updating, there's a chance of corrupt files if the server was writing some when the unclean shutdown happened.
  11. Look for a bios update.
  12. Rebuild on top but it it happens again to the same disk in the near future consider replacing it, I would also recommend replacing/swapping cables first to rule them out.
  13. That's normal, just type old one twice.
  14. Not idea why this is happening: May 2 16:04:52 M93p kernel: e1000e 0000:00:19.0 eth117: renamed from eth1 Try deleting network.rules.cfg (flash/config), then reboot, also make sure there's an IP address configured, static or dhcp.
  15. Parity still needs to be synced, it doesn't matter if there's data or not.
  16. Parity check accomplishes the same as an extended SMART test, so as long as it's regularly done, like once a month, it will catch any issues.
  17. It is, but if for example someone starts without cache it will be created on the array, and it won't be moved unless the services are disabled by the user.
  18. Looks like a problem with the enclosure, there was a reset and lost communication with all disks: May 3 04:41:15 Tower kernel: scsi 3:0:13:0: Enclosure NETAPP DS424IOM3 0212 PQ: 0 ANSI: 5 May 3 04:41:15 Tower kernel: scsi 3:0:13:0: Power-on or device reset occurred
  19. Most likely faulty of nothing works there.
  20. Wait for the extended SMART test to finish and check the result (or post SMART report).
  21. Also is that a real LSI or some crossflashed controller form Dell or other brand? These can sometimes require disabling SMBbus on PCIe.
  22. Yes, and a single error is no case for concern, but if it keeps rising replace the SATA cable. A few reallocated sectors can be OK, especially if they remain stable, if it keeps climbing it's best to replace it.
  23. Latest for both r2.3 for board and 20.00.07.00 for the LSI. Unlikely, unless nothing works on those slots, make sure you do a CMOS reset.
  24. It should work on any slot, and by coincidence I have the same board with a 9207-8i in one of the CPU slots, make sure both bios and LSI firmware are up to date and reset CMOS on the board.
×
×
  • Create New...