Announcement

Collapse
No announcement yet.

KDE Partition Manager/ext4 mount cannot access Help.

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

    KDE Partition Manager/ext4 mount cannot access Help.

    I sincerely apologize for asking for help with this.
    Two days and I am loosing my mind. I have watched videos and read many a how to. nothing is working

    Using KDE Partition Manager,
    Trying to format an external 500GB hard drive as ext4.

    What I tried:
    1 Unmounted drive
    2 selected fat32 partition
    3 delete partition
    4 create new partition table GTP
    5 New
    partition type=Primary
    file system=ext4
    label=TEST
    6 Apply

    At this stage the disk “TESTDISK” will mount but “Access is Denied”
    In KDE Partition Manager TESTDISK shows Mount Point =none
    is this the problem?

    If I try, Edit Mount Point, and the try select path I get an error: can not create io slave.

    thank you
    Tags: None
    • Top
    • Bottom
    #2
    With the external drive connected, and KDE Partition Manager running, take a screen shot and post it here so we can see what is being seen.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
    • Top
    • Bottom

    Comment

      #3
      thank you much for the reply

      i tried this again and this time it will not mount

      the test prior a created a mount point "/media/mydrive" it mounted but no access.
      thanks again
      Attached Files
      • Top
      • Bottom

      Comment

        #4
        Okay. With this drive still connected/mounted, open a konsole and type: sudo blkid and press Enter. Copy/paste the output.
        Windows no longer obstructs my view.
        Using Kubuntu Linux since March 23, 2007.
        "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
        • Top
        • Bottom

        Comment

          #5
          /dev/sda1: UUID="b9bc9f85-85f2-46c3-9830-38d7cd68cf01" TYPE="ext4" PARTUUID="436b584b-01"
          /dev/sdb1: LABEL="mydrive" UUID="0fe989be-76d7-49c4-8aed-2c6e0625c470" TYPE="ext4" PARTUUID="78242a88-41d1-4892-9069-7529324afc0c"
          • Top
          • Bottom

          Comment

            #6
            that output is from this
            Attached Files
            • Top
            • Bottom

            Comment

              #7
              So - not to steal Snowhog's thunder - but what is your issue exactly?

              From what I see above, the drive is partitioned and formatted and Dolphin has mounted it at /media/mydrive.

              The sort of odd thing is usually USB drives are mounted at /media/<YOUR USERNAME>/blahblah , "blahblah" being a drive label or device ID.

              Anyway, stuff auto-mounted under /media will have root ownership if it's a POSIX file system like EXT4. For you to access it, your need to make it yours. Assuming the above info is accurate and you're the primary user, this will do that:

              sudo chown 1000:1000 /media/mydrive

              Please Read Me
              • Top
              • Bottom

              Comment

                #8
                Thank you for the reply
                Yes the drive mounts as root
                so if I understand your instruction placing the code below in terminal will allow read and write access to me the user is that correct?

                “sudo chown 1000:1000 /media/mydrive “
                use this as is?

                Thank you again

                EDIT:

                after looking this up
                sudo chown 1000:1000 = user:group for media/this drive
                is this correct?
                I do not want to do any damage
                Last edited by mxlance; Jan 12, 2019, 06:41 PM.
                • Top
                • Bottom

                Comment

                  #9
                  Yes. As I said, if you're the primary user of your Kubuntu install, you are by default user and group 1000. Therefor, 1000:1000 is you - in a linux sense - lol. I obviously don't know your actuall username and primary group name. So without that info I suggested:

                  1000:1000

                  which, in a numerical way, is the same as

                  YOUR-USER-NAME:YOUR-PRIMARY-GROUP-NAME

                  Please Read Me
                  • Top
                  • Bottom

                  Comment

                    #10
                    Originally posted by oshunluvr View Post
                    Yes. As I said, if you're the primary user of your Kubuntu install, you are by default user and group 1000. Therefor, 1000:1000 is you - in a linux sense - lol. I obviously don't know your actuall username and primary group name. So without that info I suggested:

                    1000:1000

                    which, in a numerical way, is the same as

                    YOUR-USER-NAME:YOUR-PRIMARY-GROUP-NAME
                    While this is probably true in 99.99% of cases, there a a few circumstances where the user id and primary group might not be 1000. For copy-paste one-liners when the username/primary group are unknown, one could use something like "$(id -u):$(id -g)" instead [it will return the current user's username and primary group].

                    for example:
                    Code:
                    sudo chown -R $(id -u):$(id -g) /media/mydrive
                    • Top
                    • Bottom

                    Comment

                      #11
                      Oops!
                      So I have messed up thinks now.
                      My system will not start unless the external drive (I was using as a text to learn how to format, mount and read and write to) is plugged into the system.

                      After many hours with google I believe I understand how I messed things up but I am reluctant to attempt a repair.

                      I now know that I should have backed up my etc folder, but I did not.

                      So how do I fix this and start fresh?

                      sudo blkid =
                      /dev/sda1: UUID="b9bc9f85-85f2-46c3-9830-38d7cd68cf01" TYPE="ext4" PARTUUID="436b584b-01"

                      fstab =
                      <file system> <mount point> <type> <options> <dump> <pass>
                      # / was on /dev/sda1 during installation
                      UUID=b9bc9f85-85f2-46c3-9830-38d7cd68cf01 / ext4 errors=remount-ro 0 1
                      /swapfile none swap sw 0 0
                      UUID=a33862f3-45dd-42da-a88b-14a7d8a6e21a none ext4 users 0 0
                      UUID=0fe989be-76d7-49c4-8aed-2c6e0625c470 /media/deepcat2 ext4 defaults 0 0

                      Thanks for all the help
                      • Top
                      • Bottom

                      Comment

                        #12
                        On the assumption that the last line in your /etc/fstab file (UUID=0fe989be-76d7-49c4-8aed-2c6e0625c470 /media/deepcat2 ext4 defaults 0 0) is for the external drive, just open it in kate and put a # sign and a space before it so it looks like:

                        #                         UUID=0fe989be-76d7-49c4-8aed-2c6e0625c470 /media/deepcat2 ext4 defaults 0 0

                        Save the file (you'll be prompted for your password) and close kate. Logout and reboot.
                        Windows no longer obstructs my view.
                        Using Kubuntu Linux since March 23, 2007.
                        "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                        • Top
                        • Bottom

                        Comment

                          #13
                          Just to be clear and avoid further issues
                          I believe the entry below in BOLD was a previous attempt with the external drive that is still showing.
                          Could that be correct and if so should I apply the same # to it also?


                          <file system> <mount point> <type> <options> <dump> <pass>
                          # / was on /dev/sda1 during installation
                          UUID=b9bc9f85-85f2-46c3-9830-38d7cd68cf01 / ext4 errors=remount-ro 0 1
                          /swapfile none swap sw 0 0
                          UUID=a33862f3-45dd-42da-a88b-14a7d8a6e21a none ext4 users 0 0
                          UUID=0fe989be-76d7-49c4-8aed-2c6e0625c470 /media/deepcat2 ext4 defaults 0 0
                          • Top
                          • Bottom

                          Comment

                            #14
                            Originally posted by mxlance View Post
                            Just to be clear and avoid further issues
                            I believe the entry below in BOLD was a previous attempt with the external drive that is still showing.
                            Could that be correct and if so should I apply the same # to it also?


                            <file system> <mount point> <type> <options> <dump> <pass>
                            # / was on /dev/sda1 during installation
                            UUID=b9bc9f85-85f2-46c3-9830-38d7cd68cf01 / ext4 errors=remount-ro 0 1
                            /swapfile none swap sw 0 0
                            UUID=a33862f3-45dd-42da-a88b-14a7d8a6e21a none ext4 users 0 0
                            UUID=0fe989be-76d7-49c4-8aed-2c6e0625c470 /media/deepcat2 ext4 defaults 0 0
                            As you installed Kubuntu to a single partition; no separate /home partition; I would comment (# and space) both lines, save, logout and reboot just to ensure that you are then able to successfully get back in to a working Desktop.
                            Windows no longer obstructs my view.
                            Using Kubuntu Linux since March 23, 2007.
                            "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                            • Top
                            • Bottom

                            Comment

                              #15
                              It Worked!!!
                              Thank you, Thank You, Thank You.

                              Now i can try this again
                              • Top
                              • Bottom

                              Comment

                              Previous 1 2 3 template Next
                              Working...
                              X