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 17:51:11 +0530

 21.03.2018, 17:40, "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 17:36:52 +0530
 >
 > Â 21.03.2018, 17:25, "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: Martin Husemann <martin%duskware.de@localhost>
 > Â > Cc: "gnats-bugs%netbsd.org@localhost" <gnats-bugs%netbsd.org@localhost>
 > Â > Subject: Re: port-amd64/53113: NetBSD_8.0_BETA/amd64 fails to boot.
 > Â > Date: Wed, 21 Mar 2018 17:21:48 +0530
 > Â >
 > Â > Â 21.03.2018, 17:06, "Martin Husemann" <martin%duskware.de@localhost>:
 > Â > Â > On Wed, Mar 21, 2018 at 04:34:24PM +0530, Utkarsh Anand wrote:
 > Â > Â >> Â Thankfully, I didn't try them again. Turns out the images are faulty.
 > Â > Â >> Â I tested them on virtualbox. Have a look at the screenshots:
 > Â > Â >
 > Â > Â > I have no idea what you are doing and why you are jumping to conclusions.
 > Â > Â > If you don't tell us what you did / tested and what happened, it is hard
 > Â > Â > to help.
 > Â > Â The hard disk images used for the running those virtual machine instances were generated from build.sh and they are unaltered. They haven't been touched by dd explicitly. This concludes that `dd` is not responsible for the fault. I think you understand it now.
 > Â >
 > Â > Â Meanwhile I'm trying to recover the USB key on FreeBSD. It says that the device has bad superblock (Values in superblock disagree with first alternate). Do you know where the backup superblocks are located (for use with -b option). That would be really helpful right now.
 > Â Leave it. I figured it out. Only that -b doesn't work in freebsd.
 > Â > Â >
 > Â > Â > Martin
 
 OK. Seems like I lost my USB key, but that's another issue.
 newfs -N /dev/da1s1a shows:
 super-block backups (for fsck_ffs -b #) at:
 192, 716544, 1432896, 2149248
 but,
 fsck_ffs -b <insert one of those numbers here> /dev/da1s1a
 says that they are not file system super blocks.
 So, I guess, now I'll move on to cross-building once again, on another system.