Hey Samuel,
I have spent time trying to reproduce it locally on my machine in qemu
today.
I have a secondary 50gb image and i start it in qemu as a
qemu-system-x86_64 \
-m 1024 -s -machine pc -cpu
host -accel kvm \
-drive
file=/home/loshmi/Projects/hurd/debian-hurd_32.img,if=ide,index=0,format=raw,cache=writethrough
\
-drive
file=/home/loshmi/Projects/hurd/hurd-build-drive.img,if=ide,index=1,format=raw,cache=writethrough
\
-boot order=c \
-netdev user,id=net0,net=
192.168.76.0/24,dhcpstart=192.168.76.5,hostfwd=tcp:127.0.0.1:2222-:22 \
-device e1000,netdev=net0 \
-serial stdio
then from inside hurd i did:
$ cd /dev
$ sudo ./MAKEDEV hd1
$ sudo mke2fs /dev/hd1
$ sudo tune2fs -j /dev/hd1
$ sudo fsck.ext2 -f /dev/hd1
$ sudo settrans -ca /mnt/build /hurd/ext2fs.static /dev/hd1
$ cd /mnt/build/
$ sudo apt-get source util-linux
$ cd util-linux-2.41
than had to fight with autoconf version etc, but in the end for me
configure and then run works without any issues , i tried multiple times,
even while running synthetic background tasks.
I wonder is it because my laptop is backed by nvme or something similar, or
do you find that something is a miss in my emulation?
As far as:
/dev/sd3: Superblock needs_recovery flag is clear, but journal has data.
/dev/sd3: Run journal anyway
That happens if it locks up and it has to be restarted, because journal
didn't manage to commit/checkpoint so things are still there.
The issue is that it locked up on real machine.
Regards,
Milos
On Thu, Jun 25, 2026 at 3:25 AM Samuel Thibault <[email protected]>
wrote:
> Hello,
>
> I'm getting hangs quite often on my i386 hurd box, just by compiling the
> util-linux package on a 50G partition.
>
> One time, I got at reboot:
>
> /dev/sd3: Superblock needs_recovery flag is clear, but journal has data.
> /dev/sd3: Run journal anyway
>
> /dev/sd3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> (i.e., without -a or -p options)
>
> Samuel
>
