This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 41%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
What to do when our AKS shows a node to have a: "EXT4-fs (sdc): Remounting filesystem read-only"? And how do you think this may have happened, i.e. for the node to go from a Ready condition to a ReadonlyFIlesystem condition?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 4%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hello
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Michailidis, Tony (DFO/MPO),
I have provided information to your query, did you get a chance to look into it. If you have further queries, please let me know. If the solution is helpful, please click Upvote.
Thank you.
Hi Michailidis, Tony (DFO/MPO),
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
The possible causes for the node to go from a Ready condition to ReadonlyFilesystem condition are if the disk size is full, it may change to read only mode, if there are any node's underlying corruption or hardware issues.
Please try below troubleshooting steps which might help you:
Check the Node status and describe the Node which is in NotReady state. Once try restarting the Node. Try unmounting and remounting the file system. Check the disk size if it is full df -h
For more information, please check: Node Problem Detector (NPD) in Azure Kubernetes Service (AKS) nodes
Troubleshoot Linux virtual machine boot issues due to filesystem errors
If you have further queries, please do let us know.
@anashetty Yes, thank you. Pressure on the disks was detected and once that went away it went back to "ready".
Hi Michailidis, Tony (DFO/MPO),
If the answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. Thank you for helping to improve Microsoft Q&A!