I had a cascade of failures that I eventually thought was a BIOS problem. The BIOS would not even diagnose. However, I did get it to run tonight and it says I have a CD/DVD Drive failure. That kept me from doing a last ditch effort to update through a reinstall. I also got a warning that the usb wasn’t working. When it did boot to Plasma, the screen did not fully draw the desktop properly, leaving incomplete and non-responsive boxes onscreen until the system froze and I had to power off to reboot. I did get a marginally functioning desktop when I booted into icewm. I disconnected everything to connect up an old pc for awhile and now, having reconnected everything to the troubled pc, I have Plasma back. !?! I did not attempt to reinstall via usb since, for a couple of days, usb drives were not recognized either. But for some reason, they are tonight.
When I try to do zypper dup, it fails as shown:
Failed to provide Package kernel-firmware-20190409-1.1.noarch (openSUSE-Tumbleweed-Oss). Do you want to retry retrieval?
[repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Can’t provide file ‘./noarch/kernel-firmware-20190409-1.1.noarch.rpm’ from repository ‘repo-oss’
History:
- Can’t hardlink/copy /var/adm/mount/AP_0x7E65EB/noarch/kernel-firmware-20190409-1.1.noarch.rpm to /var/cache/zypp/packages/repo-oss
- Can’t provide ./noarch/kernel-firmware-20190409-1.1.noarch.rpm
Abort, retry, ignore? [a/r/i] (a):
This is package 15 of 360. Zypper reports it as completely downloaded. Previously, I tried to ignore and move on, but I got many instances of the same error on other files. I ran zypper clean with no noticeable effect. I also got warnings that zypper could not write to disk because it was full. The disk is not full. I don’t think that even the partition is full. But, if I run df, I get this:
Filesystem 1K-blocks Used Available Use% Mounted ondevtmpfs 4010068 0 4010068 0% /dev
tmpfs 4020368 19008 4001360 1% /dev/shm
tmpfs 4020368 1564 4018804 1% /run
tmpfs 4020368 0 4020368 0% /sys/fs/cgroup
/dev/sda6 41945088 41045168 82208 100% /
/dev/sda6 41945088 41045168 82208 100% /var/lib/mariadb
/dev/sda6 41945088 41045168 82208 100% /var/lib/mysql
/dev/sda6 41945088 41045168 82208 100% /var/opt
/dev/sda6 41945088 41045168 82208 100% /opt
/dev/sda6 41945088 41045168 82208 100% /var/log
/dev/sda6 41945088 41045168 82208 100% /var/cache
/dev/sda6 41945088 41045168 82208 100% /var/lib/machines
/dev/sda6 41945088 41045168 82208 100% /var/crash
/dev/sda6 41945088 41045168 82208 100% /boot/grub2/x86_64-efi
/dev/sda6 41945088 41045168 82208 100% /var/tmp
/dev/sda6 41945088 41045168 82208 100% /var/lib/libvirt/images
/dev/sda6 41945088 41045168 82208 100% /var/lib/mailman
/dev/sda6 41945088 41045168 82208 100% /var/lib/pgsql
/dev/sda6 41945088 41045168 82208 100% /var/lib/named
/dev/sda6 41945088 41045168 82208 100% /tmp
/dev/sda6 41945088 41045168 82208 100% /boot/grub2/i386-pc
/dev/sda6 41945088 41045168 82208 100% /srv
/dev/sda6 41945088 41045168 82208 100% /var/spool
/dev/sda6 41945088 41045168 82208 100% /usr/local
/dev/sda7 161349660 14483020 146866640 9% /home
tmpfs 804072 16 804056 1% /run/user/1000
/dev/sdc1 2003072 706752 1296320 36% /run/media/bill/84D6-4404
I don’t understand why every folder shows the same status, 100% used, with the same file sizes. Maybe I’m looking in the wrong place or don’t understand the representation. For example, Dolphin shows /boot/grub2/i386-pc as 1.8 MB
I don’t know if the machine will boot from a usb drive. It should, but in past attempts at fixing this problem, the usb was not recognized just like the failed CD/DVD drive. If I can copy the Tumbleweed net install to a usb drive, I would gladly do a reinstall if that would let me update.