Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. This means filesystem corruption, likely the result of the NVMe device dropping offline, a scrub might fix it, also see here for better pool monitoring.
  2. Check filesystem on disk3, also good idea to convert all reiserfs disks to xfs.
  3. Check all paths on Settings -> VMs, diags also might give more clues.
  4. Cache device dropped offline: Feb 4 08:35:37 Tower kernel: ata9: hard resetting link Feb 4 08:35:37 Tower kernel: ata9.00: both IDENTIFYs aborted, assuming NODEV Feb 4 08:35:37 Tower kernel: ata9.00: revalidation failed (errno=-2) Feb 4 08:35:37 Tower kernel: ata9.00: disabled Feb 4 08:35:37 Tower kernel: ata9: EH complete Before that there were some media errors so, possibly a failing device, but since it dropped there's no SMART, power cycle the server and run an extended SMART test.
  5. Make sure you sue the md device if they are still in the array or you need to specify the partition if not, e.g.: xfs_repair /dev/md1 xfs_repair /dev/sdX1
  6. You can always backup and recreate the flash drive, then restore only super.dat and the key, both from the config folder, all users shares will be recreated at first array start, user shares are just top level folders, but they will use default settings.
  7. Try this and then post that log after a crash.
  8. JorgeB

    CPU Usage

    Dashboard include IOWAIT.
  9. The problem appears to be the Marvell controller, and they are known for dropping devices, it's also affecting your cache device which is the other device connected there, see below for a list of recommended controllers:
  10. HP expanders (or any SAS expander) should work with any SAS controller, I have one with an LSI, though IIRC you do need an HP controller if you want to update its firmware.
  11. Make sure "power supply idle control" is correctly set.
  12. You need to manually move some data (or a vdisk) from disk1 to another disk, vdisks are also much better on a cache device/pool, or performance will suffer a lot due to parity, also make sure to update to latest stable.
  13. Yep, you can alos swap cables/slot just to rule that out. Sorry, never used NFS.
  14. Both don't look good, you can run an extended SMART test to confirm.
  15. The test didn't finish. Yes, if the original drive is not detected or the SMART test fails. Rebuild would be the size of the new drive. Don't understand what you mean.
  16. Try replacing/swapping cables, both power and SATA, it the disk1 remains missing no way to rebuild disk2 with single parity.
  17. Do you mean the drive is not available in Unraid? This can only be a drive or connection problem, if it ends showing up you should also run an extended SMART test to confirm if there are pending sectors or not.
  18. If the cache is unmountable array can be started in normal mode.
  19. Most likely: Feb 3 11:22:24 STOWER20 kernel: aacraid: Host bus reset request. SCSI hang ? You can try a different slot if available.
  20. Platter density does more for performance than RPMs, there are 5400rpm drives cables of 200MB/s+ (on the outer sectors), older 7200RPM drives can be much slower than that, obviously if you compare same density with different RPMs the 7200rpm wins, e.g.: Older WD Green/Red/Blue that used 1TB platters, like 1, 2, 3 and 4TB models, speed starts at around 150MB/s and ends at around 80MB/s. Toshiba P300, same 11TB platters @ 7200rpm speed starts at 200MB/s and ends at around 100MB/s.
  21. Cache filesystem is corrupt, likely the result of the previous issues, best to re-format and restore data from a backup, if there's important data and no backups there are some recovery options here.
×
×
  • Create New...