logfile.txt content on Write Error.
Adam Billyard
David, not sure if this is helpful / useful to figuring what went wrong.
PRU 0 pc 027b
00: 00000000 000000ff 00052b79 00000002 00000f00 00000000 a702f4fb b2abd87a
08: 04000010 0a000018 aac49cfa 00000000 00009c40 7a43fe6d 20450734 f9a98098
16: 6ac77c22 0002200c 00000000 00000000 00000000 9bd7f3be 0000000e 9f400000
24: 0032de80 0032de61 00052b70 00000000 00000014 0000010e 388cc8c1 000100c1
0000: 9f400000 000fffff 4a300000 00000000 00000000 00000000 00000000 00000000
0020: 4140102a 5de54569 b24bfcb9 ce08dcb8 00000001 00000000 00000000 00000d00
0040: 0000057c 000100c1 00000000 00000f00 000a3dbb 0000033e 9069f406 00000006
0060: 00000000 00000000 00000000 00000000 00000000 0000000e 00000000 00000800
0080: 00000000 ffffffff 00000001 00000014 00000027 00000000 00009c40 0032de80
00a0: 2216e189 0000000e 00000000 00000f00 3da10af5 d1824e88 03459097 95ba5462
00c0: 96745b78 74dff645 0aa933c2 a638e2d6 9f5896f5 b1570f23 078f40db ed360e4b
00e0: 42a1683c 239be6a6 a332bb53 38821d30 0032de7f 000523d8 0000422c a5f84d26
0400: e043afee 9c7b3639 808fe12c bf1d5acc 9a29feb8 beeafdf2 6542f487 6e7bf7b9
0420: d4484867 5bd967e2 0bb6f7c0 ac1cee83 33882a36 21566313 bbe04126 a1bfbc9f
0440: 62864562 1791e05c 60e10580 1e4ef54a 8459c78a 12115fa2 bbe73bd2 84bd342f
0460: 405f1cf8 60e1c6d3 ad8a1959 cf04a8a2 89769e38 07e4d71e 0e659d82 fb938aa4
PRU 1 pc 01b7
00: 0000001f 00000780 00000002 00000400 0000001e 0002200c 0000000c 20d10003
08: 04000014 0a000018 00000850 00001459 fb299dc2 00000454 aaaaaaaa aaaa8000
16: 29d1c8f4 00005164 0000422c f25700b2 00000000 0011141e 0000000c 9f400000
24: 0032bd37 00002210 49000000 49004100 00000007 0000000c 90198404 00000000
0000: 9f400000 000fffff 4a302000 00000000 00000000 00000000 00000000 00000000
0020: 56662b05 70bb9109 309d8c85 10411db0 00000000 00000000 00000000 82d9bbd4
0040: b244de9d e327a6d6 a2346514 5811dd8b 0000000c 4cdec7e1 00005164 a2eca152
0060: 0ccccccd 0000001e 00000014 00000007 00000400 00000040 a9d6e5f4 40e2fd28
0080: 02000027 0300003b 02000027 02000027 02000027 0300003b 02000027 02000027
00a0: 02140027 0314003b 02140027 02140027 02140027 0314003b 02140027 02140027
00c0: 152a8f30 a71b1a4e cb3164a4 02b49525 0001000c 9f405164 3ae62519 ec3e91a0
00e0: 0032bce9 003294ed 0032bd37 000525c4 b76f978b 000525e5 0000001f 000523fb
0400: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0420: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0440: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0460: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0000: 02140027 02140027 02140027 02140027 02140027 00000000 02140027 02140027
0020: 4c886450 c02bb116 8ab2307f e8e36b91 aa9fcdc6 dd5312c4 c369501f 23b08e34
0040: c9303d5a e0e17486 3ea13ef0 04071a68 5d9c55e1 5b2ab494 6a485e8b fa37eb64
0060: deb6822f 3c303584 bf149c99 55c4c168 378927c0 6c0165f5 39d3064e e00168fc
David Gesswein
are normal emulator has been requested to terminate. Wasn't supposed to
generate a dump for normal exit. Will need to check.
If these dumps are being generated when the emulator shouldn't be shutting
down then something is going wrong. If you are using the autostart it may be
a sag on 12V that is triggering the power lost shutdown.
> You received this message because you are subscribed to the Google Groups "MFM Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mfm-discuss...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/mfm-discuss/ca916b15-d378-4dc6-88d8-3641fdad42aen%40googlegroups.com.
Adam Billyard
I am guessing this is a timing issue in PRU0/PRU1 (?) - I was trying to see somewhere in the code when a write fails that would log useful info. / or I can could add logging.
It is spurious in that I’ve installed Unix on the disk and it boots and generally behaves - so vast majority of read/writes work just fine.
Adam
David Gesswein
mount -t tmpfs tmpfs /mnt -o size=120m
copy your emualtor file to /mnt and then start mfm_emu using the file in
/mnt. The flash memory on the beaglebone is slow to write. I do some things in
the code to hide it but it may be causing your problems.
If this works we can change the scripts to
copy to ram and back or you can buy a fast random write USB stick or uSD card
and run off of it.
I had one person report that copying to ram and back and running from
ram fixed their problem.
Let me know if this isn't clear enough.
Have you checked the emulator file to see if mfm_util sees errors after
you get the write error? If you do thats a different problem.
Adam Billyard
To view this discussion on the web visit https://groups.google.com/d/msgid/mfm-discuss/ZE5prM9UpmR28apf%40hugin3.
David Gesswein
>
> Running mfm_util —analyze on a Known Good emufile gives pasted in below. Not sure what the next step is - add all those to the .badblock list?
>
> Unknown header flag byte 24 on cyl 0 head 0 physical sector 1
> Unknown header flag byte 3c on cyl 0 head 0 physical sector 2
> Unknown header flag byte 26 on cyl 0 head 0 physical sector 3
> Unknown header flag byte 3e on cyl 0 head 0 physical sector 4
> Unknown header flag byte 26 on cyl 0 head 0 physical sector 5
> Unknown header flag byte 3e on cyl 0 head 0 physical sector 6
> Unknown header flag byte 06 on cyl 0 head 0 physical sector 7
>
what they mean. These shouldn't be an issue.
Each batch of these has similar pattern and spacing from the last so
seem like they may be intentional but hard to say.
I pulled out the sector headers for one track where the errors occur
155 2 0:0xa1,0xfe,0x00,0x41,0x88,0x00,0x4f,0x0e,0xc0,0xb4,
155 2 5:0xa1,0xfe,0x00,0x41,0x89,0x00,0x1e,0x0a,0x3a,0xb0,
155 2 10:0xa1,0xfe,0x00,0x41,0x8a,0x00,0xed,0x07,0x34,0xbc,
0x8b missing
155 2 2:0xa1,0xfe,0x00,0x41,0x8c,0x00,0x4a,0x19,0x69,0x21,
155 2 7:0xa1,0xfe,0x00,0x41,0x8d,0x00,0x1b,0x1d,0x93,0x25,
155 2 12:0xa1,0xfe,0x00,0x41,0x8e,0x00,0xe8,0x10,0x9d,0x29,
155 2 14:0xa1,0xfe,0x00,0x41,0x8f,0x00,0xb9,0x14,0x67,0x2d,
These two sectors have identical sector headers
155 2 16:0xa1,0xfe,0x00,0x41,0x90,0x00,0x51,0x7f,0x35,0xca,
155 2 4:0xa1,0xfe,0x00,0x41,0x90,0x00,0x51,0x7f,0x35,0xca,
155 2 9:0xa1,0xfe,0x00,0x41,0x91,0x00,0x00,0x7b,0xcf,0xce,
0x92 missing
155 2 1:0xa1,0xfe,0x00,0x41,0x93,0x00,0xa2,0x72,0x3b,0xc6,
155 2 6:0xa1,0xfe,0x00,0x41,0x94,0x00,0x54,0x68,0x9c,0x5f,
155 2 11:0xa1,0xfe,0x00,0x41,0x95,0x00,0x05,0x6c,0x66,0x5b,
0x96 missing
155 2 3:0xa1,0xfe,0x00,0x41,0x97,0x00,0xa7,0x65,0x92,0x53,
Duplicate
155 2 15:0xa1,0xfe,0x00,0x41,0x98,0x00,0x5b,0x50,0x66,0xe0,
155 2 8:0xa1,0xfe,0x00,0x41,0x98,0x00,0x5b,0x50,0x66,0xe0,
Duplicate
155 2 13:0xa1,0xfe,0x00,0x41,0x99,0x80,0x22,0xd6,0xe1,0xe6,
155 2 17:0xa1,0xfe,0x00,0x41,0x99,0x80,0x22,0xd6,0xe1,0xe6,
Having duplicate and missing sector headers is suspicious that something
went wrong since not sure why they would intentionally do this. Other odd
thing is the sector interleave is different. Since some of the is
clearly the computer formatting these cylinders different its hard to
say if the emulator is doing anything wrong.
The duplicates cause the missing LBA printing code to get confused so the
messages aren't fully correct.
At 160 it switches back to the more common interlave pattern
160 2 0:0xa1,0xfe,0x00,0x43,0xa4,0x00,0x61,0x57,0x3f,0x29,
160 2 2:0xa1,0xfe,0x00,0x43,0xa5,0x00,0x30,0x53,0xc5,0x2d,
160 2 4:0xa1,0xfe,0x00,0x43,0xa6,0x00,0xc3,0x5e,0xcb,0x21,
160 2 6:0xa1,0xfe,0x00,0x43,0xa7,0x00,0x92,0x5a,0x31,0x25,
160 2 8:0xa1,0xfe,0x00,0x43,0xa8,0x00,0x6e,0x6f,0xc5,0x96,
...
Ii would be really nice if an existing disk could be
recovered to see if it has the same strange sector headers.
Do your write errors provide any information on what it thinks is causing
the error?