|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
SATA failures on 2 x net5501-70 unitsI recently purchased two new net5501-70 units from Soekris.eu, and
have spent a few hours today trying to make sense of the errors I'm getting with two different SATA laptop drives. (In the longer term I would probably buy E5Kxxx or E7Kxxx drives for better reliability, but I'd like to de-risk the SATA support first...). Detailed config info at the bottom of this email. Results for combios v1.33 with SATA drive connected:- - Cold boot sometimes hangs silently (4 LEDs on, no RS232 output) with the Hitachi drive. - Cold boot doesn't always see either SATA drive. - Warm boot doesn't always see either SATA drive. - FreeBSD 7.0p2 installer PXEboots OK but does not see either SATA drive ("no disks found" when "standard installation" is chosen from menu) even when Combios has found the drive. Results for combios v1.33b with SATA drive connected:- - as 1.33, except... - Samsung SATA drive is never detected by the Combios (warm or cold). - Hitachi SATA drive is occasionally detected by the Combios, but then not by the FreeBSD installer. All rather frustrating! Questions... - Why isn't SATA working? - is there a manufacturing problem on recent net5501-70 units? - is the combios support not yet stable for SATA drives? - is there a much older combios I should be using? (I also tried 1.32i with the Hitachi drive but that didn't help.) - When the SATA drives are detected by combios, why doesn't the FreeBSD 7.0p2 installer see them? Do I need to add something to the GENERIC kernel? - Are PATA/IDE drives more reliable than SATA drives on the net5501? Thanks for any pointers! - Martin. ---------------- Config. Info:- ---------------- SATA drives used: 1 x Hitachi Travelstar 5K160 160GB, 1 x Samsung HM160JI 160GB. (one drive on each net5501.) Cards used: none (no CF, no PCI, no miniPCI). PSU used: 12 volt 5 amp Mascot unit. Combios settings: ConSpeed = 9600 ConLock = Enabled ConMute = Disabled BIOSentry = Enabled PCIROMS = Enabled PXEBoot = Enabled FLASH = Secondary BootDelay = 5 FastBoot = Disabled BootPartition = Disabled BootDrive = 80 FF FF FF ShowPCI = Enabled Reset = Hard CpuSpeed = Default _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsLe Sun, 22 Jun 2008 15:38:10 +0100,
Martin Johnson <martin.johnson.uk.lists@...> a écrit : > - When the SATA drives are detected by combios, why doesn't the > FreeBSD 7.0p2 installer see them? Do I need to add something to the > GENERIC kernel? No, it should work out of the box. I've installed a 7.0 release and now i run 7-STABLE. Well, I don't have any problem on my net5501 with a WDC WD2500BEVS disk. ComBios 1.33 > - Are PATA/IDE drives more reliable than SATA drives on the net5501? The SATA is done by a chipset behind the ATA controller (the CS5536 companion chipset), so this is not a real SATA. I mean the OS only see the ATA controller. > Thanks for any pointers! > > - Martin. > > > ---------------- > Config. Info:- > ---------------- > SATA drives used: 1 x Hitachi Travelstar 5K160 160GB, 1 x > Samsung HM160JI 160GB. (one drive on each net5501.) > Cards used: none (no CF, no PCI, no miniPCI). > PSU used: 12 volt 5 amp Mascot unit. > Combios settings: > ConSpeed = 9600 > ConLock = Enabled > ConMute = Disabled > BIOSentry = Enabled > PCIROMS = Enabled > PXEBoot = Enabled > FLASH = Secondary > BootDelay = 5 > FastBoot = Disabled > BootPartition = Disabled > BootDrive = 80 FF FF FF > ShowPCI = Enabled > Reset = Hard > CpuSpeed = Default Same here. _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsOn 22 Jun 2008, at 16:55, Patrick Lamaizière wrote: > Le Sun, 22 Jun 2008 15:38:10 +0100, > Martin Johnson <martin.johnson.uk.lists@...> a écrit : > >> - When the SATA drives are detected by combios, why doesn't the >> FreeBSD 7.0p2 installer see them? Do I need to add something to the >> GENERIC kernel? > > No, it should work out of the box. I've installed a 7.0 release and > now > i run 7-STABLE. > > Well, I don't have any problem on my net5501 with a WDC WD2500BEVS > disk. > ComBios 1.33 That's useful. I just found a WDC2500BEVS on the shelf. Tried it with net5501 S/N 57N00725 with these results in combios 1.33: 10 warm boot cycles: pass: 3, fail (drive not detected): 7 10 cold boot cycles: fail (4 LED silent hang) : 2 fail (drive not detected): 5 pass: 3 When drive is detected, using "boot f0" for the FreeBSD 7.0 installer is not successful: the FreeBSD kernel can't see the drive. So, I guess I need to repeat this test on my other recent net5501, and then again on my two older net5501's (which are running ATA drives) to try to confirm that it is a manufacturing fault with the last batch of net5501's. 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. I also have a 2500BEVE drive that I could try, similar but slightly newer. Thanks! - Martin _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsLe Sun, 22 Jun 2008 17:55:32 +0100,
Martin Johnson <martin.johnson.uk.lists@...> a écrit : Hello, > So, I guess I need to repeat this test on my other recent net5501, > and then again on my two older net5501's (which are running ATA > drives) to try to confirm that it is a manufacturing fault with the > last batch of net5501's. My box is two months old. > 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. The ComBios reports : Pri Mas WDC WD2500BEVS-00UST0 LBA Xlt 1024-255-63 134 GByte (The drive is a 250 Gbyte but it does not seem to hurt.) # atacontrol cap ad0 Protocol Serial ATA v1.0 device model WDC WD2500BEVS-00UST0 serial number WD-WXC208956619 firmware revision 01.01A01 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 488397168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 128/0x80 automatic acoustic management yes no 254/0xFE 128/0x80 dmesg: atapci0: <AMD CS5536 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 ata0: <ATA channel 0> on atapci0 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci0 ata1: [ITHREAD] ad0: 238475MB <WDC WD2500BEVS-00UST0 01.01A01> at ata0-master UDMA100 Regards. _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsOn 22 Jun 2008, at 18:29, Patrick Lamaizière wrote: > Le Sun, 22 Jun 2008 17:55:32 +0100, > Martin Johnson <martin.johnson.uk.lists@...> 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 Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsLe Sun, 22 Jun 2008 19:09:54 +0100,
Martin Johnson <martin.johnson.uk.lists@...> a écrit : > 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. I asked for this some time ago, see. http://www.nabble.com/Net5501-and-SATA-disk-on-FreeBSD-td16986487.html I patched the ata driver to not check the cable. _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsOn 22 Jun 2008, at 19:31, Patrick Lamaizière wrote: > Le Sun, 22 Jun 2008 19:09:54 +0100, > Martin Johnson <martin.johnson.uk.lists@...> a écrit : > > >> 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. > > I asked for this some time ago, see. > http://www.nabble.com/Net5501-and-SATA-disk-on-FreeBSD-td16986487.html > > I patched the ata driver to not check the cable. Thanks! So, there's nothing wrong with my older net5501, it's working as expected for FreeBSD 7.0. That's ironic: the ATA driver is mis-detecting the SATA cable, and selecting a mode that's slower than necessary. Whereas just last month, I submitted a patch ( http://lists.soekris.com/pipermail/soekris-tech/2008-May/014425.html ) to address the opposite case, where the ATA driver mis-detects a PATA cable and selects UMDA100, which is too fast and therefore causes errors. Cheers, - Martin. _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
|
|
Re: SATA failures on 2 x net5501-70 unitsAn update for anyone seeing the same issue.... Combios 1.33 was used
for all tests. NOT WORKING: My two recent net5501's do not work with any SATA drive: I tested five different SATA laptop drive models. Cortex Systems told me that they are currently investigating, and Soren's list post of 26th June sounds like the same issue. Hopefully Soren will find a solution soon. WORKING: My older net5501 works OK with all five SATA test drives. After netbooting, I was able to install a minimal FreeBSD 7.0 installation on each drive, and then reboot cleanly into FreeBSD. (But, the same hard drives would not then boot up if transferred to either of the newer net5501 units.) LESSON LEARNT: At first, my older net5501 had problems with two out of my five SATA test drives: lots of disk errors when the FreeBSD installer tried to use it. This turned out to be my fault! The two SATA drives that gave errors were from a laptop which used an ATA hard disk password. Using the laptop to clear the password fixed that problem. FEATURE REQUEST: If it's easy, it might be helpful if the ComBIOS could check and report if the hard drive has a password set. It would also be possible to clear the password but (by design) this erases any data on the hard disk, and takes a long time for that reason. (Aside: apparently some drives have a default master password which can be used with suitable utilities to remove the user password non- destructively.) Cheers, - Martin _______________________________________________ Soekris-tech mailing list Soekris-tech@... http://lists.soekris.com/mailman/listinfo/soekris-tech |
| Free Forum Powered by Nabble | Forum Help |