Sponsored Content
Operating Systems Solaris Hardware RAID not recognize the new disk [Sun T6320] Post 302599084 by little2712 on Thursday 16th of February 2012 06:58:13 AM
Old 02-16-2012
yes i also face this type of problems once a time,,where LBA,s are not the same due to which we have order other disk with same LBA..plz check that part number should be same...
 

9 More Discussions You Might Find Interesting

1. Solaris

Hardware RAID

I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies

2. Solaris

Sun T5120 hardware RAID question

Hi everyone I've just purchased a Sun T5120 server with 2 internal disks. I've configured hardware RAID (mirror) and as a result the device tree in Solaris only contains 1 hard drive. My question is, how would I know when one of the drives become faulty? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

3. Solaris

Add new disk to Sun StorEdge 3310 RAID

HI guys. Bit of a noob so bear with me. I have 2 new disks I want to add to my StorEdge 3310 but am getting lost in the steps. We have another 3310 (JBOD) that I was able to plug the disks into and they instantly showed up. Did a few minor commands after (drvconfig, devfsadm etc..) and I was... (4 Replies)
Discussion started by: jamie_collins
4 Replies

4. Hardware

Sun Blade T6320 memory configuration

Can you mix DIMMs in a T6320 (sparc) blade? I have read/heard that the DIMMs in a memory bay must be identical but can you have different size DIMMs installed in the blade? For instance, can you have 1 4GB DIMM in bay 0, 2 2GB DIMMs in bay 1, 4 1 GB DIMMs in bay 2 and 2 2GB DIMMs in bay 3 for a... (0 Replies)
Discussion started by: bluescreen
0 Replies

5. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

6. Hardware

Hardware RAID on Sun T2000 Server

Hi All I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command. Following is the hardware RAID output. root@oracledatabaseserver / $ raidctl RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies

7. Solaris

Solaris recognize HW Raid ??

Hardware: HP P2000 HP DL380 G7 with Solaris Software: Solaris 10 05/08 I had made a Hardware raid on P2000 and install solaris on G7, The raid card controller is working fine. How can I make the raid works on OS?? "raidclt" is getting nothing :wall::wall: Thanks (11 Replies)
Discussion started by: stanley1024
11 Replies

8. Hardware

Sun T3-1 hardware RAID

Hi all I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS. The documentation doesn't make it clear if: 1. The... (6 Replies)
Discussion started by: soliberus
6 Replies

9. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies
SG_UNMAP(8)							     SG3_UTILS							       SG_UNMAP(8)

NAME
sg_unmap - send SCSI UNMAP command (known as 'trim' in ATA specs) SYNOPSIS
sg_unmap [--anchor] [--grpnum=GN] [--help] [--in=FILE] [--lba=LBA,LBA...] [--num=NUM,NUM...] [--timeout=TO] [--verbose] [--version] DEVICE DESCRIPTION
Send a SCSI UNMAP command to DEVICE to unmap one or more logical blocks. This command was introduced in SBC-3 revision 18 under the broad heading of "logical block provisioning". Logical blocks may also be unmapped by the SCSI WRITE SAME command; see the sg_write_same utility. The unmap capability is closely related to the ATA DATA SET MANAGEMENT command with the "Trim" bit set. Logical blocks to be unmapped can be specified in one of two ways to this utility. One way is by supplying the start LBAs to the '--lba=' option and the corresponding number(s) to unmap to the '--num=' option. The other way is by putting start LBA and number to unmap pairs in a file whose name is given to the '--in=' option. All values are assumed to be decimal unless prefixed by "0x" (or "0X") or have a trailing "h" (or "H") in which case they are interpreted as hexadecimal. When the '--lba=' option is given then the '--num=' option must also be given. If one has a comma separated list as its argument then the other must have the same number of elements in its list. The arguments can use a single space as a separator but need to be in quotes or escaped to not be misinterpreted by the shell. With the '--in=FILE' option an even number of values must be found and are interpreted as pairs: the first value in each pair is a starting LBA and the second value is the number to unmap from that LBA. Everything from and including a "#" on a line is ignored as are blank lines. Values may be comma, space and tab separated or appear on separate lines. OPTIONS
Arguments to long options are mandatory for short options as well. -a, --anchor sets the 'Anchor' bit in the command (introduced in sbc3r22). -g, --grpnum=GN sets the 'Group number' field to GN. Defaults to a value of zero. GN should be a value between 0 and 31. -h, --help output the usage message then exit. -I, --in=FILE where FILE is a file name containing pairs of values. The first member of each pair is a starting LBA and the second member of the pair is the number of logical blocks to unmap from and including that starting LBA. Values are interpreted as decimal unless indi- cated otherwise. This option cannot be present with the '--lba=' option. -l, --lba=LBA,LBA... where LBA,LBA... is a string of comma (or space) separated values that are interpreted as starting logical block addresses. Each number is interpreted as decimal unless prefixed by '0x' or '0X' (or it has a trailing 'h' or 'H'). An argument that contains any space separators needs to be quoted (or otherwise escaped). When this option is given then the '--num=' option must also be given and they must contain the same number of elements in their arguments. -n, --num=NUM,NUM... where NUM,NUM... is a string of comma (or space) separated values that are interpreted as a number of logical blocks to unmap. Each number is interpreted as decimal unless prefixed by '0x' or '0X' (or it has a trailing 'h' or 'H'). Note that 0 blocks is accept- able. An argument that contains any space separators needs to be quoted (or otherwise escaped). When this option is given then the '--lba=' option must also be given and they must contain the same number of elements in their arguments. -t, --timeout=TO where TO is a timeout value (in seconds) for the UNMAP command. The default value is 60 seconds. -v, --verbose increase the level of verbosity, (i.e. debug output). -V, --version print the version string and then exit. NOTES
Some limits: an LBA can be up to 64 bits, a NUM up to 32 bits (imposed by structure of UNMAP SCSI command parameter data). The NUM is fur- ther constrained by the MAXIMUM UNMAP LBA COUNT field in the BLOCK LIMITS VPD page (0xb0). The maximum number of LBA,NUM pairs is limited to 128 by this utility and may be further constrained by the MAXIMUM UNMAP BLOCK DESCRIPTOR COUNT field in the BLOCK LIMITS VPD page. Since it is unclear how long the UNMAP command will take to execute a '--timeout=" option has been provided. The default timeout period is 60 seconds. If all the logical blocks on a logical unit (e.g. a disk drive) are to be unmapped then the FORMAT UNIT SCSI command (see the sg_format utility) may be considered as an alternative. Support for logical block provisioning is indicated by the LBPME bit in the response to the SCSI READ CAPACITY (16) command (see the sg_readcap utility). In SBC-3 revision 25 the LBPU and ANC_SUP bits where added to the Logical Block Provisioning VPD page. When LBPU is set it indicates that the device supports the UNMAP command. When the ANC_SUP bit is set it indicates the device supports anchored LBAs. EXAMPLES
In the examples directory of the sg3_utils package there is a sg_unmap_example.txt file that shows the format that the '--in=' option accepts. EXIT STATUS
The exit status of sg_unmap is 0 when it is successful. Otherwise see the sg3_utils(8) man page. AUTHORS
Written by Douglas Gilbert. REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2009-2011 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_format,sg_get_lba_status,sg_readcap,sg_vpd,sg_write_same(sg3_utils) sg3_utils-1.35 November 2012 SG_UNMAP(8)
All times are GMT -4. The time now is 09:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy