Install 3.2 on A3000 crashes

[hth313]

I recently got Amiga OS 3.2 and the 3.2.2 update. I created floppies and a superkicksstart floppy as well for my A3000.
Kickstart 47.111 (3.2.2) loads from floppy and shows its screen. I insert the Install floppy, it starts to tick and eventually goes to Guru (well system error).
The machine is an A3000 with 8 or 12 MB RAM, SD2SCSI drive. It can boot 3.1. Is this a good place to ask, or should I go elsewhere?

[hth313]

(I forgot the memory size, checked now, it is 12MB)

It is a normal Amiga 3000 25MHz, 68030/68882, 12MB fast, 2Mb chip memory and Kickstart 1.4 ROM.
The machine has A2065 ethernet, Retina Z3 and ASDG dual serial port boards installed.

I used my own tool to create the SuperKickstart, putting the bonus code in. In the past I have created multiple 3.1 kickstart floppies this way with no issues. The 3.2 kickstart went to yellow screen, but there seemed to be a problem with that release, then I made a 47.111 kickstart from the 3.2.2 update. I use the MakeSuperDisk tool from AmiNet to create the floppy with both 3.2.2 and 1.3 Kickstarts on it.

Cold boot on the Kickstart gives boing ball boot screen, insert Update 3.2 floppy results in Guru 8700 0000 0741DAD0 after a while.

Loading 3.1 kickstart and booting from Install floppy works. It does not seem to want to boot from the A3000 modules floppy.


The HD is a SCSISD
File systems on SCSI:
  Custom file system 19.0  (PFS? see below)
  FFS 40.1
Partitions:
  WB_2.x FFS  67 MB  (System3.1)
  WB_1.3 FFS  55 MB  (hidden after boot)
  AROS partition 1.7GB PDS\03 Block size 1024 (AROS:)
  DH8 partition 1.7GB PDS\03 Block size 1024  (App:)
  DH9 partition 1.7GB PDS\03 Block size 1024  (Work:)
(the rest of the HD is unpartitioned)

[hth313]

That did not help so much initially, it only showed black screen, reading from floppy and GURU, before it steps the startup-sequence trying a lot of different settings.

After playing with the low level options I found that if I disable the AROS partition (which is not bootable), then it boots properly.
It works having the other PDS partitions (WORK: and APP:) enabled.
Not sure why it looks at the AROS partition and why that would cause it to crash.

I do not really need the AROS partition anymore, so I could clear it. I will keep it for a little while in case someone wants me to experiment with it in some way. Well, I should also take a look at it that I do not have something of value there before I wipe it.

[hth313]

I have attached the hddreport.

[hth313]

I am not able to boot with SuperKick 3.2 unless I disable the AROS partition, and then you would get no information about it. I can make such hddreport too.

Your suspicion sounds reasonable. It does blink the HD light during floppy load a little bit more than I would expect.
Did workbench.library use to be in the kickstart or has the way it searches for it changed?

Anyway, I will do as suggested, disable the AROS partition for now and wipe it at some future point.

Thank you for the help!

[hth313]

I installed 3.2 but 47.111 kickstart sees all my HD partition as not bootable.
If I boot from the Install floppy, start HDToolBox the partition is marked as bootable. Is this related to that I have a FFS installed on the HD and it is too old, or something else?

[hth313]

Seems to work now. I updated FFS, but it did not seem to do it. Then cold boot resulted in errors. Apparently it did not install the new Kickstart in devs: so I did that manually. Reboot and install MMU support for the machine, cold boot and finally it boots nicely!