Date: Sat, 25 Apr 2009 17:07:29 -0700 From: smallpox <smallpox@gmail.com> To: freebsd-hardware@freebsd.org Subject: altus 1300 / penguincomputing major issues with hard disks Message-ID: <49F3A5C1.8030801@gmail.com>
next in thread | raw e-mail | index | archive | help
I acquired a few of these last year and apparently they're perfect for linux, they're a bit outdated but I cannot stand linux. I've run one of these servers pretty stable with SATA150 and SATA300 drives but I received two 'FACTORY RECERTIFIED' drives back from Seagate (yes, they're a mess) but these were the older 500GIG 7200.10 ones. I popped them in at the datacente rand immediately came the box: Apr 24 17:03:48 x kernel: ad6: 114473MB <Seagate ST3120827AS 3.42> at ata3-master SATA150 Apr 24 17:03:48 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:03:48 x kernel: ad10: 476940MB <Seagate ST3500630AS 3.AAE> at ata5-master SATA300 then i rebooted it to add the second 500 gig drive and: Apr 24 17:07:42 x kernel: ad6: 114473MB <Seagate ST3120827AS 3.42> at ata3-master SATA150 Apr 24 17:07:42 x kernel: ad8: 476940MB <Seagate ST3500630AS 3.AAE> at ata4-master SATA300 Apr 24 17:07:42 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA48 status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=976773151 Apr 24 17:07:42 x kernel: ad10: 476940MB <Seagate ST3500630AS 3.AAE> at ata5-master SATA300 Apr 24 17:07:42 x kernel: SMP: AP CPU #1 Launched! Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=128 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=128 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=128 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=16 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=0 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=512 Apr 24 17:07:42 x kernel: Trying to mount root from ufs:/dev/mirror/gm0s1a after some major lag and lock ups.. Apr 24 17:12:09 x kernel: ad6: 114473MB <Seagate ST3120827AS 3.42> at ata3-master SATA150 Apr 24 17:12:09 x kernel: ad8: 476940MB <Seagate ST3500630AS 3.AAE> at ata4-master SATA300 Apr 24 17:12:09 x kernel: ad10: 476940MB <Seagate ST3500630AS 3.AAE> at ata5-master SATA300 Apr 24 17:12:09 x kernel: SMP: AP CPU #1 Launched! Apr 24 17:12:09 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:12:09 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 then again major lag / lockup Apr 24 17:13:44 x kernel: ad10: FAILURE - device detached Apr 24 17:13:44 x kernel: subdisk10: detached Apr 24 17:13:44 x kernel: ad10: detached Apr 24 17:13:57 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:13:58 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:13:58 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:13:59 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:13:59 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:14:00 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:14:00 x kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad8. Apr 24 17:14:05 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=9856 Apr 24 17:14:10 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=11392 Apr 24 17:14:16 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=17792 Apr 24 17:14:21 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=23296 Apr 24 17:14:57 x kernel: ad8: FAILURE - device detached Apr 24 17:14:57 x kernel: subdisk8: detached Apr 24 17:14:57 x kernel: ad8: detached Apr 24 17:14:57 x kernel: GEOM_MIRROR: Cannot write metadata on ad8 (device=gm0, error=6). Apr 24 17:14:57 x kernel: GEOM_MIRROR: Cannot clear metadata on disk ad8 (error=6). Apr 24 17:14:57 x kernel: GEOM_MIRROR: Synchronization request failed (error=6). ad8[WRITE(offset=11927552, length=131072)] Apr 24 17:14:57 x kernel: GEOM_MIRROR: Device gm0: provider ad8 disconnected. Apr 24 17:14:57 x kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad8 stopped. the two replacement drives that i got failed to work. took them home, ran short/long smart tests on both and they passed, now i'm at the office testing both of them and they seem fine. i was running 7.1-p3 amd64. so overall, this is what is happening. one system is ad4: 381554MB <Seagate ST3400620AS 3.AAE> at ata2-master SATA150 (giving me a million g_vfs_done) errors and i could link you to a pic, not sure if i'm allowed to so i will hope to see responses then do it. stuff like this "g_vfs_done() :ad4s1a[WRITE(offset=87081893888, length=16384)]error = 6" another system ad4: 1430799MB <Seagate ST31500341AS CC1G> at ata2-master SATA300 ad6: 1430799MB <Seagate ST31500341AS CC1G> at ata3-master SATA300 ad8: 190782MB <WDC WD2000JD-00HBB0 08.02D08> at ata4-master SATA150 smart shows both ad4/ad6 have read errors and some reallocated sectors, seagate says those firmware shouldn't be involved in their disgusting problems. and the system that's giving me the hard time locally which i tried the two 500 gig drives in it had two 120GB drives, both seagate. luckily i started using the second one last month as the main one just died or i think it died. what are the odds that i'm having an unlucky streak with these new/old drives and it's NOT my sata controller? i've been having this trouble for a while now on BSD on one of them so i was forced to use CentOS (without issues) but i dislike it. is there anything i could run? i have remote kvm access to the one with the g_vfs problems and the local one too but prefer not to break the local one. is this hardware just too old for freebsd to support it? as far as new support cause it seems like it just barely works. i guess i will get two western digital drives and try it on the local one next weekend.. i just need to figure this out asap. thanks. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49F3A5C1.8030801>