Jump to content

JorgeB

Moderators
  • Posts

    67,574
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Feb 16 15:44:29 iT3640-DURS kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices. Feb 16 15:44:29 iT3640-DURS kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
  2. 1st upgrade parity, then the disk.
  3. You should also post the diagnostics, it might give some more clues.
  4. Diags are after rebooting so we can't see what happened but the disk looks OK, I would replace/swap cables to rule them out them rebuild on top.
  5. No, but if you have a backup of libvirt.img you can just restore that.
  6. Not seeing any cache issues, but might have missed it because of all the log spam.
  7. Disk dropped offline so there's no SMART, power down, check connection and post new diags.
  8. Click the format button, next to array start/stop.
  9. You can jus wipe them and them Unraid will offer to format, with the array stopped wipe both with: blkdiscard /dev/sdX Start array and format.
  10. Rebooting suggests more a hardware issue but you can try this to see if it catches anything.
  11. No sorry, don't remember ever seeing anything like this before, If you swap HBAs does the problem follow the HBA or stay with the same disks?
  12. All of them, it takes around 80 secs for each.
  13. That suggests the USB flash drive is not mounting at /boot, make sure the flash drive is in a USB 2.0 port.
  14. Correct, use the original assignments. No need if the above is true, just check "parity is already valid" before first array start.
  15. Cache device dropped offline: Feb 15 01:04:15 MNAS kernel: ata3: hard resetting link Feb 15 01:04:20 MNAS kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 15 01:04:30 MNAS kernel: ata3.00: qc timeout (cmd 0xec) Feb 15 01:04:30 MNAS kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 15 01:04:30 MNAS kernel: ata3.00: revalidation failed (errno=-5) Feb 15 01:04:30 MNAS kernel: ata3.00: disabled Check/replace cables.
  16. It's failing to balance and remove the other device due to corruption, best bet is to backup and re-format the pool.
  17. It's a known issue: https://forums.unraid.net/bug-reports/stable-releases/683-shfs-error-results-in-lost-mntuser-r939/
  18. Cache filesystem is severely corrupt, you should backup and re-format, also good idea to run memtest to check the RAM for errors.
  19. Problem appears to be the 2nd LSI, it's timing out waiting for the devices, try swapping them around or using different slots if available.
  20. Difficult to say if it will help or not.
  21. Sorry, meant -l, but it confirms there's GPT corruption, you can usually fix that with gdisk, use gdisk with each data disk: gdisk /dev/sdX Will should also detected the corrupt GPT and if you type w it will write the corrections, the try to start array again.
  22. Better would be to have a second server as a backup, but you can also use some drives with the UD plugin to backup some or all your data, you'd need to use scripts with rsync or similar.
  23. Those errors are quiet common, see them in many diags.
×
×
  • Create New...