Hi folks,

After my 'audio partition invalidated' problem, which some of you may have read about, I now have another problem.

My Peg won't boot.

I put the drive back into the peg, on the IDE channel nearest the front of the machine, at the end of the cable.
On switching on, the MOS (1.4) logo comes up, then all I get is a black screen.
If I boot from the MOS1.3 CD, it boots but no HD is shown.

Any ideas?

I think the RDB is Lost, or maybe the Sys Partition is no longer bootable, check with SCSIConfig!

[ Edited by ThePlayer on 2005/3/24 6:24 ]

Quote:

How do I do that?


Thanks,
Robert.

Open on MOSCD the Tool drawer then start SCSIConfig, choose your HD from the left Window and press Partition button, then there must apear some Partitions in the left side of the new Window. At least one Partition must be bootable, check by doubleclicking the Partitions!

Quote:

Play with slave/master primary/secondary to boot from CD & use HDD. Or boot from another HDD.

(Note: sometimes MOS can show and use more IDE devices than firmware)

Your problem is in the bad first partition on HDD.
Repair/reformat it - and all will be ok.

@Wilse

Can you see the device or partitions from the open firmware?

I forget the command now but you can ls the device and it should show the paritions and their respective FileSystems. If it's supported filesystem you can even list the contents of it.

ls /pci/ide/device@<channel>,<device>:<partition number> maybe ?

0,0:0 for the first parition on primary ide channel, master drive afair

ls /pci/ide/device@0,0 should list the partitions

Entirely possible the MBR (Boot Sector) or RDB has become corrupted I guess, however, given that you get the MOS logo....safe to assume it finds the first FFS partition and the boot.img .. so I doubt it's an MBR problem.

One other thing - when you are in SCSIconfig, check that the MOUNT flag is set (checked/ticked) on your MOS system partition and also it has BOOT flag and right BOOTPRI (assuming the drive/partition shows up!)..heck you migth as well check 'em all...FS type, MASK, MAXTRANSFER etc.

I think chances are this partition got corrupted also...and you will end up having to re-write the RDB, format and start over.

Steve

[ Edited by JKD on 2005/3/23 15:09 ]

@ThePlayer:

Quote:

OK, I've found the partitions.
The first FFS partition, 'bi0' has a tick in the boot checkbox.

Quote:

OK, assuming I can do this from the CD, what's the procedure?

I've experienced something similar

MOS booting untill the logo appears, and then it stops.
I my case I reformatted the sys: partition which worked for me
Can you boot up using your 1.3?
if so
boot up using the 1.3 cd
use 1.3 to backup your sys: -- if you can find it -- partition (copy it to another partition or something) and then reformat (quick) your sys:
and then copy everything back

I don't know if it will work for you
As I don't know if I had the same problem, but this solution worked for me

[ Edited by bas on 2005/3/24 0:21 ]

The 1st FFS ??

Dunno bout your setup, but the most common one seems to be like this:

1 small FFS with only the boot.img, this is the one that has to called from the OF

1 "Workbench" in SFS with all the other files from the MOS-CD, this is the one that turns into sys:.

Note that in this case it is best to uncheck "mount" for the FFS and it is absolutl vital that the SFS-WB has a higher BootPri than any other parttiion.

For me it sounds as if you set a (high) BootPri for the partition with only the boot.img on it, hence it stops at the splash-screen.

@Kronos:

Quote:

Ahhh - would this normally be DH1?

Quote:

I haven't changed the boot priority, at least not that I remember but I'll check it anyway.

Thanks,
Robert.

@Kronos

As far as I recall, the FFS partition containing the boot.img does not even need to be bootable in an Amiga sense...or I was smoking crack when I installed my Peg (looong ago now)

I think you are on the right track with the boot/bootpri. I'm not sure why these flags might have been corrupted but we dod lots of things when troubleshooting and I guess SFS ran wild over his drive in teh first instance?

Quote:

Normally it should be DH0 as the partition with the boot.img stays invisible for MOS (or is simple named different to avoid confusion).

@JDK

AFAIK every FFS or SFS has a bootpri, even if it just -127

But your right in rehasing what I allready wrote, boot-pri has no effect on the OF loading the boot.img.

[ Edited by Kronos on 2005/3/24 0:38 ]

Replying to myself:

> would this normally be DH1?

I found it. It's DH0.

So is the verdict to back up then quick format it?

-EDIT-
Forgot to say I unchecked 'mount' on the FFS partition, saved and reset. Same result.

[ Edited by Robert on 2005/3/23 23:47 ]

The verdict is:

Check wether any other partion has a higher boot-pri, and that only "DH0" has "Boot" flagged.

If that doesn't help, whipe away all partitions (no sense in fiddling for another week).

Quote:

OK, done. No difference.
Quote:

Wouldn't it be safer to do them one at a time?

Hi Robert.

Try this Guide:
http://www.morphos-news.de/beta2help/qstart_en.html#hdse

Maybe help you.

Sorry for my English.

Happy Days! Pegasos is finally working properly again again.

Thanks all for your help.