Announcement

Collapse
No announcement yet.

Why did os make sda1 partition read-only ?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Why did os make sda1 partition read-only ?

    Hi,

    I am stumped here as to why partition sda1 was made read-only ?

    Code:
    reel@BM2LTSR66RBin:/media/hd/home/reel$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0

# / was on /dev/sda1 during installation
/dev/sda1 	/               ext4    errors=remount-ro 0       1

# swap was on /dev/sda3 during installation
/dev/sda3	 none            swap    sw              0       0
UUID=e0e4bb02-3527-4ae8-88a7-78c96d69c3df	/media/hd	auto	defaults,nofail	0	2
reel@BM2LTSR66RBin:/media/hd/home/reel$
    Need write permission on media/hd too.

    Thanks.
    Last edited by kdeuser; Feb 14, 2015, 05:46 PM.
    Tags: None
    • Top
    • Bottom
    #2
    Hi,

    I am stumped here as to why partition sda1 was made read-only ?

    Code:
    reel@BM2LTSR66RBin:/media/hd/home/reel$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0

# / was on /dev/sda1 during installation
/dev/sda1 	/               ext4    errors=remount-ro 0       1

# swap was on /dev/sda3 during installation
/dev/sda3	 none            swap    sw              0       0
UUID=e0e4bb02-3527-4ae8-88a7-78c96d69c3df	/media/hd	auto	defaults,nofail	0	2
reel@BM2LTSR66RBin:/media/hd/home/reel$
    Need write permission on media/hd too.

    Thanks.
    • Top
    • Bottom

    Comment

      #3
      Is it read-only, or are you just asking about the errors=remount-ro parameter?

      Assuming this is your running OS partition you wouldn't be able to boot up normally if it was read-only.
      I'd rather be locked out than locked in.
      • Top
      • Bottom

      Comment

        #4
        Originally posted by SecretCode View Post
        Is it read-only, or are you just asking about the errors=remount-ro parameter?

        Assuming this is your running OS partition you wouldn't be able to boot up normally if it was read-only.
        I am asking about the errors plus can not boot into kde but can in Gnome ,Ubuntu , kodi and xfce.

        I get errors also using xfce on using any kde app , os tells me `can not write sda1 ` or something along those lines.
        Last edited by kdeuser; Feb 14, 2015, 06:49 PM.
        • Top
        • Bottom

        Comment

          #5
          What is your drive and partition layout? Do you have multiple installs or are these desktop environments loaded in the same installation?

          The output of mount would be useful.
          I'd rather be locked out than locked in.
          • Top
          • Bottom

          Comment

            #6
            df -h would be useful as well ,,,,,,, (one of his errors gave hint of a full file system) + he is runing a custom OS targeted at certain hardware which he is using .

            VINNY
            i7 4core HT 8MB L3 2.9GHz
            16GB RAM
            Nvidia GTX 860M 4GB RAM 1152 cuda cores
            • Top
            • Bottom

            Comment

              #7
              I'm not sure I totally understand your question, but for starts, what is the output of mount?
              Code:
              mount
              I used guided install and used my entire disk sda. I didn't not create a separate /home directory when I installed kubuntu.

              Here is the output of mount on mine.
              Code:
              life0riley@precise-desktop:~$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sdb1 on /media/multimedia type ext4 (rw)
/dev/sdc1 on /media/backup01 type ext4 (rw)
life0riley@precise-desktop:~$
              sigpic
              • Top
              • Bottom

              Comment

                #8
                This is a double post.

                Can a moderator please combine it with this one?
                https://www.kubuntuforums.net/showth...tion-read-only
                I would have read the other posts before I posted duplicate information.

                Thanks
                sigpic
                • Top
                • Bottom

                Comment

                  #9
                  sda1 (your "/", or root dir) is not read-only, if you are going by the fstab you have. What you see is that if there are errors on the partition, it will remount it as read-only as a safety precaution.
                  • Top
                  • Bottom

                  Comment

                    #10
                    Originally posted by SecretCode View Post
                    What is your drive and partition layout? Do you have multiple installs or are these desktop environments loaded in the same installation?

                    The output of mount would be useful.
                    Print of gpart :

                    Click image for larger version Name: drives-gpart.png Views: 1 Size: 62.9 KB ID: 642749

                    Yes, the desktops are options at login screen.

                    Output of mount :

                    Code:
                    reel@BM2LTSR66RBin:/media/hd/home/reel$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
