Why use 60 sec on da0 during boot?

Jim Pingle jim at hpcisp.com
Sat Nov 19 09:51:28 PST 2005


Lukas Ertl wrote:
> On 11/9/05, Ingeborg Hellemo <Ingeborg.Hellemo at cc.uit.no> wrote:
> 
>>Fresh new ProLiant dl380 2 CPU/dual core
>>Fresh new FreeBSD 6.0-RELEASE
>>
>>
>>During boot I arrive at
>>
>>da0 at ciss0 bus 0 target 0 lun 0
>>da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
>>da0: 135.168MB/s transfers
>>da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
>>
>>then nothing happens for about 60 seconds and then everything proceedes as
>>usual (starting daemons, mounting NFS-disks etc.)
> 
> 
> I see this behaviour on my DL380s, too.  I don't have a fix, but a
> workaround: disable the floppy drive in the BIOS.

I also see this behavior, though I see it on a few systems which are all
Dual CPU PIII 800MHz. They each have different SCSI or RAID controllers (one
has an amr card, one has an mlx controller, and one I believe just had an
ahc controller. The motherboards all have Intel serverworks chipsets.

These are all fresh installs of FreeBSD 6.0 (and updated to -STABLE). It
happens with GENERIC and with a lightly modified custom kernel (remove
unused cpu types, add smp)

In each case, during this pause the floppy light is on solid, so I'm not
sure it has anything to do with the SCSI controller(s).

For me, it goes like so:

...
Waiting 5 seconds for SCSI devices to settle
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 17364MB (35561472 sectors) RAID 0 (optimal)
amrd1: <LSILogic MegaRAID logical drive> on amr0
amrd1: 34728MB (71122944 sectors) RAID 0 (optimal)
sa0 at ahc0 bus 0 target 0 lun 0
sa0: <SONY SDX-500C 0107> Removable Sequential Access SCSI-2 device
sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
SMP: AP CPU #1 Launched!
[long pause]
Trying to mount root from ufs:/dev/amrd0s1a
...

I haven't tried to time the pause, but I believe it was a different duration
on each system. (Particularly long with a higher end Mylex card)

For me it's just a minor annoyance, everything works fine otherwise.

If anyone wants more information I can try to gather some next week when I'm
back in the office.

Jim


More information about the freebsd-stable mailing list