Jump to content

JorgeB

Moderators
  • Posts

    67,797
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If you need more help with this please use the existing plugin support thread:
  2. Then it's likely a disk problem, despite the healthy looking SMART.
  3. What Unraid release? Some NIC detection issues were fixed on 6.10.3, so make sure you're on that release.
  4. Jun 17 18:09:46 unRAID kernel: FAT-fs (sda1): Directory bread(block 15303) failed Jun 17 18:09:46 unRAID kernel: FAT-fs (sda1): Directory bread(block 15304) failed Jun 17 18:09:46 unRAID kernel: FAT-fs (sda1): Directory bread(block 15305) failed Jun 17 18:09:46 unRAID kernel: FAT-fs (sda1): Directory bread(block 15306) failed Jun 17 18:09:46 unRAID kernel: FAT-fs (sda1): Directory bread(block 15307) failed Flash drive problems, you can first try backup and reformatting it, if more issues you should replace it.
  5. Do you have a previous flash backup or do you know how every device was assigned?
  6. The link above should help you fix that, but can't really help more than that since this is not my area of expertise.
  7. For now you can only have one array, you could create a two disk raid1 btrfs pool, multiple arrays have been mentioned as a possible future feature.
  8. Note that Marvell controllers are not recommended because they can sometimes drop disks without a reason.
  9. I didn't mean a PSU limit, but you could have a cable issue.
  10. Try replacing both cables, power and SATA, if you don't have new ones swap both cables with another disk and try again.
  11. 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller [1022:780c] Subsystem: ASRock Incorporation FCH IDE Controller [1849:780c] Kernel driver in use: pata_atiixp Kernel modules: pata_atiixp Controller is still in IDE mode.
  12. You can use the command above but then would need to reset the pool with Unraid before next array start, best to use the the other option.
  13. Everything looks go so far, all disks are mounting and there are no read errors, if there are errors during the sync grab new diags before rebooting.
  14. Could just be causing a voltage drop on that cable.
  15. If the old flash is still in use get the /boot/config folder, all you need is there, including the key.
  16. Diags after after stopping the array so not much to see, grab new ones during data transfer.
  17. You don't need to delete dockers:
  18. AFAIK nothing changed from 10.2 to 10.3 that would affect the Realtek NIC, please post the diagnostics from 10.3
  19. Two of the SATA ports are set to IDE, go into the BIOS and change them to AHCI/SATA, usually ports 5/6, this is a known issue with these AMD chipsets and it's where parity is connected.
  20. What do you mean by this? After updating you don't need to touch any cfg files, also please post the diagnostics.
  21. Enable the syslog server and post that after a crash.
×
×
  • Create New...