Re: [zfs-discuss] Setting up ZFS on AHCI disks
I solved the mystery - an astounding 7 out of the 10 brand new disks I was using were bad. I was using 4 at a time, and it wasn't until a good one got in the mix that I realized what was wrong. FYI, these were Western Digital WD15EADS and Samsung HD154UI. Each brand was mostly bad, with one or two good disks. The bad ones are functional enough that the BIOS can tell what type they are, but I got a lot of errors when I plugged them into a Linux box to check them. The whole thing is bizarre enough that I wonder if they got damaged in shipping or if my machine somehow damaged them. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
isainfo -k returns amd64, so I don't think that is the answer. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
On Fri, Apr 16, 2010 at 11:46:01AM -0700, Willard Korfhage wrote: > The drives are recent - 1.5TB drives I'm going to bet this is a 32-bit system, and you're getting screwed by the 1TB limit that applies there. If so, you will find clues hidden in dmesg from boot time about this, as the drives are probed. -- Dan. pgpTSqZVxspOO.pgp Description: PGP signature ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
> There should be no need to create partitions. > Something simple like this > hould work: > zpool create junkfooblah c13t0d0 > > And if it doesn't work, try "zpool status" just to > verify for certain, that > device is not already part of any pool. It is not part of any pool. I get the same "cannot label" message, and dmsg still shows the task file error messages that I mentioned before. The drives are new, and I don't think they are bad. Likewise, the motherboard is new, although I see the last BIOS release was September, 2008, so the design has been out for a while. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
No Areca controller on this machine. It is a different box, and the drives are just plugged into the SATA ports on the motherboard. I'm running build svn_133, too. The drives are recent - 1.5TB drives, 3 Western Digital and 1 Seagate, if I recall correctly. They ought to support SATA-2. They are brand new, and haven't been used before. I have the feeling I'm missing some simple, obvious step because I'm still pretty new to OpenSolaris. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Willard Korfhage > > devfsadm -Cv gave a lot of "removing file" messages, apparently for > items that were not relevant. That's good. If there were no necessary changes, devfsadm would say nothing. > I still get the same error message, but I'm guessing now that means I > have to create a partition on the device. However, I am still stymied There should be no need to create partitions. Something simple like this should work: zpool create junkfooblah c13t0d0 And if it doesn't work, try "zpool status" just to verify for certain, that device is not already part of any pool. > for the time being. fdisk can't open any of the /dev/rdsk/c13t*d0p0 > devices. I tried running format, and get this There may be something weird happening in your system. I can't think of any reason for that behavior. Unless you simply have a SATA card that has no proper driver support from opensolaris while in AHCI mode. > Error: can't open disk '/dev/rdsk/c13t0d0p0'. Yeah. Weird. > AVAILABLE DRIVE TYPES: > 0. Auto configure > 1. other > Specify disk type (enter its number): 0 > Auto configure failed > No Solaris fdisk partition found. Yeah. Weird. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
Your adapter read-outs look quite different than mine. I am on ICH-9, snv_133. Maybe that's why. But I thought I should ask on that occasion: -build? -do the drives currently support SATA-2 standard (by model, by jumper settings?) - could it be that the Areca controller has done something to them partition-wise? Regards, Tonmaus -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
devfsadm -Cv gave a lot of "removing file" messages, apparently for items that were not relevant. cfgadm -al says, about the disks, sata0/0::dsk/c13t0d0 disk connectedconfigured ok sata0/1::dsk/c13t1d0 disk connectedconfigured ok sata0/2::dsk/c13t2d0 disk connectedconfigured ok sata0/3::dsk/c13t3d0 disk connectedconfigured ok I still get the same error message, but I'm guessing now that means I have to create a partition on the device. However, I am still stymied for the time being. fdisk can't open any of the /dev/rdsk/c13t*d0p0 devices. I tried running format, and get this AVAILABLE DISK SELECTIONS: 0. c12d1 /p...@0,0/pci-...@1f,1/i...@0/c...@1,0 1. c13t0d0 /p...@0,0/pci1043,8...@1f,2/d...@0,0 2. c13t1d0 /p...@0,0/pci1043,8...@1f,2/d...@1,0 3. c13t2d0 /p...@0,0/pci1043,8...@1f,2/d...@2,0 4. c13t3d0 /p...@0,0/pci1043,8...@1f,2/d...@3,0 Specify disk (enter its number): 1 Error: can't open disk '/dev/rdsk/c13t0d0p0'. AVAILABLE DRIVE TYPES: 0. Auto configure 1. other Specify disk type (enter its number): 0 Auto configure failed No Solaris fdisk partition found. At this point, I not sure whether to run fdisk, format or something else. I tried fdisk, partition and label, but gut the message "Current Disk Type is not set." I expect this is a problem because of the "drive type unknown" appearing on the drives. I gather from another thread that I need to run fdisk, but I haven't been able to do it. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Tonmaus > > are the drives properly configured in cfgadm? I agree. You need to do these: devfsadm -Cv cfgadm -al ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Setting up ZFS on AHCI disks
Hi, are the drives properly configured in cfgadm? Cheers, Tonmaus -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
