Jump to content

JorgeB

Moderators
  • Posts

    67,582
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. With the array stopped use wipefs on both cache devices, first the partition then the device (all data there will be lost): wipefs -a /dev/sdX1 then wipefs -a /dev/sdX Start array and there will be an option to format cache.
  2. What options did you use the run the filesystem check? Make sure you do it without -n or nothing will be done, if you did it without -n post the output. Also note that Marvell controllers and SATA port multipliers are not recommend.
  3. Delete and recreate the docker image, but if it keeps getting corrupt out of the blue you likely have a hardware problem, like bad RAM.
  4. That's just the syslog, but if all disks look fine this seems like a good way to go: You still need to do a new config, then sync the new parity.
  5. No, it will show current link speed.
  6. Copy super.dat from the existing flash drive, in the config folder.
  7. 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.
  8. 1st upgrade parity, then the disk.
  9. You should also post the diagnostics, it might give some more clues.
  10. 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.
  11. No, but if you have a backup of libvirt.img you can just restore that.
  12. Not seeing any cache issues, but might have missed it because of all the log spam.
  13. Disk dropped offline so there's no SMART, power down, check connection and post new diags.
  14. Click the format button, next to array start/stop.
  15. 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.
  16. Rebooting suggests more a hardware issue but you can try this to see if it catches anything.
  17. 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?
  18. All of them, it takes around 80 secs for each.
  19. That suggests the USB flash drive is not mounting at /boot, make sure the flash drive is in a USB 2.0 port.
  20. Correct, use the original assignments. No need if the above is true, just check "parity is already valid" before first array start.
  21. 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.
×
×
  • Create New...