tmpfs on /media type tmpfs (rw,relatime,size=10240k)
/dev/sda4 on /media/hd type ext4 (rw,_netdev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
nfsd on /proc/fs/nfsd type nfsd (rw)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=reel)
/dev/sdb1 on /media/hd1 type jfs (rw)
/dev/sdd1 on /media/hd2 type jfs (rw)
reel@BM2LTSR66RBin:/media/hd/home/reel$
                    • Top
                    • Bottom

                    Comment

                      #11
                      Originally posted by vinnywright View Post
                      df -h would be useful as well ,,,,,,, (one of his errors gave hint of a full file system) + he is runing a custom OS targeted at certain hardware which he is using .

                      VINNY
                      Output of df -h :

                      Code:
                      reel@BM2LTSR66RBin:/media/hd/home/reel$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        13G  9.2G  2.9G  77% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            2.0G   20K  2.0G   1% /dev
tmpfs           406M  1.4M  404M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            2.0G  152K  2.0G   1% /run/shm
none            100M   48K  100M   1% /run/user
tmpfs            10M     0   10M   0% /media
/dev/sda4       280G  5.8G  260G   3% /media/hd
/dev/sdb1       1.9T  1.3T  557G  71% /media/hd1
/dev/sdd1       1.9T  1.8T   49G  98% /media/hd2
reel@BM2LTSR66RBin:/media/hd/home/reel$
                      • Top
                      • Bottom

                      Comment

                        #12
                        Originally posted by claydoh View Post
                        sda1 (your "/", or root dir) is not read-only, if you are going by the fstab you have. What you see is that if there are errors on the partition, it will remount it as read-only as a safety precaution.
                        You mean that errors do exist so sda1 mounted read-only.

                        The errors i get now are on opening ( trying to ) open any kde app i get the following :

                        Code:
                        [B]configuration file `/media/hd/home/reel/.kde/share/config/knotifyrc` not writable[/B]
                        Click on ok and next error :

                        Code:
                        [B]configuration file `/media/hd/home/reel/.kde/share/config/ksnapshotrc`

Please contact your system administrator[/B]
                        The same error occurs when trying to boot into kde plasma desktop , except ............/ksnapshotrc is replaced by kdmserverrc

                        I think if this could be fixed , i would be free to boot into kde.
                        Last edited by kdeuser; Feb 15, 2015, 05:03 AM.
                        • Top
                        • Bottom

                        Comment

                          #13
                          But /media/hd is the mount point for /dev/sda4, not sda1.

                          I'm confused as to why you have the .kde folder at /media/hd/home/reel not the normal home directory location /home/reel (assuming reel is your logged in username).

                          What is the output of
                          Code:
                          df -hT /media/hd/home/reel/.kde/share/config/

df -hT ~
                          Also
                          Code:
                          touch ~/testfile

touch /media/hd/home/reel/test-file
                          I'd rather be locked out than locked in.
                          • Top
                          • Bottom

                          Comment

                            #14
                            @ SecretCode,

                            Hi there, the readouts you requested :

                            Code:
                            reel@BM2LTSR66RBin:/media/hd/home/reel$ df -hT /media/hd/home/reel/.kde/share/config/
Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sda4      ext4  445G  387M  422G   1% /media/hd
reel@BM2LTSR66RBin:/media/hd/home/reel$ df -hT ~
Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sda4      ext4  445G  387M  422G   1% /media/hd
reel@BM2LTSR66RBin:/media/hd/home/reel$
                            Code:
                            reel@BM2LTSR66RBin:/media/hd/home/reel$ touch ~/testfile
reel@BM2LTSR66RBin:/media/hd/home/reel$ touch /media/hd/home/reel/test-file
reel@BM2LTSR66RBin:/media/hd/home/reel$
                            • Top
                            • Bottom

                            Comment

                              #15
                              Right ... so your home directory really is on this drive. Also, it's definitely writable. The problem is not a partition being read-only, and certainly not sda1

                              Please post output of
                              Code:
                              readlink -f ~

ls -l /media/hd/home/reel/.kde/share/config/knotifyrc
                              I'd rather be locked out than locked in.
                              • Top
                              • Bottom

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X