Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Jun 2008 17:21:34 +0200
From:      "Marcel Grandemange" <thavinci@thavinci.za.net>
To:        "'George Vagner'" <george@vagner.com>
Cc:        freebsd-questions@freebsd.org
Subject:   RE: Unstable File Server
Message-ID:  <002201c8d7a0$51bf4d50$f53de7f0$@za.net>
In-Reply-To: <200806261441.m5QEfUkC043968@ns1.vagner.com>
References:  <6.0.0.22.2.20080625111437.02543058@mail.computinginnovations.com> <200806261441.m5QEfUkC043968@ns1.vagner.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Ad2 is the only one out of the troubled drives that is in a bay that seems
to be giving issues.
And when replacing it with the 20gb issues went away.

Im considering changing motherboards from the MSI im using to an intel.
Mabey FreeBSD has issues with the via chipset used for the IDE & Sata
controllers.

Any input there? Also it would be nice if someone can explain to me exactly
what the errors meen that ive been experiencing, seeing as they seem to be
different depending on drive.


Thank You.

-----Original Message-----
From: George Vagner [mailto:george@vagner.com] 
Sent: Thursday, June 26, 2008 4:44 PM
To: 'Derek Ragona'; 'Marcel Grandemange'
Cc: freebsd-questions@freebsd.org
Subject: RE: Unstable File Server

I have had those exact problems with my removable tray.

Try eliminating the tray for a while and see...





