Announcement

Collapse
No announcement yet.

How do I allocate more HD space for Kubuntu?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #76
    Getting this error when booting to the new sda3 install?

    Does it let you continue booting with "Skip"?

    If so, post the contents of /etc/fstab and the results of

    sudo blkid -c /dev/null -o list

    Also, look through your log files (run dmesg at least) and see what's causing the error.

    Please Read Me

    Comment


      #77
      YES, the options are Skip and Manually, I have only chosen 'Skip' and the OS seems normal.
      /etc/fstab.d/ is an empty folder

      granpasmurf@Petersen:~$ sudo blkid -c /dev/null -o list
      [sudo] password for granpasmurf:
      device fs_type label mount point UUID
      -------------------------------------------------------------------------------
      /dev/sda2 swap <swap> 27fc3bd0-ba2a-44d9-bcdb-7f70882765ea
      /dev/sda3 ext4 / 8283dd32-66c3-4c8f-a369-f8fcc6428c63
      /dev/sda4 ext4 (not mounted) f5832725-1864-49c2-87f7-8d7b464eae56
      /dev/sda5 ext4 /home 138c7e8a-ab14-461c-9bce-ed83424a14ba
      /dev/sda6 ext4 (not mounted) 1db51d0b-ac03-4877-90e8-bc1539535790
      granpasmurf@Petersen:~$
      Last edited by GranPaSmurf; Feb 18, 2014, 07:07 AM. Reason: updated
      Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

      Comment


        #78
        review of logs

        Caveat: I don't know what I'm looking at and don't know what I looking for.
        however these entries were either red-lined or otherwise caught my eye:
        Authentication Log:
        05:03 AM
        [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.35" (uid=0 pid=1557 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=839 comm="NetworkManager ")
        Kernal Log:
        02/18/14 05:02:33 AM type=1400 audit(1392721352.061:11): apparmor="STATUS" operation="profile_replace" parent=410 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=434 comm="apparmor_parser"
        02/18/14 05:02:34 AM EXT4-fs (sda3) re-mounted. Opts: (null)
        02/18/14 05:02:34 AM EXT4-fs (sda5) mounted filesystem with ordered data mode. Opts: (null)
        02/18/14 05:02:50 AM init failsafe main process (647) killed by TERM signal
        02/18/14 05:02:51 AM init avahi-cups-reload main process (756) terminated with status 1

        also attached is dmesg:
        Attached Files
        Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

        Comment


          #79
          I'll look closer at this tonight, but fstab.d is a folder that is not currently used by Kubuntu but will be in the future. The file I asked about is /etc/fstab - no .d. That is where your system mounts are. It's possible you had a thumb drive in and logged out or rebooted. Try going into system settings and uncheck "restore previous session" - If you can't find it, I'll post again later tonight.

          EDIT: System Settings >>Startup and Shutdown >> Session Management. Select "start with Empty Session"
          Last edited by oshunluvr; Feb 18, 2014, 01:57 PM.

          Please Read Me

          Comment


            #80
            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>
            # / was on /dev/sda3 during installation
            UUID=8283dd32-66c3-4c8f-a369-f8fcc6428c63
            / ext4 errors=remount-ro 0 1
            # /home was on /dev/sda5 during installation
            UUID=138c7e8a-ab14-461c-9bce-ed83424a14ba /home ext4 defaults 0 2
            # swap was on /dev/sda2 during installation
            UUID=27fc3bd0-ba2a-44d9-bcdb-7f70882765ea none swap sw 0 0
            /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
            Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

            Comment


              #81
              That looks ok to me. Have you tried rebooting since change the session restore?

              Please Read Me

              Comment


                #82
                Possibly sda5 needs a scan. If you're still getting the "Skip or Manual" message, tey doing this in a terminal:

                sudo touch /forcefsck

                ​then rebooting.

                Please Read Me

                Comment


                  #83
                  start up images

                  no change after sudo touch /forcefsck
                  If I edit GRUB, can i take out all the old stuff?
                  Click image for larger version

Name:	startup 01.jpg
Views:	1
Size:	139.4 KB
ID:	640663Click image for larger version

Name:	startup02.jpg
Views:	1
Size:	58.0 KB
ID:	640664Click image for larger version

Name:	snapshot1.jpg
Views:	1
Size:	57.8 KB
ID:	640665
                  Last edited by GranPaSmurf; Feb 18, 2014, 08:38 PM.
                  Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

                  Comment


                    #84
                    It could be the format of fstab. Try this, in a terminal:

                    kdesudo kate /etc/fstab

                    Then under the "View" menu, see if "Dynamic Word Wrap F10" is checked. If yes, uncheck it. Then in the file if this still appears as two lines:

                    Code:
                    UUID=8283dd32-66c3-4c8f-a369-f8fcc6428c63
                    / ext4 errors=remount-ro 0 1
                    Change it so it's one line as it's supposed to be, like so:

                    Code:
                    UUID=8283dd32-66c3-4c8f-a369-f8fcc6428c63 / ext4 errors=remount-ro 0 1
                    and save. Then reboot to verify the error goes away.

                    As far as the grub menu, we'll fix that in a bit. I want to be sure all is well with this install before we proceed.

                    IF YOU ARE SURE you examined the files on /dev/sda6 and nothing is left there you want, you may delete it when you are ready. Then you can boot to your Gparted live CD and expand sda5 to fill all the remaining free space in the expanded partition.

                    Please Read Me

                    Comment


                      #85
                      Originally posted by oshunluvr View Post
                      It could be the format of fstab. Try this, in a terminal:

                      kdesudo kate /etc/fstab

                      Then under the "View" menu, see if "Dynamic Word Wrap F10" is checked. If yes, uncheck it. Then in the file if this still appears as two lines:

                      Code:
                      UUID=8283dd32-66c3-4c8f-a369-f8fcc6428c63
                      / ext4 errors=remount-ro 0 1
                      Change it so it's one line as it's supposed to be, like so:

                      Code:
                      UUID=8283dd32-66c3-4c8f-a369-f8fcc6428c63 / ext4 errors=remount-ro 0 1
                      and save. Then reboot to verify the error goes away.
                      the start up error went away
                      Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

                      Comment


                        #86
                        Ok, there you go! Not sure how that extra carriage return got there, but who cares!

                        Before we start deleting stuff, let's fix grub.

                        After selecting and booting to your new sda3 install, run this command:

                        sudo grub-install /dev/sda

                        If it reports any errors, post them here. If not, do this:

                        sudo update-grub

                        and reboot. It should then default to your new install.

                        Please Read Me

                        Comment


                          #87
                          Well, I bricked it again. As per earlier post, I re-examined files & none were needed. only empty folders.
                          booted to Gparted disk and selected sda6, deleted it. Rebooted and now have:
                          Loading Operating System...
                          error: no such partition.
                          grub rescue>

                          I learned decades ago not to do anything of consequence after dark. I will pick this up in the morning
                          Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

                          Comment


                            #88
                            Likely grub was running off of the "failed" 13.10 install from before. Grub can be re-installed in several ways. Boot to your Live USB or CD of Kubuntu. Open a terminal. Then:

                            sudo mount /dev/sda3 /mnt
                            sudo update-grub
                            sudo grub-install --root-directory=/mnt /dev/sda3


                            If you get no errors, try rebooting from the hard drive again

                            Please Read Me

                            Comment


                              #89
                              Started from Live CD, then :
                              Mount : can't find /dev /sda /mnt. In /etc m/fstab or /etc/mtb

                              Sent from my TouchPad using Tapatalk
                              Last edited by GranPaSmurf; Feb 19, 2014, 09:23 AM.
                              Using Linux only for a few years, using mostly mouse on GUI (sorry gurus). Kubuntu 19.04 beta on home-built: GigaByte board - AMD Phenom II, 3000 6 core, RAM 4 Gb,

                              Comment


                                #90
                                Is that a typo? You can't mount sda by itself nor can you have those spaces in there.

                                Do:

                                sudo blkid -c /dev/null -o list

                                a post the output. The mount command should be:

                                sudo mount /dev/sda3 /mnt

                                Please Read Me

                                Comment

                                Working...
                                X