- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Omnistack systemd-journald failed to write entry i...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 01:56 AM - last edited on 07-03-2023 08:55 AM by support_s
06-26-2023 01:56 AM - last edited on 07-03-2023 08:55 AM by support_s
Omnistack systemd-journald failed to write entry ignoring read-only file system
I have 2 hosts with hpe simplivity and omnicube 2 node. Can I restart omncube 39? What should I do?
warning all guest
guest omni
esxi 2 host
warning
- Tags:
- storage controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2023 02:49 AM
06-28-2023 02:49 AM
Re: Omnistack systemd-journald failed to write entry ignoring read-only file system
Hi semaphore,
Please check if the OVC 37 has 4 IP addresses. If yes, you can reboot OVC 39.
In case OVC 37 doesn't have 4 IPs, then please check for any Storage HA violations using svt-vm-show --violations. If all VMs are in storage HA, it is safe to reboot. Powered down VMs and templates may appear as non Storage HA compliant and is an expected behavior.
Moreover, please check hardware status of host of OVC 39 and check if all drives and RAIDs are healthy. You can follow up OVC shutdown with a host reboot as well if possible after putting the host in maintenance mode.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2023 11:51 PM - edited 07-05-2023 11:52 PM
07-05-2023 11:51 PM - edited 07-05-2023 11:52 PM
Re: Omnistack systemd-journald failed to write entry ignoring read-only file system
thank answer
From what I have studied and found that this problem occurred after the power in the sever room went out. After that, I turned it on and found that The back light of the node 38 card pci accetor server is red and yellow which is different from the host 36 that is the same cluster. It is green so I think it's possible that the problem might be caused by a bad pci.
yes ip 4 ip at vm 37
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2023 06:46 AM
09-08-2023 06:46 AM