[{"data":1,"prerenderedAt":58},["ShallowReactive",2],{"/2025/10/15-read-only-file-system-error-in-linux":3},{"id":4,"title":5,"body":6,"date":49,"description":46,"extension":50,"meta":51,"navigation":52,"path":53,"robots":54,"seo":55,"stem":56,"__hash__":57},"posts/2025/10/15 read-only-file-system-error-in-linux.md","15 Read Only File System Error In Linux",{"type":7,"value":8,"toc":45},"minimark",[9,18,25,28,31,33],[10,11,13],"post-title",{":date":12},"date",[14,15,17],"h1",{"id":16},"read-only-file-system-error-in-linux","Read-only File System Error in Linux",[19,20,21],"notes",{},[22,23,24],"p",{},"This is a repost from my old blog. First posted in 2/8/2019.",[26,27],"br",{},[22,29,30],{},"I was moving the content of CentOS boot drive to a new hard drive. CentOS has MBR partition with xfs file system. It worked great, boot fine, but when I tried to do yum install, it barked that it can't do the install because the file system is read-only.",[26,32],{},[22,34,35,36,44],{},"After a decent amount of research, I found out that the problem lies on the ",[37,38,43],"code",{"className":39},[40,41,42],"bg-gray-200","p-2","rounded","/etc/fstab",". Because it is new hard drive, the UUID is different and grub2-mkconfig used the new UUID to configure the grub.cfg. However, when it is booted, it checked the /etc/fstab and found the discrepancy. Once I changed the /etc/fstab to reflect the new UUID, the error went away.",{"title":46,"searchDepth":47,"depth":47,"links":48},"",2,[],"2025-10-15T00:00:00.000Z","md",{},true,"/2025/10/15-read-only-file-system-error-in-linux",null,{"title":5,"description":46},"2025/10/15 read-only-file-system-error-in-linux","1pv7rfouCrypAMgge9DryyO7lJRJ3eBzp98tdLruU-U",1785167452873]