Derek G Nokes
2010-Oct-15 00:08 UTC
[zfs-discuss] adding new disks and setting up a raidz2
I am relatively new to OpenSolaris / ZFS (have been using it for maybe 6
months). I recently added 6 new drives to one of my servers and I would like to
create a new RAIDZ2 pool called ''marketData''.
I figured the command to do this would be something like:
zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0s0 c0t5000C5001A81E100d0s0
c0t5000C500268C0576d0s0 c0t5000C500268C5414d0s0 c0t5000C500268CFA6Bd0s0
c0t5000C500268D0821d0s0
Unfortunately I get an error:
[b]cannot open ''/dev/dsk/c0t5000C500268CFA6Bd0s0'': I/O
error[/b]
Can anyone give me some clues as to what is wrong?
I have included the zpool status and format output from my system
[b]ZPOOL STATUS[/b]
root at dnokes.homeip.net:~# zpool status
pool: rpool
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using ''zpool upgrade''. Once this is
done, the
pool will no longer be accessible on older software versions.
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t5000C50019F5B5BAd0s0 ONLINE 0 0 0
c0t5000C50019E0EB23d0s0 ONLINE 0 0 0
errors: No known data errors
[b]FORMAT[/b]
root at dnokes.homeip.net:~# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000C5001A6B9C5Ed0 <ATA-ST31500341AS-CC4H-1.36TB>
/scsi_vhci/disk at g5000c5001a6b9c5e
1. c0t5000C5001A81E100d0 <ATA-ST31500341AS-CC4H-1.36TB>
/scsi_vhci/disk at g5000c5001a81e100
2. c0t5000C50019E0EB23d0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
/scsi_vhci/disk at g5000c50019e0eb23
3. c0t5000C50019F5B5BAd0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
/scsi_vhci/disk at g5000c50019f5b5ba
4. c0t5000C500268C0576d0 <ATA-ST31500341AS-CC1H-1.36TB>
/scsi_vhci/disk at g5000c500268c0576
5. c0t5000C500268C5414d0 <ATA-ST31500341AS-CC1H-1.36TB>
/scsi_vhci/disk at g5000c500268c5414
6. c0t5000C500268CFA6Bd0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189>
/scsi_vhci/disk at g5000c500268cfa6b
7. c0t5000C500268D0821d0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189>
/scsi_vhci/disk at g5000c500268d0821
Thanks in advance.
--
This message posted from opensolaris.org
Richard Elling
2010-Oct-15 00:17 UTC
[zfs-discuss] adding new disks and setting up a raidz2
On Oct 14, 2010, at 5:08 PM, Derek G Nokes wrote:> I am relatively new to OpenSolaris / ZFS (have been using it for maybe 6 months). I recently added 6 new drives to one of my servers and I would like to create a new RAIDZ2 pool called ''marketData''. > > I figured the command to do this would be something like: > > zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0s0 c0t5000C5001A81E100d0s0 c0t5000C500268C0576d0s0 c0t5000C500268C5414d0s0 c0t5000C500268CFA6Bd0s0 c0t5000C500268D0821d0s0 > > Unfortunately I get an error: > > [b]cannot open ''/dev/dsk/c0t5000C500268CFA6Bd0s0'': I/O error[/b]This can happen if slice0 is size 0. KISS would say to do: zpool create marketData raidz2 \ c0t5000C5001A6B9C5Ed0 \ c0t5000C5001A81E100d0 \ c0t5000C500268C0576d0 \ c0t5000C500268C5414d0 \ c0t5000C500268CFA6Bd0 c0t5000C500268D0821d0 This method will create slice0 (s0) as the full disk, on your behalf. -- richard> > Can anyone give me some clues as to what is wrong? > > I have included the zpool status and format output from my system > > > [b]ZPOOL STATUS[/b] > root at dnokes.homeip.net:~# zpool status > pool: rpool > state: ONLINE > status: The pool is formatted using an older on-disk format. The pool can > still be used, but some features are unavailable. > action: Upgrade the pool using ''zpool upgrade''. Once this is done, the > pool will no longer be accessible on older software versions. > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > c0t5000C50019F5B5BAd0s0 ONLINE 0 0 0 > c0t5000C50019E0EB23d0s0 ONLINE 0 0 0 > > errors: No known data errors > > [b]FORMAT[/b] > root at dnokes.homeip.net:~# format > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c0t5000C5001A6B9C5Ed0 <ATA-ST31500341AS-CC4H-1.36TB> > /scsi_vhci/disk at g5000c5001a6b9c5e > 1. c0t5000C5001A81E100d0 <ATA-ST31500341AS-CC4H-1.36TB> > /scsi_vhci/disk at g5000c5001a81e100 > 2. c0t5000C50019E0EB23d0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126> > /scsi_vhci/disk at g5000c50019e0eb23 > 3. c0t5000C50019F5B5BAd0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126> > /scsi_vhci/disk at g5000c50019f5b5ba > 4. c0t5000C500268C0576d0 <ATA-ST31500341AS-CC1H-1.36TB> > /scsi_vhci/disk at g5000c500268c0576 > 5. c0t5000C500268C5414d0 <ATA-ST31500341AS-CC1H-1.36TB> > /scsi_vhci/disk at g5000c500268c5414 > 6. c0t5000C500268CFA6Bd0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189> > /scsi_vhci/disk at g5000c500268cfa6b > 7. c0t5000C500268D0821d0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189> > /scsi_vhci/disk at g5000c500268d0821 > > Thanks in advance. > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Derek,> I am relatively new to OpenSolaris / ZFS (have been using it for maybe 6 months). I recently added 6 new drives to one of my servers and I would like to create a new RAIDZ2 pool called ''marketData''. > > I figured the command to do this would be something like: > > zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0s0 c0t5000C5001A81E100d0s0 c0t5000C500268C0576d0s0 c0t5000C500268C5414d0s0 c0t5000C500268CFA6Bd0s0 c0t5000C500268D0821d0s0I would assume that one or more of these VDEVs are not formatted, or have valid disk labels, a requirement when specifying the ''s0'' portion of the Solaris device name. If 100% of all blocks on each of these disks are to be included within the marketData storage pool, then ZFS is very capable of formatting and/or labeling the underlying devices as follows: zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0 c0t5000C5001A81E100d0 c0t5000C500268C0576d0 c0t5000C500268C5414d0 c0t5000C500268CFA6Bd0 c0t5000C500268D0821d0 - Jim> > Unfortunately I get an error: > > [b]cannot open ''/dev/dsk/c0t5000C500268CFA6Bd0s0'': I/O error[/b] > > Can anyone give me some clues as to what is wrong? > > I have included the zpool status and format output from my system > > > [b]ZPOOL STATUS[/b] > root at dnokes.homeip.net:~# zpool status > pool: rpool > state: ONLINE > status: The pool is formatted using an older on-disk format. The pool can > still be used, but some features are unavailable. > action: Upgrade the pool using ''zpool upgrade''. Once this is done, the > pool will no longer be accessible on older software versions. > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > c0t5000C50019F5B5BAd0s0 ONLINE 0 0 0 > c0t5000C50019E0EB23d0s0 ONLINE 0 0 0 > > errors: No known data errors > > [b]FORMAT[/b] > root at dnokes.homeip.net:~# format > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c0t5000C5001A6B9C5Ed0 <ATA-ST31500341AS-CC4H-1.36TB> > /scsi_vhci/disk at g5000c5001a6b9c5e > 1. c0t5000C5001A81E100d0 <ATA-ST31500341AS-CC4H-1.36TB> > /scsi_vhci/disk at g5000c5001a81e100 > 2. c0t5000C50019E0EB23d0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126> > /scsi_vhci/disk at g5000c50019e0eb23 > 3. c0t5000C50019F5B5BAd0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126> > /scsi_vhci/disk at g5000c50019f5b5ba > 4. c0t5000C500268C0576d0 <ATA-ST31500341AS-CC1H-1.36TB> > /scsi_vhci/disk at g5000c500268c0576 > 5. c0t5000C500268C5414d0 <ATA-ST31500341AS-CC1H-1.36TB> > /scsi_vhci/disk at g5000c500268c5414 > 6. c0t5000C500268CFA6Bd0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189> > /scsi_vhci/disk at g5000c500268cfa6b > 7. c0t5000C500268D0821d0 <DEFAULT cyl 60798 alt 2 hd 255 sec 189> > /scsi_vhci/disk at g5000c500268d0821 > > Thanks in advance. > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Derek G Nokes
2010-Oct-15 03:21 UTC
[zfs-discuss] adding new disks and setting up a raidz2
Thank you both. I did try without specifying the ''s0'' portion before posting and got the following error: root at dnokes.homeip.net:~# zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0 c0t5000C5001A81E100d0 c0t5000C500268C0576d0 c0t5000C500268C5414d0 c0t5000C500268CFA6Bd0 c0t5000C500268D0821d0 cannot label ''c0t5000C500268CFA6Bd0'': try using fdisk(1M) and then provide a specific slice Any idea what this means? Thanks again. -- This message posted from opensolaris.org
Edward Ned Harvey
2010-Oct-15 04:08 UTC
[zfs-discuss] adding new disks and setting up a raidz2
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of Derek G Nokes > > root at dnokes.homeip.net:~# zpool create marketData raidz2 > c0t5000C5001A6B9C5Ed0 c0t5000C5001A81E100d0 c0t5000C500268C0576d0 > c0t5000C500268C5414d0 c0t5000C500268CFA6Bd0 c0t5000C500268D0821d0 > cannot label ''c0t5000C500268CFA6Bd0'': try using fdisk(1M) and then > provide a specific slice > > Any idea what this means?I think it means there is something pre-existing on that drive. Maybe ZFS related, maybe not. You should probably double-check everything, to make sure there''s no valuable data on that device... And then ... Either zero the drive the long way via dd ... or use your raid controller to "initialize" the device, which will virtually zero it the short way ... In some cases you have no choice, and you need to do it the long way. time dd if=/dev/zero of=/dev/rdsk/c0t5000C500268CFA6Bd0 bs=1024k
Cindy Swearingen
2010-Oct-15 17:57 UTC
[zfs-discuss] adding new disks and setting up a raidz2
Derek, The c0t5000C500268CFA6Bd0 disk has some kind of label problem. You might compare the label of this disk to the other disks. I agree with Richard that using whole disks (use the d0 device) is best. You could also relabel it manually by using the format-->fdisk--> delete the current partition, create a new partition using the EFI option, and save the configuration. Thanks, Cindy On 10/14/10 21:21, Derek G Nokes wrote:> Thank you both. I did try without specifying the ''s0'' portion before posting and got the following error: > > root at dnokes.homeip.net:~# zpool create marketData raidz2 c0t5000C5001A6B9C5Ed0 c0t5000C5001A81E100d0 c0t5000C500268C0576d0 c0t5000C500268C5414d0 c0t5000C500268CFA6Bd0 c0t5000C500268D0821d0 > cannot label ''c0t5000C500268CFA6Bd0'': try using fdisk(1M) and then provide a specific slice > > Any idea what this means? > > Thanks again.
Derek G Nokes
2010-Oct-17 04:48 UTC
[zfs-discuss] adding new disks and setting up a raidz2
I tried using format to format the drive and got the following: Ready to format. Formatting cannot be interrupted and takes 5724 minutes (estimated). Continue? y Beginning format. The current time is Sat Oct 16 23:58:17 2010 Formatting... Format failed Retry of formatting operation without any of the standard mode selects and ignoring disk''s Grown Defects list. The disk may be able to be reformatted this way if an earlier formatting operation was interrupted by a power failure or SCSI bus reset. The Grown Defects list will be recreated by format verification and surface analysis. Retry format without mode selects and Grown Defects list? y Formatting... Illegal request during format ASC: 0x24 ASCQ: 0x0 Illegal request during format ASC: 0x24 ASCQ: 0x0 failed Is there any way for me to determine whether the disk is defective from OpenSolaris? I tried rotating the disk to a different bay and the problem moved to the new bay (c0t5000C500268D0821d0p0). When I try using format fdisk I get an error as well (fdisk: Error in ioctl DKIOCSMBOOT on /dev/rdsk/c0t5000C500268D0821d0p0) I also noticed that the format command take much much longer with this particular disk compared to the other 7. -- This message posted from opensolaris.org
Richard Elling
2010-Oct-18 03:35 UTC
[zfs-discuss] adding new disks and setting up a raidz2
On Oct 16, 2010, at 9:48 PM, Derek G Nokes wrote:> I tried using format to format the drive and got the following: > > Ready to format. Formatting cannot be interrupted > and takes 5724 minutes (estimated). Continue? y > Beginning format. The current time is Sat Oct 16 23:58:17 2010 > > Formatting...Uhm... silly question, but why are you formatting a disk? For the past 20+ years they come pre-formatted. You should not need to reformat a modern drive.> Format failed > > Retry of formatting operation without any of the standard > mode selects and ignoring disk''s Grown Defects list. The > disk may be able to be reformatted this way if an earlier > formatting operation was interrupted by a power failure or > SCSI bus reset. The Grown Defects list will be recreated > by format verification and surface analysis. > > Retry format without mode selects and Grown Defects list? y > Formatting... > Illegal request during format > ASC: 0x24 ASCQ: 0x0This is an indication that the features don''t match. Perhaps a firmware bug?> Illegal request during format > ASC: 0x24 ASCQ: 0x0 > failed > > Is there any way for me to determine whether the disk is defective from OpenSolaris? I tried rotating the disk to a different bay and the problem moved to the new bay (c0t5000C500268D0821d0p0). When I try using format fdisk I get an error as well (fdisk: Error in ioctl DKIOCSMBOOT on /dev/rdsk/c0t5000C500268D0821d0p0) > > I also noticed that the format command take much much longer with this particular disk compared to the other 7.Do yourself a favor and get rid of it. -- richard -- OpenStorage Summit, October 25-27, Palo Alto, CA http://nexenta-summit2010.eventbrite.com USENIX LISA ''10 Conference, November 7-12, San Jose, CA ZFS and performance consulting http://www.RichardElling.com