Start a Conversation

Unsolved

C

1 Rookie

 • 

1 Message

8

August 22nd, 2024 02:16

S5296-ON system fs mounted read-only? how to diagnose and fix?

I'm trying to figure out what is wrong with my S5296-ON and ideally fix it.

Issuing most commands results in an error such as:

OS10# show event history 
Input/output errorTraceback (most recent call last):
  File "/opt/dell/os10/cli/scripts/robject.py", line 49, in robject_main
    t_str = rutils.apply_xsl(TEMPLATE_PATH+template_file, xmlstr, tmpl_param)
  File "/opt/dell/os10/cli/scripts/rutils.py", line 181, in apply_xsl
    xslroot = etree.parse (filename)
  File "src/lxml/lxml.etree.pyx", line 3427, in lxml.etree.parse (src/lxml/lxml.etree.c:81110)
  File "src/lxml/parser.pxi", line 1811, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:117841)
  File "src/lxml/parser.pxi", line 1837, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:118188)
  File "src/lxml/parser.pxi", line 1741, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:117100)
  File "src/lxml/parser.pxi", line 1138, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:111646)
  File "src/lxml/parser.pxi", line 595, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:105102)
  File "src/lxml/parser.pxi", line 706, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:106810)
  File "src/lxml/parser.pxi", line 635, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:105664)
  File "/opt/dell/os10/cli/render-templates/event_history.xsl", line 1
lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1

The system fs seems to be mounted read-only:

OS10# system mount

...
/dev/mapper/OS10-SYSROOT on /os10 type ext4 (ro,relatime,discard,data=ordered)
/dev/mapper/OS10-SYSROOT on / type ext4 (ro,relatime,discard,data=ordered)
/dev/mapper/OS10-SYSROOT on /home type ext4 (ro,relatime,discard,data=ordered)
/dev/mapper/OS10-SYSROOT on /config/certs type ext4 (ro,relatime,discard,data=ordered)
/dev/mapper/OS10-SYSROOT on /config/severity-profiles type ext4 (ro,relatime,discard,data=ordered)
/dev/mapper/OS10-SYSROOT on /var/lib/docker type ext4 (ro,relatime,discard,data=ordered)

...

This contrasts with a different switch where it is mounted read-write. And trying to remount it doesn't work either (though I'm not sure that I should expect it to):

OS10# system "sudo mount -o rw,remount /"
sudo: unable to mkdir /var/lib/sudo/ts: Read-only file system

...

sudo: unable to mkdir /var/lib/sudo/lectured: Read-only file system
mount: cannot remount /dev/mapper/OS10-SYSROOT read-write, is write-protected
%Error: while executing(system).Ret val[32].

I need to know why it's read-only and whether it can be fixed. I hesitate to reboot it in this state. Can anyone offer some advice?

Thanks very much in advance.

Moderator

 • 

2.4K Posts

August 22nd, 2024 08:14

Hello,

I reviewed it. It is hard to define what causes the read-only mode. It is difficult to understand at once what is causing the problem. And some of the steps that can be taken require serious steps and in-depth investigation. This usually means the system found a problem and switched the filesystem to read-only to avoid damaging data.
For example when the disk is completely full, the system might remount the filesystem as read-only. To check the logs, you can use the command dmesg | grep "EXT4-fs error". You can also run a filesystem check with fsck to identify any errors. However, these commands can be risky and might not work as expected. Do not attempt them and other commands you can find if you’re unsure. Since some advanced depth investigation is required, I recommend contacting and consulting your local support team under your warranty.

 

 

No Events found!

Top