• Content Count

  • Joined

  • Last visited

Community Reputation

26 Good

1 Follower

About Helmonder

  • Rank
    Advanced Member
  • Birthday 03/22/1971


  • Gender
  • Location
    The Netherlands, Eindhoven

Recent Profile Visitors

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

  1. Rebuild and repair done, all good ! Verzonden vanaf mijn iPhone met Tapatalk
  2. I know... the disk got thrown off the array though... Now doing a rebuild on itself and simultaneously also doing the repair...
  3. Any idea ? Jun 10 18:41:43 Tower kernel: XFS (md8): Corruption warning: Metadata has LSN (1:2006775) ahead of current LSN (1:2006631). Please unmount and run xfs_repair (>= v4.3) to resolve. Jun 10 18:41:43 Tower kernel: XFS (md8): Metadata corruption detected at xfs_agi_verify+0x63/0x12e [xfs], xfs_agi block 0x2 Jun 10 18:41:43 Tower kernel: XFS (md8): Unmount and run xfs_repair Jun 10 18:41:43 Tower kernel: XFS (md8): First 128 bytes of corrupted metadata buffer: Jun 10 18:41:43 Tower kernel: XFS (md8): metadata I/O error in "xfs_read_agi+0x7c/0xc8 [xfs
  4. https://tweakers.net/aanbod/2736776/supermicro-x9scm-f-met-1230-v2-33ghz-en-16gb-ecc-memory.html Verzonden vanaf mijn iPhone met Tapatalk
  5. Think I found it allready, you are a life saver… I connected the cage fan directly to the motherboard… It appears i can connect the fan to the cage and the cage to the motherboard. With the wat I connected it right now the cage does not see the fan and alerts… It also explains why in reality everything worked fine :-) Will check for real this afternoon, but wuite positive this is the issue ! Verzonden vanaf mijn iPhone met Tapatalk
  6. CSE-M35T-1B Verzonden vanaf mijn iPhone met Tapatalk
  7. oeh… that is a good one… i was in contact with supermicro and they confirmed that the only beep like this is for overheating and that could not be the case here… did not think of the cage itself as a potential.. it has been in the server for a longer amount of time (though unused and unplugged for years).. i will check that this weekend !
  8. That is not likely since the fan on the cage is powered by the motherboard and that fan is also plugged in when the cage is not, and then everything works..
  9. I read that…. “System overheat condition” but as said that does seem very unlikely if that happens immediately after a powerup when 1 extra drivecage is connected… unplug it, power up, no beep, powerdown, plug in, power up, beep.. That cannot be an overheat condition..it -does- seem to be power related though… Verzonden vanaf mijn iPhone met Tapatalk
  10. Hi, This weekend I added another M1015 in my system to add another 5 disks. The M1015 was flashed fine and when I add one SSD to that adapter that adapter is recognised fine in unraid and that SSD is now part of my cache pool (this to confirm that adding the card works). Now the moment I give my drive cage power and startup my system my server starts beeping continuously (and immediately at boot). This long beep normally means something like an overheat but I do not think that is likely since it happens immediately at startup.. My setup: Supermicro X11SSM-F, Version 1.01 In
  11. Solved it… unrelated issue… cache drive was full.. Verzonden vanaf mijn iPhone met Tapatalk
  12. Just had to reboot unraid…. After the reboot farming is unavailable and an error in connection… Been like that for an hour, can that still be a startup thing that will solve itself or is something else wrong ? Verzonden vanaf mijn iPhone met Tapatalk
  13. Hi ! Sofar I have created 7 plots and that is continuing nicely. I am wondering however: how can I actually determine that the -farming- is working ? I am aware that it can take months and months before there could be any payout, but I do not see any indication that there is something going that is “farming” (besides the “farming active” on the main page). How can I see that I am at least -trying- to create a profit ? Verzonden vanaf mijn iPhone met Tapatalk
  14. Soon (tm) is the answer you will get out of the forum ;-)
  15. Its still just sitting there…. Cache drive has more then enough free… 100g+ .. I removed the plots and restarted the process with 1 plot at a time.. I had been fiddling with the type of cache drive (Only, Prefered). I can imagine that had created some conflicting data.. Since this morning it is tugging along at its first plot and now sitting at 3:4 but still running.. So I am guessing all is fine now !