soydemadrid

  • Content Count

    9
  • Joined

  • Last visited

  1. Hi thanks for helping. I've checked with a Multimeter and I'm only getting 0.3v or something very low on those pins. Basically no voltage at all - the PSU is ok though as it works with my other Helios4 no problem. So it does seem to be a dead Helios4 board if there is any way I can isolate the issue and fix it? Thanks again for any help
  2. Hi I wondered if anyone could please help me out. I have two Helios4 NAS drives and one seems to have blown and won't work. The other is fine. I've emailed Kobol too just to see if they can help but I hoped that maybe someone here may have a spare main board they can sell me or offer advice on how I can have the unit repaired? Thanks if anyone can please help. I'll be happy to buy your old unit etc if you're upgrading to the new Helios NAS or such anyway... Or if there is a way I can test where it is blown and replace the components with someone's help?? Thanks again
  3. Hi thanks for the replies - I think you're right in that the grep stuff doesn't have anything to do with my Helios becoming unreachable. Here is the output of the diagnostics: http://ix.io/1mNq With the LEDS I mean that 8 is on but the activity isn't blinking when the unit crashes or becomes unavailable. The output of less -x | less looks ok. There are listings of just my ssh remote access user and a few runlevel/reboot/shutdown entries but nothing looks weird... Thanks again for any help. I did wonder if it might be something going on with my ne
  4. I'm also getting loads of other weird errors before the above too like this: Tons and tons of them that go on for hundreds and thousands of entries - too much to list here but hopefully you get the idea...
  5. Hi I hope someone can please help. I keep finding my Helios4 with its lights out and inaccessible. I can't ssh in and have to just power it off and reboot. I can't find much to debug it, but I was using ssh today with it to grep some files and try find a few things and it suddenly spat out loads of errors all over the place as follows: I don't know if the above is related to my problem but I hope someone can fix as it is a real pain when I try to print something (I have an office Cups network printer on the Helios) or access Samba or such and they aren't there or availabl
  6. Hi thanks, I followed your link to other posts on here about it but there didn't seem to be a clear fix or instructions for the Helios4. Is there a simple way to disable it? Thanks
  7. Hi can anyone help. I've got CSF firewall running on my Helios4 and I keep getting emails saying that rsyslog isn't running. I checked the logs and it seems stuck at this error: liblogging-stdlog[10738]: action 'action 11' suspended, next retry is Sun Mar 11 15:36:43 2018 [v8.24.0 try http://www.rsyslog.com/e/2007 ] Is there any fix for this? Thanks for any help
  8. Hi thanks that did the trick and now console access if much easier and snappier!! Everything pinging nicely now too. Thanks again for the fix!
  9. Hi I've just received two Helios4 kits. I'm having some teething problems getting them both set up on my network though. My local network router is on 192.168.1.1 and has a dhcp pool of .3 to .150 I then have one Helios4 with a static IP set of .200 and the other Helios4 set as .250 They can both ping out no problem, both to 8.8.8.8 for example and google.com They can also both ping other devices on my local network and other devices can ping them... But the problem is they can't ping each other! Another odd thing is when