Jump to content

steve1977

Members
  • Content Count

    943
  • Joined

  • Last visited

Community Reputation

2 Neutral

About steve1977

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am starting to think that this may indeed be a different topic. Maybe disk 9 is even faulty rather than my "common" controller / cable issue? I tried to run a SMART on disk 12, but failed. Any insights from the diagnostic on disks 9&13 or 12? Thanks! tower-diagnostics-20190819-2305.zip
  2. And here we go. The cables of disks 9 & 13 are indeed quite old. Disk 12 has rather new cables (disk 12 is disabled and connected to M1015). So if the issue now is disk 9 & 13, I will look into new cables over the weekend. Updated log attached. Thanks! tower-diagnostics-20190819-1837.zip
  3. Oh... Very interesting... I never had a single failed disk on a disk connected to the onboard controller. Also disk 12 is on the M1015. So, this is something different this time. Let me unplug and replug disks 9 and 13. Will get back with a new log shortly. If error remains on non-M1015 disks, I'll do the recabling. This is indeed new!
  4. Same old controller issue I am facing 😞 Thought it was solved, but seems it is back. I wish it was a cabling issue, but very unlikely. I just fail to get the M1015 to run stable. Will spend some more time on it over the weekend. Maybe a dedicated fan for the M1015 will help. It gets incredibly hot, which is what I believe is causing the unstable connection of disks connected to the M1015.
  5. Btw, you may see in the log that I bought a new controller card. Just to avoid that the card is the issue. This should already be flasghed to IT mode?
  6. Weird... The disk just reappeared without me doing anything. I started to rebuild the parity, but this is not gonna go anywhere give slow speed... Attached a new log. tower-diagnostics-20190819-1728.zip
  7. And here we go with the log. tower-diagnostics-20190819-1712.zip
  8. It seems like a second disk is disabled now. Shall I just set up a "new config". I don't think I have written a lot to the disabled drives, so hopefully no data loss. Thoughts?
  9. I think it depends what version of Clover you had installed when installing High Sierra? If sufficiently recent, the update should go through. If too old, you may need to update Clover. Unfortunately, I don't know how to update Clover.
  10. Thanks. Let me give this a try. Did you eventually get Picard 2.1.3. to work?
  11. I assume this will become easier once Catalina is officially released?
  12. I have some issues with my M1015 controller card. One harddisk got disabled by an error, which was likely caused by a cable/controller rather than a harddisk error. Upon rebooting Unraid, the disk completely disappeared (disk 12) and I can no longer see the disk at all. It shows unassigned. Coincidentally, my cache drive also shows "unassigned". I had an NVME assigned to it before reboot. I can re-add it (the NVME shows). It then shows "blue" (not "green"), which seems strange as this was working before the renboot. Any thoughts? Log attached. tower-diagnostics-20190804-0123.zip
  13. Thinking to upgrade to allow me to run 3-4 VMs in parallel rather than 2 now. Also need the single core speed for gaming on one of the three VMs. Does this upgrade make sense?
  14. Can Unraid help me in trouble-shooting what's causing the issue? Or do you have a best guess? Mobo should not be the issue: M/B: ASUSTeK COMPUTER INC. PRIME X299-A Version Rev 1.xx BIOS: American Megatrends Inc. Version 0402. Dated: 06/13/2017 CPU: Intel® Core™ i7-7800X CPU @ 3.50GHz HVM: Enabled IOMMU: Enabled Cache: 384 KiB, 6144 KiB, 8448 KiB Memory: 32 GiB DDR4 (max. installable capacity 3072 GiB)