Jump to content

JorgeB

Moderators
  • Posts

    67,675
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Log is being spammed, reboot and post new diags after array start.
  2. It's logged as a disk problem, but in LBA 0 which is strange, still should run an extended SMART test, if the test passes swap cables/slot with another disk to rule that out.
  3. Disk dropped offline so there's no SMART report, this is usually a power/connection problem, check/replace cables and post new diags.
  4. Nothing logged before the reboot, that points to a hardware issue.
  5. Syslog is being spammed with USB errors which makes it much more difficult to look at, but yes the issue is on 4 drives using the same controller, they likely also share the same miniSAS cable, could also be a power issue if they also share that, it's these disks: Jul 31 04:49:17 Apollo kernel: md: disk4 read error, sector=2933128232 Jul 31 04:49:46 Apollo kernel: md: disk1 read error, sector=2933128232 Jul 31 04:49:46 Apollo kernel: md: disk3 read error, sector=2933128232 Jul 31 04:49:46 Apollo kernel: md: disk0 read error, sector=2933128232
  6. SSDs have the same size, but the first one was was likely formatted before v6.9.x, the new alignment now makes them have a smaller partition.
  7. Run reiser fsck with the --rebuild-tree option on the disks that were asking for that.
  8. Possibly a connection/power problem on that disk, but could also be related to the previous issue.
  9. No, that's just a flash drive backup, you should also backup your appdata folder.
  10. That's good, FYI there was a way to possibly also recover any data on the failed disk, but because you're rebuilding parity that's no longer possible.
  11. You need to format the disk before use, after array start, next to array start/stop buttons.
  12. Issue starts with this: Jul 31 11:43:47 NAS kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0007 address=0xce464000 flags=0x0000] Device 01:00.1 is the AMD SATA controller, after these errors the disks drop offline one by one: Jul 31 11:44:53 NAS kernel: ata1: reset failed, giving up Jul 31 11:44:53 NAS kernel: ata1.00: disabled Jul 31 11:45:19 NAS kernel: ata6: reset failed, giving up Jul 31 11:45:19 NAS kernel: ata6.00: disabled etc
  13. Problem with the onboard SATA controller, all the devices dropped offline, quite common with some Ryzen boards, look for a BIOS update or use an ad-don controller.
  14. This is one of the reasons we don't recommend USB enclosures, they usually don't pass the correct serials, if parity is still valid there might be a way out, please post current diagnostics.
  15. Without nothing logged we can't see what the problem is, and this is usually hardware related, but try downgrading to see if it helps.
  16. Nothing being logged before the crash suggests a hardware problem.
  17. Nothing being logged suggests a hardware issue, is this the actual CPU you're using? Intel(R) Core(TM) i7-5775C CPU @ 3.30GHz This is not on the list of supported CPUs for that board, firstly it only supports 4th gen Core series CPUs, secondly it doesn't officialy support i5 or i7, only the equivalent Xeon, you might want to try using a supported CPU to see if that's the problem.
  18. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  19. You should post the complete diags, in case there are known issues with that hardware, you can also enable syslog mirror to flash then post that log after a crash.
  20. Array can be online as long as the disks are not actively in use, some reads/writes won't delay the test by much, but it it's being used constantly then it can take much longer.
  21. I would prefer to be on site, but if you have notifications enable to be able to cancel the rebuild if anything goes wrong it should be fine.
×
×
  • Create New...