• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Please let me know if the UPS that I want to buy is good or not for my PC.

The UFS driver is affected by a bug...the fix has been committed but it does not work on Ubuntu noble....
 
The UFS driver is affected by a bug...the fix has been committed but it does not work on Ubuntu noble....
What about not mounting the UFS partition and not using that driver ? A bug in the UFS driver could cause memory corruption elsewhere leading to segfaults.

Here is a link with message by someone having trouble with zfs filesystem and the same error message in the logs:


So it looks like this bug affects other parts of the kernel.
 
--> What about not mounting the UFS partition and not using that driver ? A bug in the UFS driver could cause memory corruption elsewhere leading to segfaults.

I don't think this is the cause. I mount the UFS disk in Linux very rarely.

The ZFS disk just recreated (and that now is powered by the USB hub) is showing again permanents errors (I'm running FreeBSD) ; I'm thinking to convert the ZFS disks into UFS disks.
 
FreeBSD does not work with ext4 as file system. But I can use UFS instead of ZFS. (I say this because the ZFS file systems broken here are those of the external USB disk such as the SATA disks where I have installed FreeBSD : there are no difference if they are USB or SSD SATA,both tend to break very fast). Its not a good idea to use ext4 for the extenal disks because the fuse driver for ext* on FreeBSD is not stable,such as the NTFS one.
 
Surprising, why didn't they just port the code from Linux ? Well, as far as stability of your Ubuntu system is concerned, try not to mount those UFS disks and switch to ext4 if that does not help.
 
I don't know. I rarely use Ubuntu. I use it only when I should copy a large amount of heavy files from a disk to another one because if do it in FreeBSD it will take ages. I'm more worried about the stability of the disks where I keep my personal files and where are stored the FreeBSD system files. The downside is that I can't switch from FreeBSD to Ubuntu to copy a big amount of files to an UFS disk because 1) the UFS driver on Ubuntu is bugged 2) it is read only. So,I should find another method. Maybe not rebooting in Linux but doing the operation in FreeBSD using a bhyve / Linux virtual machine where I attach the NTFS / ZFS disks where I want to copy the files from / to. That's because Linux has a stable NTFS and ZFS driver so that it can be used like a bridge. At the same time I can copy the files from and to the UFS and the ZFS disks directly in FreeBSD. Yeah the tricky path is from / to NTFS / ZFS (because this can't be done in FreeBSD) and from / to UFS / ZFS (because this cannot be done in Linux). I've also tried to use ZFS in Windows :). I did it,it can be done without having the problem of the data corruption,but my system is tricky and cumbersome). A new idea that I'm thinking to materialize is to configure SSHFS to transfer the files from / to Linux / FreeBSD.
 
Last edited:
Looking more narrowly - the question was why do you have problems with the Ubuntu system, and it seems there is a known bug that gets triggered when you mount UFS filesystem. So the solution is to not do that and see whether any other problems arise.

As for copying files, if you are doing developement it can be helpful to have one stable system using, for example, Ubuntu and ext4 that hosts the files and you copy them back and force over network using NFS for Linux and BSD and samba for Windows. 10Gb adapters (and switches) are pretty cheap nowadays.
 
I have a problem / not very well understood / at the moment,that affects my ZFS disks but I suspect that it affects even the UFS disks. Even if the disks behave differently. The UFS disks don't get corrupted under stress. The bug in the UFS driver on Ubuntu does not matter because I use it rarely. The problem that I have hits the disks when I use Ubuntu or FreeBSD,with and without the bug triggered by the loading of the UFS driver.
 
Last edited:
Might want to start a new thread as this is no longer about the UPS
 
Might want to start a new thread as this is no longer about the UPS

Are you sure that the cause of my problem is not the UPS ? at the moment I didn't find the real cause,so I'm opened to a lot of hypothesis,including the UPS,since I read that someone has had problems like mine and he said that it was the UPS that he had bought.

I've reinstalled FreeBSD on a UFS fs and I still have problems. On the kernel log,I see a lot of these errors :

Code:
pid 5334 (bsdisks), jid 0, uid 0: exited on signal 6 (core dumped)

everytime it happens,Firefox stops working and I should restart it.
 
Last edited:
Well, there is your answer - corrupt memory will give you all those weird errors you saw. If you are lucky it is just one stick. It depends on the surge, but I would find it surprising if it damaged RAM well inside the computer without obviously frying other components closer to power input.

It could just be a bad stick, or it could be an overheating stick - check your cooling.
 
Already made the tests for both the sticks,one at a time. Both are heavily damaged.
 
Kingston has a lifetime warrantee
 
Last edited:
I'm having a doubt. And if the memory sticks are good,but my motherboard isn't ? I need to check this asking to someone to try my banks using his motherboard.
 
You really don't want to risk trying bad RAM in a good machine as that could corrupt their OS; better if you can borrow some RAM to try in your machine.
 

"Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers"

You have Kingston DDR4-2666 RAM
 
It could be a coincidence. From my point of view is still valid the theory of the memory banks corrupted.
Read well : "to improve",not to fix.
 
Upgrade the BIOS
 
Usage : efiflash [Input or Output File Name] [Command]..

Switch options for Efiflash.exe:

/C - Clear DMI data. (default: Keep DMI data)
/S - Save Original BIOS Image to Disk
/R - Reboot System after BIOS Update
/DB- Update both main & backup BIOS

so,is this command the correct one ?

Code:
efiflash Z390AORUSPRO.F13 /S /R /DB ?

should I keep or clear the DMI data ?
 
Back
Top