Quick anecdote with Plasma [ Its already solve, i just want tell it ]

inukaze · 04-16-2024, 08:08 AM

Yesterday i connect a aditional HDD just to extract file to my main HDD (Where is Slackware64 15.0 installed)

During the file transfer, the electricity cut off for few minutes, when i restart, the system says the in inconsistent, i reboot and start via pendrive with Porteus and i check every partition i can, after i shutdown pc.

i disconnect the additional hdd, and power on, and start slackware, but hang up on login screen of Plasma. i press Alt+Ctrl+Backspace and i select Xfce and this start without problems

i try to execute "systemsettings5" does not show nothing but does not start.
i try like 3 times but ever the same result i decide make the follow on xfce terminal:

Code:

cd "$HOME"
rm "$HOME/.config/plasma-org.kde.plasma.desktop-appletsrc"
rm -rf .kde/share/config/plasma-*
rm -rf .kde/share/config/kdeglobals
rm -rf .kde4/share/config/plasma-*
rm -rf .cache

i restart, and well Plasma try to start but does not show nothing right, i change to xfce and try execute again systemsettings5 and gave me errors with kcm, qml and kirigami. i just decide use the follow commands :

Code:

slackpkg remove kcm
slackpkg remove kwallet
slackpkg remove kirigami
rm -rf /usr/share/kpackage/kcms/kcm_landingpage
rm -rf /usr/lib64/qt5/qml/org/kde/kirigami*

i reboot and see some errors on sddm related to kirigami again to xfce-terminal

Code:

slackpkg reinstall kirigami2 plasma-framework qqc2-breeze-style sddm sddm-theme-artix kcm kwallet ; ldconfig

after i restart, and well i decide to post that here right now, because i think should exist a very ease method to fix when plasma hang up during login show the gearwell animation and with less steps

pan64 · 04-16-2024, 09:32 AM

not really. An outage like that may cause any kind of issues, there is no general way to recover (except the reinstall).

henca · 04-16-2024, 12:10 PM

Data on multiple partitions might break at a power outage. However, a partition written to is more likely to break at a power outage.

Some people might claim that there is not much need to care about broken file systems today when we have journaling file systems, and I might be old school, but this is how I prefer my installations:

The root partitions should be rather small to minimize risk of hard to fix corruptions.
/var and /tmp which might get a lot of writes should be on separate partitions.
/usr and /opt which contain a lot of data but don't get much writes should be on separate partitions. This makes big amounts of data more likely to survive a power outage.
If you have a local /home it should be on a separate partition, that might also make it easier to move /home to newer installations or share /home on multiboot installations.

To say that the root partition still is small these days might sound as a joke when it is bloated with things like /lib/firmware, but at least I try to keep it as small as possible.

In your case it seems as if file got broken both in /home and in /usr. At this point, you have found some problems and been able to repair them, but you might not be sure that you have found all problems caused by the power outage.

regards Henrik

inukaze · 04-16-2024, 06:36 PM

Quote:

Originally Posted by henca

Data on multiple partitions might break at a power outage. However, a partition written to is more likely to break at a power outage.

Some people might claim that there is not much need to care about broken file systems today when we have journaling file systems, and I might be old school, but this is how I prefer my installations:

The root partitions should be rather small to minimize risk of hard to fix corruptions.
/var and /tmp which might get a lot of writes should be on separate partitions.
/usr and /opt which contain a lot of data but don't get much writes should be on separate partitions. This makes big amounts of data more likely to survive a power outage.
If you have a local /home it should be on a separate partition, that might also make it easier to move /home to newer installations or share /home on multiboot installations.

To say that the root partition still is small these days might sound as a joke when it is bloated with things like /lib/firmware, but at least I try to keep it as small as possible.

In your case it seems as if file got broken both in /home and in /usr. At this point, you have found some problems and been able to repair them, but you might not be sure that you have found all problems caused by the power outage.

regards Henrik

right now i am thinking on resize partitions becuase Windows 10 & Slackware 15.0 (32 Bits) i am not using on home are doing nothing, i prefer re-assing that space on my main s.o

Code:

 df -H

Quote:

S.ficheros Tamaño Usados Disp Uso% Montado en
tmpfs 34M 1,3M 33M 4% /run
devtmpfs 8,4M 0 8,4M 0% /dev
/dev/sda6 75G 65G 6,2G 92% /
tmpfs 1,6G 117M 1,5G 8% /dev/shm
cgroup_root 8,4M 0 8,4M 0% /sys/fs/cgroup
/dev/sda3 1,1G 94M 914M 10% /boot
/dev/sda7 75G 17G 55G 23% /media/Slack32
tmpfs 313M 21k 313M 1% /run/user/1000
/dev/sda1 54G 41G 14G 76% /media/win10
/dev/sda2 109G 103G 5,7G 95% /media/Compartido

my root partition is 65G, but i not have much free space, i does not had install too much on Slackware(64) 15.0

i can grow up the free for /run /tmpfs with fstab options ? because sometimes working with libreoffice take around 30 mins to i can use again the pc looks like hang up, but i think just can be the swap partition use.

if you ask why i assing that space for boot partition is becuase i ever make a working chroot on there, and i ever put things like :
fsck (and all modules i can use)
mc
vi
vim
joe
nano
links2
gpm

