On 22 Jun 2008, at 18:29, Patrick Lamaizière wrote:
> Le Sun, 22 Jun 2008 17:55:32 +0100,
> Martin Johnson <[EMAIL PROTECTED]> a écrit :
>
>> Do you know what firmware revision your WDC2500BEVS has? When my
>> drive is detected, the combios reports 'WDC WDC2500BEVS-00UST0'. It
>> would be interesting to see if we have the same drive firmware.
>
> It is the same drive.
Thanks for the update..
Well, interesting results from more testing...
1) My two new net5501-70 boxes, SN 57N00725 and 57N00726, don't work
with the WDC hard drive either. Very intermittent drive detection
(warm and cold boot); occasional lockups on power on; drive not seen
in FreeBSD.
2) An older net5501-70 box, SN 57N00126, detects the WDC drive
reliably on both warm and cold boots. However, it gets errors from it
in the FreeBSD installer, which cannot write to the drive at all:
ad1: DMA limited to UDMA33, device found non-ATA66 cable
ad1: 238475MB stray irq7
<WDC WD2500BEVS-00UST0 01.01A01> at ata0-slave UDMA33
ad1: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=488397151
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
ad1: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=488397164
ad1: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=488397167
ad1: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=488397167
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=128
ad1: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=488397105
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=16
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=512
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=64
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=2
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=16
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=128
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=1
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=4<ABORTED> LBA=0
I guess this drive has gone bad, but I wonder whether FreeBSD was
confused by some old Linux ReiserFS data on the drive be to blame?
That drive was quite new and lightly used. I can try writing zeroes
all over the drive when I get my work laptop back tomorrow.
3) Going back to the Hitachi hard drive in the older net5501-70, it
all works perfectly:
ad1: DMA limited to UDMA33, device found non-ATA66 cable
ad1: 152627MB <Hitachi HTS541616J9SA00 SB4OC70P> at ata0-
slave UDMA33
The FreeBSD 7.0p2 installation proceeds happily and boots OK
afterwards. Master or slave makes no difference.
Conclusions... I guess my two new net5501-70 boxes, SN 57N00725 and
57N00726, have manufacturing faults. I will email Soekris Europe for
replacement.
I am puzzled about this message though: "ad1: DMA limited to UDMA33,
device found non-ATA66 cable". My PATA drives manage ATA66 mode on
the net5501-70, so it seems a bit of a shame if the SATA drives only
manage ATA33. What DMA speeds are other people seeing on SATA drives
on the net5501-70? Perhaps a default conservative setting on FreeBSD
7.0-RELEASE.
Cheers,
- Martin.
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
