Problem to start OS, fsck

[peterbsd]

Hello,

I had installed and functional NetBSD 10.0 and suddenly I am not able to start OS.

Starting root file system check:
fsck: no match for '00000000-0000-0000-0000-000000000000': No such process
automatic file system check failed; help !
ERROR: ABORTING BOOT (sending SIGTERM to parent)

Terminated rc_real_work "${@}" 2>&1 |
Done (1) rc_post_process

My actions from last successful booted NetBSD:
On NetBSD I installed only firefox, nothing more.
I rebooted into Windows, created FAT32 partition there placed it after NetBSD (FFSv2) + swap. Then I booted back to NetBSD.
After it denies to start I rebooted back to Windows and deleted new FAT32 partition, but it does not help resolve problem.

What means this zeroed GUID ? And how is it relating to "No such process" ?
What should I try to resolve it, what man/doc to look at ?
I am afraid to not damage existing partitions with fsck.

[peterbsd]

Resolved.

I booted from USB key and found that in /etc/fstab are two above zero-ed GUID in lines for root mount point and swap, so I found with gpt right GUIDs and put them into fstab. After reboot OS started again.

Still it is question why they was zeroed ?
Has it something with my new created partition from Windows ?
After repair I tried again to create new FAT32 partition from Win and after reboot NetBSD is ok, so I don't want why and which process (action) zeroed these GUIDs

[jmccue]

I remember in the past, windows did odd things and all projects recommended you should install windows first before installing other things for dual boot. Plus I remember some versions of windows like to play with the boot partition.

Maybe that was the issue ? I have not dual booted any Microsoft system since the MS-DOS Days. So YMMV.

[peterbsd]

I think the same, that there are some incompatibilities NetBSD<->Win relating to GPT disks.
I had serious problems to install NetBSD on GPT disk with existing partitions created by Win (I asked for the help in my previous thread and also I reported found bugs in installer - in extended partitioning section).

This problem is something similar, fortunately with simple above resolution.