Arch Linux booting with read only filesystems












1














I installed Arch today and when I logged in I noticed that my filesystem is read only.



How can I fix this?










share|improve this question















migrated from stackoverflow.com Sep 10 '12 at 18:09


This question came from our site for professional and enthusiast programmers.















  • assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
    – behrooz
    Sep 10 '12 at 18:05
















1














I installed Arch today and when I logged in I noticed that my filesystem is read only.



How can I fix this?










share|improve this question















migrated from stackoverflow.com Sep 10 '12 at 18:09


This question came from our site for professional and enthusiast programmers.















  • assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
    – behrooz
    Sep 10 '12 at 18:05














1












1








1







I installed Arch today and when I logged in I noticed that my filesystem is read only.



How can I fix this?










share|improve this question















I installed Arch today and when I logged in I noticed that my filesystem is read only.



How can I fix this?







linux arch-linux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 13 '12 at 11:03









Mat

5,42812429




5,42812429










asked Sep 10 '12 at 18:00







user1659754











migrated from stackoverflow.com Sep 10 '12 at 18:09


This question came from our site for professional and enthusiast programmers.






migrated from stackoverflow.com Sep 10 '12 at 18:09


This question came from our site for professional and enthusiast programmers.














  • assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
    – behrooz
    Sep 10 '12 at 18:05


















  • assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
    – behrooz
    Sep 10 '12 at 18:05
















assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
– behrooz
Sep 10 '12 at 18:05




assuming fstab is misconfigured and /dev/sda1 is root.romount root as rw with mount -o remount,rw /dev/sda1 /;nano /etc/fstab-----and change fstab to mount it rw
– behrooz
Sep 10 '12 at 18:05










2 Answers
2






active

oldest

votes


















0














I would try to figure out why the boot process or kernel marked the file system as read-only.



Normally if something is detected during boot it will try to fix the filesystem with fsck and if it can't then not mount the filesystem.



I have seen running Linux servers switch their filesystems to read-only when there was a problem with the underlying SAN and the kernel couldn't write to the SAN.



As behrooz said, it might be something as simple - bug highly unlikely - as something changed your /etc/fstab file so that your filesystems are read-only.






share|improve this answer





























    0














    you might want to check your /etc/fstab.... do you see the flags as (rw). if not, you might want to boot from the install CD/USB Pen Drive and modify the fstab file to (rw).






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f472439%2farch-linux-booting-with-read-only-filesystems%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown
























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      I would try to figure out why the boot process or kernel marked the file system as read-only.



      Normally if something is detected during boot it will try to fix the filesystem with fsck and if it can't then not mount the filesystem.



      I have seen running Linux servers switch their filesystems to read-only when there was a problem with the underlying SAN and the kernel couldn't write to the SAN.



      As behrooz said, it might be something as simple - bug highly unlikely - as something changed your /etc/fstab file so that your filesystems are read-only.






      share|improve this answer


























        0














        I would try to figure out why the boot process or kernel marked the file system as read-only.



        Normally if something is detected during boot it will try to fix the filesystem with fsck and if it can't then not mount the filesystem.



        I have seen running Linux servers switch their filesystems to read-only when there was a problem with the underlying SAN and the kernel couldn't write to the SAN.



        As behrooz said, it might be something as simple - bug highly unlikely - as something changed your /etc/fstab file so that your filesystems are read-only.






        share|improve this answer
























          0












          0








          0






          I would try to figure out why the boot process or kernel marked the file system as read-only.



          Normally if something is detected during boot it will try to fix the filesystem with fsck and if it can't then not mount the filesystem.



          I have seen running Linux servers switch their filesystems to read-only when there was a problem with the underlying SAN and the kernel couldn't write to the SAN.



          As behrooz said, it might be something as simple - bug highly unlikely - as something changed your /etc/fstab file so that your filesystems are read-only.






          share|improve this answer












          I would try to figure out why the boot process or kernel marked the file system as read-only.



          Normally if something is detected during boot it will try to fix the filesystem with fsck and if it can't then not mount the filesystem.



          I have seen running Linux servers switch their filesystems to read-only when there was a problem with the underlying SAN and the kernel couldn't write to the SAN.



          As behrooz said, it might be something as simple - bug highly unlikely - as something changed your /etc/fstab file so that your filesystems are read-only.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 13 '12 at 10:57









          Lars Nordin

          1584




          1584

























              0














              you might want to check your /etc/fstab.... do you see the flags as (rw). if not, you might want to boot from the install CD/USB Pen Drive and modify the fstab file to (rw).






              share|improve this answer


























                0














                you might want to check your /etc/fstab.... do you see the flags as (rw). if not, you might want to boot from the install CD/USB Pen Drive and modify the fstab file to (rw).






                share|improve this answer
























                  0












                  0








                  0






                  you might want to check your /etc/fstab.... do you see the flags as (rw). if not, you might want to boot from the install CD/USB Pen Drive and modify the fstab file to (rw).






                  share|improve this answer












                  you might want to check your /etc/fstab.... do you see the flags as (rw). if not, you might want to boot from the install CD/USB Pen Drive and modify the fstab file to (rw).







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 5 '14 at 0:23









                  Ghassan

                  32624




                  32624






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f472439%2farch-linux-booting-with-read-only-filesystems%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                      Alcedinidae

                      Origin of the phrase “under your belt”?