[SOLVED] Low space on boot

Penstroke4 · 04-04-2023, 09:32 PM

Quote:

Originally Posted by mrmazda

All good here, and with less freespace than OP has:

Code:

# df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda23      6.2G  5.3G  568M  91% /
# inxi -C
CPU:
  Info: dual core model: Intel Core2 Duo E8400 bits: 64 type: MCP cache:
    L2: 6 MiB

Drives:
  Local Storage: total: 698.64 GiB used: 153.06 GiB (21.9%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3750525AS
    family: Barracuda 7200.12 size: 698.64 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.0 speed: 3.0 Gb/s type: HDD rpm: 7200
    serial: <filter> rev: JC4B temp: 38 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 49d 19h cycles: 789
    read: 231.2 GiB written: 629.72 GiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
#

<<<<<<<<<<<<<<<<
Below is an extract following the command:-

Code:

 
# df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda9        73G   67G  5.2G  93% /

Code:

# inxi -c
CPU: dual core Intel Pentium G3260 (-MCP-)
speed/min/max: 993/800/3300 MHz
Kernel: 6.2.7-200.fc37.x86_64 x86_64 Up: 7m
Mem: 2053.1/7828.4 MiB (26.2%)
Storage: 2.04 TiB (26.1% used) Procs: 281
Shell: Bash inxi: 3.3.25

Code:

# inxi -DGSaz --vs --zl --hostname
inxi 3.3.25-00 (2023-02-07)
System:
  Host: fedora Kernel: 6.2.7-200.fc37.x86_64
    arch: x86_64 bits: 64 compiler: gcc
    v: 2.38-25.fc37
    parameters: BOOT_IMAGE=(hd0,msdos8)/vmlinuz-6.2.7-200.fc37.x86_64
    root=UUID=1ae30cdf-07b6-4e89-b0f2-7e2ac2a7c4d4
    ro rootflags=subvol=root
    resume=UUID=ac1205ac-eef2-4534-b75a-6be24364697a
    rhgb quiet
  Desktop: GNOME v: 43.3 tk: GTK v: 3.24.37
    wm: gnome-shell dm: 1: LightDM v: 1.32.0
    note: stopped 2: SDDM Distro: Fedora
    release 37 (Thirty Seven)
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core
    Processor Integrated Graphics
    vendor: Gigabyte driver: i915 v: kernel
    arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: VGA-1
    empty: none bus-ID: 00:02.0
    chip-ID: 8086:0402 class-ID: 0300
  Display: wayland server: X.org v: 1.20.14
    with: Xwayland v: 22.1.8
    compositor: gnome-shell driver: X:
    loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: 0
  Monitor-1: VGA-1 res: 1920x1080 size: N/A
    modes: N/A
  API: OpenGL v: 4.6 Mesa 22.3.7
    renderer: Mesa Intel HD Graphics (HSW GT1)
    direct-render: Yes
Drives:
  Local Storage: total: 2.04 TiB
    used: 544.45 GiB (26.1%)
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk
    model: SSD PLUS 240GB
    family: Marvell based SSDs size: 223.57 GiB
    block-size: physical: 512 B logical: 512 B
    sata: 3.2 speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 04RL temp: 33 C
    scheme: MBR
  SMART: yes state: enabled health: PASSED
    on: 229d 23h cycles: 3641
  ID-2: /dev/sdb maj-min: 8:16
    vendor: Seagate model: ST1000DM010-2EP102
    family: BarraCuda 3.5 (CMR)
    size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.0
    speed: 3.0 Gb/s type: HDD rpm: 7200
    serial: <filter> rev: CC46 temp: 35 C
  SMART: yes state: enabled health: PASSED
    on: 18 hrs cycles: 23 read: 72.2 MiB
    written: 0 KiB Pre-Fail:
    attribute: Spin_Retry_Count value: 100
    worst: 100 threshold: 97
  ID-3: /dev/sdc maj-min: 8:32 type: USB
    vendor: Western Digital
    model: WD10JPVT-00A1YT0 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B
    type: HDD rpm: 5400 serial: <filter>
    rev: 0001 scheme: GPT
  SMART Message: Unknown USB bridge. Flash
    drive/Unsupported enclosure?

Where is the mistakes? Thanks

mrmazda · 04-04-2023, 09:43 PM

Quote:

Originally Posted by Penstroke4

Where is the mistakes?

A big one you can correct by editing is to place code tags around any command output you paste here so that it retains the legibility it presented on your own screen. It's hard to decipher command output that's all bunched together without the whitespace the command originally produced.

Penstroke4 · 04-04-2023, 10:56 PM

Quote:

Originally Posted by michaelk

Post the output of the command:
inxi -N

or if inxi is not installed the output of

lspci | grep Ethernet

<<<<<<<<<<< Below is an extract following the command:

# inxi -N
Network:
Device-1: Realtek RTL8111/8168/8411 PCI
Express Gigabit Ethernet driver: r8169

mrmazda · 04-04-2023, 11:05 PM

I have a PC with OS, CPU and graphics almost same as yours:

Code:

# df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda13      7.8G  6.0G  1.4G  82% /
# inxi -C
CPU:
  Info: dual core model: Intel Pentium G3220 bits: 64 type: MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1750 min/max: 800/3000 cores: 1: 798 2: 2703
# inxi -DGSaz --vs --zl --hostname
inxi 3.3.26-00 (2023-03-28)
System:
  Host: ab85m Kernel: 6.2.9-200.fc37.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 2.38-25.fc37 parameters: BOOT_IMAGE=/boot/vmlinuz
    root=LABEL=<filter> noresume audit=0 ipv6.disable=1 net.ifnames=0
    mitigations=auto consoleblank=0
  Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
    vt: 7 dm: 1: TDM 2: XDM Distro: Fedora release 37 (Thirty Seven)
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: DP-1,HDMI-A-2,HDMI-A-3 empty: HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0402 class-ID: 0300
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
    s-diag: 944mm (37.18")
  Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
    built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
    serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
    size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  Monitor-3: HDMI-A-3 mapped: HDMI-3 pos: top-left model: NEC EA243WM
    serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
    size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
    max: 1920x1200 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.7 renderer: Mesa Intel HD Graphics (HSW GT1)
    direct-render: Yes
Drives:
  Local Storage: total: 238.47 GiB used: 78.21 GiB (32.8%)
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: TEAM T253X2256G
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B sata: 3.2
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2A0 scheme: GPT
  SMART: yes state: enabled health: PASSED on: 20d 7h cycles: 373
    read: 8.3 MiB written: 9.9 MiB
#

Notable differences are:

I'm using an SSD instead of HDD
I'm using TDM instead of LightDM or SDDM
I'm using TDE instead of Gnome or XFCE
I only use Xorg, never Wayland
I don't boot using rhgb quiet
My / filesystem is much smaller, with only 1.4G of freespace
Your kernel is a little older
I'm having no issues with free disk space, RAM, lagging, buffering or screen freezes.

Maybe a newer kernel would help?

Penstroke4 · 04-04-2023, 11:31 PM

Quote:

Originally Posted by mrmazda

I have a PC with OS, CPU and graphics almost same as yours:

Code:

# df -h /
Filesystem      Size  Used Avail Use% Mounted on


#

Notable differences are:

I'm using an SSD instead of HDD
I'm using TDM instead of LightDM or SDDM
I'm using TDE instead of Gnome or XFCE
I only use Xorg, never Wayland
I don't boot using rhgb quiet
My / filesystem is much smaller, with only 1.4G of freespace
Your kernel is a little older
I'm having no issues with free disk space, RAM, lagging, buffering or screen freezes.

Maybe a newer kernel would help?

<<< My system has a [240gb] SSD as disk0, an ide hdd[1TB]as disk1.
My fedora is installed in SSD [disk0] along with Windows 10 -dual boot using Grub2win
whilst disk1 is mainly for data & backup.
If I were to follow, what is the apps name for TDM, TDEr,hgb to download & install.
Can I upgrade my kernel without reinstalling Fedora 37
thanks

mrmazda · 04-04-2023, 11:56 PM

Quote:

Originally Posted by Penstroke4

If I were to follow, what is the apps name for TDM, TDEr,hgb to download & install.

TDM and TDE installation instructions are here. rhgb is a boot parameter I omit that inxi reports you are using.

Quote:

Can I upgrade my kernel without reinstalling Fedora 37

Of course. Kernels are upgraded along with normal Fedora upgrades thus:

Code:

sudo dnf upgrade

As your freespace is running low, I suggest to free some before adding software or upgrading. Very likely you will gain a good amount from doing:

Code:

sudo dnf clean packages

Another place where considerable space is often wasted is keeping old journal log files. Check in the directory /var/log/journal/ if it exists. If it does, it will contain at least one subdirectory that may contain a number of large, useless old log files. Any more than a few weeks or months old can be safely deleted. Keeping these logs, if they exist, to a manageable size, can be done automatically by customizing /etc/systemd/journald.conf.

pan64 · 04-05-2023, 12:30 AM

I can't see that "low space on boot", probably a df -h will give some additional info.

Penstroke4 · 04-05-2023, 06:57 PM

Quote:

Originally Posted by JZL240I-U

Try the command

bootctl

(and man bootctl)

<<<<<<<
have tried with bootctl

-The response is:
Coundn't find EFI system partition. It is recommended to mount-it to /boot
or /efi.
Alternatively, use --esp-path= to specify path to mount point.
System: Not booted with EFI

Q1:What does it mean? If its the cause then why did this freezes,dropping ethernet connection did not happen when I was using
Fedora 36. All these problem started after I have upgraded to Fedora 37.

-Q2: Assuming that I need to mount the EFI partition, what must I do?
(mine is dual booted Fedora 37 with Windows 10 using Grub2win boot loader- Grub2win was installed when I had installed
Fedora 36)
Thanks

Penstroke4 · 04-05-2023, 08:12 PM

Quote:

Originally Posted by pan64

I can't see that "low space on boot", probably a df -h will give some additional info.

<<<<< After issuing the command:

Code:

 $ df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           3.9G   57M  3.8G   2% /dev/shm
tmpfs           1.6G   18M  1.6G   2% /run
/dev/sda9        73G   68G  3.7G  95% /
tmpfs           3.9G   15M  3.9G   1% /tmp
/dev/loop4      128K  128K     0 100% /var/lib/snapd/snap/bare/5
/dev/loop0      7.7M  7.7M     0 100% /var/lib/snapd/snap/adguard-home/5523
/dev/loop1      7.7M  7.7M     0 100% /var/lib/snapd/snap/adguard-home/5361
/dev/loop3     1011M 1011M     0 100% /var/lib/snapd/snap/android-studio-canary/35
/dev/loop2      996M  996M     0 100% /var/lib/snapd/snap/android-studio/125
/dev/loop5      146M  146M     0 100% /var/lib/snapd/snap/blue-recorder/126
/dev/loop6      117M  117M     0 100% /var/lib/snapd/snap/core/14784
/dev/loop7      117M  117M     0 100% /var/lib/snapd/snap/core/14946
/dev/loop8       56M   56M     0 100% /var/lib/snapd/snap/core18/2714
/dev/loop9       56M   56M     0 100% /var/lib/snapd/snap/core18/2721
/dev/loop10      64M   64M     0 100% /var/lib/snapd/snap/core20/1828
/dev/loop11      64M   64M     0 100% /var/lib/snapd/snap/core20/1852
/dev/loop12      73M   73M     0 100% /var/lib/snapd/snap/core22/583
/dev/loop14     6.3M  6.3M     0 100% /var/lib/snapd/snap/extract-deb/30
/dev/loop13      73M   73M     0 100% /var/lib/snapd/snap/core22/607
/dev/loop15      81M   81M     0 100% /var/lib/snapd/snap/ffmpeg/1286
/dev/loop16     165M  165M     0 100% /var/lib/snapd/snap/gnome-3-28-1804/161
/dev/loop18     522M  522M     0 100% /var/lib/snapd/snap/gimp/393
/dev/loop17     165M  165M     0 100% /var/lib/snapd/snap/gnome-3-28-1804/194
/dev/loop19     347M  347M     0 100% /var/lib/snapd/snap/gnome-3-38-2004/119
/dev/loop20     350M  350M     0 100% /var/lib/snapd/snap/gnome-3-38-2004/137
/dev/loop21     103M  103M     0 100% /var/lib/snapd/snap/iptvnator/83
/dev/loop23     236M  236M     0 100% /var/lib/snapd/snap/kde-frameworks-5/27
/dev/loop22     461M  461M     0 100% /var/lib/snapd/snap/gnome-42-2204/68
/dev/loop25     400M  400M     0 100% /var/lib/snapd/snap/obs-studio/1284
/dev/loop24     256K  256K     0 100% /var/lib/snapd/snap/gtk2-common-themes/13
/dev/loop28      92M   92M     0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop29      44M   44M     0 100% /var/lib/snapd/snap/pdf2go/51
/dev/loop26     1.1G  1.1G     0 100% /var/lib/snapd/snap/libreoffice/270
/dev/loop30     103M  103M     0 100% /var/lib/snapd/snap/iptvnator/79
/dev/loop35     128K  128K     0 100% /var/lib/snapd/snap/sweeper/9
/dev/loop27     461M  461M     0 100% /var/lib/snapd/snap/gnome-42-2204/65
/dev/loop31     920M  920M     0 100% /var/lib/snapd/snap/libreoffice/265
/dev/loop32      90M   90M     0 100% /var/lib/snapd/snap/photonotebook/44
/dev/loop33      99M   99M     0 100% /var/lib/snapd/snap/pyqt5-runtime-lite/4
/dev/loop34      70M   70M     0 100% /var/lib/snapd/snap/smartstock/137
/dev/loop37     512K  512K     0 100% /var/lib/snapd/snap/utorrent/102
/dev/loop41     1.0M  1.0M     0 100% /var/lib/snapd/snap/timecard/1
/dev/loop36      88M   88M     0 100% /var/lib/snapd/snap/sqlitebrowser/3233
/dev/loop38      23M   23M     0 100% /var/lib/snapd/snap/syncthing-arubislander/31
/dev/loop39      23M   23M     0 100% /var/lib/snapd/snap/syncthing-arubislander/30
/dev/loop42      93M   93M     0 100% /var/lib/snapd/snap/whatsapp-for-linux/55
/dev/loop40      79M   79M     0 100% /var/lib/snapd/snap/taskade/27
/dev/loop43     323M  323M     0 100% /var/lib/snapd/snap/wine-platform-6-stable/19
/dev/loop46     347M  347M     0 100% /var/lib/snapd/snap/wine-platform-runtime/340
/dev/loop44      64M   64M     0 100% /var/lib/snapd/snap/whatsapp-for-linux/56
/dev/loop50     256K  256K     0 100% /var/lib/snapd/snap/zsync/1
/dev/loop45     100M  100M     0 100% /var/lib/snapd/snap/wine-platform-3-stable/14
/dev/loop47     347M  347M     0 100% /var/lib/snapd/snap/wine-platform-runtime/342
/dev/loop49     467M  467M     0 100% /var/lib/snapd/snap/wine-platform-runtime-core20/58
/dev/loop51     467M  467M     0 100% /var/lib/snapd/snap/wine-platform-runtime-core20/60
/dev/loop48     454M  454M     0 100% /var/lib/snapd/snap/wine-platform-7-devel-core20/24
/dev/sda9        73G   68G  3.7G  95% /home
/dev/sda8       974M  307M  600M  34% /boot
tmpfs           783M  188K  783M   1% /run/user/1000
 $

Penstroke4 · 04-05-2023, 08:24 PM

Quote:

Originally Posted by mrmazda

TDM and TDE installation instructions are here. rhgb is a boot parameter I omit that inxi reports you are using.
Of course. Kernels are upgraded along with normal Fedora upgrades thus:

Code:

sudo dnf upgrade

As your freespace is running low, I suggest to free some before adding software or upgrading. Very likely you will gain a good amount from doing:

Code:

sudo dnf clean packages

Another place where considerable space is often wasted is keeping old journal log files. Check in the directory /var/log/journal/ if it exists. If it does, it will contain at least one subdirectory that may contain a number of large, useless old log files. Any more than a few weeks or months old can be safely deleted. Keeping these logs, if they exist, to a manageable size, can be done automatically by customizing /etc/systemd/journald.conf.

Code:

I have tried the suggestion, sudo dnf upgrade. Has downloaded 890.mb,-running ,transaction check and etc. 
Gives better internet speed improvements but freezing is awful. Takes tens of seconds to response to simple mouse clicks.
Freezing, lagging is awful.Is just not practical to operate. 
What options do I have besides re-installing Fedora 37

pan64 · 04-06-2023, 12:03 AM

hm. That is quite strange, it looks like /dev/sda9 mounted twice (/ and /home are both the same device). That is definitely incorrect, you ought to fix it somehow.

mrmazda · 04-06-2023, 12:34 AM

Quote:

Originally Posted by pan64

hm. That is quite strange, it looks like /dev/sda9 mounted twice (/ and /home are both the same device). That is definitely incorrect, you ought to fix it somehow.

I did ask for output from cat /etc/fstab early in thread, but it never came. Same partition mounted to both / and /home doesn't bode well for successful repair. Did OP save any older copies of fstab we can take a look at and compare to the forthcoming current version?

Penstroke4 · 04-06-2023, 12:45 AM

Quote:

Originally Posted by pan64

hm. That is quite strange, it looks like /dev/sda9 mounted twice (/ and /home are both the same device). That is definitely incorrect, you ought to fix it somehow.

Code:

As I am completely new to linux\Fedora, I am unaware of my mistake and has allowed it to happen. so what must I do to
correct the mistake? 
Do I have to re-install Fedora? and if yes how should I partition it?
Thanks

Penstroke4 · 04-06-2023, 12:54 AM

Quote:

Originally Posted by mrmazda

I did ask for output from cat /etc/fstab early in thread, but it never came. Same partition mounted to both / and /home doesn't bode well for successful repair. Did OP save any older copies of fstab we can take a look at and compare to the forthcoming current version?

Code:

I may have tried going to /etc/fstab earlier but was lost in xfce terminal (is a linux newbie -do not know how to operate a terminal)
and gave up trying.
Now at this point what must I do? Do I have to re-install Fedora?
Thanks

mrmazda · 04-06-2023, 01:15 AM

Quote:

Originally Posted by Penstroke4

Now at this point what must I do? Do I have to re-install Fedora?

Code tags are for pasting input/output from running commands, to preserve their formatting, not for ordinary comments.

Command output can be redirected to a file, and the file used to copy and paste from. e.g.:

Code:

cat /etc/fstab > newfile.txt

would make a copy of /etc/fstab named newfile.txt in the current directory.

Whether you have a repairable problem I have doubts about, especially if you are unable to show us the content of /etc/fstab. Starting over by installing afresh is very likely to be the easier path forward. I would like to see output from sudo fdisk -l and content of /etc/fstab first.