-----Original Message-----
From: owner-freebsd-questions@freebsd.org
[mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Derek Ragona
Sent: Wednesday, June 25, 2008 12:23 PM
To: Marcel Grandemange
Cc: freebsd-questions@freebsd.org
Subject: RE: Unstable File Server

At 10:59 AM 6/25/2008, Marcel Grandemange wrote:
>The raid card is an Adaptec 2420sa, however devices on that controller
never
>have shown troubles.
>
>
>
>To give a breakdown:
>
>
>
>Mount points:
>
>
>
>/dev/ad0s1e on /tmp (ufs, local, soft-updates)
>/dev/ad0s1f on /usr (ufs, local, soft-updates)
>/dev/ad0s1d on /var (ufs, local, soft-updates)
>/dev/ad6s1d on /mnt/750sg (ufs, local, noatime, soft-updates)
>/dev/aacd0s1d on /mnt/RaidVolume (ufs, local, noatime, soft-updates)
>/dev/ad2s1d on /mnt/250GbMax (ufs, local, noatime, soft-updates)
>
>
>
>
>
>DMESG:
>
>
>
>ad0: 114472MB <Seagate ST3120026A 3.06> at ata0-master UDMA100
>ad2: 239372MB <Maxtor 6L250R0 BAH41G10> at ata1-master UDMA133
>acd0: DVDROM <SAMSUNG DVD-ROM SD-616F/E104> at ata1-slave UDMA33
>ad6: 715404MB <Seagate ST3750330AS SD15> at ata3-master SATA150
>aacd0: <Volume> on aac0
>aacd0: 523996MB (1073143808 sectors)
>
>
>
>pciconf -vl
>
>
>
>hostb0@pci0:0:0:0: class=0x060000 card=0x02961106 chip=0x02961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>hostb1@pci0:0:0:1: class=0x060000 card=0x00000000 chip=0x12961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>hostb2@pci0:0:0:2: class=0x060000 card=0x00000000 chip=0x22961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>hostb3@pci0:0:0:3: class=0x060000 card=0x00000000 chip=0x32961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>hostb4@pci0:0:0:4: class=0x060000 card=0x00000000 chip=0x42961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>hostb5@pci0:0:0:7: class=0x060000 card=0x00000000 chip=0x72961106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'P4M800 Standard Host Bridge'
>class = bridge
>subclass = HOST-PCI
>pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0xb1981106 rev=0x00
>hdr=0x01
>vendor = 'VIA Technologies Inc'
>device = 'ProSavageDDR P4X600,Apollo KT400/A/600 CPU to AGP Bridge'
>class = bridge
>subclass = PCI-PCI
>cbb0@pci0:0:5:0: class=0x060700 card=0x00000000 chip=0x04751180 rev=0x81
>hdr=0x02
>vendor = 'Ricoh Company, Ltd.'
>device = 'RL5c475 Cardbus Controller'
>class = bridge
>subclass = PCI-CardBus
>aac0@pci0:0:6:0: class=0x010400 card=0x029d9005 chip=0x02869005 rev=0x02
>hdr=0x00
>vendor = 'Adaptec Inc'
>device = 'AAC-RAID (Rocket)'
>class = mass storage
>subclass = RAID
>re0@pci0:0:7:0: class=0x020000 card=0x43001186 chip=0x43001186 rev=0x10
>hdr=0x00
>vendor = 'D-Link System Inc'
>device = 'dlg10028 Used on DGE-528T Gigabit adaptor'
>class = network
>subclass = ethernet
>atapci0@pci0:0:15:0: class=0x010400 card=0x71041462 chip=0x31491106
rev=0x80
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT8237 VT6410 SATA RAID Controller'
>class = mass storage
>subclass = RAID
>atapci1@pci0:0:15:1: class=0x01018a card=0x71041462 chip=0x05711106
rev=0x06
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT82C586A/B/VT82C686/A/B/VT823x/A/C Bus Master IDE Controller'
>class = mass storage
>subclass = ATA
>uhci0@pci0:0:16:0: class=0x0c0300 card=0x71041462 chip=0x30381106 rev=0x81
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host
Controller'
>class = serial bus
>subclass = USB
>uhci1@pci0:0:16:1: class=0x0c0300 card=0x71041462 chip=0x30381106 rev=0x81
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host
Controller'
>class = serial bus
>subclass = USB
>uhci2@pci0:0:16:2: class=0x0c0300 card=0x71041462 chip=0x30381106 rev=0x81
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host
Controller'
>class = serial bus
>subclass = USB
>uhci3@pci0:0:16:3: class=0x0c0300 card=0x71041462 chip=0x30381106 rev=0x81
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host
Controller'
>class = serial bus
>subclass = USB
>ehci0@pci0:0:16:4: class=0x0c0320 card=0x71041462 chip=0x31041106 rev=0x86
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT6202/12 USB 2.0 Enhanced Host Controller'
>class = serial bus
>subclass = USB
>isab0@pci0:0:17:0: class=0x060100 card=0x32271106 chip=0x32271106 rev=0x00
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT8237 PCI-to-ISA Bridge'
>class = bridge
>subclass = PCI-ISA
>vr0@pci0:0:18:0: class=0x020000 card=0x71041462 chip=0x30651106 rev=0x78
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'VT6102 Rhine II PCI Fast Ethernet Controller||Used by GERICOM in
>laptop Webengine Advanced'
>class = network
>subclass = ethernet
>vgapci0@pci0:1:0:0: class=0x030000 card=0x71041462 chip=0x72051106 rev=0x01
>hdr=0x00
>vendor = 'VIA Technologies Inc'
>device = 'KM400 VIA Technologies, Inc. VT8378 [S3 UniChrome] Graphics
>Adapter'
>class = display
>subclass = VGA
>
>
>
>Now the issues im having:
>
>
>
>Jun 20 15:40:24 gw2 kernel: ad2: WARNING - WRITE_DMA48 UDMA ICRC error
>(retrying request) LBA=367592031
>Jun 20 15:40:24 gw2 kernel: ad2: FAILURE - WRITE_DMA48
>status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=367592031
>Jun 20 15:40:24 gw2 kernel: g_vfs_done():ad2s1d[WRITE(offset=188207087616,
>length=131072)]error = 5
>Jun 20 15:40:41 gw2 kernel: ad2: WARNING - WRITE_DMA48 UDMA ICRC error
>(retrying request) LBA=368639871
>Jun 20 15:40:41 gw2 kernel: ad2: FAILURE - WRITE_DMA48
>status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=368639871
>Jun 20 15:40:41 gw2 kernel: g_vfs_done():ad2s1d[WRITE(offset=188743516160,
>length=131072)]error = 5
>Jun 20 15:50:45 gw2 kernel: ad2: WARNING - WRITE_DMA48 UDMA ICRC error
>(retrying request) LBA=402834719
>Jun 20 15:50:45 gw2 kernel: ad2: FAILURE - WRITE_DMA48
>status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=402834719
>Jun 20 15:50:45 gw2 kernel: g_vfs_done():ad2s1d[WRITE(offset=206251343872,
>length=131072)]error = 5
>Jun 20 15:58:05 gw2 kernel: ad2: WARNING - WRITE_DMA48 UDMA ICRC error
>(retrying request) LBA=431801119
>Jun 20 15:58:05 gw2 kernel: ad2: FAILURE - WRITE_DMA48
>status=51<READY,DSC,ERROR> error=4<ABORTED> LBA=431801119
>Jun 20 15:58:05 gw2 kernel: g_vfs_done():ad2s1d[WRITE(offset=221082075136,
>length=131072)]error = 5
>
>
>
>AND
>
>
>
>Jun 25 10:11:34 gw2 kernel: acd0: WARNING - unknown CMD (0x4a ) read data
>overrun 18>8
>Jun 25 10:11:55 gw2 kernel: acd0: WARNING - TEST_UNIT_READY t askqueue
>timeout - completing request directly
>Jun 25 10:13:54 gw2 kernel: acd0: WARNING - PREVENT_ALLOW tas kqueue
timeout
>- completing request directly
>Jun 25 10:13:55 gw2 kernel: pid 2998 (hald-addon-mouse-sy), u id 0: exited
>on signal 11 (core dumped)
>Jun 25 10:14:15 gw2 kernel: acd0: WARNING - TEST_UNIT_READY t askqueue
>timeout - completing request directly
>Jun 25 10:16:15 gw2 kernel: acd0: WARNING - PREVENT_ALLOW tas kqueue
timeout
>- completing request directly
>Jun 25 10:18:15 gw2 kernel: acd0: WARNING - TEST_UNIT_READY t askqueue
>timeout - completing request directly
>Jun 25 10:20:15 gw2 kernel: acd0: WARNING - READ_TOC taskqueu e timeout -
>completing request directly
>Jun 25 10:22:15 gw2 kernel: acd0: WARNING - READ_TOC taskqueue timeout -
>completing request directly
>
>
>
>AND
>
>
>
>Jun 25 13:46:00 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:04 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:08 gw2 kernel: ad6: WARNING - SET_MULTI taskqueue timeout -
>completing request directly
>Jun 25 13:46:08 gw2 kernel: ad6: FAILURE - WRITE_DMA48 timed out
>LBA=1358069247
>Jun 25 13:46:17 gw2 kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE
>taskqueue timeout - completing request directly
>Jun 25 13:46:21 gw2 kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE
>taskqueue timeout - completing request directly
>Jun 25 13:46:25 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:29 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:33 gw2 kernel: ad6: WARNING - SET_MULTI taskqueue timeout -
>completing request directly
>Jun 25 13:46:33 gw2 kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry
>left) LBA=1358069375
>Jun 25 13:46:42 gw2 kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE
>taskqueue timeout - completing request directly
>Jun 25 13:46:46 gw2 kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE
>taskqueue timeout - completing request directly
>Jun 25 13:46:50 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:54 gw2 kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE
>taskqueue timeout - completing request directly
>Jun 25 13:46:58 gw2 kernel: ad6: WARNING - SET_MULTI taskqueue timeout -
>completing request directly
>Jun 25 13:46:58 gw2 kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry
left)
>LBA=191
>Jun 25 13:47:07 gw2 kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE
>taskqueue timeout - completing request directly
>
>
>
>Device ad2 is an IDE device and is on same cable as DVDROM however the
Drive
>itself is master.
>
>I replaced ad2 with an old 20Gb and it behaved itself however other devices
>still giving hassels..
>
>(Ad2 is in a removable bay), so same cables etc.
>
>
>
>
>
>Thank You kindly for assistance so far!
>
>

