Ata0: timeout waiting for write DRQ error pfSense 2.3.0 and later (SOLVED)
-
For the people that experience the error during bootup :
ata0: timeout waiting for write DRQ
I like to share my experience to solve this error.
Till now i always used the 4Gb CF cards from Kingston (standard speed) without any problems.
Since version pfSense 2.3 and later, i noticed the above error during bootup,
what sometimes shows up 6 times or more and extends the bootup time.
This with brand new CF card right out the package.
When i use a image of pfSense 2.2.6 on desame CF card,it gives no errors, so the CF card seems not the guilty one.
WRONG !!!
Today i have tested a Sandisk 8Gb Ultra (50MB/sec) and used the same image as on the Kingston CF card,
and tadaaaaaaa, no single error and much faster bootup time ;DSince pfSense 2.1 the speed of the CF card is locked down to PIO4 or 16,7MB/sec on the Watchguard Firebox E-series by adding :
hint.ata.0.dma=PIO4 to the bootloader.conf
So buying high speed CF cards was a waste of money, because the full speed is not reached.
But now since pfSense 2.3 , it seems to have a benefit for using a High Speed CF card above a normal speed for
preventing the ata0… error on bootup.And further, i have a feeling that the upgrade problems from 2.3.1 to 2.3.1.5 that many people
experience, are also caused by a too slow CF card.
For this to confirm, i gonna test this also further and will post the results.Hope that this info is a help for people that experience the same error.
Grtz
DeLorean -
I think I know what your issue is from what you posted since I custom make CF cards for people that want them ready to go, let me know if you still have this issue
-
I think I know what your issue is from what you posted since I custom make CF cards for people that want them ready to go, let me know if you still have this issue
In the meanwhile i havn't experienced this behavior, since i don't use the standard Kingston CF cards anymore
on the x550e of x750e boxes.
With the High speed versions of different brands, there are no errors of this kind.
I like to hear if you know the reason.Grtz
DeLorean
