Re: port-amd64/53113: NetBSD_8.0_BETA/amd64 fails to boot.

[Utkarsh Anand <utkarsh009%yandex.com@localhost>]

The following reply was made to PR port-amd64/53113; it has been noted by GNATS.

From: Utkarsh Anand <utkarsh009%yandex.com@localhost>
To: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%netbsd.org@localhost>,
	"port-amd64-maintainer%netbsd.org@localhost" <port-amd64-maintainer%netbsd.org@localhost>,
	"gnats-admin%netbsd.org@localhost" <gnats-admin%netbsd.org@localhost>,
	"netbsd-bugs%netbsd.org@localhost" <netbsd-bugs%netbsd.org@localhost>
Cc: 
Subject: Re: port-amd64/53113: NetBSD_8.0_BETA/amd64 fails to boot.
Date: Wed, 21 Mar 2018 21:14:50 +0530

 21.03.2018, 20:15, "Leonardo Taccari" <leot%netbsd.org@localhost>:
 > The following reply was made to PR port-amd64/53113; it has been noted by GNATS.
 >
 > From: Leonardo Taccari <leot%NetBSD.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: port-amd64/53113: NetBSD_8.0_BETA/amd64 fails to boot.
 > Date: Wed, 21 Mar 2018 15:40:44 +0100
 >
 > Â Hello Utkarsh,
 >
 > Â Utkarsh Anand writes:
 > Â > [...]
 > Â > https://imgur.com/P0qpxnf
 > Â > [...]
 > Â > As you can see, it still has the same problem. But sysinst works.
 > Â > So, I tried installing NetBSD on a new raw disk image and it
 > Â > succeeded. But, upon subsequent reboot, it showed me an error that
 > Â > the file system is read-only. I was not able to create new files.
 > Â > [...]
 >
 > Â At least according that image (manually typed by myself so can
 > Â contains some errors):
 >
 > Â Â [...]
 > Â Â wd0 at atabus0 drive 0
 > Â Â wd0: <QEMU HARDDISK>
 > Â Â wd0: 1450 MB, 2946 cyl, 16 head, 63 sec, 512 bytes/sect x 2969600 sectors
 > Â Â [...]
 > Â Â boot device: wd0
 > Â Â root on wd0a dumps on wd0b
 > Â Â root file system type: ffs
 > Â Â [...]
 > Â Â mount_ffs: /dev/sd0a on /: specified device does not match mounted device
 > Â Â cp: /etc/gettytab: Read-only file system
 > Â Â init: can't add utmpx record for 'system boot': Bad file descriptor
 > Â Â init: can't add utmpx record for 'runlevel': Bad file descriptor
 > Â Â init: can't add utmpx record for 'console': Bad file descriptor
 > Â Â [...]
 >
 > Â ...are there any entry in `/etc/fstab' that refers to `sd0a' instead of
 > Â `wd0a'? (if yes I would substitute `sd0a' with `wd0a' as it sounds like
 > Â that NetBSD is installed in `wd0').
 I haven't attached the disk on which I installed NetBSD in the screenshot. But, I installed it on /dev/wd1a and that's what present in /etc/fstab. But, as I said, it's a read-only filesystem so I can neither manipulate nor create new files on it. Isn't there anybody who has tried cross-building recently?
 I have also attached the screenshots a vm having netbsd installed in both wd0a and wd1a (just in case):
 https://imgur.com/ydM5I8r
 https://imgur.com/ILanlKE
 PS: TERM was also not set, but that wasn't a big problem.