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_SYNC(8)							     SG3_UTILS								SG_SYNC(8)

NAME
sg_sync - send SCSI SYNCHRONIZE CACHE command SYNOPSIS
sg_sync [--16] [--count=COUNT] [--group=GN] [--help] [--immed] [--lba=LBA] [--sync-nv] [--timeout=SECS] [--verbose] [--version] DEVICE DESCRIPTION
Send SYNCHRONIZE CACHE(10) or SYNCHRONIZE CACHE(16) command to DEVICE. These commands are defined for SCSI block devices (see SBC-3). If successful these commands make sure that any blocks whose latest versions are held in cache are written to (also termed as "synchronized with") the medium. If the LBA and COUNT arguments are both zero (their defaults) then all blocks in the cache are synchronized. If LBA is greater than zero while COUNT is zero then blocks in the cache whose addresses are from and including LBA to the highest lba on the device are synchronized. If both LBA and COUNT are non zero then blocks in the cache whose addresses lie in the range LBA to LBA+COUNT-1 inclusive are synchronized with the medium. OPTIONS
Arguments to long options are mandatory for short options as well. -S, --16 performs a SYNCHRONIZE CACHE(16) command. Default is to perform a SYNCHRONIZE CACHE(10) command. -c, --count=COUNT where COUNT is the number of blocks to synchronize from and including LBA. Default value is 0. When 0 then all blocks in the cache from and including LBA argument to the highest block address are synchronized. -g, --group=GN where GN is the group number which can be between 0 and 31 inclusive. The default value is 0 . Group numbers are used to segregate data collected within the device. This is a new feature in SBC-2 and can probably be ignored for the time being. -h, --help output the usage message then exit. -i, --immed sets the IMMED bit in the SYNCHRONIZE CACHE command. This instructs the device, if the format of the command is acceptable, to return a GOOD status immediately rather than wait for the blocks in the cache to be synchronized with (i.e. written to) the medium. -l, --lba=LBA where LBA is the lowest logical block address in the cache to synchronize to the medium. Default value is 0 . -s, --sync-nv synchronize the (volatile) cache with the non-volatile cache. Without this option (or if there is no non-volatile cache in the device) the synchronization is with the medium. The SYNC_NV bit was made obsolete in SBC-3 revision 35d. -t, --timeout=SECS where SECS is the number of seconds the OS allows the SYNCHRONIZE CACHE(16) to complete before it tries to cancel the command. Can- celling commands (typically with the task management function "abort task") is best avoided. Note this option is only active together with the --16 option. The default timeout is 60 seconds for both SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16). Note that timeout issues can be avoided with the --immed option. -v, --verbose increase the level of verbosity, (i.e. debug output). -V, --version print the version string and then exit. NOTES
With the SYNCHRONIZE CACHE(16) command LBA can be up to 64 bits in size and COUNT up to 32 bits in size. With the SYNCHRONIZ CACHE(10) com- mand LBA can be up to 32 bits in size and COUNT up to 16 bits in size. Various numeric arguments (e.g. LBA) may include multiplicative suffixes or be given in hexadecimal. See the "NUMERIC ARGUMENTS" section in the sg3_utils(8) man page. EXIT STATUS
The exit status of sg_sync 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) 2004-2013 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_start(sg3_utils) sg3_utils-1.37 July 2013 SG_SYNC(8)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy