Ave!

Since I upgraded my Pegasos II from G3 to G4, it needs to be restarted after I turn it on, because one of my hard disks is not awailable as fast as the machine would go and boot from it (there is an OFW port waiting for input, and ls /pci/ide doesn't see my hd). After rebooting (with the reset button on the case) everything goes OK, and there is no problem until switch off.

Is it any chance to set something in OFW or do some magic stuff to avoid this? It's so unconvenient... :(

Some people solved it by upgrading their firmware,
some like me didn't, better luck with next hard disk :P

Some time ago I tried upgrading, but Linux crashed every time with the new firmware, so I have downgraded back.

Buying a new HD is not a solution... :( (I already have a 120 and a 200GB one...)

Isn't it sufficient to increase the timeout duration of the autoboot variable?

setenv auto-boot-timeout n

Hi Guys,

I have two 120 GB Maxtor HDs installed. Both were fine, but some time ago the one installed at the secondary port got problems with the first boot. Either I have to do a reset immediately after turning the Peg on or I wait until MOS has completely booted, wait for 30 secs (the HD LED is on all of that time, then it turns off) and then reboot. After this the second HD works fine until I turn the Peg off.

A firmware upgrade solved other problems but not thisone for me.

Funny: if I turn on the Peg and boot into Linux the second HD is immediately recognized by Linux and I can access that second HD without reboot.

Increasing the boot-timeout would be a bad solution because I would have to set the timeout to one minute or so, and I would have to wait this minute everytime I reboot, but it would only be necessary the first boot after turning the Peg on.

So, how does Linux manage to access the second HD immediately after turning the Peg on, without having to reboot? Would it be possible to write a tool which wakes up the HD while booting MOS, similar to the via-wakeup-proggy?

Hi Guys,

I have two 120 GB Maxtor HDs installed. Both were fine, but some time ago the one installed at the secondary port got problems with the first boot. Either I have to do a reset immediately after turning the Peg on or I wait until MOS has completely booted, wait for 30 secs (the HD LED is on all of that time, then it turns off) and then reboot. After this the second HD works fine until I turn the Peg off.

A firmware upgrade solved other problems but not thisone for me.

Funny: if I turn on the Peg and boot into Linux the second HD is immediately recognized by Linux and I can access that second HD without reboot.

Increasing the boot-timeout would be a bad solution because I would have to set the timeout to one minute or so, and I would have to wait this minute everytime I reboot, but it would only be necessary the first boot after turning the Peg on.

So, how does Linux manage to access the second HD immediately after turning the Peg on, without having to reboot? Would it be possible to write a tool which wakes up the HD while booting MOS, similar to the via-wakeup-proggy?

It didnt help me but...

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=4666&forum=11#44256

Lots of people have this problem.

I had 512 MB, but fortunatly, when I bought a 1 GB DDR module, this problem disapeared...

So, try to change your memory, it may help.

Yeah, by increasing the memory the memory check of OF is slowing down startup and the drive has time for spin up.

Well, the problem will be gone with the upcoming hybrid drives. They have a flash memory which allows the harddrive to deliver boot informations and even entire kernels while the drive itself isn't ready.

Geit