sha256: ///var/db/locate.database: Input/output error / cp: ///usr/lib/debug/usr/bin/llvm-objdump.debug: Input/output error

Do you like this error ?

Code: 
[50626.815437] traps: Isolated Web Co[94124] general protection fault ip:75fb1f3846f2 sp:7ffedb7b41d0 error:0 in _libxul.so (deleted)[75fb1af46000+6526000]

the error is reported even if I have removed and reinstalled Firefox...the file is not on the disk anymore and perhaps its name is changed,but...it crashes anyway :D
 
The ZFS disk just recreated (and that now is powered by the USB hub) is showing again permanents errors.
 
two things, a bunch of these more recent errors come from Linux; freebsd doesn't write log messages that look like that. second, it sounds like your drive is failing, thus leading to corruption. when this happens to code on disk, applications will crash. you should replace the disk.
 
VladiBG said:
In provided log i see many USB hub connect/disconnect events.
Do not use USB attached disks.
Click to expand...

Sure. I've disconnected a lot of USB disks,but I still see the same errors. Now,I would use a different file system on one USB disk,to check what happens. BTW I don't know which file system can I use instead of ZFS. I can say that in that disk I need to store the bhyve vms that are files of 200 GB each one. Can you suggest me a file system supported by FreeBSD that allows it ? vfat maybe ? or ?
 
atax1a said:
two things, a bunch of these more recent errors come from Linux; freebsd doesn't write log messages that look like that. second, it sounds like your drive is failing, thus leading to corruption. when this happens to code on disk, applications will crash. you should replace the disk.
Click to expand...

In FreeBSD I see different errors,but I suspect,I'm almost sure,they have the same origin. They happens not only on the USB disks,but also in the SATA SSD disks (I've bought one of them 1 month ago ; I've installed FreeBSD on ZFS there and now it is corrupted). I'm sure that my USB disks don't have hardware problems.

Yesterday 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. Sometimes even the PC reboots.
 
cracauer@ said:
waitaminute - what filesystem are you using on there right now?
Click to expand...

I've recreated the ZFS structure on two USB disks,UFS on another one. Plus,I'm using ZFS on a Sata SSD disk. On another one I'm using UFS. I see problems in every disk,doesnt care which FS is used,but UFS does not corrupt itself,only the applications stop working and they create a core dump. In ubuntu I use ext4 and I don't see errors there,I see errors on the external disks attached. Not in the UFS disks because it is read only,but in ZFS disks. One only time I seen a big corruption in the NTFS disk,but I'm not sure if it correlated with the obscure problem that I'm having,because it happened one time only.
 
cracauer@ said:
If the computer reboots your hardware is broken.
Click to expand...

I'm trying to try different solutions to determine if and when the errors happens. Now I want to "format" one USB disk with a different file system. Not UFS and not ZFS,but one fs that's supported by Linux and FreeBSD and that allows to store files of 200 GB. Can you suggest one ?
 
ZioMario

Post in thread 'sha256: ///var/db/locate.database: Input/output error / cp: ///usr/lib/debug/usr/bin/llvm-objdump.debug: Input/output error'

Code: 
# memtester 8000 5
memtester version 4.6.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 8000MB (8388608000 bytes)
got  8000MB (8388608000 bytes), trying mlock ...locked.
Loop 1/5:
  Stuck Address       : ok     
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok...
 
cracauer@ said:
That's not memtest86+.
Click to expand...

What's the difference ? It's just another memtester. I found the fs i was looking for : exFAT,that's well supported by FreeBSD :

www.micski.dk

How to mount exFAT formatted SD memory card on FreeBSD

This is the procedure for mounting the exFAT file system on FreeBSD. exFAT are used on SD memory cards, such as SDSC, SDHC and SDXC.
www.micski.dk www.micski.dk

will be a test to see if it gives problems of corruptions or reboots when I copy my files from and to the disk formatted with it.

# pkg install fusefs-exfat
Click to expand...

fusefs : not a good sign.
 
memtest86+ runs as its own operating system, not under the control of a kernel. you need to boot directly to it, not run it from inside another OS.

For reference, https://memtest.org provides .iso files that you can dump directly to a flash drive and boot to. let this run overnight, then come back with the results.
 
Memory corrupted :

ibb.co

Whats-App-Image-2025-02-02-at-03-44-40 hosted at ImgBB

Image Whats-App-Image-2025-02-02-at-03-44-40 hosted in ImgBB
ibb.co ibb.co
ibb.co

Whats-App-Image-2025-02-02-at-03-45-25 hosted at ImgBB

Image Whats-App-Image-2025-02-02-at-03-45-25 hosted in ImgBB
ibb.co ibb.co
ibb.co

Whats-App-Image-2025-02-02-at-10-52-05 hosted at ImgBB

Image Whats-App-Image-2025-02-02-at-10-52-05 hosted in ImgBB
ibb.co ibb.co
ibb.co

Whats-App-Image-2025-02-02-at-10-53-13 hosted at ImgBB

Image Whats-App-Image-2025-02-02-at-10-53-13 hosted in ImgBB
ibb.co ibb.co
ibb.co

Whats-App-Image-2025-02-02-at-11-18-29 hosted at ImgBB

Image Whats-App-Image-2025-02-02-at-11-18-29 hosted in ImgBB
ibb.co ibb.co
 
at first glance that indeed smells like bad memory; in all our years we've never seen a motherboard go bad before the RAM, so we'd swap the RAM first. but yeah, bad RAM explains your symptoms.
 
Just always use ECC RAM and you will never need to run memtest or to scratch your head.
On a more serious note, I think that in my life I have almost all of these potential sources of bad memory:
  • bad memory chip
  • bad memory module connector
  • bad memory slot
  • bad trace from a memory slot to a CPU socket
  • bad pin in a CPU socket
  • bad pin on a CPU
  • a CPU with a defect
I hear that overclocking and unstable power can also cause such issues, but I have not experienced those myself.
 
You must log in or register to reply here.
Back
Top