From owner-freebsd-scsi@FreeBSD.ORG Sun Apr 23 17:21:30 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 569C816A402 for ; Sun, 23 Apr 2006 17:21:30 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC7A643D55 for ; Sun, 23 Apr 2006 17:21:29 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A7702.dip.t-dialin.net [84.154.119.2]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k3NHLJiq071300; Sun, 23 Apr 2006 19:21:22 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k3NHLG7O059955; Sun, 23 Apr 2006 19:21:17 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k3NHMFR7026353; Sun, 23 Apr 2006 19:22:15 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200604231722.k3NHMFR7026353@fire.jhs.private> To: freebsd-scsi@freebsd.org In-Reply-To: Message from Oliver Fromme of "Fri, 21 Apr 2006 12:50:17 +0200." <200604211050.k3LAoHsf097325@lurza.secnetix.de> Date: Sun, 23 Apr 2006 19:22:15 +0200 From: "Julian H. Stacey" Cc: Oliver Fromme Subject: Re: USB Ram Stick X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2006 17:21:30 -0000 Hi Oliver, cc list. Thanks for your response :-) Oliver Fromme wrote: > Julian Stacey wrote: > > On FreeBSD-6.0-RELEASE I took a friend's 2G stick containing the > > usual MBR with one partition allocated as aprox. 2 Gig of DOS > > file system, & read the entire raw stick onto hard disc. > > > > (I still have that image BTW, 2138177536 Apr 3 01:40 sony-stick-da0 , > > but I dont care about the data, I care about the expensive stick!) > > > > I wrote the image back to my identical stick (with dd), it wouldn't continue > > writing after a while, (cant remember exact message). > > The exact message would be very useful to know. Lost, I was travelling at the time; either I saved it & then lost it after travel, or it was unsaved as boringly common, eg as in a message I just got: dd: /dev/da0: Input/output error 1000448+0 records in 1000448+0 records out 512229376 bytes transferred in 809.536057 secs (632744 bytes/sec) (while sizing a 1 Gig stick, & it failing half way). ( My laptop, or FreeBSD, doesnt seem to always get on with the Belkin Cardbus USB 2.0 adapter - the Belkin adapter runs too hot to hold & BSD sometimes crashes (& my brother's Belkin died shortly after use in my laptop, http://berklix.com/~jhs/hardware/toshiba/satellite.s5100-603/ whereas his Belkin USB had until then run fine in his near identical Toshiba that runs just MS-XP (I suspect BSD is running the card in full power mode, whereas perhaps MS-XP is doing standby cycles or similar) ) ... However the Belkin is a side issue, I'm using my USB-1 built in ports on various other machines to analyse this 2G bad stick. > Are you absolutely sure that your stick is really identical, > including the size? 4 x 2G sticks were bought at same time from same vendor, so nominaly the same size, however in light of your writing below, No, your most probably right, the sticks would likely have been of slightly different sizes (but I can't check as I now only have access to mine, the other 3 are with MS users 1000 kilometres away, who don't have much clue or eg dd to measure bytes). > The sizes sometimes seem to differ by > small amounts, even between sticks of the exact same brand > and model. > > For example, a shop here recently sold 1GB sticks for 25 EUR > so a friend of mine bought two of them. I tried them both: > one had 2096640 blocks, the other had 2096768 blocks. > > I'm not an expert, but my guess is that the manufacturer > tests the chips and excludes bad areas, so the capacities > vary. > > Maybe your image was a little too big for the second stick. Yes, thanks, good point, seems a ~ 50% chance. I've sized several sticks of mine now you mention this, & they all come up short of nominal capacity. (I'd wrongly expected a more conservative architecture, with extra blocks to be patched in as needed to retain nominal capacity). > > Now /dev/da0* is just da0 , no other entries. > > > > I've tried creating a new MBR with fdisk, but failed. > > Did you try to clean it before? i.e. > dd if=/dev/zero of=/dev/da0 count=100 > (See the example in the bsdlabel(8) manpage.) Yes, pretty sure I did, but did it again: dd: /dev/da0: Input/output error 1+0 records in 0+0 records out 0 bytes transferred same for dd if=/dev/zero of=/dev/da0 count=1 same for dd if=/dev/zero of=/dev/pass0 count=100 > > camcontrol format da0 -w > > You are about to REMOVE ALL DATA from the following device: > > pass0: Removable Direct Access SCSI-2 device > > pass0: Serial Number > > pass0: 1.000MB/s transfers > > Are you SURE you want to do this? (yes/no) > > Formatting...Format Complete > > I assume that didn't do anything at all. Yes, it didn't help. bsdlabel -w da0 bsdlabel: /dev/da0 read: Input/output error The only hope now before I give up & try to get the stick replaced, is if anyone might know how I could use manipulate this camcontrol modepage da0 -l 0x00 Vendor-Specific camcontrol modepage da0 -m 0x00 -b bf 01 f8 43 07 28 80 c0 07 28 00 00 00 00 34 e0 bf bf 19 ba 05 28 eb 8b 04 08 5c 9b ab 07 00 b3 07 28 01 00 00 00 80 c0 07 28 00 b3 07 28 54 e0 bf 01 f8 43 07 28 01 00 00 00 98 86 04 08 b4 e0 bf bf 51 b8 05 28 eb 8b 04 08 5c 9b ab 07 10 30 07 28 88 e0 bf bf 01 00 00 00 8c e0 bf bf 84 e0 bf bf 19 ba 05 28 7f 8c 04 08 00 b0 07 28 00 b1 07 28 00 b2 07 28 00 b3 07 28 00 b1 07 28 00 b1 07 01 6e b7 05 28 00 b3 07 28 3c cb 09 28 04 e1 bf 01 00 b3 07 28 60 e0 bf bf 04 00 00 00 04 00 00 00 d8 e0 bf bf 01 00 00 00 dc e0 bf bf 00 10 00 01 f8 43 07 28 01 00 00 00 98 86 04 08 f4 e0 bf bf 26 9a 05 28 eb 8b 04 08 5c 9b ab 07 00 b0 07 28 e4 e0 bf bf 01 00 00 00 b4 1b 08 28 14 e1 Or, might /dev/pass0 be of some use ? Any other ideas anyone ? Thanks. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 24 11:03:03 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFAEB16A408 for ; Mon, 24 Apr 2006 11:03:03 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54F6B43D76 for ; Mon, 24 Apr 2006 11:02:56 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3OB2uDu035630 for ; Mon, 24 Apr 2006 11:02:56 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3OB2ttU035624 for freebsd-scsi@freebsd.org; Mon, 24 Apr 2006 11:02:55 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 24 Apr 2006 11:02:55 GMT Message-Id: <200604241102.k3OB2ttU035624@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 11:03:03 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP o [2005/12/12] kern/90282 scsi [sym] SCSI bus resets cause loss of ch de o [2006/02/04] kern/92798 scsi [ahc] SCSI problem with timeouts o [2006/02/10] kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems wit o [2006/03/22] kern/94838 scsi Kernel panic while mounting SD card with 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai o [2006/04/21] kern/96133 scsi [scsi] [patch] add scsi quirk for joyfly 6 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 24 13:02:46 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.ORG Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F30816A402 for ; Mon, 24 Apr 2006 13:02:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F9DE43D4C for ; Mon, 24 Apr 2006 13:02:45 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wluzyr@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k3OD2cP7029842 for ; Mon, 24 Apr 2006 15:02:44 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k3OD2c6k029841; Mon, 24 Apr 2006 15:02:38 +0200 (CEST) (envelope-from olli) Date: Mon, 24 Apr 2006 15:02:38 +0200 (CEST) Message-Id: <200604241302.k3OD2c6k029841@lurza.secnetix.de> From: Oliver Fromme To: freebsd-scsi@FreeBSD.ORG In-Reply-To: <200604231722.k3NHMFR7026353@fire.jhs.private> X-Newsgroups: list.freebsd-scsi User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 24 Apr 2006 15:02:44 +0200 (CEST) Cc: Subject: Re: USB Ram Stick X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-scsi@FreeBSD.ORG List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 13:02:46 -0000 Julian H. Stacey wrote: > Hi Oliver, cc list. There's no need to send me a copy, I'm reading the list. I would prefer that you simply reply back to the list. Thanks. > Oliver Fromme wrote: > > Julian Stacey wrote: > > > I wrote the image back to my identical stick (with dd), it wouldn't continue > > > writing after a while, (cant remember exact message). > > > > The exact message would be very useful to know. > > Lost, I was travelling at the time; either I saved it & then lost > it after travel, or it was unsaved as boringly common, eg as in a > message I just got: > dd: /dev/da0: Input/output error Hmm ... yes, most likely it was an "Input/output error", too. > I've sized several sticks of mine now you mention this, & they all > come up short of nominal capacity. (I'd wrongly expected a more > conservative architecture, with extra blocks to be patched in as > needed to retain nominal capacity). Extra blocks cost extra money, I guess. :-) Given that prices have fallen considerably, the market on USB memory sticks is probably pretty tough, like the DRAM market. > > Did you try to clean it before? i.e. > > dd if=/dev/zero of=/dev/da0 count=100 > > (See the example in the bsdlabel(8) manpage.) > > Yes, pretty sure I did, but did it again: > dd: /dev/da0: Input/output error > 1+0 records in 0+0 records out 0 bytes transferred > same for dd if=/dev/zero of=/dev/da0 count=1 Not good. Looks like a low-level problem (you also get a bunch of kernel error messages, I assume). In such cases I usually try to add quirks for the device to /sys/cam/scsi/scsi_da.c. According to my experience there's a good chance the device will work with a quirk. (Disclaimer: I'm not a CAM expert; I just happen to have some experience with various USB mass storage devices.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 26 08:29:09 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7639716A402 for ; Wed, 26 Apr 2006 08:29:09 +0000 (UTC) (envelope-from pldv@sinstelecom.net) Received: from mail.sinstelecom.net (mail.sinstelecom.net [80.92.97.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D36A43D48 for ; Wed, 26 Apr 2006 08:29:08 +0000 (GMT) (envelope-from pldv@sinstelecom.net) Received: from [192.168.2.15] (account pldv@sinstelecom.net HELO dreadpc.office.sinstelecom.net) by mail.sinstelecom.net (CommuniGate Pro SMTP 5.0.9) with ESMTPA id 1348406 for freebsd-scsi@freebsd.org; Wed, 26 Apr 2006 12:29:21 +0400 Date: Wed, 26 Apr 2006 12:29:06 +0400 From: =?windows-1251?B?z+vg6vH+6iDE7Ojy8Ojp?= X-Mailer: The Bat! (v3.65.03) Professional X-Priority: 3 (Normal) Message-ID: <04981116.20060426122906@sinstelecom.net> To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Subject: unsubscribe freebsd-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?windows-1251?B?z+vg6vH+6iDE7Ojy8Ojp?= List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 08:29:09 -0000 Здравствуйте, majordomo. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RC #2: Tue Apr 25 15:33:24 MSD 2006 dread@ftp1.zelnet.ru:/usr/obj/usr/src/sys/ftp1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100800 Logical CPUs per core: 2 real memory = 2147352576 (2047 MB) avail memory = 2066108416 (1970 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 mpt0: port 0xc800-0xc8ff mem 0xdedc0000-0xdedcffff,0xdedb0000-0xdedbffff irq 26 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt0: Capabilities: ( RAID-0 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) mpt1: port 0xcc00-0xccff mem 0xdedf0000-0xdedfffff,0xdede0000-0xdedeffff irq 25 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. mpt1: Capabilities: ( RAID-0 SAFTE ) mpt1: 0 Active Volumes (1 Max) mpt1: 0 Hidden Drive Members (6 Max) pci1: at device 0.1 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 em0: port 0xdc00-0xdc3f mem 0xdeea0000-0xdeebffff irq 54 at device 4.0 on pci3 em0: Ethernet address: 00:04:23:bc:ea:26 em1: port 0xdc80-0xdcbf mem 0xdeee0000-0xdeefffff irq 55 at device 4.1 on pci3 em1: Ethernet address: 00:04:23:bc:ea:27 pci1: at device 0.3 (no driver attached) pcib4: at device 30.0 on pci0 pci4: on pcib4 drm0: port 0xec00-0xecff mem 0xdf000000-0xdfffffff,0xdefff000-0xdeffffff irq 17 at device 12.0 on pci4 info: [drm] Initialized mach64 1.0.0 20020904 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A orm0: at iomem 0xc0000-0xca7ff,0xca800-0xce7ff,0xce800-0xcf7ff,0xcf800-0xd07ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.333 msec Waiting 5 seconds for SCSI devices to settle acd0: CDROM at ata0-slave UDMA33 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! da0 at mpt1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 2097144MB (4294950912 512 byte sectors: 255H 63S/T 267348C) Trying to mount root from ufs:/dev/da0s1a em0: link state changed to UP em1: link state changed to UP (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 89 c7 3c 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 8a 2b bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 10 a6 76 3c 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 10 b0 a1 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 c8 c2 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 14 18 93 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) I ran "dd bs=65536 if=/dev/da2e of=/dev/null" which completed successfully, reading all 2T with no errors. -- С уважением, Плаксюк Дмитрий Викторович Cлужба технической поддержки Городской сети: т. (095) 530-3101 mailto:pldv@sinstelecom.net From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 26 10:58:52 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F27B716A406 for ; Wed, 26 Apr 2006 10:58:52 +0000 (UTC) (envelope-from pldv@sinstelecom.net) Received: from mail.sinstelecom.net (mail.sinstelecom.net [80.92.97.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82F0D43D73 for ; Wed, 26 Apr 2006 10:58:46 +0000 (GMT) (envelope-from pldv@sinstelecom.net) Received: from [192.168.2.15] (account pldv@sinstelecom.net HELO dreadpc.office.sinstelecom.net) by mail.sinstelecom.net (CommuniGate Pro SMTP 5.0.9) with ESMTPA id 1349392 for freebsd-scsi@freebsd.org; Wed, 26 Apr 2006 14:59:02 +0400 Date: Wed, 26 Apr 2006 14:58:45 +0400 From: =?windows-1251?B?z+vg6vH+6iDE7Ojy8Ojp?= X-Mailer: The Bat! (v3.65.03) Professional X-Priority: 3 (Normal) Message-ID: <415166775.20060426145845@sinstelecom.net> To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Subject: unsubscribe freebsd-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?windows-1251?B?z+vg6vH+6iDE7Ojy8Ojp?= List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 10:58:53 -0000 Здравствуйте, majordomo. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RC #2: Tue Apr 25 15:33:24 MSD 2006 dread@ftp1.zelnet.ru:/usr/obj/usr/src/sys/ftp1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100800 Logical CPUs per core: 2 real memory = 2147352576 (2047 MB) avail memory = 2066108416 (1970 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 mpt0: port 0xc800-0xc8ff mem 0xdedc0000-0xdedcffff,0xdedb0000-0xdedbffff irq 26 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt0: Capabilities: ( RAID-0 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) mpt1: port 0xcc00-0xccff mem 0xdedf0000-0xdedfffff,0xdede0000-0xdedeffff irq 25 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. mpt1: Capabilities: ( RAID-0 SAFTE ) mpt1: 0 Active Volumes (1 Max) mpt1: 0 Hidden Drive Members (6 Max) pci1: at device 0.1 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 em0: port 0xdc00-0xdc3f mem 0xdeea0000-0xdeebffff irq 54 at device 4.0 on pci3 em0: Ethernet address: 00:04:23:bc:ea:26 em1: port 0xdc80-0xdcbf mem 0xdeee0000-0xdeefffff irq 55 at device 4.1 on pci3 em1: Ethernet address: 00:04:23:bc:ea:27 pci1: at device 0.3 (no driver attached) pcib4: at device 30.0 on pci0 pci4: on pcib4 drm0: port 0xec00-0xecff mem 0xdf000000-0xdfffffff,0xdefff000-0xdeffffff irq 17 at device 12.0 on pci4 info: [drm] Initialized mach64 1.0.0 20020904 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A orm0: at iomem 0xc0000-0xca7ff,0xca800-0xce7ff,0xce800-0xcf7ff,0xcf800-0xd07ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.333 msec Waiting 5 seconds for SCSI devices to settle acd0: CDROM at ata0-slave UDMA33 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! da0 at mpt1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 2097144MB (4294950912 512 byte sectors: 255H 63S/T 267348C) Trying to mount root from ufs:/dev/da0s1a em0: link state changed to UP em1: link state changed to UP (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 89 c7 3c 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 8a 2b bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 10 a6 76 3c 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 10 b0 a1 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 13 c8 c2 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) (da0:mpt1:0:0:0): WRITE(10). CDB: 2a 0 14 18 93 bc 0 0 80 0 (da0:mpt1:0:0:0): CAM Status: SCSI Status Error (da0:mpt1:0:0:0): SCSI Status: Check Condition (da0:mpt1:0:0:0): ABORTED COMMAND asc:47,0 (da0:mpt1:0:0:0): SCSI parity error (da0:mpt1:0:0:0): Retrying Command (per Sense Data) I ran "dd bs=65536 if=/dev/da2e of=/dev/null" which completed successfully, reading all 2T with no errors. -- С уважением, Плаксюк Дмитрий Викторович Cлужба технической поддержки Городской сети: т. (095) 530-3101 mailto:pldv@sinstelecom.net From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 26 19:58:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB7D616A400 for ; Wed, 26 Apr 2006 19:58:44 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12BD243D45 for ; Wed, 26 Apr 2006 19:58:43 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6615.dip.t-dialin.net [84.154.102.21]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k3QJweEo081990 for ; Wed, 26 Apr 2006 21:58:41 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k3QJwd5e072617 for ; Wed, 26 Apr 2006 21:58:40 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k3QJxuO0072830 for ; Wed, 26 Apr 2006 21:59:56 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200604261959.k3QJxuO0072830@fire.jhs.private> To: freebsd-scsi@freebsd.org In-Reply-To: Message from Oliver Fromme of "Mon, 24 Apr 2006 15:02:38 +0200." <200604241302.k3OD2c6k029841@lurza.secnetix.de> Date: Wed, 26 Apr 2006 21:59:56 +0200 From: "Julian H. Stacey" Subject: Re: USB Ram Stick X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 19:58:44 -0000 Oliver Fromme wrote: > Julian H. Stacey wrote: > > Hi Oliver, cc list. > > There's no need to send me a copy, I'm reading the list. > I would prefer that you simply reply back to the list. > Thanks. OK. I like a copy - so many threads & lists to skim. > > Oliver Fromme wrote: > > > Julian Stacey wrote: > > > > I wrote the image back to my identical stick (with dd), it wouldn't continue > > > > writing after a while, (cant remember exact message). > > > > > > The exact message would be very useful to know. > > > > Lost, I was travelling at the time; either I saved it & then lost > > it after travel, or it was unsaved as boringly common, eg as in a > > message I just got: > > dd: /dev/da0: Input/output error > > Hmm ... yes, most likely it was an "Input/output error", too. > > > I've sized several sticks of mine now you mention this, & they all > > come up short of nominal capacity. (I'd wrongly expected a more > > conservative architecture, with extra blocks to be patched in as > > needed to retain nominal capacity). > > Extra blocks cost extra money, I guess. :-) > > Given that prices have fallen considerably, the market on > USB memory sticks is probably pretty tough, like the DRAM > market. Yes. > > > Did you try to clean it before? i.e. > > > dd if=/dev/zero of=/dev/da0 count=100 > > > (See the example in the bsdlabel(8) manpage.) > > > > Yes, pretty sure I did, but did it again: > > dd: /dev/da0: Input/output error > > 1+0 records in 0+0 records out 0 bytes transferred > > same for dd if=/dev/zero of=/dev/da0 count=1 > > Not good. Looks like a low-level problem (you also get a > bunch of kernel error messages, I assume). Yes, on insertion: kernel: umass0: Generic Flash Disk, rev 2.00/1.00, addr 3 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 kernel: da0: Removable Direct Access SCSI-2 device kernel: da0: 1.000MB/s transfers kernel: da0: 2038MB (4173824 512 byte sectors: 255H 63S/T 259C) ( BTW 2136997888 = 4173824 x 512, & source stick I copied from was 2138177536 so your guess of slightly smaller target stick correct). Then 4 of: { Then 4 of: { kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 0 1 0 0 1 0 kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition kernel: (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:30,2 kernel: (da0:umass-sim0:0:0:0): Cannot read medium - incompatible format kernel: (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) } Then 1 of { kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 0 1 0 0 1 0 kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition kernel: (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:30,2 kernel: (da0:umass-sim0:0:0:0): Cannot read medium - incompatible format kernel: (da0:umass-sim0:0:0:0): Retries Exhausted } } > In such cases I usually try to add quirks for the device > to /sys/cam/scsi/scsi_da.c. According to my experience > there's a good chance the device will work with a quirk. Not sure this is [now] just a FreeBSD driver problems. The slightly larger 2G stick read to hard disc no problem. Problem came on or after writing back to the slightly smaller stick. I'm wondering if eg somehow the proprietary control page got scrambled so badly it now thinks its doing 1024 or 256 byte sectors or something equally weird - or maybe the RAM part just died & only the USB IC is answering. ( I tried reading the stick with Win-XP too, but no good: Win-XP is too clueless of course: half the clicks think there's no problem, & the other half give no clue what's wrong, doesnt report a device read error, let alone report an MBR unavailable, nor did XP offer to re MBR it, & DOS window with fdisk /mbr found no fdisk. I loathe XP, but checked what I was doing with XP worked on a normal stick (to confirm it wasn't me failing with XP). ) Either this stick died of its own accord, or possibly FreeBSD did something radical to it (though if so, & how is a mystery). Thanks for the pointer to the quirk table. I used it in desperation to turn on all of DA_Q_NO_SYNC_CACHE | DA_Q_NO_6_BYTE | DA_Q_NO_PREVENT It didn't help make the stick useable though. Still I get loads of (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:30,2 (da0:umass-sim0:0:0:0): Cannot read medium - incompatible format (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) That Sony 2G stick is going back to vendor ! It cost 55 pounds = 79 Euro. I learnt the quirk table though, detected a quirk in another stick & submiting via send-pr (from my notes here: http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sys/cam/scsi/ http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/sys/cam/scsi/ So something useful came from the work, thanks for your help Oliver :-) -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 26 21:59:04 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEB0016A46F for ; Wed, 26 Apr 2006 21:59:04 +0000 (UTC) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: from daemon.egr.msu.edu (daemon.egr.msu.edu [35.9.44.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B388343D4C for ; Wed, 26 Apr 2006 21:59:04 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: by daemon.egr.msu.edu (Postfix, from userid 21281) id 3F9721CC36; Wed, 26 Apr 2006 17:59:04 -0400 (EDT) Date: Wed, 26 Apr 2006 17:59:04 -0400 From: Adam McDougall To: scsi@freebsd.org Message-ID: <20060426215903.GB1063@egr.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: Recommendation for scsi disk array? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 21:59:05 -0000 I am setting up two 1U servers to be FreeBSD Postgres servers. I want to use a 3U SCSI disk array attached to each one for the PG data. I have 73G hitachi disks already that I want to use to populate 8 out of 16 slots of each of two arrays. Redundant 120v power supplies are important, hot swappable would definitely be nice, swappable redundant fans would probably be good. I don't really need environmental monitoring, and I will raid each array using a PCI card (lsi logic) in each server. Does anyone have any product/company recommendations, or past experience with a suitable product or company that hopefully still exists? Any warnings or bad experiences with any products out there? I should purchase soon and need to work on the product research. Thanks. From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 26 22:02:05 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC94A16A401 for ; Wed, 26 Apr 2006 22:02:05 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3922943D45 for ; Wed, 26 Apr 2006 22:02:05 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6615.dip.t-dialin.net [84.154.102.21]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k3QM23FH082312 for ; Thu, 27 Apr 2006 00:02:03 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k3QM21v8073112 for ; Thu, 27 Apr 2006 00:02:02 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k3QM3Ir4074287 for ; Thu, 27 Apr 2006 00:03:18 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Received: (from jhs@localhost) by fire.jhs.private (8.13.1/8.13.1/Submit) id k3QM3IXf074286; Thu, 27 Apr 2006 00:03:18 +0200 (CEST) (envelope-from jhs) Date: Thu, 27 Apr 2006 00:03:18 +0200 (CEST) Message-Id: <200604262203.k3QM3IXf074286@fire.jhs.private> To: freebsd-scsi@freebsd.org From: "Julian Stacey" Organization: http://berklix.com Munich Unix, BSD, Internet Consultancy Fcc: sent-mail User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com/~jhs/cv/ Subject: DA_Q_NO_SYNC_CACHE cam/scsi/scsi_da.c change between 6.0 & 6.1-RC X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 22:02:05 -0000 Hi SCSI people, I just sent a send-pr http://www.freebsd.org/cgi/query-pr.cgi?pr=96381 for a quirk table entry to avoid kernel error "Synchronize cache failed" on one of my memory sticks. Then checked it on 6.1-RC1, & added this text to my patch in http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sys/cam/scsi/scsi_da.c.integral.REL=ALL.diff Since sending in the send-pr for 6.0-RELEASE, This patch doesnt seem necessary on 6.1-RC1, (ie without my patch, my laptop no longer bleats: Synchronize cache failed) I guess someone has changed other USB code affecting DA_Q_NO_SYNC_CACHE ? If that's so, maybe other quirk table entries for DA_Q_NO_SYNC_CACHE might need to be removed too ? Julian -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 27 12:02:37 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7D6C16A404 for ; Thu, 27 Apr 2006 12:02:37 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3080C43D5D for ; Thu, 27 Apr 2006 12:02:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3RC2WQ1026635; Thu, 27 Apr 2006 07:02:32 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4450B2CC.1@centtech.com> Date: Thu, 27 Apr 2006 07:02:20 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Adam McDougall References: <20060426215903.GB1063@egr.msu.edu> In-Reply-To: <20060426215903.GB1063@egr.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1426/Wed Apr 26 13:03:01 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: scsi@freebsd.org Subject: Re: Recommendation for scsi disk array? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 12:02:37 -0000 Adam McDougall wrote: > I am setting up two 1U servers to be FreeBSD Postgres servers. > I want to use a 3U SCSI disk array attached to each one for the PG data. > I have 73G hitachi disks already that I want to use to populate 8 > out of 16 slots of each of two arrays. Redundant 120v power supplies > are important, hot swappable would definitely be nice, swappable > redundant fans would probably be good. I don't really need environmental > monitoring, and I will raid each array using a PCI card (lsi logic) in > each server. > > Does anyone have any product/company recommendations, or past experience with a > suitable product or company that hopefully still exists? Any warnings > or bad experiences with any products out there? I should purchase soon > and need to work on the product research. Thanks. I highly recommend the arrays from ACNC: http://www.acnc.com We have over 20 of them in use. They have triple redundant hot swappable power supplies too. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 27 13:39:08 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E28DD16A404 for ; Thu, 27 Apr 2006 13:39:08 +0000 (UTC) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: from daemon.egr.msu.edu (daemon.egr.msu.edu [35.9.44.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A451943D53 for ; Thu, 27 Apr 2006 13:39:08 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: by daemon.egr.msu.edu (Postfix, from userid 21281) id 3D1101CC36; Thu, 27 Apr 2006 09:39:08 -0400 (EDT) Date: Thu, 27 Apr 2006 09:39:08 -0400 From: Adam McDougall To: Eric Anderson Message-ID: <20060427133907.GJ1063@egr.msu.edu> References: <20060426215903.GB1063@egr.msu.edu> <4450B2CC.1@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4450B2CC.1@centtech.com> User-Agent: Mutt/1.5.11 Cc: scsi@freebsd.org Subject: Re: Recommendation for scsi disk array? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 13:39:09 -0000 On Thu, Apr 27, 2006 at 07:02:20AM -0500, Eric Anderson wrote: Adam McDougall wrote: >I am setting up two 1U servers to be FreeBSD Postgres servers. >I want to use a 3U SCSI disk array attached to each one for the PG data. >I have 73G hitachi disks already that I want to use to populate 8 >out of 16 slots of each of two arrays. Redundant 120v power supplies >are important, hot swappable would definitely be nice, swappable >redundant fans would probably be good. I don't really need environmental >monitoring, and I will raid each array using a PCI card (lsi logic) in >each server. > >Does anyone have any product/company recommendations, or past experience >with a suitable product or company that hopefully still exists? Any >warnings >or bad experiences with any products out there? I should purchase soon >and need to work on the product research. Thanks. I highly recommend the arrays from ACNC: http://www.acnc.com We have over 20 of them in use. They have triple redundant hot swappable power supplies too. That is actually what I am replacing because they have been unreliable. We have four, one had host scsi channel go out when a mounting rail was attached to it, one forgot its firmware when we shut it off for moving it, one new one had massive problems talking to the disks and had to be replaced. one failed the raid with a multiple disk failure an hour or so AFTER we moved the array, and the other I was going to use to replace the previously mentioned failure but some error messages from some of the disks on bootup made me think twice about it, so it is gathering dust. In short, once you get it working, don't EVER move or touch the array or you are putting the array at risk (mostly the data). From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 27 13:42:53 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C070816A400 for ; Thu, 27 Apr 2006 13:42:53 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DB3F43D4C for ; Thu, 27 Apr 2006 13:42:53 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3RDgpQa038944; Thu, 27 Apr 2006 08:42:51 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4450CA50.3010303@centtech.com> Date: Thu, 27 Apr 2006 08:42:40 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Adam McDougall References: <20060426215903.GB1063@egr.msu.edu> <4450B2CC.1@centtech.com> <20060427133907.GJ1063@egr.msu.edu> In-Reply-To: <20060427133907.GJ1063@egr.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1426/Wed Apr 26 13:03:01 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: scsi@freebsd.org Subject: Re: Recommendation for scsi disk array? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 13:42:53 -0000 Adam McDougall wrote: > On Thu, Apr 27, 2006 at 07:02:20AM -0500, Eric Anderson wrote: > > Adam McDougall wrote: > >I am setting up two 1U servers to be FreeBSD Postgres servers. > >I want to use a 3U SCSI disk array attached to each one for the PG data. > >I have 73G hitachi disks already that I want to use to populate 8 > >out of 16 slots of each of two arrays. Redundant 120v power supplies > >are important, hot swappable would definitely be nice, swappable > >redundant fans would probably be good. I don't really need environmental > >monitoring, and I will raid each array using a PCI card (lsi logic) in > >each server. > > > >Does anyone have any product/company recommendations, or past experience > >with a suitable product or company that hopefully still exists? Any > >warnings > >or bad experiences with any products out there? I should purchase soon > >and need to work on the product research. Thanks. > > I highly recommend the arrays from ACNC: > > http://www.acnc.com > > We have over 20 of them in use. > > They have triple redundant hot swappable power supplies too. > > > That is actually what I am replacing because they have been unreliable. > > We have four, one had host scsi channel go out when a mounting rail was > attached to it, one forgot its firmware when we shut it off for moving it, > one new one had massive problems talking to the disks and had to be replaced. > one failed the raid with a multiple disk failure an hour or so AFTER we > moved the array, and the other I was going to use to replace the previously > mentioned failure but some error messages from some of the disks on bootup > made me think twice about it, so it is gathering dust. > > In short, once you get it working, don't EVER move or touch the array or you > are putting the array at risk (mostly the data). Well, first, I must admit I am actually using the fiber channel arrays, not the direct attached scsi arrays. Secondly, I've never had any problems of the sort with them, and we've move ours around several times, even across town to a new datacenter. Sorry you've had such bad luck! What does ACNC say about it? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------