[SOLVED with REINSTALL & RESTORE] BFS health issue -- checkfs (seems) cannot fix it

KitsunePrefecture · February 18, 2024, 7:34pm

Ahoy,

Only one glitch remained from this earlier issues that forced me to not use my Dell Precion 6700M for a week.

I used

checkfs -c /boot
checkfs /boot
checkfs -c /boot

combo

as I used to do after an unwanted or forced reboot …
and now I have a remaining error message - it does not matter how many times I iterated the commands.
It hat not happened earlier , never. I could clean BFS fully earlier. Now it remains.

oss_audigyls (inode = 2690977), has invalid block run(s)

Welcome to the Haiku shell.

~> checkfs -c /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        39601 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           37384
        directories     1473
        attributes      415
        attr. dirs      281
        indices         48

        direct block runs               42386 (9.30 GiB)
        indirect block runs             821 (in 51 array blocks, 734.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        39601 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           37384
        directories     1473
        attributes      415
        attr. dirs      281
        indices         48

        direct block runs               42386 (9.30 GiB)
        indirect block runs             821 (in 51 array blocks, 734.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs -c /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        39601 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           37384
        directories     1473
        attributes      415
        attr. dirs      281
        indices         48

        direct block runs               42386 (9.30 GiB)
        indirect block runs             821 (in 51 array blocks, 734.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~>

What is your opinion about it ?
Is there another tool or command to fix it ?

EDIT #1:

This status escalated to a barely usable 64 bit Haiku* that I try to investigate and resolve in this state - if possible.

mention it as purely 64 bit Haiku as meanwhile I switched
from
R1B4 (hrev56578 + 95)
to
nightly (hrev57588)

KitsunePrefecture · February 18, 2024, 8:47pm

I used
shutdown
in Terminal, to turn off my PC -
It was needed to switch the used USB port in which my Kingston thumbdrive with Haiku BFS filesystems were plugged in.
I had a faint chance that another port usage eliminates the usb_disk error messages in syslog at least …

Anyway …
I used again the combo above, and get a new error message :

VCS_INFO_detect_git (inode = 3897793), could not be opened

~> checkfs -c /boot
VCS_INFO_detect_git (inode = 3897793), could not be opened
oss_audigyls (inode = 2690977), has invalid block run(s)
        39634 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        2 blocks could be freed

        files           37408
        directories     1480
        attributes      416
        attr. dirs      282
        indices         48

        direct block runs               42415 (9.33 GiB)
        indirect block runs             819 (in 50 array blocks, 733.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        39635 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           37409
        directories     1480
        attributes      416
        attr. dirs      282
        indices         48

        direct block runs               42416 (9.33 GiB)
        indirect block runs             819 (in 50 array blocks, 733.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs -c /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        39635 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           37409
        directories     1480
        attributes      416
        attr. dirs      282
        indices         48

        direct block runs               42416 (9.33 GiB)
        indirect block runs             819 (in 50 array blocks, 733.73 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~>

…the horrible virtual memory errors possibly leads back to a PC issue which may requires some maintenance - swipe off dust and possibly replace thermal paste as well, as finally I suspected some HW error also arises at me - if none has serious errors like at me.
In Diagnostics on Saturday the memory checks finished successfully and Thermal sensor had not alarmed at CPU, as it did on last time, so I was dare to boot Haiku and installed latest updates as I shared in an another thread before - yesterday - but finally I had to revert back haikuwebkit where the previous error came at crash report

0x7fd17cd4f390	0x17bb15f468c	WebCore::TimerBase::heapDecreaseKey() + 0x5c

arised again. That never ever comes up at haikuwebkit 1.9.8.1 for me.

However cannot use many apps now :-))

For example

VLC crashed with

0x7f3bb889afd0	0x11c9767c5c	llvm::object_creator<_GLOBAL__N_1::CommandLineParser>::call() + 0x4c

Falcon crashed with folllowing errors in crash reports :

0x7febbc446b70	0x18fd6976c5c	llvm::object_creator<_GLOBAL__N_1::CommandLineParser>::call() + 0x4c

QMPlay2 not even starts on GUI !..
… launched in Terminal - results in the following :

~> /boot/system/apps/QMPlay2/QMPlay2 
[18 Feb 2024 21:30:02.853] QMPlay2 crashed (SIGSEGV)


[1]+  Megállítva            /boot/system/apps/QMPlay2/QMPlay2
~>

As you can see … QMPlay2 crashed …
I got back the prompt after [CTRL] + [Z] used in Terminal.

Dooble also cannot be launched from GUI … just as QMPlay2.
Strange fact also - it does not come up in Deskbar’s
Last used programs menu item. I have to launch it always from Applications menu item.
When I attempted to launch it in Terminal – something may happened in the background, but in this case – no messages, just get back the prompt finally after some few secs :

~> /boot/system/apps/Dooble/Dooble 
~>

KitsunePrefecture · February 18, 2024, 9:28pm

When I launched Haiku R1B4 64 bit … I get only by filtering syslog for error in messages

Welcome to the Haiku shell.

~> grep -E -i error /var/log/syslog|grep -v DEFERRED
USER: Error in AllUnarchived method of object of type 5BView
USER: An error occured during unarchival, cleaning up.
DAEMON 'DHCP': /dev/net/iprowifi4965/0: DHCP status = No error

Above mentioned usb_disk errors and virtual memory issues happens LATER - unfortunately
there are no timestamps in syslog messages :-((

~> grep -E -i error /var/log/syslog|grep -v DEFERRED
USER: Error in AllUnarchived method of object of type 5BView
USER: An error occured during unarchival, cleaning up.
DAEMON 'DHCP': /dev/net/iprowifi4965/0: DHCP status = No error
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: read failed: I/O error
KERN: could not read block 3897792: bytesRead: -1, error: I/O error
KERN: bfs: could not read inode: 3897792: I/O error
KERN: bfs: Could not open inode at 3897792: I/O error
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3017032085:  2233] ReadFileData(28397931, 0xffffffffd22b0000, 22419) failed to read data: I/O error
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3027050268:  2233] ReadFileData(28397931, 0xffffffffd22b0000, 22419) failed to read data: I/O error
KERN: reading page from cache 0xffffffffd2076d48 returned: I/O error!
KERN: vm_page_fault: vm_soft_fault returned error 'I/O error' on fault at 0xfb453f1f10, ip 0xfb41fe0c5c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xc665c8b04c, write 0, user 1, exec 0, thread 0x8b9
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3433072800:  2357] ReadFileData(28397931, 0xffffffffd2450000, 22419) failed to read data: I/O error
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3444583446:  2357] ReadFileData(28397931, 0xffffffffd2450000, 22419) failed to read data: I/O error
KERN: reading page from cache 0xffffffffd2076d48 returned: I/O error!
KERN: vm_page_fault: vm_soft_fault returned error 'I/O error' on fault at 0x12742a5cf10, ip 0x1273f64bc5c, write 0, user 1, exec 0, thread 0x935
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3502798173:  2462] ReadFileData(28397931, 0xffffffffd2460000, 22419) failed to read data: I/O error
KERN: usb xhci 0: transfer error on slot 2 endpoint 3: Stall
KERN: usb error xhci 0: cancel queued transfers: halted endpoint, reset!
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: usb_disk: block read failed when filling partial buffer: I/O error
KERN: usb_disk: read failed: I/O error
KERN: unknown: [3512820898:  2462] ReadFileData(28397931, 0xffffffffd2460000, 22419) failed to read data: I/O error
KERN: reading page from cache 0xffffffffd2076d48 returned: I/O error!
KERN: vm_page_fault: vm_soft_fault returned error 'I/O error' on fault at 0x66244b3f10, ip 0x66210a2c5c, write 0, user 1, exec 0, thread 0x99e
~>

KitsunePrefecture · February 18, 2024, 10:05pm

So, it is finally USB port independent …

EDIT :

At least

Streamradio <|:-p

and

Webpositive <|:-P

are

Atomic-Blast-Proof …

…they works !

EDIT :

{ HERE it would have been a fancy anim gif that would show some dancing in front of a display, but as Humdinger would get shocked again about it … I ignore my urge … and just recommend to listen the next title I written at bottom - I could, using Streamradio, selecting : EBS | Movie Soundtracks radio station –

I have a mostly crappy Haiku now … but who cares ?!
→ I have Web+, so I can read and write,
→ meanwhile I’m listening cool, and various enthusiastic or just nostalgic movie theme musics … even Enya or more 8D
thanks to Streanradio (!) …
So try listen this great song below or other …}

JEFF WAYNE - THE EVE OF THE WAR

KitsunePrefecture · February 24, 2024, 10:38pm

Well,

meanwhile I changed to nightly - hrev57588 -

~> uname -a
Haiku Haikkurat.szabadpart.net 1 hrev57588 Feb 21 2024 07:03:15 x86_64 x86_64 Haiku
~>

… using the bash script from @SantiagoLema.

Thanks for that - installation was qiute easy with git - it was really smooth and simple to switch from beta4 to selected nightly using it.
I understood considerations, but as this Haiku 64 bit installation until now became crappy enough to not busy with risks or concerns.

I was hoping at least my USB (ehci) errors would be eliminated by new kernel / driver inventions, but seems my high hopes were cheated …

~> grep -E -i error /var/log/syslog|grep -v DEFERRED
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558

[deleted same lines to fit this text section or post character limit ]

KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 1: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0xb3f700) error: 0x00088d46
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558

