My system , Leap 15.0 started to freeze. I first noticed it when watching a video on youtube. … Got suspicioues and wanted to get install the latest patches via Yast.
System stopped after a few downloads, Error msg
Can’t find a writable directory to create an attach point !!!
In Event notification the "KDE free space notifier deamon :
Running low on disk space !!!
Checked the disk space:
/home 158 GiB free of 168 GiB
/root 24 GiB free of 10 GiB
… to me it looks like a hardware issue. I have a SSD from Kensington.
Valid comment … but I can’t do your suggested check … since I can’t fire up my system any longer. So I guess I have to try to use the rescue boot option and try the command you suggested.
Hi, thanks for the link.
Unfortunately I can not work one my (faulty)system. After a few (3-4) commands the system freezes and I have to reboot.
when booting with the rescue system, and enter
$btrfs filesystem show /
$Error: not a valid btrfs file system
comes up
I have the suspicion that there is not a snapper overflow… but don’t know since the command “snapper” is not known.
if it is a hardware fault, how can I interrogated the ssd ?
From an installation point of view the system has no special add ons for file system or other things.
I can’t provide screenshots due to the almost immediate freeze and I access the forum via an iPad.
I wonder how I reasonably progress since I am not familiar with filesystem maintenance.
When I boot “Rescue System” from 15.0 installation media, after keying Ctrl-Alt-F3 I see:
openSUSE Leap 15.0 Rescue System
rescue login: root
Have a lot of fun...
tty3:rescue:~ # btrfs --help
usage: btrfs filesystem <group>] <command> <args>]
btrfs filesystem df [options] <path>...
I don’t think “(recovery mode)” in your Grub menu is intended for solving a freespace shortage. The “$” prompt is a signal you’re not where you need to be, but maybe you can use:
$ btrfs filesystem show /
From $ prompt, please show complete output from
$ df; $ cat /etc/fstab; lsblk
These commands’ output each can be redirected to file by appending > someeasytorememberfilename to make copy and paste the output here easier.
Thanks for your reply. I guess I have not properly explained the situation I am faceing. My system freezes ,after boot and a few commands within 5 minutes. I basically have no chance to capture the command results and therefore post them on the forum.
I noted the problem when the system froze during a YouTube video (did a reboot) . By coincidence I Decided to install updates via yast. There the download stoped half way through and a msg came , something like can’t establish link to create file pointing to the assumption the disk is full which was also indicated b
y the idea freespace daemon.
I can’t execute the commands in my system have booted.
Via the grub rescue system … entered by typing
btrfs file system show
lable : none uuid 9a01…
total device 1 Fs bytes used 13.9 GiB
devid 1 size 40 GiB used 16 GiB path /dev/sda3
I give you a subset of the output for df; cat /etc/fstab; lsblk
1k blocks. Used. Available used
dev/loop0 66560. 66560. 0. 100%
dev/loop1. 13184. 13184. 0. 100%
devtmpfs. 3994304. 8. 3994296. 1%
dev/loop2. 50816. 50816. 0. 100%
dev/loop3. 45184. 45184. 0. 100%
dev/loop4. 4224. 4224. 0. 100%
As I said when executing the commands on the original system the system freezes and no out put
On the page I provided a link to in comment #7 are the instructions you need to follow, in particular, what it shows at
Disk Space Full Because of Snapper
where is says
List the snapshots in Snapper
and
Delete one or more snapshots from Snapper
These two snapper commands (list and delete) need to be done before there is time for the system to freeze. Once you have deleted at least one snapshot you should be able to work normally again.
Which AMD AM4 Chipset is present on your Mainboard? – X470, X370, X300, B450, B350, A320, A300?
I’m beginning to suspect that, the X470, B450, A320 chipsets are preferred for the 2nd generation Ryzen™ CPUs (Zen+) …
Is the UEFI/BIOS version currently on your Mainboard the correct one for the Ryzen™ CPU/APU you’re using?
Please be aware that, despite the Leap 15.0 Kernel version (4.12) being supposedly OK for Ryzen™ CPUs, usually at least Kernel version 4.15 is needed to properly support Ryzen™ CPUs and, definitely needed if you have an APU – Vega graphics …
Therefore, you may have to move to Tumbleweed (Kernel version 4.20) …
For the case of Btrfs, “du” and “df” do not behave correctly.
You have to use “btrfs filesystem df /” and “btrfs filesystem du --summarize /” for correct results.
More options are available via the “btrfs-filesystem” man page.
But, please be aware that, because of possible issues with the AMD Ryzen™ CPU/APU, you may have a corrupt Btrfs file system – meaning that, you’ll have to re-install the system – with reformatted system and user partitions – once the Ryzen™ issues have been resolved …
@mrmazda:
re requested command outputs: I am unable to execute the commands, the system freezes after hitting “return”
if, and I don’t know, the rescue system uses the existing files of the original system, I cannot find a fault. Mind you “snapper” can’t be executed in the rescue system.
@dcurtisfra:
The system was only recently (6 month ago) built.
Motherboard
Asus Prime B350-Plus. Chipset => B350
CPU
Ryzen 5 1500x Quadcore
Considering this hardware, do I have to move to Tumbleweed to get the right kernel version?
I think I have no choice other than to re-install maintaining the /home to save my user data and then maybe upgrade to tumbleweed.
I wonder der if that system is using the same filesystem/contend. I could via the rescue system mount the original partition , sda3, where my OS resides.
As I said , no error was reported. On the other hand ,there was clearly a diskspace shortage noted by the kde diskspace deamon.
That one needs some effort on your part. It does not automatically mount HD partitions.
I wonder der if that system is using the same filesystem/contend. I could via the rescue system mount the original partition , sda3, where my OS resides. As I said , no error was reported. On the other hand ,there was clearly a diskspace shortage noted by the kde diskspace deamon.
Mounting your 15.0 system partition while in rescue boot is what is needed. I don’t know the specifics of what you need to do, because I do not install or use BTRFS. The basic procedure would be to mount it, confirm lack of freespace is due to excessive number of snapshots maintained, and once confirmed, remove at least one. “How to repair a broken/unmountable btrfs filesystem” on the comment #7 URL seems like would be the instructions you need to follow.
@mrmazda
Success !!! I followed the instructions on the link you provided. … again … however I noted that I did not mount the filesystem in the first go.
The results were still umbigoues. There was no clear indication the I unlocked something. The commands snapper and zipper did not work.
l
I think the command btrfs scrub … did the job.
I fired the original OS up to my surprise it did not freeze after a few minutes. In the konsole I called up snapper and deleted a number of old entries.
So that is all good, BUT , I don’t know what has happened. It seam to be speculations since I never found direct evidence that the filesystem was out of space.
Anyway, if it happens in the future again I will reinstall with a different filesystem. So my question , what file system do you use for the OS?
@dcurtisfra
It looks like we found and corrected the problem. However since I never found a definit answer that the filesystem is full, your assumption may still be correct.
What are your thoughts ? Is it possible to upgrade from leap 15 to the latest tumbleweed ?