What might cause a write error?

[Tim Radde]

I created a totally blank RD53 image (1024cyl, 8 heads).  Using my Gotek images I am trying to install BSD 2.9 onto a bigger drive as the 10MB RD51 didn't have much space left over.  The new image formatted with no errors.  But on trying to restore the /root partition data I got a write error.  This did not happen with the RD51 image.  I created both the same way as directed in the directions.  I don't know what format actually does and it likely does not touch the entire drive. But it did take quite some time to complete. First time I tried I thought it was not working as the Pro was reporting a disk controller error.  Seems this was due to no drive existing that it could see yet.  Just trying to get an idea of what might have caused this?  I had seen a post from someone about 8 heads maybe being an issue and Dave saying it should not be an issue.  Should I just move down to an RD31 image of 20MB?  I'd prefer the 70MB of the RD53 though.  Thanks.

[David Gesswein]

Its tough to say what is going wrong without having the machine. I would
first try mfm_util to create an extracted data file and see if it reports any
errors. If it does do the same with the image that is working to see if it has
the same errors.

> --
> 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 visit https://groups.google.com/d/msgid/mfm-discuss/a46507b8-5a29-404b-8a52-543ce907940an%40googlegroups.com.

[Tim Radde]

I had hoped there might be something in the logfile.  The only real message it shows is that it could not find the emu file to open.  I think that was when I was moving to the new file.  I had

stopped the service so kind of surprised that's there.  I don't know how to use mfm_util to create this extract file.  I ran it with this command: mfm_util -m rd53_emu.emu -e rd53_emu_extracted

and got this error:
Original decode arguments: --heads 8 --cylinders 1024  --rate 10000000
mfm_util: unrecognized option '--rate'
Generating extract file without analyze requires options: sectors header_crc data_crc format

Do I need to use the analyze option? I know how many sectors but have no idea what to put in for header_crc or data_crc_format.

You received this message because you are subscribed to a topic in the Google Groups "MFM Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mfm-discuss/D1djvzL0hNc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mfm-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mfm-discuss/aP2G%2BBGsAJWp3KCp%40hugin3.

[Tim Radde]

Putting in the analyze option seems to be letting it run.

[Tim Radde]

Results: 

Command line to read disk:
--format Elektronika_85 --sectors 16,0 --heads 8 --cylinders 1024 --header_crc 0xffff,0x1021,16,0 --data_crc  0xffff,0x1021,16,0 --sector_length 512 --retries 50,4 --drive 0
Found cyl 0 to 1023, head 0 to 7, sector 0 to 15                              
Expected 131072 sectors got 131072 good sectors, 0 bad header, 0 bad data
0 sectors marked bad or spare
0 sectors corrected with ECC. Max bits in burst corrected 0

No errors.

[Tim Radde]

It could be the Gotek images are faulty.  The first 2 of 5 ran fine.  Last time I used real floppy images.  This time I could not get Image Disk to create the actual floppy but the Gotek could read

the image on it.  I would not expect a write error though.  Maybe it was just a weird glitch.  I will try the install again to see.

[Tim Radde]

Well, trying it again.  Skipped the format as it takes about an hour.  Got an error on first diskette image instead of 3rd.  Don't know what was left behind from the first restor.  So I am going back

to doing the format and then the mkfs (make file systesm) and the restor.  To see if it makes it all the way thru.  If not I may drop down to a smaller image that had 6 heads for a bit more space.

[Tim Radde]

Ok, did the reformat.  Took about 45 mins.  Not 1 hour.  I got the /root dump restored.  But the /usr would not load.  It would start but fail.  I believe this is due to the USB /usr floppy images

are not quite correct.  It reads for awhile and then displays a volume error.  On the Pro display is a hard error on the floppy.  I had tried to make real floppies from these images with ImageDisk

but it would not work.  The original /root and /usr floppy images I was able to make real floppies and those worked fine.  These are .dsk images and the Hxc Floppy emulator will not load

those.  They will load as raw files but when converted to any of the other types (hfe, img, imd) they do not work.  I don't know how to fix this.  I need to make a new Maint1 floppy which has

the changes for using other disks.  And the kernel floppy which has the changes for the new unix to boot, rdboot, and rdfmt.  I am kind of stuck in the middle.  I have floppies for most but

can't make these two.  And those two also do not want to work in the GoTeks, where other images work just fine.

[Tim Radde]

Does anyone have an idea of how to convert these xhomer .dsk file (floppy images) to something that Image Disk can create real floppies or that my Gotek with FlashFloppy can read and use?

I have tried all kinds of things.  I just can't seem to make sense of their format.  Thanks.

[David Gesswein]

I would suggest for floppy issues
https://forum.vcfed.org/index.php?forums/dec/

To get best response provide what image you are having trouble with, the
command you tried to use, and what error you are seeing.

> To view this discussion visit https://groups.google.com/d/msgid/mfm-discuss/9761df71-fb2f-443c-a126-e1ca855f0fe6n%40googlegroups.com.

[Tim Radde]

I believe my problems stem from the floppy images they provide.  They are saved as ".dsk" and I believe they are Simh format.  Which can not be directly used with a GoTek. Physical vs Logical ordering.

I am trying to find a conversion too.  They provide tools to go TO the Simh format.  Xhomer is built on a version of Simh.

To view this discussion visit https://groups.google.com/d/msgid/mfm-discuss/aP9yKgy6QxFJB9qw%40hugin3.

[David Gesswein]

https://forum.vcfed.org/index.php?threads/d-gesswein-mfm-emulator-and-simh.1245248/page-2#post-1358044

> > https://groups.google.com/d/topic/mfm-discuss/D1djvzL0hNc/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > mfm-discuss...@googlegroups.com.
> > To view this discussion visit
> > https://groups.google.com/d/msgid/mfm-discuss/aP9yKgy6QxFJB9qw%40hugin3.
> >
>

> --
> 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 visit https://groups.google.com/d/msgid/mfm-discuss/CABTODK-4r6WkO%3DEL2%3DNaq9YusP3H%3DuJ%3DmvBg7gJi0mXLK_aT%2Bw%40mail.gmail.com.

[Tim Radde]

Got that and ran it.  Now I have to see if it worked.  Trying a direct load into the HxCFloppyEmulator did not work.  Loading a raw file worked but I doubt if it really loaded 

correctly.  Only by putting it on the GoTek and trying will I know.  I have tried this before but those were with the Simh files that xhomer provided.

To view this discussion visit https://groups.google.com/d/msgid/mfm-discuss/aP90BrrO1EUqGrIP%40hugin3.

[Tim Radde]

Well, the floppy image now mounts.  But no files show up.  So not really much better.  And the other image that would  not mount also mounts today.  No files there either.

[Tim Radde]

I have put BSD to the side for now.  I have a very basic 2.9 install but it''s missing /usr.  So not very useful.  I tried everything but the image files provided do not read via FlashFloppy.  I tried the 

python scipt to turn them from Simh to real.  Nope.  Did not help.  I tried converting using HxCFloppy Emulator.  None worked.  So I have moved to try Venix 2.0.  The first set of files booted

and installed the root area, but the /usr floppies would get an error.  Got a different set and these install and I have a basic working Venix for now with more floppies containing other

useful stull like Kermit.  The MFM emulator itself is working just fine.