Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 7 subscribers
  • Views 16692 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

After up2date, slave node death

papali

 Hi, after the reboot of the slave node after the up2date from 9.413-4 to 9.500-9 release, the boot stops with this error

If I try the command fsck /dev/sda6

$ sh: fsck.ddf_raid_member: not found

Any idea?

The node master is running ok.

Thanks.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to mod2402

    Yes Mod while I appreciate the subject line and understand I may not be configured for clustering, I have the exact same symptom and error messages caused by the same up2date to version9.500.9. I can start my own thread but searches in the forum led me here because of the error message. Something in that release caused this error.

  • 0 in reply to Varick Williams

    I contacted the sophos technical support but could not give me support because it was not possible to connect it remotely to a PC that I connected via the serial port to the slave node, then I decided to reinstall the slave node and rebuild the cluster.

    I tried connecting from a pc to the master node (that worked perfectly) but not even there it was possible to connect via serial port.
    Do I think it's only possible with appliances?

  • 0 in reply to papali

    Hi papali,

    you should connect via ssh to the master and then you can switch to slave with ha_utils ssh

    regards

    mod

  • 0 in reply to mod2402

    Hi mod2402, I tried, but there was only 1 node, probably the slave node failed to load the modules needed to be recognized as online?

Unfiltered HTML