Without looking at your adaptec card to see if it has a Silicon Image RAID 
chip, usually marked as an SIL#### on the chip I can't say for sure but SIL 
RAID chips do cause DMA issues.  I had a 2 channel Adaptec card that used a 
SIL chip and it wouldn't work well with FreeBSD.  I got similar errors that 
you are seeing.  Unfortunately with the SIL RAID chips some versions of the 
same chip (they don't change chip versions with all chip changes) will work 
with FreeBSD.

I would say your problem is either the RAID card or the drive(s).  I would 
try diagnostics on the drives from the manufacturer's websites.  If the 
drives pass these tests I would replace the RAID card since you already 
tried new cables.

         -Derek



>From: Derek Ragona [mailto:derek@computinginnovations.com]
>Sent: Wednesday, June 25, 2008 5:08 PM
>To: Marcel Grandemange; tundra@tundraware.com
>Cc: freebsd-questions@freebsd.org
>Subject: RE: Unstable File Server
>
>
>
>At 09:37 AM 6/25/2008, Marcel Grandemange wrote:
>
>
>
>If you see in forum I had replaced all cables with brand new ones, upgraded
>the PSU three times, and even tried multiple PCI controllers. The only
place
>I have not picked up issues yet is with the aacd array, almost everything
>else has been giving issues on and off, however only under heavy data
>transfer.
>
>The drive im receiving the most issues from is also brand new and worked
>perfectly under windows.
>The 250gb Maxtor drive also works without hassels under windows.
>
>I have also recently replaced the DVD rom because for no apparent reason it
>started giving issues aswell.
>(Even though it wasn't in use or even mounted)
>
>I havant had issues with small drives, the boot drive has never reported
any
>form of errors and I replaced the Maxtor 250 with an old 20gb Seagate to
>test and that worked flawlessly aswell.
>
>
>I have no idea anymore of what to do.
>
>
>What RAID card are you using?  Or is it built into the motherboard, in
which
>case what RAID chip is in use?
>
>Is the older 20gb drive using the same drive interface?
>
>         -Derek
>
>
>
>
>
>
>-----Original Message-----
>From: Tim Daneliuk [mailto:tundra@tundraware.com]
>Sent: Wednesday, June 25, 2008 4:19 PM
>To: Marcel Grandemange
>Cc: freebsd-questions@freebsd.org
>Subject: Re: Unstable File Server
>
>Marcel Grandemange wrote:
> > Good day!
> >
> > I hope someone might be able to assist me over here!
> >
> >
> >
> > I have a multipurpose FreeBSD server, and one of the roles is being a
file
> > server.
> >
> > This role however seems to continuously bring the machine to it's knees.
> >
> >
> >
> > I have tried seeking help elsewhere namely
> >
> > http://www.daemonforums.org/showthread.php?t=980
> >
> >
> >
> > But still can't seem to get this going. Id really appreciate some input,
> > thank you!
>
>Have you tried swapping out the drive cables with new/UDMA133 ones.  Every
>time I think
>I've found a problem w/FBSD disk handling it ends up being the cables :)
>
>
>__________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
>"freebsd-questions-unsubscribe@freebsd.org"
>
>
>__________ NOD32 3205 (20080621) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.eset.com <http://www.eset.com/>;
>
>
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>
>
>
>__________ NOD32 3205 (20080621) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.eset.com
>
>
>--
>This message has been scanned for viruses and
>dangerous content by  <http://www.mailscanner.info/>; MailScanner, and is
>believed to be clean.
>
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


__________ NOD32 3205 (20080621) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002201c8d7a0$51bf4d50$f53de7f0$>