[deleted same lines to fit this text section or post character limit ]

KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 2: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0xf79f80) error: 0x000d8d40
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [830820110:  1709] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: ReadFileData(27985806, 0xffffffffb9710000, 24677) failed to read data: I/O error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [830820138:  1709] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 2: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0xf7c480) error: 0x24001d40
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [830851570:  1709] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: ReadFileData(28397931, 0xffffffffb9710000, 22419) failed to read data: I/O error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [830851600:  1709] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 2: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0xf7d780) error: 0xa4001d40
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [830862107:  1709] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: ReadFileData(28397931, 0xffffffffb9710000, 22419) failed to read data: I/O error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: reading page from cache 0xffffffffd8050468 returned: I/O error!
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'I/O error' on fault at 0x8665fc2f10, ip 0x8662bb1c5c, write 0, user 1, exec 0, thread 0x6ad
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558

[deleted same lines to fit this text section or post character limit ]

KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 2: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0x1013300) error: 0xa8001d40
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [851884135:  1717] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: ReadFileData(28397931, 0xffffffffb7bd0000, 22419) failed to read data: I/O error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [851884174:  1717] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb error ehci 2: KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: qtd (0x1013e80) error: 0x98002d40
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: usb_disk: request_sense: key: 0x03; asc: 0x11; ascq: 0x00; Unrecovered read error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: unknown: [851904508:  1717] KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: ReadFileData(28397931, 0xffffffffb7bd0000, 22419) failed to read data: I/O error
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: reading page from cache 0xffffffffd8050468 returned: I/O error!
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: vm_page_fault: vm_soft_fault returned error 'I/O error' on fault at 0xedf8b3bf10, ip 0xedf572ac5c, write 0, user 1, exec 0, thread 0x6b5
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558

