Jump to content

JorgeB

Moderators
  • Posts

    67,771
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Disk is OK for now, just keep monitoring.
  2. It's not as long as you know what you're doing, you can also temporarily limit a share to certain disks just for testing.
  3. Diags are not taken during the write, but disks 1 and 2 and SMR, do you get the same slow speeds when transferring to disks 3 or 4? If yes post new diags grabbed during a transfer.
  4. Docker image is corrupt, delete and recreate.
  5. Don't know about that, but no driver is being loaded for that NIC: 03:00.0 Ethernet controller [0200]: Aquantia Corp. Device [1d6a:94c0] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8812]
  6. Use the 9211-8i firmware, the onboard HBA should also be updated since all p20 releases except for the latest one (20.00.07.00) have known issues.
  7. No driver but you're using a very old Unraid release, try v6.9.2 or latest v6.10-0-rc4
  8. Seems unlike, other than trim possibly not working they should work fine, unless there's some firmware/compatibility issue, and it's using a very old firmware, so you should update to latest.
  9. Problem is that the driver for that NIC doesn't build with recent kernel releases, you can ask the manufacturer to see if they release an updated driver, if yes LT would likely include it in a future release.
  10. You can move from a disk share to another disk share and from a user share to another user share, just not from a disk share to a user share or vice versa. /mnt/cache and /mnt/temp are both disk shares so that's fine, anything with /mnt/user/share_name is a user share.
  11. Apr 21 18:59:16 MaxisNAS kernel: BTRFS info (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 192445355, gen 0 Btrfs is detecting a lot of data corruption, you should run memtest, if these are old errors you should run a scrub, delete any corrupt files and reset the stats.
  12. You can use the other Ethernet ports, but it must be set as eth0, you can just delete network-rules.cfg from the flash drive and reboot.
  13. No driver for that NIC, what version did you update from? IIRC it already didn't work with v6.9 because the driver didn't build with the kernel used.
  14. No valid btrfs filesystems are being found by btrfs device scan on boot, if there were they were wiped/gone sometime before this boot, the pools existed and were formatted?
  15. Bug is fixed on v6.10.0-rc4, so you can upgrade first then do the replacement using the GUI.
  16. Never a great sign but it should still be OK unless it keeps climbing, you can run an extended SMART test to confirm.
  17. Extended SMART test failed, that's all you need for an RMA.
  18. It's a known issue, fixed in v6.10-rc.
  19. Apr 20 05:36:49 Tower kernel: ahci 0000:00:17.0: Found 2 remapped NVMe devices. Apr 20 05:36:49 Tower kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
  20. There appears to still be something preventing any writes to the devices.
  21. Not with the information posted, full diags might show more, also worth trying to connect the drive to a SATA port.
  22. Often SAS drives come with some kind of format or encryption protection, see below if any of these help: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
×
×
  • Create New...