From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3cc25353d73631c0fcf0ab1e30a417f5@felloff.net>
Date: Fri,  2 Sep 2016 19:41:13 +0200
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
In-Reply-To: <57C9AADA.70201@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Plan9 and VMs
Topicbox-Message-UUID: 9c6bdb8a-ead9-11e9-9d60-3106f5b1d025

> I'm sure the problem is the mix "obsolete(Win+VMware) + up-to-date Plan9  distro".

doubt it. i'm actually testing every release on a windows 7 with vmware
doing a install from scratch, then building amd64 on the newly installed
system and reboot into 64 bit kernel as a regression test.

however, in your case i'd suggest a more systematic approach and actually
check what the status of the mbr / partition table is. you can do that
from the system booted off the iso. just run disk/fdisk /dev/sdC0/data
and see if the plan9 partition has a "*" there.

the mbr should look like this:

cpu% dd -if /dev/sdC0/data -count 1 | xd -x1
1+0 records in
1+0 records out
0000000  fa 31 c0 8e d0 bc ec 7b 89 e5 8e d8 be 00 7c 8e <- start of mbr code (should be identical to /386/mbr)
0000010  c0 bf 00 06 b9 00 01 fc f3 a5 ea 1f 06 00 00 30
0000020  c0 38 c2 75 02 b2 80 88 56 12 be 90 07 bf 20 07
0000030  ff d7 be be 07 b9 04 00 b4 80 30 c0 8a 5c 00 38
0000040  dc 74 13 38 d8 75 1f 81 c6 10 00 49 75 ee be 33
0000050  07 bf fd 06 ff d7 89 f7 81 c6 10 00 49 74 0f 8a
0000060  5c 00 38 dc 75 f2 be 4a 07 bf fd 06 ff d7 b4 41
0000070  bb aa 55 8a 56 12 cd 13 72 50 81 fb 55 aa 75 4a
0000080  81 e1 01 00 74 44 c6 46 00 10 c6 46 01 00 c6 46
0000090  02 01 c6 46 03 00 c7 46 04 00 7c c7 46 06 00 00
00000a0  8b 85 08 00 89 86 08 00 8b 85 0a 00 89 86 0a 00
00000b0  c7 46 0c 00 00 c7 46 0e 00 00 89 ee b4 42 cd 13
00000c0  73 24 be 56 07 bf fd 06 ff d7 8a 75 01 8b 8d 02
00000d0  00 b8 01 02 8a 56 12 bb 00 7c cd 13 73 08 be 56
00000e0  07 bf fd 06 ff d7 bb 00 7c 8b 87 fe 01 81 f8 55
00000f0  aa 75 07 89 fe ea 00 7c 00 00 be 60 07 bf 20 07
0000100  ff d7 be 6c 07 bf 20 07 ff d7 31 c0 cd 16 31 db
0000110  8e c3 bb 72 04 b8 34 12 26 89 07 ea 00 00 ff ff
0000120  60 31 db ac 08 c0 74 09 b4 0e cd 10 ac 08 c0 75
0000130  f7 61 c3 4e 6f 20 61 63 74 69 76 65 20 65 6e 74
0000140  72 79 20 69 6e 20 4d 42 52 00 49 6e 76 61 6c 69
0000150  64 20 4d 42 52 00 49 2f 4f 20 65 72 72 6f 72 00
0000160  49 6e 76 61 6c 69 64 20 50 42 53 00 0d 0a 50 72
0000170  65 73 73 20 61 6c 6d 6f 73 74 20 61 6e 79 20 6b
0000180  65 79 20 74 6f 20 72 65 62 6f 6f 74 2e 2e 2e 00
0000190  4d 42 52 2e 2e 2e 00 00 00 00 00 00 00 00 00 00 <- last byte of mbr code at 0x196 (407 bytes)
00001a0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00001b0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01 <- partition table starts at 0x1BE, will be different for you
00001c0  01 00 39 fe ff ff 3f 00 00 00 5f e0 7f 01 00 00
00001d0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00001e0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00001f0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa <- 55AA boot signature, bios looks for this

once we know the status of that, we can worry about *why* it is this way
in your case.

maybe your download got corrupted? (we did have this case in the past)
just to make sure, the latest 9front-5368.b4963e7e3204.iso.bz2 file
has sha2-512 sum of:

fdd73ded92d912bebb11b7bf301fcf6c362c1df28d9d3b0ddb73a19ceaf2a1dfd5afc27f4f5a0330201f62004d86c84bc704dfcba0078bdfbc6ebcff6f14b1d3

--
cinap