[deleted same lines to fit this text section or post character limit ]

KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: debug_server: KillTeam(): Error getting info for team 1717: Operation on invalid team
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558

[deleted same lines to fit this text section or post character limit ]

KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x90, ip 0xd00e4cc04c, write 0, user 1, exec 0, thread 0x558
KERN: PCI:   Extended capabilities: Advanced Error Reporting, Serial Number
KERN: PCI:   Extended capabilities: Virtual Channel, Advanced Error Reporting
KERN: PCI:   Extended capabilities: Virtual Channel, Advanced Error Reporting
KERN: ahci: sata_request::finish ATA command 0xa0 failed: status 0x51, error 0x20
KERN: ahci: sata_request::finish ATA command 0xa0 failed: status 0x51, error 0x20
KERN: usb_disk: got device name "KingstKERN: on DT Micro PMAP": No error
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: KDiskDeviceManager::InitialDeviceScan() returned error: Bad data
KERN:   media status:      No error
KERN:   media status:      No error
KERN:   media status:      No error
KERN:   media status:      No error
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
AUTH 'sshd'[823]: error: setsockopt IPV6_V6ONLY: Operation not supported
AUTH 'sshd'[823]: error: Couldn't create pid file "/packages/openssh-9.6p1-1/.self/var/run/sshd.pid": No such file or directory
DAEMON 'DHCP': /dev/net/ipro1000/0: DHCP status = No error
KERN: intel_extreme: compute_dpll_g4x: best MHz: 140 (error: 0)
DAEMON 'DHCP': /dev/net/iprowifi4965/0: DHCP status = No error
USER: Error in AllUnarchived method of object of type 5BView
USER: An error occured during unarchival, cleaning up.
KERN: PCI:   Extended capabilities: Advanced Error Reporting, Serial Number
KERN: PCI:   Extended capabilities: Virtual Channel, Advanced Error Reporting
KERN: PCI:   Extended capabilities: Virtual Channel, Advanced Error Reporting
KERN: ahci: sata_request::finish ATA command 0xa0 failed: status 0x51, error 0x20
KERN: ahci: sata_request::finish ATA command 0xa0 failed: status 0x51, error 0x20
KERN: usb_disk: got device name "Kingston DT Micro PMAP": No error
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: KDiskDeviceManager::InitialDeviceScan() returned error: Bad data
KERN:   media status:      No error
KERN:   media status:      No error
KERN:   media status:      No error
KERN:   media status:      No error
KERN: ntfs: error: identify_partition: boot signature doesn't match
AUTH 'sshd'[823]: error: setsockopt IPV6_V6ONLY: Operation not supported
AUTH 'sshd'[823]: error: Couldn't create pid file "/packages/openssh-9.6p1-1/.self/var/run/sshd.pid": No such file or directory
DAEMON 'DHCP': /dev/net/ipro1000/0: DHCP status = No error
KERN: intel_extreme: compute_dpll_g4x: best MHz: 140 (error: 0)
DAEMON 'DHCP': /dev/net/iprowifi4965/0: DHCP status = No error
USER: Error in AllUnarchived method of object of type 5BView
USER: An error occured during unarchival, cleaning up.

