• Content Count

  • Joined

  • Last visited

  1. I have now made following: removed array md0 from fstab umount -l /dev/md0 mdadm --stop /dev/md0 mdadm --zero-superblock /dev/sdb mdadm --zero-superblock /dev/sdc reboot ... This was clearly Software issue - now it works with all disks connected. Perhaps anyone else with similar problem?
  2. Hi, Yes - System activity led is blinking Yes - power indicator led is also on System is not possible to reach either by console or network STEP-1 I have tried starting system without mentioned disk on SATA port 4 and then is OK (access possible). STEP-2 I changed SATA cable for port4 and reconnecting disk - system becomes unnaccessible again. STEP-3 I have tried starting system without disk on SATA port 3 and then is OK (access possible). STEP-4 I tried and changed SATA cable for port 3 and reconnecting disk - system becomes unnaccessible again. My result: If Disks on SATA3 and SATA4 are both connected - system doesnt start. Last operation (before malfunction) was creating mirror (inside OpenMediaVault) between this two disks (both 1TB - on SATA 3 and SATA4 ports ) Is it a SW bug of some sort? Info: At this point data loss is not a problem - I have this for testing purposes for now. Regards
  3. Hi, I'm new proud user of Helios4 Batch3. I started to "play" with different options on this board - and after a 24 hours of use - board doesnt start anymore. Status led blinks but and disk leds blink for short time. It is not possible to connect via terminal console or network. I'think that problem (at least logs point that way) with missing or unavail mount point or (one) disk problem. But nevertheless I think that system itself should still be accessible. Am I wrong? Some disks can fail but not all mount points reside on them. If I disconnect all disks (physically) then connection(s) is/are possible again. I'm still completely new to this board and system. Please advise. Regards.