and i still thinking how i can do again like with Slackware64 14.2 when i can use "links -g" and start in "VGA 1024x768@24Bpp" with working network connection, for that dates i do too much crazy things but i lost the mayor part, just i can find one or two things i don't forget to put on internet like this -> https://unix.stackexchange.com/quest...n-audio-nv-glx

i ever do things like that, because from 1998 i ever i say the boot partition must containt tools for fix the most common problems of the rest of partitions like incoherent filesystem, or for fix configuration file.

Similar to "Initial Boot Disk" for Windows 95/98/98SE for Installatition, ever start MCDEX and came with tools like "chkdsk", "edit", "mouse", "doskey".

henca · 04-17-2024, 01:21 AM

Tmpfs is a RAM disk, whenever you put something on a directory mounted from tmpfs it will be put in RAM memory or possibly in swap. If the system is rebooted, anything saved in such a location will be lost, but the good thing is that tmpfs can never be corrupted by a power outage.

In your example above you basically have everything except /boot in a single big 65 GB / partition. These 65 GB include /home, /usr, /var, /tmp and /opt. It seems as if your partitioning scheme is mostly done to keep different operating systems installed, being able to multi boot and share data between different OS.

My suggestion of splitting directory tree up in different partitions might have a disadvantage that free disk space will be scattered among different partitions. On the other hand, if /tmp or /var/log fills up it will not affect other partitions if /tmp and /var are on separate partitions.

This might not be the right time to rearrange your directory structure in different partitions, but such a partitioning scheme might be worth to consider for new installations if you live somewhere where power outages occur frequently. Another possible solution to avoid the bad consequences of power outages is to buy an UPS. Some UPSes come with software capable of doing a clean shutdown at a power outage. For some systems I have used UPSes, but I have never used such software. In my experience most power outages are rather short and an UPS will be able to keep power for a few minutes.

regards Henrik

yancek · 04-17-2024, 07:01 AM

Your filesystem partition (sda6) of 75GB shows as 92% full and when it gets to 95%, it may fail or you will be having problems with it and get reports about the disk being full as 5% is reserved for the system. You need to make some changes, rearrange partitions or add a drive.

inukaze · 04-17-2024, 06:30 PM

I prefer re-arrange partitions, 8 years ago, when i use Manjaro i use the follow partitions :

/boot -> Ext2 - Primary
/media/winxp -> ntfs - Primary [ i still thinking right now, how i can extract the main win10 certifies for web browsing, to import to win xp, win10 corrupt that start just for use "Reboot" button on win10, is too much delicated software, make me lost a lot of time, first for entry on recovery the use should force restart when the windows logo appears, 3 times, and after you can try to fix with commands, and not every time works ]

/ -> btrfs - Logical
/usr/share/icons -> ext3 - Logical
/usr/share/themes -> ext3 - Logical
/usr/share/sounds/sf2 -> ext3 - Logical
/media/Debian -> ext3 - Logical
/media/Fedora -> ext3 - Logical

/media/GoboLinux -> ext3 - Logical -> i love the working method of this distro. is something strange at the begin but allow have multiple versions of software without conflict and you can predeterminate with "ls" the version you like the main.

/media/Gentoo -> ext3 - Logical [ i never start again from Stage1 XD is more ease from Stage 3 ]
/var -> ext3 - Logical

/home -> ext3 [ Another HDD ] Primary

/opt -> ext3 [ Same home HDD ] Primary, i put my selfcontent apps here, because ever works on any distro, somethings i need make a "libs/32Bits,64Bits" and custom script for make it work like with RetroArch or Mupen64plus or PPSSPP-SDL or DOSBox-X but ever i can use on any distro after make test.

henca · 04-18-2024, 12:58 AM

Another thing you might want to consider is trying virtualization with something like qemu. If you have enough RAM you might find it more convenient to run different operating systems in different virtual machines rather than rebooting a multiboot system.

m v h Henrik

inukaze · 04-18-2024, 10:52 AM

Quote:

Originally Posted by henca

Another thing you might want to consider is trying virtualization with something like qemu. If you have enough RAM you might find it more convenient to run different operating systems in different virtual machines rather than rebooting a multiboot system.

m v h Henrik

i just have 3GB RAM DDR2 667 MHz / MT

inukaze · 04-18-2024, 04:38 PM

Today on my job pc, i ask for net support to change my from one vlan to another because the DHCP are not assing me an automatic IP. Meanwhile on another area i solve things.

The curious was the support guy ask me how configure, he open the Network settings on Plasma Settings to change configuration. but nothing there becuase at that moment i am using manual IP. i enter on terminal and use su to access root and use netconfig command

and i set NetworkManager and use
/etc/rc.d/rc.networkmanager start

the plasma settings close, and he try to open again, i open terminal tab and use like normal user the command systemsettings5 , and gave me "Error: cannot open display: localhost:0.0" that for me is completly absurd, the systemsettings depend of ip for get value from variable display ? wtf ?

the localhost ip are not changed. and the another thing is absurdo for me, is why use netconfig delete and regenerate a new /etc/hosts file ? i lost a lot of blocked ip :v