Page 1 of 1
OS4.0 hdd booting problems
Posted: Wed Jul 02, 2014 10:48 pm
by gbozkurt
Hi,
I have OS4.0 for classic amiga (1200 ppc) bought from amigakit. Registered here.
I formated my hdd for clean installation.
After partitioning with Mediatoolbox and formatting the hdd, OS4.0 is installing with no problem.
But when i'm booting, it says "not a valid os disk"
I tried 4 different HDD (850 gb ide seagate, 1 gb Quantum ide, 2.1 Gb Western ide, and 4 Gb Fujitsu ide)
Same result.
I tried os 4.0 partition templates or custom specification, no change.
I tried FFS and SFS , same result.
Quick format or long format is not changing the situation
When i'm booting with CD rom, OS4.0 see my partititons and read all the drawers.
But booting is impossible ..
I made all on the manual.
There is no problem with my mediator, ppc, hdd or mobo.
3.1 and 3.9 are working wit mediator.
Where i'm doing wrong ? Thank you
Re: OS4.0 hdd booting problems
Posted: Thu Jul 03, 2014 11:54 pm
by Hans
Hmm, no replies yet. This thread should be moved to the "Platform: Classic" section; maybe it'll get a response there.
I have never used AmigaOS 4.x on a classic machine, so I can't really help. Having said that, here are a few things that you could check:
- Which version of FFS did you use for the boot partition (i.e., what's the "dostype" that you entered when partitioning)? IIRC, the latest versions of FFS cannot be read by the old 68k kickstart ROMs
- Were you supposed to install the filesystem into the RDB?
- Is your OS4 boot partition in the first 4 GB of the drive? I vaguely remember there being some kind of limitation on where the boot partition could be
Hans
Re: OS4.0 hdd booting problems
Posted: Fri Jul 04, 2014 12:15 am
by nbache
Hans wrote:- Which version of FFS did you use for the boot partition (i.e., what's the "dostype" that you entered when partitioning)? IIRC, the latest versions of FFS cannot be read by the old 68k kickstart ROMs
No, I think that part is okay, but the file system (obviously) needs to be a 68k version, not the native PPC version.
- Were you supposed to install the filesystem into the RDB?
The 68k version should be, yes (while no PPC filesystem should ever be installed into any RDB).
Also, an slb (found in L:) should be installed into the RDB; this is done in the preparation part of Media Toolbox.
But these things should all be described in the manual.
Best regards,
Niels
Re: OS4.0 hdd booting problems
Posted: Fri Jul 04, 2014 12:22 am
by Hans
nbache wrote:Hans wrote:- Which version of FFS did you use for the boot partition (i.e., what's the "dostype" that you entered when partitioning)? IIRC, the latest versions of FFS cannot be read by the old 68k kickstart ROMs
No, I think that part is okay, but the file system (obviously) needs to be a 68k version, not the native PPC version.
AFAIK "DOS\06" and "DOS\07" cannot be read by the old 68K FFS (i.e., the one in the 3.x kickstart ROMs). I could be wrong though. In any case, those details should be in the manual
Hans
Re: OS4.0 hdd booting problems
Posted: Fri Jul 04, 2014 3:17 pm
by Christopher Follett
gbozkurt wrote:Hi,
I have OS4.0 for classic amiga (1200 ppc) bought from amigakit. Registered here.
I formated my hdd for clean installation.
After partitioning with Mediatoolbox and formatting the hdd, OS4.0 is installing with no problem.
But when i'm booting, it says "not a valid os disk"
I tried 4 different HDD (850 gb ide seagate, 1 gb Quantum ide, 2.1 Gb Western ide, and 4 Gb Fujitsu ide)
Same result.
I tried os 4.0 partition templates or custom specification, no change.
I tried FFS and SFS , same result.
Quick format or long format is not changing the situation
When i'm booting with CD rom, OS4.0 see my partititons and read all the drawers.
But booting is impossible ..
I made all on the manual.
There is no problem with my mediator, ppc, hdd or mobo.
3.1 and 3.9 are working wit mediator.
Where i'm doing wrong ? Thank you
Maybe the drive has a higher priority than anything else. I hate this in All Amiga WB / OS. It should just ignore non formatted drives. No instead it just refuses to boot.
Check early startup menu.
Hans wrote:nbache wrote:Hans wrote:- Which version of FFS did you use for the boot partition (i.e., what's the "dostype" that you entered when partitioning)? IIRC, the latest versions of FFS cannot be read by the old 68k kickstart ROMs
No, I think that part is okay, but the file system (obviously) needs to be a 68k version, not the native PPC version.
AFAIK "DOS\06" and "DOS\07" cannot be read by the old 68K FFS (i.e., the one in the 3.x kickstart ROMs). I could be wrong though. In any case, those details should be in the manual
Hans
You are correct. 68K, does not like DOS6/ 7.
Re: OS4.0 hdd booting problems
Posted: Fri Jul 04, 2014 4:27 pm
by thomasrapp
Christopher Follett wrote:You are correct. 68K, does not like DOS6/ 7.
No, you are wrong. FFS V51 (68k) comes with OS 4.0 and it is required to install OS 4.0 on a partition with long file names (DOS\7 or SFS). And it is required to put the file system used (68k) into the RDB because DOS\7 is not known to Kickstart 3.x (as is SFS).
And no, it is not needed to install an SLB. Kick 3.x takes this part and boots from the OS 4.0 partition, the BootStrap command then loads Kick 4.0.
Re: OS4.0 hdd booting problems
Posted: Fri Jul 04, 2014 6:59 pm
by DarrenHD
gbozkurt wrote:Hi,
I have OS4.0 for classic amiga (1200 ppc) bought from amigakit. Registered here.
I formated my hdd for clean installation.
After partitioning with Mediatoolbox and formatting the hdd, OS4.0 is installing with no problem.
But when i'm booting, it says "not a valid os disk"
I tried 4 different HDD (850 gb ide seagate, 1 gb Quantum ide, 2.1 Gb Western ide, and 4 Gb Fujitsu ide)
Same result.
I tried os 4.0 partition templates or custom specification, no change.
I tried FFS and SFS , same result.
Quick format or long format is not changing the situation
When i'm booting with CD rom, OS4.0 see my partititons and read all the drawers.
But booting is impossible ..
I made all on the manual.
There is no problem with my mediator, ppc, hdd or mobo.
3.1 and 3.9 are working wit mediator.
Where i'm doing wrong ? Thank you
To me this sounds like the filesystem is not in the RDB. Please read this blog post, specifically the section on "Adding a file system into the Rigid Disk Block (RDB)".
http://blog.hyperion-entertainment.biz/?p=210
Also ensure the partition is marked as bootable and has the highest priority. Please report back, thanks!
Darren
Re: OS4.0 hdd booting problems
Posted: Sat Jul 05, 2014 2:23 am
by Hans
thomasrapp wrote:Christopher Follett wrote:You are correct. 68K, does not like DOS6/ 7.
No, you are wrong. FFS V51 (68k) comes with OS 4.0 and it is required to install OS 4.0 on a partition with long file names (DOS\7 or SFS). And it is required to put the file system used (68k) into the RDB because DOS\7 is not known to Kickstart 3.x (as is SFS).
And no, it is not needed to install an SLB. Kick 3.x takes this part and boots from the OS 4.0 partition, the BootStrap command then loads Kick 4.0.
That makes sense. So, the version of FFS in the 3.x kickstart ROM can't handle DOS6/7, but the one provided on the OS4 CD does. Forgetting to install that into the RDB could be what went wrong.
Hans
Re: OS4.0 hdd booting problems
Posted: Sat Jul 05, 2014 1:03 pm
by Christopher Follett
thomasrapp wrote:Christopher Follett wrote:You are correct. 68K, does not like DOS6/ 7.
No, you are wrong. FFS V51 (68k) comes with OS 4.0 and it is required to install OS 4.0 on a partition with long file names (DOS\7 or SFS). And it is required to put the file system used (68k) into the RDB because DOS\7 is not known to Kickstart 3.x (as is SFS).
And no, it is not needed to install an SLB. Kick 3.x takes this part and boots from the OS 4.0 partition, the BootStrap command then loads Kick 4.0.
Sorry, thats what I ment, should have said ROM FFS doesnt like it.
Re: OS4.0 hdd booting problems
Posted: Sat Jul 05, 2014 4:05 pm
by danbeaver
Yes, there is an error with the HDD setup and an improper RDB (lacking a bootable file system), or an improper partition (>4 GB) are the best guesses. Screen pics of the MediaToolbox in action would help with the diagnosis and treatment.