Amiga 3000 scsi boot initial delay

dschallock · 23 February 2021, 16:49

Heya friends.

I have an Amiga 3000 tower. Using Scsi to SD v5. Everything is working fine but....
When I first boot, the hard drive light stay solid on for like 7-10 seconds. No activity really just solid on. Then it start to flicker and it boots up in another 10 seconds.

Whatever that initial scan, wait... whatever that is happening. Any way that can be avoided? It would speed up my boot time by alot.

Also, I don't think it used to do this when I was booting from an old fashioned hardrive.

Thanks for the help Amiga scsi masters!

Kin Hell · 23 February 2021, 17:21

Not familiar with SCSI to SD v5, but....

Is that the only SCSI Device on your SCSI Bus?

If only for everyone knowing what set up you have there.

dschallock · 23 February 2021, 17:45

Quote:

Originally Posted by Kin Hell

Not familiar with SCSI to SD v5, but....

Is that the only SCSI Device on your SCSI Bus?

If only for everyone knowing what set up you have there.

Hi, I have the SCSI2SD and a CDROM on the SCSI chain. Both are working.

mr.spiv · 23 February 2021, 19:04

Quote:

Originally Posted by dschallock

Hi, I have the SCSI2SD and a CDROM on the SCSI chain. Both are working.

Which kickstart and workbench? Do you also have this delay if you boot without startup sequence?

mark_k · 23 February 2021, 19:08

Set SCSI2SD SCSI ID to 0. Use HDToolbox to set the last unit flag in its RDB. Try using SetBatt (on Aminet) to reduce SCSI selection timeout and disable multiple LUN support.

Hedeon · 23 February 2021, 20:09

It doesn't stay lit here. It goes quite quickly to checking all the SCSI IDs (LED flickering a number of times). And I have a SCSI2SD too. And my ID for the SCSI2SD is 6.

It's not that the floppy disk drive is incorrectly connected?

mousehouse · 23 February 2021, 21:22

Is it just the SCSI LED from the controller or is the SCSI2SD also active at that time? There's a LED on the PCB to check that...

alexscotti · 23 February 2021, 22:03

How large is your partition?

matt3k · 24 February 2021, 13:32

Try pfs3 as boot partition file system. Had a similar thing on a acard in a 3000.

tuf · 10 August 2021, 21:25

Same problem here. SCSI2SD causes a ~10 second delay on initial boot with a solid HD light. Didn't exist before with an older SCSI to IDE converter. I'll try the suggestions above and see if there's any improvements.

Shadowfire · 14 August 2021, 18:28

The A3000 starts looking for devices at device 0, and works its way up to device 7.
Set the SCSI2HD to device 0, set the A3000 internal scsi controller to device 7.
Finally, run HDToolBox; it will scan the device chain and say "Drives have been added or removed" and then permit it to update the device 0 partition data (DON'T CHANGE ANYTHING ELSE UNLESS YOU KNOW WHAT YOU ARE DOING). After doing this, when the A3000 checks device #0 while booting, it will see the flag from HDToolBox saying that device #0 is the highest drive and stop wasting time checking the higher device numbers.
This also means that if you add another drive, the A3000 won't see it unless you rerun HDToolBox and update the drive partition again.

Edit: Didn't see the post by Mark_K

tuf · 15 August 2021, 05:29

As a follow up, I checked my SCSI2SD 5.2 and it turns out it had 4.8.4 installed on it. I updated it and it immediately fixed the boot delay issue. It boots so fast now the startup-sequence fails b/c things don't have time to validate before a 2nd reboot to loadmodules.

Jope · 16 August 2021, 08:45

Run once with no startup-sequence to fix the validation. To fix it permanently, move to PFS3 ;-)

Your startup-sequence shouldn't be writing anything to disk before loadmodule, it's a good idea to fix that if it becomes invalid every time?

23 February 2021, 16:49	#1
dschallock Registered User Join Date: Jul 2016 Location: Northern California Posts: 174	Amiga 3000 scsi boot initial delay Heya friends. I have an Amiga 3000 tower. Using Scsi to SD v5. Everything is working fine but.... When I first boot, the hard drive light stay solid on for like 7-10 seconds. No activity really just solid on. Then it start to flicker and it boots up in another 10 seconds. Whatever that initial scan, wait... whatever that is happening. Any way that can be avoided? It would speed up my boot time by alot. Also, I don't think it used to do this when I was booting from an old fashioned hardrive. Thanks for the help Amiga scsi masters!

23 February 2021, 17:21	#2
Kin Hell 0ld0r Git Join Date: Mar 2009 Location: Cornwall, UK Posts: 1,570	Not familiar with SCSI to SD v5, but.... Is that the only SCSI Device on your SCSI Bus? If only for everyone knowing what set up you have there. Last edited by Kin Hell; 23 February 2021 at 17:28.

14 August 2021, 18:28	#11
Shadowfire Registered User Join Date: Aug 2001 Location: Connecticut USA Posts: 617	The A3000 starts looking for devices at device 0, and works its way up to device 7. Set the SCSI2HD to device 0, set the A3000 internal scsi controller to device 7. Finally, run HDToolBox; it will scan the device chain and say "Drives have been added or removed" and then permit it to update the device 0 partition data (DON'T CHANGE ANYTHING ELSE UNLESS YOU KNOW WHAT YOU ARE DOING). After doing this, when the A3000 checks device #0 while booting, it will see the flag from HDToolBox saying that device #0 is the highest drive and stop wasting time checking the higher device numbers. This also means that if you add another drive, the A3000 won't see it unless you rerun HDToolBox and update the drive partition again. Edit: Didn't see the post by Mark_K Last edited by Shadowfire; 14 August 2021 at 18:35.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Amiga 3000 Locks on any SCSI on boot.	matt3k	support.Hardware	4	09 December 2019 08:14
Amiga 3000 hdd boot problems	Borgy	support.Hardware	19	20 October 2017 21:30
amiga 3000 won't boot from scsi	curiousottman	support.Hardware	12	16 April 2014 23:20
Amiga 3000 os3.9 boot disk	GreenMeanie	support.Apps	4	26 March 2008 15:43
Boot delay option	Bloodwych	request.UAE Wishlist	9	25 January 2004 23:01

23 February 2021, 19:08	#5
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,335	Set SCSI2SD SCSI ID to 0. Use HDToolbox to set the last unit flag in its RDB. Try using SetBatt (on Aminet) to reduce SCSI selection timeout and disable multiple LUN support.

23 February 2021, 20:09	#6
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 1,993	It doesn't stay lit here. It goes quite quickly to checking all the SCSI IDs (LED flickering a number of times). And I have a SCSI2SD too. And my ID for the SCSI2SD is 6. It's not that the floppy disk drive is incorrectly connected?

23 February 2021, 21:22	#7
mousehouse Registered User Join Date: Sep 2019 Location: Netherlands Posts: 107	Is it just the SCSI LED from the controller or is the SCSI2SD also active at that time? There's a LED on the PCB to check that...

23 February 2021, 22:03	#8
alexscotti Registered User Join Date: Sep 2019 Location: Seattle Posts: 7	How large is your partition?

24 February 2021, 13:32	#9
matt3k Registered User Join Date: Aug 2018 Location: NY / USA Posts: 290	Try pfs3 as boot partition file system. Had a similar thing on a acard in a 3000.

10 August 2021, 21:25	#10
tuf Registered User Join Date: Dec 2008 Location: Atlanta, GA USA Posts: 35	Same problem here. SCSI2SD causes a ~10 second delay on initial boot with a solid HD light. Didn't exist before with an older SCSI to IDE converter. I'll try the suggestions above and see if there's any improvements.

15 August 2021, 05:29	#12
tuf Registered User Join Date: Dec 2008 Location: Atlanta, GA USA Posts: 35	As a follow up, I checked my SCSI2SD 5.2 and it turns out it had 4.8.4 installed on it. I updated it and it immediately fixed the boot delay issue. It boots so fast now the startup-sequence fails b/c things don't have time to validate before a 2nd reboot to loadmodules.

16 August 2021, 08:45	#13
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,861	Run once with no startup-sequence to fix the validation. To fix it permanently, move to PFS3 ;-) Your startup-sequence shouldn't be writing anything to disk before loadmodule, it's a good idea to fix that if it becomes invalid every time?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)