Why have all my files become read-only?












0















Okay so I was trying to install spotify onto my ubuntu...and I don't know what I did wrong, but I do not have spotify and all of my files have become read-only (everything in the file system has a padlock on it)!!! This means I cannot do anything in terminal without getting the error that it canot open anything because its a read only file system...any suggestions?



-



Thanks for replying so fast! I tried to follow these instructions on terminal ..none of the stuff was working anyway



Debian



1. Add this line to your list of repositories by



editing your /etc/apt/sources.list



deb http://repository.spotify.com stable non-free



2. If you want to verify the downloaded packages,



you will need to add our public key



sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59



3. Run apt-get update



sudo apt-get update



4. Install spotify!



sudo apt-get install spotify-client



Now i keep getting this error if I try and do a fsck: permission denied while trying to open /dev/sda1 you must have r/w access to the file system or be root.



I think the error happened when it kept telling me dev is not recognised so I tried to install devscripts...:( ...which was what someone else suggested (if you're having trouble installing spotify)




  • My history is just the following ..I was trying to do a screenshot but I cant save anything :(



24 vi/etc/apt/sources.list
25 deb
26 debc (spotify link) stable non-free
27 sudo apt-get install devscripts
28 debc http://repository.spotify.com stable non-free
29 deb (spotify link) stable non-free
30 apt-get install debian-reference
31 yes
32 sudo apt-key adv--keyserver.ubuntu.com--recv-keys 4E9CFF4E
33 sudo add-apt-repository "deb (spotify link) stable non-fr










share|improve this question
















bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

    – geirha
    Jul 18 '12 at 12:13











  • You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

    – Gibbs
    Jul 18 '12 at 12:23











  • I edited the answer above... i'll post all the history too. thanks for getting back so fast

    – Hala
    Jul 18 '12 at 12:29











  • where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

    – Hala
    Jul 18 '12 at 12:35











  • take a look at askubuntu.com/questions/7489/…

    – user827992
    Jul 18 '12 at 12:37
















0















Okay so I was trying to install spotify onto my ubuntu...and I don't know what I did wrong, but I do not have spotify and all of my files have become read-only (everything in the file system has a padlock on it)!!! This means I cannot do anything in terminal without getting the error that it canot open anything because its a read only file system...any suggestions?



-



Thanks for replying so fast! I tried to follow these instructions on terminal ..none of the stuff was working anyway



Debian



1. Add this line to your list of repositories by



editing your /etc/apt/sources.list



deb http://repository.spotify.com stable non-free



2. If you want to verify the downloaded packages,



you will need to add our public key



sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59



3. Run apt-get update



sudo apt-get update



4. Install spotify!



sudo apt-get install spotify-client



Now i keep getting this error if I try and do a fsck: permission denied while trying to open /dev/sda1 you must have r/w access to the file system or be root.



I think the error happened when it kept telling me dev is not recognised so I tried to install devscripts...:( ...which was what someone else suggested (if you're having trouble installing spotify)




  • My history is just the following ..I was trying to do a screenshot but I cant save anything :(



24 vi/etc/apt/sources.list
25 deb
26 debc (spotify link) stable non-free
27 sudo apt-get install devscripts
28 debc http://repository.spotify.com stable non-free
29 deb (spotify link) stable non-free
30 apt-get install debian-reference
31 yes
32 sudo apt-key adv--keyserver.ubuntu.com--recv-keys 4E9CFF4E
33 sudo add-apt-repository "deb (spotify link) stable non-fr










share|improve this question
















bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

    – geirha
    Jul 18 '12 at 12:13











  • You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

    – Gibbs
    Jul 18 '12 at 12:23











  • I edited the answer above... i'll post all the history too. thanks for getting back so fast

    – Hala
    Jul 18 '12 at 12:29











  • where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

    – Hala
    Jul 18 '12 at 12:35











  • take a look at askubuntu.com/questions/7489/…

    – user827992
    Jul 18 '12 at 12:37














0












0








0








Okay so I was trying to install spotify onto my ubuntu...and I don't know what I did wrong, but I do not have spotify and all of my files have become read-only (everything in the file system has a padlock on it)!!! This means I cannot do anything in terminal without getting the error that it canot open anything because its a read only file system...any suggestions?



-



Thanks for replying so fast! I tried to follow these instructions on terminal ..none of the stuff was working anyway



Debian



1. Add this line to your list of repositories by



editing your /etc/apt/sources.list



deb http://repository.spotify.com stable non-free



2. If you want to verify the downloaded packages,



you will need to add our public key



sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59



3. Run apt-get update



sudo apt-get update



4. Install spotify!



sudo apt-get install spotify-client



Now i keep getting this error if I try and do a fsck: permission denied while trying to open /dev/sda1 you must have r/w access to the file system or be root.



I think the error happened when it kept telling me dev is not recognised so I tried to install devscripts...:( ...which was what someone else suggested (if you're having trouble installing spotify)




  • My history is just the following ..I was trying to do a screenshot but I cant save anything :(



24 vi/etc/apt/sources.list
25 deb
26 debc (spotify link) stable non-free
27 sudo apt-get install devscripts
28 debc http://repository.spotify.com stable non-free
29 deb (spotify link) stable non-free
30 apt-get install debian-reference
31 yes
32 sudo apt-key adv--keyserver.ubuntu.com--recv-keys 4E9CFF4E
33 sudo add-apt-repository "deb (spotify link) stable non-fr










share|improve this question
















Okay so I was trying to install spotify onto my ubuntu...and I don't know what I did wrong, but I do not have spotify and all of my files have become read-only (everything in the file system has a padlock on it)!!! This means I cannot do anything in terminal without getting the error that it canot open anything because its a read only file system...any suggestions?



-



Thanks for replying so fast! I tried to follow these instructions on terminal ..none of the stuff was working anyway



Debian



1. Add this line to your list of repositories by



editing your /etc/apt/sources.list



deb http://repository.spotify.com stable non-free



2. If you want to verify the downloaded packages,



you will need to add our public key



sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59



3. Run apt-get update



sudo apt-get update



4. Install spotify!



sudo apt-get install spotify-client



Now i keep getting this error if I try and do a fsck: permission denied while trying to open /dev/sda1 you must have r/w access to the file system or be root.



I think the error happened when it kept telling me dev is not recognised so I tried to install devscripts...:( ...which was what someone else suggested (if you're having trouble installing spotify)




  • My history is just the following ..I was trying to do a screenshot but I cant save anything :(



24 vi/etc/apt/sources.list
25 deb
26 debc (spotify link) stable non-free
27 sudo apt-get install devscripts
28 debc http://repository.spotify.com stable non-free
29 deb (spotify link) stable non-free
30 apt-get install debian-reference
31 yes
32 sudo apt-key adv--keyserver.ubuntu.com--recv-keys 4E9CFF4E
33 sudo add-apt-repository "deb (spotify link) stable non-fr







filesystem






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 18 '12 at 12:35







Hala

















asked Jul 18 '12 at 11:56









HalaHala

612




612





bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

    – geirha
    Jul 18 '12 at 12:13











  • You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

    – Gibbs
    Jul 18 '12 at 12:23











  • I edited the answer above... i'll post all the history too. thanks for getting back so fast

    – Hala
    Jul 18 '12 at 12:29











  • where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

    – Hala
    Jul 18 '12 at 12:35











  • take a look at askubuntu.com/questions/7489/…

    – user827992
    Jul 18 '12 at 12:37



















  • Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

    – geirha
    Jul 18 '12 at 12:13











  • You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

    – Gibbs
    Jul 18 '12 at 12:23











  • I edited the answer above... i'll post all the history too. thanks for getting back so fast

    – Hala
    Jul 18 '12 at 12:29











  • where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

    – Hala
    Jul 18 '12 at 12:35











  • take a look at askubuntu.com/questions/7489/…

    – user827992
    Jul 18 '12 at 12:37

















Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

– geirha
Jul 18 '12 at 12:13





Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands?

– geirha
Jul 18 '12 at 12:13













You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

– Gibbs
Jul 18 '12 at 12:23





You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions.

– Gibbs
Jul 18 '12 at 12:23













I edited the answer above... i'll post all the history too. thanks for getting back so fast

– Hala
Jul 18 '12 at 12:29





I edited the answer above... i'll post all the history too. thanks for getting back so fast

– Hala
Jul 18 '12 at 12:29













where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

– Hala
Jul 18 '12 at 12:35





where i've put "spotify link" it refers to repository.spotify.com ...i cant post links more than twice..

– Hala
Jul 18 '12 at 12:35













take a look at askubuntu.com/questions/7489/…

– user827992
Jul 18 '12 at 12:37





take a look at askubuntu.com/questions/7489/…

– user827992
Jul 18 '12 at 12:37










2 Answers
2






active

oldest

votes


















0














Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.



For example, if a file that should be writable says:



-r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext


You can give yourself write permissions using chmod ug+w file.ext.



If a file that belongs to you says:



-rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext


You can take control of it using sudo chown user file.ext.



Similarly chgrp to change the group (the second 'user' above) if that is wrong.






share|improve this answer































    0














    This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:



    UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1



    This is an instruction to remount the drive read-only if there are errors.
    In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.



    But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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%2faskubuntu.com%2fquestions%2f165056%2fwhy-have-all-my-files-become-read-only%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














      Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.



      For example, if a file that should be writable says:



      -r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext


      You can give yourself write permissions using chmod ug+w file.ext.



      If a file that belongs to you says:



      -rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext


      You can take control of it using sudo chown user file.ext.



      Similarly chgrp to change the group (the second 'user' above) if that is wrong.






      share|improve this answer




























        0














        Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.



        For example, if a file that should be writable says:



        -r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext


        You can give yourself write permissions using chmod ug+w file.ext.



        If a file that belongs to you says:



        -rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext


        You can take control of it using sudo chown user file.ext.



        Similarly chgrp to change the group (the second 'user' above) if that is wrong.






        share|improve this answer


























          0












          0








          0







          Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.



          For example, if a file that should be writable says:



          -r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext


          You can give yourself write permissions using chmod ug+w file.ext.



          If a file that belongs to you says:



          -rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext


          You can take control of it using sudo chown user file.ext.



          Similarly chgrp to change the group (the second 'user' above) if that is wrong.






          share|improve this answer













          Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.



          For example, if a file that should be writable says:



          -r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext


          You can give yourself write permissions using chmod ug+w file.ext.



          If a file that belongs to you says:



          -rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext


          You can take control of it using sudo chown user file.ext.



          Similarly chgrp to change the group (the second 'user' above) if that is wrong.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 18 '12 at 13:05









          otusotus

          578621




          578621

























              0














              This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:



              UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1



              This is an instruction to remount the drive read-only if there are errors.
              In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.



              But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)






              share|improve this answer




























                0














                This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:



                UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1



                This is an instruction to remount the drive read-only if there are errors.
                In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.



                But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)






                share|improve this answer


























                  0












                  0








                  0







                  This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:



                  UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1



                  This is an instruction to remount the drive read-only if there are errors.
                  In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.



                  But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)






                  share|improve this answer













                  This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:



                  UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1



                  This is an instruction to remount the drive read-only if there are errors.
                  In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.



                  But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 28 '14 at 17:31









                  labnutlabnut

                  17416




                  17416






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f165056%2fwhy-have-all-my-files-become-read-only%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

                      數位音樂下載

                      When can things happen in Etherscan, such as the picture below?

                      格利澤436b