R1/beta3 32-bit won't boot

[KantosKan]

I reformatted a partition, and re-installed R1/beta2, on my HP 12-core opteron computer. It boots, and runs reasonably well. Then I upgraded to R1/beta3. It now will not boot. It freezes on the launch icon of the boot sequence. When I reboot into another partition, it shows no disk space left on the existing 32-bit partition. Previously there was more than 100MB free. The disk was completely filled while trying to launch.

listdev output and syslog output attached. I also have pictures of the on-screen debugging while booting, if needed.

[KantosKan]

listdev output

[KantosKan]

syslog file after the attempt to boot

[waddlesplash]

Please try the very latest nightly build and see what happens.

[KantosKan]

OK, I installed hrev 55895, 32-bits. When I tried to boot, it stalled with a white screen after the launch icon. Then I tried again with safe mode, and safe graphics mode. It stalled with a white screen, with some text:

debugger for team 488 on interface local (shredder) created and initialized successfully [thread stopped 488 sh] current thread 488 "sh" debugger>drawfmanager::File::Load("boot/system/bin/bash"): no .debug_info or .debugabbrev debugger>drawfmanager::File::Load("boot/system/runtime_loader"): no .debug_info or .debugabbrev debugger>drawfmanager::File::Load("boot/system/runtime_loader"): no .debug_info or .debugabbrev debugger>drawfmanager::File::Load("boot/system/lib/libncurses.so.6.2.0"): no .debug_info or .debugabbrev debugger>drawfmanager::File::Load("boot/system/lib/libncurses.so.6.2.0"): no .debug_info or .debugabbrev

[waddlesplash]

Please type "bt" at the prompt, take a picture, and upload it here.

[KantosKan]

backtrace

[KantosKan]

OK, picture attached. It behaved differently on this boot, likely because the first attempt to boot caused the file system on the disk to be nearly completely filled. Image uploaded is IMG_1277.jpg

[diver]

The kernel panic related to bfs driver on this photo is being tracked in #6781.

Can you reproduce the white screen debugger (after the launch icon) and type bt there?

[diver]

BTW you should be able to exit KDL by typing es.

[KantosKan]

img_1279: trying to boot into hrev55895 from the hard disk
img_1280: same, after bt
img_1281: trying to boot using safe mode and safe graphics mode
img_1282: showing the free space on the installation volume, immediately after mounting it while booted from usb stick, after re-installing hrev55895
img_1283: suddenly the disk is full, a few seconds after mounting it
img_1284: the installer crashes, while trying to install on the filled-up disk
img_1285: after mounting the hard disk after rebooting from the usb stick after the installer crash.

it is puzzling that it always is able to boot from the usb stick, but not from the hard disk after installing the same os.

[diver]

app_server crashed in freetype code, do you maybe have some custom fonts installed? Does the crash goes away of you remove them?

[diver]

Can you check where did the free space go? Check with DiskUsage.

[KantosKan]

There are no custom fonts. It is a new installation after formatting the partition. Right now I can't find out where the free space went, because I reformatted the disk and trying installing hrev 55895 again. It installed successfully, but when booting, there was a white screen that lasted several minutes, then it finally booted into the desktop. It runs very slowly, starting Terminal can take 30 seconds or several minutes. Right-clicking on a folder can take 30 seconds or more before the file list shows up.

[diver]

Can you check if some process is using the cpu? Are you sure there is no problem with your hard drive?

[diver]

Run tail -F /var/log/syslog and see if there is anything suspicious.

[KantosKan]

Thanks for this suggestion. I tried installing R1/beta3 32bits on a different hard drive, and it works ! So it appears that the problem is with the hard drive, not the OS. I apologize for all the trouble, and really appreciate all your help.

[diver]

Great! It could be helpful if Haiku could detect this somehow and inform a user about storage problems if it manages to boot to the Desktop.

Closing.