As you can see above, if you paging the filtered syslog I provided.

Unfortunately - there is no timestamp in syslog at all.

KitsunePrefecture · February 24, 2024, 10:49pm

I have a small question – reading the last lines in syslog

USER: Error in AllUnarchived method of object of type 5BView
USER: An error occured during unarchival, cleaning up.

Is this meaning, the filesystem error I cannot fixing – is on the area of compressed HPKG packages ?

This way works for me some applications - mostly native ones - … meanwhile ported ones are not at all ?..

In this case I would really be interested in the affected package(s?) - if I could find it.

At least I would have a tool/command which can help me to find what is relates to the given inode number - (inode = 2690977) - in my case.

~> checkfs -c /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
bookmarks.json (inode = 5226635), could not be opened
        40851 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        1337 blocks could be freed

        files           38460
        directories     1633
        attributes      422
        attr. dirs      288
        indices         48

        direct block runs               43649 (9.50 GiB)
        indirect block runs             827 (in 52 array blocks, 735.54 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        40854 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           38462
        directories     1634
        attributes      422
        attr. dirs      288
        indices         48

        direct block runs               43654 (9.50 GiB)
        indirect block runs             827 (in 52 array blocks, 736.04 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~> checkfs -c /boot
oss_audigyls (inode = 2690977), has invalid block run(s)
        40854 nodes checked,
        0 blocks not allocated,
        0 blocks already set,
        0 blocks could be freed

        files           38462
        directories     1634
        attributes      422
        attr. dirs      288
        indices         48

        direct block runs               43654 (9.50 GiB)
        indirect block runs             827 (in 52 array blocks, 736.04 MiB)
        double indirect block runs      0 (in 0 array blocks, 0 bájt)
~>

MoldyMallow · February 25, 2024, 12:47am

Backup all your data as soon as you are able to. Your hard drive is a ticking time bomb!

BiPolar · February 25, 2024, 6:59am

FWIW, if you want those, you need to set syslog_time_stamps to true in the kernel settings file (~/config/settings/kernel/drivers/kernel).

KitsunePrefecture · February 25, 2024, 9:27pm

Dear Oscar,

Thanks - it worked
It was really useful for me - sometimes the events’ date/time also helps or critical info.

KitsunePrefecture · March 25, 2024, 1:59am

DISCLAIMER (Present day - 2024-03-24…25):

Well, I had written, the following lines weeks ago, just right that time, when – among the last standing applications – the filesystem degradation reached Webpositive (yet Streamradio and Terminal still worked still Haiku was up and running !)
Not so much long ago I made a compressed archival and a copy as well about my home direwctory, and aslo had an unused 64bit R1B4 installer thumbdrive I made with always trustuble dd command from a helthyi installer image. However it was 1.4 GB size actually.

------------------------------------------------------------------------------------------

Ahoy !

Well, I had not reported my further usage history and investigations here,
however I promised in another thread to write some updates
what I did meanwhile … since I had stopped to sharing my adventures … writing about a damaged Haiku 64 bit instance …

Bug-sy_Haiku

I had made a backup of

my home directory

settings/config alone as well

but as meanwhile installed, re-installed some progs, I should iterate it.

Also created an R1B4 installer USB key, with only the standard size, using the official ISO and dd command, as ehci USB still results in error, and the installer DVD I was written seems hurted or the drive I used was unreliable when I was burnt the image onto it.

Unfortunately BurnIt could not erase the disc under Haiku when I attempted to re-create it.
Unfortunately I do not remember exactly I had written these discs (as I written then 4 discs : 2 DVDs {both the Beta4 installers} and 2 CDs {both the nightlies, 32 and 64 bit} – all onto rewritable discs) on Haiku 32 bit with BurnIt or still on Windows7 using a writer SWs there.
Now I have Haiku only, and seems unusable optical discs and not fully usable writer SW.

Moreover Haiku started to behave strange lately … over, the fact that it had damaged.
Still … I had not input lags or stucks, but now I experience such behaviour :
Haiku stops for longer time … seems the active window is hanging, seemlessly blocks to write, I mean what I am typing to write to the display “immediately”

as it would get into some loops

and when it frees, continue working as normal.
As meanwhile I switched to “nightlies” and folllowed the bleeding adge “current” of those ,
I moved back from hrev57633 to hrev57609, but here it had not stopped, just mitigated to bearable :
→ it does not occur so often
(ok so when I typed previous word just happened, sh¤t, now, and now … how we can strike through what we were written, right now ?)

----------------------------------------------------------------------------------------------

Right, so the past writings ends HERE …
Long story short : Web+ finally crashed, and some things started to annoy me and I may copied or dragged some files elsewhere where those -should be moved or copied - during my backup activities - I really do not exactly know - Maybe BFS has ended so much (directories, files, inodes - I not really interested in it from this point) -
I could not boot into Haiku – I wanna say rather I could not reach the desktop as the splashscreen appeared and stayed really-really long … I gave up for it … I was a bit tired and wanted to avoid further frustration, so I turned to books and music for a while to relax and spend my time with -

I also suspected my laptop vents in air at the bottom, and I use a cooling stand which also vents up cool air, but unfortunately with flying dust as well … so maybe this way the processor and VGA cooler collected some “trouble” in the form of dust on the inner parts.
Also the cooling pastas maybe should renewed … that way I wanted to rest it for a while.

Okidoki - back on track …
anyway, the captain had not left the ship, but after ‘the shipwreck’ (BFS lethal sickness) it was just matter of time to say ‘Good bye!’ to this first 64 bit Haiku install of mine, that started with a creating of enhanced installer (a stI uffed version of Haiku installer on 14 GB instead of 1.4 GB) what finally I used as a daily driver … as I could not install Haiku from install-prepared USB key to iterate install from this onto an USB 3.0 Kingston DataTraveler 100 G3 USB stick - the wanted final destination. I complained about it in another thread.

Now I had some free time …

In this weekend - on Staturday -
there were an annual honorary trip and memorial ceremonies in the mountain of Vértes I participated - at tombs of fallen WWII soldiers and civilians some WWI soldiers as well - with my friends on the fields and forests, and some villages as well … singing loud soldier and folk songs - the popular songs of that time - and our old, new and traditional national anthems. Coronating with a feast at one of our fellows’s small house at last station - Vérteskozma.
(EDIT04 : An article about it - with gallery - ! HUNGARIAN ! … me on right holding a flag of our organisation )

After thIs relaxing event I was felt myself ready to
¤ create a pimped thin installer onto the 1.4 GB image on thumbdrive
¤ re-create/re-use my previous daily driver USB thumbdrive instance onto the 14.0 GB BFS parition – as a fat , stuffed installer – using the above created pimped thin installer.

Both succeed - I spared a long time copying back settings to the first installer drive and installed some must have apps that fitted ont this small free BFS size.
Fortunately the installed packages respects their settings directories/files’ existency - I just lost some browser stuff
( in Webpositive the history; the bookmarks, open tabs were existed with credentials as well ! thanks thanks !!)
(in Web I had not wondered I lost bookmarks - it does always, but settings were remaining : download, magnifying settings, etc. )
(Falkon behaved well : also found my tabs with my mailer site and social media sites)

I had some memory allocation growth, but I updated packages finally then it stopped - it is available on R1B4 also - so cool…
I played a lot to create a reinstall script from saved activated-packages
of the old install.

I had to re-educate myself from commandline as I forgot a lot during the 9 years since I had put UNIX/DB admin tasks onto a nail, and these BSD and GNU commands has different switches/behaviours than I was used to be familiar with as used them on AIX. Also I liked to work from rich notes and discription I made for myself for tasks. Those had lost - i let it, just as I broke with my business as advisory IT specialist

The one I had fought the most was from one line from lines.
I had used StyledEdit, pe, and vim all of them for one particular feature.
I really miss notepad++.
Not so much I miss from Windows, only notepad++ and Irfanview (with plugins) - maybe TotalCommander.
Those are both five star apps for their rich - and some, unique ! - features and easy usage.
Well I could resolve in vim finally – remember THIS : ggVGJ
This command in vim join all the lines in the file.
You wouldn’t want to know how much I anger gained and let out until I had found it on a Stackoverflow page.
The vim cheatsheat had not helped.
And yes one additional mention - it does not work in editor mode but input mode :-)) but then works like magic !.. I can confirm.

Haiku kept one funny moment for me - I remembered I had to install haiku_extras and one additional package to have additional THEMES.
I liked this Citrus theme - it really fits well to Leaves screensaver.
This way I got back that kindergarten merry surface of the '80 when computing ment COLORS as well … so now you can imagine how I hate some new UI and feel very few the necessity of a Dark mode.
So sorry, but I socialized on 8-bit and DOS machines where the more colors were the feature not the graving grayscale or even flat or minimalistic design - well MS W3.1 was really minimalistic - (those should be only on mobile devices if anywhere).
Anyway finally I remembered I want THEMES - in Hungary it as can be theme, but generally we just select from a list so now I could search for, and found thememanager and then I could slap my big head with getting redicung brain?/memory? Then finally I found the ThemeManager amond prefs, so I could went after my favorite to set up.
It had a tiny hook - after applied … all the sizes of characters went back to default - so I could went back to size them to 17-18 pixels again
So it would worth to mention to improve ThemeManager as well to respect systemwide character settings.

What I miss now ?
I completed, only tools and utilities of 512 I must find again … I assume I was read in a forum post about them and may download from some Github I think, there should be - I do not find a classic repo of him.
(EDIT03 : haha, I found it on Haikuports too - it is haikuutils package )

Against KapiX’s … that I collected meanwhile rebuilding and browsing the forum for repos I shared ther and forgot to save them into a note or file. Now I have it - both for 32bit and 64bit - saved…

Thanks for the 3 people who reached thes lines here :.p
I know these are lot words, but I left out a lot of time and I wrote to whom who do not harsh for it and read it so joyfully as I felt myself while conducting these hoardes of words about my adventures of shepherding Haiku - now … exactly back on R1B4.
I do not pity the time spent on a bleeding edge Haiku
→ once, as because the BFS degradation that cannot be fixed
→ but second, also as going with the nightlies finally.

Thanks again -

… and …
Peace !

EDIT01 : fixed typos

EDIT02 : fixed typos, finished a bloick and was adding supplementals for easier understanding.