Jump to content

JorgeB

Moderators
  • Posts

    67,064
  • Joined

  • Last visited

  • Days Won

    703

JorgeB last won the day on September 18

JorgeB had the most liked content!

Retained

  • Member Title
    On vacation, back in a week or so

Converted

  • Gender
    Male

Recent Profile Visitors

49,423 profile views

JorgeB's Achievements

Grand Master

Grand Master (14/14)

8.1k

Reputation

4k

Community Answers

  1. It's raid1, you can use this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480418
  2. Short test is not a great indication, you should always run the extended test, but based on the SMART report the disk should be OK.
  3. Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  4. Sep 18 17:26:47 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300) Sep 18 17:26:52 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 18 17:27:09 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 18 17:27:10 Tower kernel: ata6.00: configured for UDMA/133 Sep 18 17:27:10 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300) Sep 18 17:27:11 Tower kernel: ata43: SATA link down (SStatus 0 SControl 300) Sep 18 17:27:16 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Sep 18 17:27:17 Tower kernel: ata43: SATA link down (SStatus 0 SControl 300) Sep 18 17:27:17 Tower kernel: ata43: limiting SATA link speed to <unknown> Sep 18 17:27:22 Tower kernel: ata43: SATA link down (SStatus 0 SControl 3F0) Sep 18 17:27:22 Tower kernel: ata43.00: disable device Sep 18 17:27:22 Tower kernel: ata43.00: detaching (SCSI 43:0:0:0) Issues with multiple disks, and disk7 ended up dropping offline, this is usually a power/connection issue.
  5. That is expected, once a disk gets disabled it needs to be rebuilt. https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
  6. That's usually a good option, you can see some more here:
  7. It doesn't matter what is doing the writes, with writes to more than one disk
  8. Do you mean it's still disabled after replacing the cables or you replaced the cables and it got disabled again?
  9. It shows writes to disks 1 and 3 at the same time, turbo write will be disabled.
  10. If the flash drive has the same problem in a different PC it suggests it's not correctly created, try a different one.
  11. First screenshot show writes to multiples disks, turbo write is temporarily disabled when that happens, when it starts witting to a singe disk it should enable again.
  12. It's possible, if you can retest without anything connect to NFS shares
  13. That looks like a hardware issue, but please post the diagnostics.
  14. Since btrfs is detecting data corruption on both devices, first thing I would recommend is to run memtest. Then run btrfs rescue zero-log again, and if it mounts, backup what you can from the pool and then re-format.
×
×
  • Create New...