Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 32

Thread: KDE not starting after running Partioner.

  1. #21

    Default Re: KDE not starting after running Partioner.

    Here are the outputs from the various diagnostics, starting with

    df -h
    Code:
    Filesystem      Size  Used Avail Use% Mounted on
    devtmpfs         16G  4.0K   16G   1% /dev
    tmpfs            16G     0   16G   0% /dev/shm
    tmpfs            16G  1.6G   15G  11% /run
    tmpfs            16G     0   16G   0% /sys/fs/cgroup
    /dev/sda5        40G   40G     0 100% /
    /dev/sda5        40G   40G     0 100% /boot/grub2/x86_64-efi
    /dev/sda5        40G   40G     0 100% /.snapshots
    /dev/sda5        40G   40G     0 100% /usr/local
    /dev/sda5        40G   40G     0 100% /boot/grub2/i386-pc
    /dev/sda4       500M  5.0M  495M   1% /boot/efi
    /dev/sda5        40G   40G     0 100% /tmp
    /dev/sda5        40G   40G     0 100% /srv
    /dev/sda5        40G   40G     0 100% /opt
    /dev/sda5        40G   40G     0 100% /var
    /dev/sda5        40G   40G     0 100% /root
    /dev/sda6       1.7T  547G  1.1T  34% /home
    tmpfs           3.2G     0  3.2G   0% /run/user/0
    /dev/sdb1       232G   12M  232G   1% /mnt
    You see why I doubt that the problem is a single file in /var that has mysteriously appeared.

  2. #22

    Default Re: KDE not starting after running Partioner.

    This is the output from

    du -s /var/*

    Code:
    233216 /var/adm
    4 /var/agentx
    135852 /var/cache
    0 /var/crash
    42488 /var/lib
    4 /var/lock
    51300 /var/log
    4 /var/mail
    0 /var/opt
    4 /var/run
    53420 /var/spool
    13684 /var/tmp
    4 /var/yp
    Something in the cache? Should I investigate that?

  3. #23

    Default Re: KDE not starting after running Partioner.

    And here is the output from

    fdisk -l

    Code:
    Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: D0186001-388C-4CA2-A97F-D68DB47981CF
    
    
    Device          Start        End    Sectors  Size Type
    /dev/sda1        2048     321535     319488  156M EFI System
    /dev/sda2      321536    4530175    4208640    2G Microsoft basic data
    /dev/sda3     4530176   88422399   83892224   40G Microsoft basic data
    /dev/sda4    88422400   89446399    1024000  500M EFI System
    /dev/sda5    89446400  173332479   83886080   40G Linux filesystem
    /dev/sda6   173332480 3841394687 3668062208  1.7T Linux filesystem
    /dev/sda7  3841394688 3907029134   65634447 31.3G Linux swap
    
    
    
    
    
    
    
    Disk /dev/sdb: 231.9 GiB, 248973885440 bytes, 486277120 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000
    
    
    Device     Boot Start       End   Sectors   Size Id Type
    /dev/sdb1          32 486277119 486277088 231.9G  c W95 FAT32 (LBA)

  4. #24
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,646

    Default Re: KDE not starting after running Partioner.

    It is clear that sda5 is 100% full. And that is your / (root) partition.

    /var is only one of the many off springs there.

    BTW I assume that sda6 is the /home file system you changed to ext4.

    So you have to check what fills up /.

    Again that is an heuristic process. You start (as root) at the bottom, in this case /:
    Code:
    cd /
    du -sh *
    from what you see there you guess what is out of proportion. Let us assume that is /data (which you probably do not even have), then you go there and repeat
    Code:
    cd /data
    du -sh *
    etc. until you think you got the culprit.
    It then depends on what you found on how to repair. When it is a log file that runs amok, maybe check what the messages show (because that is what went wrong in the first place) and then emtpty or even remove it (most log files will be recreated when gone).

    Of course report here with waht you found or if in doubt. Success!
    Henk van Velden

  5. #25

    Default Re: KDE not starting after running Partioner.

    26G In /tmp !!!!!

    Is it going to be safe for me to just delete the lot? Or might there be something there that needs to be saved?

  6. #26
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,646

    Default Re: KDE not starting after running Partioner.

    Quote Originally Posted by johngwalker View Post
    26G In /tmp !!!!!

    Is it going to be safe for me to just delete the lot? Or might there be something there that needs to be saved?
    OK, that is something!

    As you are now running in run-level 3, IMHO you can delete all there. But first take a look to get an idea of what is still there that probably should have been deleted, or not have being created (stupid idea: a copy of the tar file of /home?).

    Thus remove and reboot!
    Henk van Velden

  7. #27
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,062
    Blog Entries
    3

    Default Re: KDE not starting after running Partioner.

    Quote Originally Posted by johngwalker View Post
    26G In /tmp !!!!!

    Is it going to be safe for me to just delete the lot? Or might there be something there that needs to be saved?
    You would know better than we.

    Here, I have "/tmp" cleaned out on boot ("man tmpfiles.d" for information on this).

    It is probably safe to clear out "/tmp" and then reboot.
    openSUSE Leap 15.1; KDE Plasma 5;

  8. #28

    Default Re: KDE not starting after running Partioner.

    Thanks for all your help. Things are now working, and to prove it I'm posting this from the PC that had the problem.

    I've learned a lot under your guidance, so I can't say that it's been wasted time. I hope I haven't ruined your Christmas.

    I used to allocate /tmp to a tmpfs file system once upon a time, and I can't remember why I stopped doing that. But that's a minor problem and probably not important now.

    Have a good New Year!

  9. #29
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,646

    Default Re: KDE not starting after running Partioner.

    Nice it is solved! Congratulations.

    I am still wondering if the filling of /tmp had anythiing to do with your fs type conversion.

    BTW, apart from having /tmp on a tmpfs, as nrickert hinted there are other posibilities. I have these notes:
    ================================
    For cleaning /tmp and /var/tmp at boot:


    When there is not already a file /etc/tmpfiles.d/tmp.conf create it as a copy


    Code:
    cp /usr/lib/tmpfiles.d/tmp.conf /etc/tmpfiles.d/tmp.conf

    Then change the lines
    Code:
    # Clear tmp directories separately, to make them easier to override
    # SUSE policy: we don't clean those directories
    d /tmp 1777 root root -
    d /var/tmp 1777 root root -

    into
    Code:
    # Clear tmp directories separately, to make them easier to override
    # My policy: empty /tmp en /var/tmp on boot.
    D! /tmp 1777 root root 1d
    D! /var/tmp 1777 root root 1d
    See
    Code:
    man 5 tmpfiles.d

    ================================
    For making /tmp a tmpfs:
    Add an entry into /etc/fstab
    Code:
    tmpfs             /tmp    tmpfs   size=25%,uid=root,gid=root,mode=1777 0 0
    See
    Code:
    man 8 mount
    specialy the section: Mount options for tmpfs.


    Before mounting this file system for the first time (either by command, or by reboot) you should clean the present /tmp directory as good as possible. Existing contents will still occupy disk space when you mount a file system over it.
    Henk van Velden

  10. #30

    Default Re: KDE not starting after running Partioner.

    Thanks for this advice. I'll have a look at the mans and have a try at setting something up.

    /tmp contained a single file of 26G, which was the culprit. This was entirely my fault. After backing up /home I tried to check the tar file using Ark in KDE and it crashed, but everything else seemed to be okay running in command mode so I went on with reformatting the /home partition. So there's no one to blame but myself.

    Once again, thanks for all your help.

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •