Re: install/58204: Problem preparing evbppc disk on i386 (mount -o log)

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR install/58204; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: install/58204: Problem preparing evbppc disk on i386 (mount -o log)
Date: Sun, 28 Apr 2024 14:56:31 -0000 (UTC)

 hashikaw%mail.ru@localhost (Kouichi Hashikawa) writes:
 
 >Sorry. I make a mistake to write, I unpacked base, comp, etc, games, gpufw, m=
 >an, misc,=20
 >modules, rescue,=20
 >text, xbase, xcomp, xetc and xserver.
 >(firmware loads kernel via tftp.)
 
 Hello,
 
 the error message still tells that
 
 a) kernel has been loaded from that filesystem
 b) init has been loaded and started from that filesystem
 c) init cannot access /dev/console
 
 c leads to your panic.
 
 
 >After panic, boot with OpenBlocks266's INSTALL kernel, and run fsck,
 >found unref file. Following example is /, but I have /usr, /var, /home,=20
 >I got same result. Is this UNREF i386's wapbl log, diffrent from powerpc??
 
 i386 is little endian, powerpc is big endian.
 
 I can see code to handle the "wrong" endianess, but not for the
 data fields referencing the journal file. If I'm not mistaken this prevents
 the journal from being found, inode 3 is then treated as a regular file.